Cannot authenticate against websocket

[Lear76]

Hi,

first of all: great work with the integration! I have been testing for a while and now I was eager to try the new Websocket function for quick responses. But for me, it does not work. I have followed the instruction to re-set the password in the Go-e app, but I still get this error in the log (sorry for the swedish):

Loggare: custom_components.goecharger_api2.pygoecharger_ha
Källa: custom_components/goecharger_api2/pygoecharger_ha/init.py:632
integration: go-e APIv2 Connect (dokumentation, ärenden)
Inträffade först: 14:38:36 (20 förekomster)
Senast loggade: 16:10:51

ws_connect(): Authentication failed: {'type': 'authError', 'message': 'Wrong password'}

Any ideas? I have tried with both complex and rather simple passwords.

[marq24]

so just allow me to repeat... you have adjusted your wallbox password via:

and then you restarted the go-e App (to ensure that the new pwd is used)...

Then you are specify the new PWD in the integration...

[Lear76]

Yes, exactly like that. And immediately after I update the new PWD in the HA integration and click Save i see this in the log:

[Lear76]

Just to be sure: I changed (and used) the "Charger password", not the Technician password

[Lear76]

Also worth noting: I just logged in to the web portal (portal.go-e.com) and there is said I needed to authenticate my charger again (after changing the password). I then put in the new password and it worked immediately.

I have the the Go-e Charger CORE

[marq24]

as I just was made aware today

the websocket connection has been available since hardware V3 - at least june 2021

So could be, that Go-e Charger CORE does not support local websocket at all - I might had been to optimistic with my announcement :-/ Something you might like to try, is what will happen, if you configure the WAN/Cloud-Version... if there websocket might be available (even if there is the de-tour) ?!

[marq24]

but... looks like that the Go-e Charger CORE is newer/modern then the Home & Gemini Series... So there might be "just" additional things, why the current websocket impl might not work...

That makes me even more curious, what would the WAN/Cloud Config of the Integration would return...

[Lear76]

Ok, I deleted the integration and created a new one with Cloud API. Put in the ID, the generated key and the integration works, but same error regarding the WebSocket:

Also the charger is quite new. I ordered it in October 2025. Here are some more info on the hardware:

[marq24]

Ok - thanks for testing the Cloud variant... if this variant have similar issues, then my initial assumption is unfortunately not correct...

On the other hand, when it's not working in the cloud, that then I would have the possibility to recreate & remote debug the issue. But of course this would mean, that you have quite some trust in a random guy you meet on the internet...

So if you would like to support the development you might like to contact me private by eMail in order to exchange some details. But it's totally fine for me, if you don't want this. I would probably not do it myself!

[marq24]

Ok - so the Hardware Version CORE is using an alternative approach to calculate the required hash - while "mine" is using pbkdf2, the new one requesting now bcrypt...

So the good thing already is, code can CHECK for the difference and can handle the current situation...

[marq24]

I have good reasons to believe, that this new version https://github.com/marq24/ha-goecharger-api2/releases/tag/2026.2.8 will solve this issue.

[Lear76]

You were absolutely correct. Works like a charm. Thank you!