Closed ChristophCaina closed 2 years ago
update: I've noticed, that also the openWB had suddenly the SoC of 45% and could not refresh the SoC value. I've changed the setting within the openWB to update the SoC "always" instead of "only when plugged in" and after a reboot, it seems to be solved for now.
Hi @a529987659852, I've found another Strange behave of the Integration when I restart HomeAssistant.
I am using the Skoda Connect Integration to get Information about my Car Into HomeAssistant. This Integration does also provide the SoC of the Car.
I'm Reading this Sensor with NodeRed and send it to the openWB over MQTT - which is just working fine.
Before my Car arrived, I did some Manual Tests - and sent an SoC value of '45' to the OpenWB.
Now, the current SoC will be used, but every time when I restart HomeAssistant, the SoC Sensor from the OpenWB Integration jumps to 45%.
I've checked the value of the node Red - whixh dies have the correct value - and also the OpenWB dies Show the correct SoC information, but the OpenWB Integration does Not - until I start the Car and the SoC will Change Düring driving.
SoC before reatartrestart of HA![Screenshot_20220615-215230~2](https://user-images.githubusercontent.com/26391061/173929966-7b8bbbe7-8fce-4774-aef0-25551ed4dea2.png)
SoC after restart![Screenshot_20220615-215349~2](https://user-images.githubusercontent.com/26391061/173930048-9898216a-4788-4a26-a9f6-376868533f7b.png)
SoC information from the openWB![Screenshot_20220615-215407~2](https://user-images.githubusercontent.com/26391061/173930115-c7ba26c3-4d98-42b3-ba80-84466996f021.png)