Closed ReneNulschDE closed 9 months ago
@StefanHesse: I just checked this with my car and the SoC gets updated. So it is not a generall problem. Let us try the simple things first:
If this does not work:
I have HA running within a Virtual machine on my Synology NAS. How can I quit HA and delete the token? If i shutdown HA the Virtual machine is off and i do not know how to delete a file on the virtual disk. Sorry for asking, but this is not my day 2 day business :-)
When you create the docker environment on your NAS, you normally define folders for your configuration data and this is stored on your normal NAS discs. You can use the NAS explorer to go to this folder and delete the data.
What was the tutorial that you used to set this up?
Otherwise you can go to the configure dialog of the MBAPI2020 component and select the second last checkbox "Delete authentication token file now. require a restart of Home Assistant after save." Then restart HA
I do not use docker any more for HA, because i had problems to add my SkyConnect USB stick. I had no idea how to add a USB device to the container. I therefore use a real virtual machine for this and if this machine is off, i have no idea how to get access to the file system. But anyway, the dialog to delete the token did the trick. Now my system is updating again and my problem is solved. I will now try to add an alarm function to get notified next time my token is not working any more. Thank you so much for your time to fix this :-)
Of course. I started debug logging now. How long should i let this run before sending you the data? I updated my HA to version 2023.11.3 on November, 23rd and the integration worked after that update until November 26th. I have an automation sending the SoC to an openWB wallbox, but this automation is not triggered becaused the mbapi2020 does not update the SoC. It is fixed at 80%. What else do you need?
Originally posted by @StefanHesse in https://github.com/ReneNulschDE/mbapi2020/issues/152#issuecomment-1829676924