Open chrisrock1984 opened 6 months ago
I don't see this issue at all. Do you have any logs to share?
I don't see this issue at all. Do you have any logs to share?
I concur. I'm on the latest HAOS and I've never experienced a crash with this integration.
Here I have posted a log ->
https://github.com/daernsinstantfortress/cupra_we_connect/issues/45#issuecomment-2094664344
I hope that helps
Thank you!!
It looks like it's got jammed into some sort of auth loop. Have you tried removing and re-adding it and double-checking your credentials? (although I presume that they are working ok the rest of the time).
Are you seeing this periodically in the logs?
2024-05-29 17:10:41.045 INFO (SyncWorker_14) [weconnect_cupra] Token expired
2024-05-29 17:10:41.045 INFO (SyncWorker_14) [weconnect_cupra] Refreshing tokens
Are the logs quiet when things are behaving?
enabled the addon again to check the logs in working state so far I got this several times -> Timeout updating weconnect_cupra
and this, but I do not know if it belongs to the addon -> Logger: urllib3.connectionpool Source: /usr/local/lib/python3.12/site-packages/urllib3/connectionpool.py:824 First occurred: 11:06:37 (2 occurrences) Last logged: 11:09:40
Retrying (Retry(total=5, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))': /v1/users/63e7096e-73f8-4aaa-b860-2db8682de018/garage/vehicles
UPDATE 12:40 Logger: custom_components.cupra_we_connect Source: custom_components/cupra_we_connect/init.py:57 integration: Cupra WeConnect (documentation, issues) First occurred: 11:18:31 (10 occurrences) Last logged: 11:49:33
Timeout updating weconnect_cupra
Another Update I have set up a new home assistant in Proxmox, totally virgin and installed this addon - same problems.
As it seems to be the only one to have this issue, I will close this Thanks for the input!
I'm really struggling to reproduce this, I'm afraid. The only thing I can suggest is if you are willing to share credentials with me so I can debug directly with your car and see if I can find if there's a difference here.
Happy to leave open until we properly resolve.
thank you for the offer, but I am afraid that sharing such infos is not a good idea.. my solution now is, that I run a second proxmox home assistant installation just for this addon and connect it to my active home assistant via remote. in addition I reboot the whole cupra vm every hour ;-)
I needed to stop using this awesome addon because 2 to 3 times a day, mostly in the morning and in the evening, this addon causes an HA Core crash. I manually need to restart the core in the console. I use the latest and greatest (non beta) version of Home Assistant
The questions are: Does somebody else have this issues? Is there active development going on?`
Thank you very much for any input!!