I use MQTT to expose OVMS values to HA thus HK, and so Siri gives me the car charge level now, and soon climate control, once I figure out how to unplug the TCU (can see it but can't get the plug out
-
happyfunball
- Posts: 10
- Joined: Thu Nov 02, 2017 8:30 pm
- Delivery Date: 15 Jan 2016
- Leaf Number: 001393
Re: Open Vehicle Monitoring System
I use HomeAssistant to drive HomeKit, and so anything on HomeAssitant can be made visible to Homekit.
I use MQTT to expose OVMS values to HA thus HK, and so Siri gives me the car charge level now, and soon climate control, once I figure out how to unplug the TCU (can see it but can't get the plug out
I use MQTT to expose OVMS values to HA thus HK, and so Siri gives me the car charge level now, and soon climate control, once I figure out how to unplug the TCU (can see it but can't get the plug out
-
happyfunball
- Posts: 10
- Joined: Thu Nov 02, 2017 8:30 pm
- Delivery Date: 15 Jan 2016
- Leaf Number: 001393
Re: Open Vehicle Monitoring System
On a related note, is there any way to get battery SOH from OVMS? Or send ODB2 codes and read the results?
-
caederus
- Posts: 12
- Joined: Sun Mar 20, 2016 9:34 am
- Delivery Date: 01 Mar 2016
Re: Open Vehicle Monitoring System
happyfunball wrote:On a related note, is there any way to get battery SOH from OVMS? Or send ODB2 codes and read the results?
SOH percentage is reported in metric v.b.soh (MQTT topic v/b/soh).
We currently get the total estimated capacity (in Ah) from bytes 33--35 of the active query 0x79b/0x7bb, then divide by the new capacity, which you must manually set with config parameter xnl.newCarAh (this defaults to 66Ah, suitable for a 24kWh battery). I would prefer to report the value directly from the 2nd MSB of 0x5b3, so there would be no need to calibrate anything. Some people seem to like the current way though, so maybe we need a choice, like we do for SOC.