Go-e Firmware 56.8 and API-v2 / Mqtt

[mmilin29]

After upgrading the charger to 56.8, mqtt communications has been stopped
Checked on 2 chargers
Is there any changes in this area ?

I had to downgrade to 56.1 to have mqtt datas back

[erxbout]

There should not be such a change but I can reproduce the issue
I will have a look!

[erxbout]

Ok seems like I only could reproduce it once.. Weird..
Could you try again and provide the serial number if it does not work (since you downgraded there should be a button where it says "Switch to 56.8" that should be faster than installing the version again)

[mmilin29]

Upgraded to 56.8 and again no mqtt datas Charger is 246728

[erxbout]

With the new firmware the mqtt shows this error "error_type=TCP_TRANSPORT connect_return_code=ACCEPTED"
With the old it just works..

Do you have some logs on the broker side regarding the issue?
Is there a connection attempt or not even an attempt registered at the broker?

[mmilin29]

I understood the problem
we configured a mqtt user who has rights only on "go-eCharger." topics but since the latest firmware 56.8 he also tries to write in "homeassistant." topics
He is denied access to these topics and he stops there
However in the go-e app the "mqtt home assistant" flag is not activated
For me there is an issue on this point

[erxbout]

Thank you for this information!

Now I can reproduce everything needed and a fix should be available in the next firmware release

[thannerfabian]

Hi, is the issue fixed in 56.9 beta?

[erxbout]

It should be..

Important bit, is that the homeassistant topics are sent after successful connection if enabled in config

If there is still a problem let me know

[thannerfabian]

Do you know, if the version is stable? And can I switch back to non beta version, after I installed a beta version?

[erxbout]

Its still in testing but should be fine

You can always go back to the version you had installed before

[thannerfabian]

Thanks! I will check it and give some feedback.

[erxbout]

@thannerfabian any feedback?

[SoftwareBaumeister]

Its still in testing but should be fine

You can always go back to the version you had installed before

Ist it? I have a new go-e Gemini flex. Yesterday I tried to run Mqtt first time and got the same error. But I got the error also on 56.1 and 56.9. Maybe I make some mistakes on my side?!? Mqtt is 'active' in the app, but it is 'not connected'.

Writing with HttpApiv2 is working. I use a mosquito-broker and node-red.

Any idea?

[thannerfabian]

@erxbout sorry for the late reply. Yes I tested it and I had the same result as @SoftwareBaumeister, it sadly didn´t work. I validated the MQTT-Connection string again and the settings were correct.

[SoftwareBaumeister]

@erxbout

Here is the log of the mosquitto-broker:

1728332354: New connection from 192.168.178.41:49842 on port 1883. 1728332354: New client connected from 192.168.178.41:49842 as go-echarger_261397 (p2, c1, k120, u'gebhardt'). 1728332354: No will message specified. 1728332354: Sending CONNACK to go-echarger_261397 (0, 0) 1728332354: Received SUBSCRIBE from go-echarger_261397 1728332354: Invalid subscription string from 192.168.178.41, disconnecting. 1728332354: Client go-echarger_261397 disconnected due to malformed packet.

192.168.178.41 is the ip of ot the go-e. Any idea?

[erxbout]

Can you edit your mosquitto config that it also logs the loglevel debug?
add a line that says:

log_type debug

When I do that I see a subscribe like this:

If your config does not allow that subscribe then our connection will be terminated by the server and we can do nothing about that..

[SoftwareBaumeister]

Can you edit your mosquitto config that it also logs the loglevel debug? add a line that says:

log_type debug

When I do that I see a subscribe like this:

If your config does not allow that subscribe then our connection will be terminated by the server and we can do nothing about that..

I found my problem. I do the wrong config at the app. At mqtt-setting on field "prefix" the last sign was not the SLASH, e.g. "go-eCharger/12345/" is ok; "go-eCharger/12345" is not working.

Now it is working. For other newbies, at "URL" you need the following syntax: "mqtt://username:password@ip:port".

[SoftwareBaumeister]

@erxbout sorry for the late reply. Yes I tested it and I had the same result as @SoftwareBaumeister, it sadly didn´t work. I validated the MQTT-Connection string again and the settings were correct.

Maybe the same problem/solution, too? Best wishes...

[thannerfabian]

@SoftwareBaumeister should there relly be a whitespace before and after the password in the connection string?

[erxbout]

The whitespaces are copy paste errors i suppose
When saving this the app will display an error and the setting will not change

So to sum it up we have two separated issues here:

• Disconnect from mqtt due to a broker that does not allow to send certain topics (homeassistant.. should be fixed in betas)
• Disconnect from mqtt due to malformed SUBSCRIBE message containing the + wildcard (bug created, no firmware with fix available so far)
  -- Temp solution: make sure there is a trailing / in prefix topic
  -- Full solution would be something like automatically add a trailing / if not set by user...

[SoftwareBaumeister]

@SoftwareBaumeister should there relly be a whitespace before and after the password in the connection string?

No! My mistake. I updated my post