jamessimpson
Novice Member
Dear all,
I have an MG ZS EV. I'm using the v3 server which connects to a cloud MQTT broker at HiveMQ Cloud. From there it's bridged to my Mosquitto broker (Home Assistant Hosted Addon). It's generally working very well. However there are a couple of wiggly weirdnesses going on...
I've got loads of manually (yaml) created Home Assistant MQTT sensors monitoring SoC, SoH, temperatures, battery metrics etc. These are all working normally. I've also got a few binary sensors which are working normally as expected (v.e.on and v.e.drivemode).
However
- the v.e.awake metric seems to report yes when the car is charging overnight, but still locked and powered off
- the v.e.locked metric doesn't seem to report the locked status of the car correctly. Sometimes it works, sometimes it doesn't (i.e. "yes" when unlocked and vice versa), even when all the other sensors work normally. Could this be a bug in the way that OVMS gets its data from the bus?
Any suggestions gratefully received!
I have an MG ZS EV. I'm using the v3 server which connects to a cloud MQTT broker at HiveMQ Cloud. From there it's bridged to my Mosquitto broker (Home Assistant Hosted Addon). It's generally working very well. However there are a couple of wiggly weirdnesses going on...
I've got loads of manually (yaml) created Home Assistant MQTT sensors monitoring SoC, SoH, temperatures, battery metrics etc. These are all working normally. I've also got a few binary sensors which are working normally as expected (v.e.on and v.e.drivemode).
However
- the v.e.awake metric seems to report yes when the car is charging overnight, but still locked and powered off
- the v.e.locked metric doesn't seem to report the locked status of the car correctly. Sometimes it works, sometimes it doesn't (i.e. "yes" when unlocked and vice versa), even when all the other sensors work normally. Could this be a bug in the way that OVMS gets its data from the bus?
Any suggestions gratefully received!
