Go-e Integration stopped providing entities although provided via MQTT about homeassistant-goecharger-mqtt HOT 27 OPEN

Hello guys,
I newly installed integration today. Experienced same problems reported by all other. Inspired by discussions in this thread I "played around a bit" with prefix when configuring integration. As soon as I used "go-eCharger" without a leading slash (default is: "/go-eCharger") all sensors, buttons etc are working :-). Not sure if reconfiguring is possible. I removed device and configured it new. Now everything is working perfect.

from homeassistant-goecharger-mqtt.

Hi,
having the same issue. Would be great to have those entities for using in automations.
Looking forward to solution comments
Thanks
Dietmar

from homeassistant-goecharger-mqtt.

Did you update Home Assistant recently? Please make sure you are using the latest release of this custom component.

from homeassistant-goecharger-mqtt.

from homeassistant-goecharger-mqtt.

I'm talking about the version of this custom component. Do you use HACS to install third party integrations?

from homeassistant-goecharger-mqtt.

Hi, having the same issues.
Installed the integration via HACS
Version: 0.21.1
Home Assistant Version: 2023.12.1 (core) & 20231208.2 (front-end)

Any advice?

from homeassistant-goecharger-mqtt.

I can join the club. All entities in the integration are gone.
MQTT shows data is running fine.
Happened from one day to the other, and i have no clue what is causing this.

from homeassistant-goecharger-mqtt.

Has anyone resolved the issue?

from homeassistant-goecharger-mqtt.

In most cases the go-e charger dropped the leading slash of the topic prefix so the integration doesn't pick up the traffic anymore. Please make sure all topics or you go-e charger starts with a /.

from homeassistant-goecharger-mqtt.

Please make sure all topics or you go-e charger starts with a /.

How would one add the "/" prefix if the setting is not available in the mobile app ?

Firmware v: 042.0
Hardware v: 2
App v: 3.2.11

from homeassistant-goecharger-mqtt.

Go to the Internet view -> Extended settings -> scroll to the bottom (MQTT section). There is a setting called Prefix. What's the prefix of your device at the moment?

from homeassistant-goecharger-mqtt.

What's the prefix of your device at the moment?

As i have the same Problem I respond here
mine is:
/go-eCharger/xxxxxx/

and xxxxxx are the IDs we got from out chargers

from homeassistant-goecharger-mqtt.

Go to the Internet view -> Extended settings -> scroll to the bottom (MQTT section). There is a setting called Prefix. What's the prefix of your device at the moment?

I don't have it.
I have the MQTT section but there is no Prefix setting/input field. With mosquitto_sub I can see that the topic published is "go-eCharger/xxxxxx/status"

from homeassistant-goecharger-mqtt.

In my App-Version it looks like this.
And I tried it with and without leading slash.

Funny thing is that everything worked on my old pi. But I moved to a new one and there I can add the devices via its 6-digit s rial and I can see in the mqtt server logs that the device is correctly registered but all entities are created as "unavailable".
What could cause this?

from homeassistant-goecharger-mqtt.

Is this still an issue? I would like to resolve the issue + get a better understanding what's going on in detail. I must admit it's hard to understand what's the issue in detail and are we all talking about the same thing. :-)

from homeassistant-goecharger-mqtt.

from homeassistant-goecharger-mqtt.

This is what my go-eCharger produces when viewed from MQTT Explorer:

I observe that this is different than the other entries as there appears to be an empty white-space parent topic. Unfortunately, I wasn't able to change the MQTT topic in the past.

from homeassistant-goecharger-mqtt.

Same problem here, it died 2 months ago.
Apparently, one of the 3 I have randomly started working again on the 1st of February?
Although this could be just a bug since I can't find any data in the history even though I'm pretty sure the integration worked when I first set it up a few months ago.
I just tried re-adding one but it still reports as Unavailable.

from homeassistant-goecharger-mqtt.

from homeassistant-goecharger-mqtt.

I think its all about having prefix indentical in go-e app and in ha integration. At least in my app I am able to configure MQTT Prefix (which I did not prior to integrate with ha). My prefix in go-e app is: "go-eCharger/xxxxxx/". All I did is to align ha config to this prefix....

from homeassistant-goecharger-mqtt.

@gerhardvilsecker Again, thanks for Your hint, but it doesn't work if the MQTT topic is not "go-eCharger/123456/", but something simpler say "myCharger".

The configuration-dialog expects the serial number, and apparently this integration uses it to construct the MQTT topic by appending it to the prefix.

from homeassistant-goecharger-mqtt.