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

[AndihX]

In my opinion it is the rx tx to rs485 that is overheating. It could be bad quality, i am not sure. lør. 3. feb. 2024 kl. 15.15 skrev Sebastian Muszynski < ***@***.***>:

…

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. :-) — Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVU7D4CY5TH33H3R2LBD6P3YRZBAPAVCNFSM6AAAAAA7MBTKXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGMZTQOJSGU> . You are receiving this because you commented.Message ID: ***@***.***>

[dubtec]

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.

[SIMULATAN]

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.

[gerhardvilsecker]

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.

[dubtec]

I’ve tried that too now also, but didn’t work for me. The reason is a bit different probably. In the meantime (after the integration hasn’t been working for quite some time already) I’ve changed the name of the charger and the MQTT topic to something much shorter. Now, when I re-install and am being asked for Serial No., I can provide that, but it’s of no value, because I don’t use the standard naming convention. For this, but also other scenarios, I think, @syssi, that just asking for the MQTT topic as it’s written in the MQTT settings of go-e App is more straightforward then trying to recreate a logic, which may not even apply in some cases. Best regards

…

Am 28.02.2024 um 10:07 schrieb gerhardvilsecker ***@***.***>: 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. — Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ6OD3DQ6III2MUS7SB6TILYV3XVXAVCNFSM6AAAAAA7MBTKXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRYGUZTGMBUGM>. You are receiving this because you commented.

[gerhardvilsecker]

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

[dubtec]

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

[XionIndigo]

Hi everyone, I am also affected. I have also tried the leading / but it has no effect on me. Actually, no matter what names I tried (with or without special characters) nothing worked. Of course, the changes were made on both sides - Charger and Integration.

[dubtec]

I actually tried changing / adopting the Python scripts of this integration, such that it wouldn’t rely on the convention to append the serial to the topic. I managed to revive most entities with this. But since this was just a hack and would probably break the integration for all others there’s no point in trying to merge it back. I also don’t have time / the expertise to make a stable version out of that.
What I’m trying to say is that, it can be done, but it requires knowledge of how the configuration is being stored and used later on.
Again, I would recommend in the configuration dialog to just ask for the base MQTT topic as a string, exactly how it is displayed in the app. I don’t think the serial really matters otherwise.

[mmick08]

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

As the go-e chargers mqtt prefix is now fully configurable in the app maybe it makes sense to replace the prefix+serial configuration within the integration with the full prefix only.

in my opinion it should not be best practice to expose the serial within your mqtt topics. Instead you should be able to choose something like: go-eCharger/home/ or go-eCharger/carport/

At the moment with the current configuration of the integration you are forced to use serial.

especially in case you have multiple go-e chargers it makes it hard to find the correct entities.

[syssi]

Let's close this issue because it's all about a changed base_topic over time because of firmware updates or new setups.

[dubtec]

@syssi Not sure why you’re closing this as this will only be solved with #148, no?

[syssi]

This is the short term mitigation of the issue: #128

But I must admit #148 will resolve the thematic entirely.