Hyundai Bluelink Integration


updated my cards to include ioniq 6 and some smaller alt ones too.

the charge port icon works like the charge port, stays on for battery level and flashes the way the car one does when car is charging.

1 Like

Hi all,

Posted on UVO thread, I guess I can also share this here.

Thanks @anon63427907 (and @fuatakgun and @wcomartin and all involved) ! This is great to be able to fetch data from uvo/bluelink

I’m using this integration and managed to push bluelink data to ABRP :slight_smile:
(inspiration came from here)

First create a rest_command in configuration.yaml:

  update_abrp:
    method: POST
    headers:
      content_type: "charset=utf-8; application/x-www-form-urlencoded"
    url: >
      {% set tlm = {
        "utc": as_timestamp(strptime(states('sensor.kona_last_updated_at'), "%Y-%m-%dT%H:%M:%S%z")),
        "soc": states('sensor.kona_ev_battery_level'),
        "soh": states('sensor.kona_ev_state_of_health_battery'),
        "est_battery_range": float(states('sensor.kona_ev_range')),
        "is_charging": states('sensor.kona_is_charging'),
        "lat": state_attr('device_tracker.kona_location', 'latitude'),
        "lon": state_attr('device_tracker.kona_location', 'longitude'),
        "odometer": states('sensor.kona_odometer')
      } -%}
      https://api.iternio.com/1/tlm/send?api_key=your_api_key_from_iternio&token=your_token_from_abrp_app&tlm={{tlm|to_json|urlencode}}
# https://documenter.getpostman.com/view/7396339/SWTK5a8w#api-endpoints

then this automation will push the telemetry each time an update is received by the integration:

  alias: Télémétrie KONA vers ABRP
  description: ''
  triggers:
  - trigger: state
    entity_id:
    - sensor.kona_last_updated_at
  conditions: []
  actions:
  - action: rest_command.update_abrp
    data: {}
    response_variable: status
  mode: single

Now I have to figure out what are the best value for scan without beeing locked until the rest of the day (got “to many request” error in bluelink app while playing with ABRP)