Go-e Integration stopped providing entities although provided via MQTT

[Phipps78]

Good morning,

a couple of days ago my Go-e integration stopped populating data in some entities, although the missing data is still provided via MQTT. (Error message in entity "Entity no longer available").
I use some of the entities to feed my Energy dashboard (e.g. sensor.go_echarger_mySN_pgrid).
I tryed to understand the root-cause but can't make it work again, so I hope you guys can help me.

Here's what I tryed and learned:

• I checked my MQTT connection using MQTT Explorer: the data from the missing entities is still being provided from Go-eCharger to MQTT server and i can see how it updates fine
• I restored my daily backup from a day earlier of when I still received data > no change
• I re-installed the Go-e Integration > no change
• I restarted Homeassistant

Here is an overview of which entities are available and which aren't:

Any advice would be greatly appreciated!

Thanks
Philipp

[freedoc35]

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

[syssi]

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

[Phipps78]

Yes, I updated to 2023.11.3.

[syssi]

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

[stormmurdoc]

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?

[AndihX]

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.

[tuglerxda]

Has anyone resolved the issue?

[syssi]

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 /.

[toleabivol]

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

[syssi]

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?

[mr-gosh]

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

[toleabivol]

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"

[mr-gosh]

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?

[syssi]

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. :-)