Hey, this works wonderfully but it would be nice if you could add ABRP integration that would sync the data from the car to ABRP.
I managed to create a proof of concept by using rest command from HA like so:
rest_command:
update_abrp:
method: POST
content_type: "charset=utf-8; application/x-www-form-urlencoded"
url: >
{% set tlm = {
"utc": float(as_timestamp(utcnow())),
"soc": states('sensor.leapmotor_t03_battery_2'),
"est_battery_range": float(states('sensor.leapmotor_t03_range_2')),
"is_charging": states('binary_sensor.leapmotor_t03_charging') == 'charging',
"odometer": states('sensor.leapmotor_t03_odometer'),
"power": (states('sensor.leapmotor_t03_charging_power')|float * -1),
"is_parked": states('binary_sensor.leapmotor_t03_parked') == 'off',
"speed": states('sensor.leapmotor_t03_speed'),
"lat": '52',
"lon": '18',
} -%}
https://api.iternio.com/1/tlm/send?api_key=xxx&token=xxx&tlm={{tlm|to_json|urlencode}}
and it worked great. But I couldn't send correct lat/lon because it's not sent via MQTT. I think it would be nice to add lat/lon to MQTT and also the ABRP integration into the LeapConnect itself to reduce complexity and sync up car refresh timer with ABRP refresh.
Hey, this works wonderfully but it would be nice if you could add ABRP integration that would sync the data from the car to ABRP.
I managed to create a proof of concept by using rest command from HA like so:
and it worked great. But I couldn't send correct lat/lon because it's not sent via MQTT. I think it would be nice to add lat/lon to MQTT and also the ABRP integration into the LeapConnect itself to reduce complexity and sync up car refresh timer with ABRP refresh.