I’m using OVMS along with my Kia Soul EV. Was using Server 2 (HTTP API) and transitioned to Server v3 (MQTT).
Have all of the data working properly, but one of the frontend elements is not working as expected. I wanted to show the battery icon based on the state of the sensors, but no icon is represented when using the below code.
Hey - what is OVMS and what are you using MQTT for with your car? I like the idea of having my car data available on my MQTT server - but I don’t think I’ve seen any integration that offers that. So, I’m sorry I can’t help you with your problem - but I’m very curious about what you’re doing.
The reason I ended up here was because I was searching for the reason my Tucson Plug-In Hybrid seemed to not be refreshing the battery state of charge. The battery sensor currently is displaying 76% when I know it’s just finished charging and is actually 100%.
I ended up looking through all of the “state” data to try and find where it was picking up the 76% from - and I found it! And I also found the 100% I was looking for.
I see in the json:
/vehicle_data/status/battery/batSoc: 76
/vehicle_data/status/evStatus/batteryStatus: 100. So, my best guess at this point is that the 76% I’m seeing might actually be referring to the 12V battery? And the EV Battery charge level is the 100.
This has had me scratching my head for 2 weeks - and I thought it just wasn’t updating properly - but this would explain it - so I’m recording it here so that someone can confirm (or re-educate me) and so hopefully the next person isn’t stuck scratching their head for nearly as long as I did.
Here is the link for the OVMS project: https://www.openvehicles.com/. Please be warned that I do not recommend this unless you are a major tech savvy with electronics and programming (which I am not, hence why I forgo the whole project).
I am only looking at 2 sensors. 1 for whether the car is charging or not and the other is the soc level. 12v reports to another sensor.
I actually see that the initial sensors that I put in the post where not the correct ones (fixed :P).
Thanks for that link. The project looks really interesting - but seems like it requires custom hardware and is targeted at full EV owners. Mine is just a PHEV.
But if you’re only looking for 2 data points, have you tried getting them from the KIA_UVO integration?
I’ve been using it for a couple of weeks and it seems pretty reliable. It’s not going to provide everything that the OVMS project does, but it might have what you need. Here’s a photo of my (work-in-progress) dashboard for the car which highlights many of the sensors the integration creates:
I appreciate the reply and info, but my car does not support KIA_UVO (aka Kia Connect). Hence why I use OVMS.
OVMS is the “custom hardware”. It comes pre-assembled and with the needed firmware. It is “almost” plug & play.
@anthonws That makes perfect sense. So this OVMS project is a solution for people that can’t use the BlueLink or KIA_Connect service? It might be worth looking into once my free BlueLink subscription expires! That’s a year away - and by then you’ll be an expert on the system and be able to answer all my questions!