Remaining range not showing

[jackyoung1]

I have added a sensor with remaining range to the card config, but it doesnt show in the card

I dont have an entity with % charge, so have left this blank

[MrBlue90]

+1 I experience the same issue since one of the recent updates.

[WJDDesigns]

This entity should be a sensor with the state 1-100 is it not?

[jackyoung1]

No, remaining range is distance as I understood it? Remaining charge is 1-100 but the range is distance?

[MartinAirN]

Could you share your config and screenshot of how it looks? Perhaps with an example of what you expect.

[MrBlue90]

type: custom:ultra-vehicle-card
title: Hyundai Tucson
image_url: >-
  https://vehicle-images.dealerinspire.com/stock-images/chrome/400e243081e3655168b59466fa1fbcc6.png
vehicle_type: Fuel
unit_type: km
level_entity: sensor.tucson_fuel_level
range_entity: sensor.tucson_fuel_driving_range
location_entity: device_tracker.tucson_location
mileage_entity: sensor.tucson_odometer
show_level: true
show_range: true
show_location: true
show_mileage: true
icon_grid_entities:
  - lock.tucson_door_lock
  - binary_sensor.tucson_fuel_low_level
  - binary_sensor.tucson_washer_fluid_warning
  - binary_sensor.tucson_tire_pressure_all
  - binary_sensor.tucson_trunk
custom_icons:
  binary_sensor.tucson_trunk: mdi:bag-checked
  lock.tucson_door_lock: mdi:car-door-lock-open
  binary_sensor.tucson_fuel_low_level: mdi:gas-station
  binary_sensor.tucson_washer_fluid_warning: mdi:wiper-wash-alert
  binary_sensor.tucson_tire_pressure_all: mdi:car-tire-alert

[MartinAirN]

Ah, you are experiencing a mismatch in the frontend and backend. Most likely due to a caching issue.

If you open HA in a private browser, login and edit the tile my guess it that it will work. If it does, clearing your cache in the app and/or browser will fix the issue.

[WJDDesigns]

Please download the newest update as well as restart HA and clear frontend cache, thanks!

[MrBlue90]

Thanks gentlemen! Updating to 1.3.1, rebooting HA, using incognito browsing (to avoid cache) and reapplying the new settings in the card solved the issue!