search

goecharger / go-eCharger-API-v2

New API specification for V3 and V4 go-eCharger
90 stars 21 forks source link

Go-e Firmware 56.8 and API-v2 / Mqtt #231

Open mmilin29 opened 1 month ago

mmilin29 commented 1 month ago

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 commented 1 month ago

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

erxbout commented 1 month ago

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 commented 1 month ago

Upgraded to 56.8 and again no mqtt datas Charger is 246728

erxbout commented 1 month ago

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 commented 1 month ago

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 commented 1 month ago

Thank you for this information!

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