Owntracks sensor.timestamp doesn't show relative time?

@Mariusthvdb wrote:

using the option relative on the Owntracks timestamp sensor still shows the timestamp, and not the relative time:

  - type: entities
    title: Owntracks
    show_header_toggle: false
    entities:
      - sensor.ot_battery
      - sensor.ot_altitude
      - sensor.ot_latitude
      - sensor.ot_longitude
      - sensor.ot_topic_id
      - entity: sensor.ot_timestamp
        format: relative
      - sensor.ot_course_over_ground
      - sensor.ot_accuracy
      - sensor.ot_vertical_accuracy
      - sensor.ot_velocity
      - sensor.ot_internet_connectivity
      - sensor.ot_type
      - sensor.ot_trigger
      - sensor.ot_copy_mode

Schermafbeelding 2019-11-22 om 17.24.45.jpg794×154 17 KB

is this a bug, or is the sensor not a real timestamp sensor. Or would I need to add other configuration settings?

this is the mqtt sensor

  - platform: mqtt
    state_topic: !secret owntracks_mqtt_topic
    name: 'Ot Timestamp'
    icon: mdi:clock
    value_template: '{{value_json.tst}}'

adding device_class: timestamp to the mqtt sensors errors on ‘invalid date’

Posts: 1

Participants: 1

Read full topic