You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to report a few timestamp issues. I could report it separately but those share common problems. Changes I suggest will make reported values compliant with current HA standards.
sensor.fordpass_lastrefresh
should be set to: device_class: timestamp
the value passed to this sensor should be ISO formatted (add T literal between date and time, for example: 2023-04-15 13:04:33+02:00)
wrong format of timestamp attributes timestamp attributes found in entities are in the wrong format. It's American format with the date formatted as month-day-year.
To allow further processing the expected format is year-month-day.
Please note, using the American format may lead to interpretation errors in other countries, for example, what date is 03-04-2023? is it 3rd April or 4th Match?
See the image below, the time of the last refresh is obviously correct (otherwise, but the timestamp attribute for ignition status has exchanged day and month values.
Also, I suggest making all timestamps ISO compliant (with T literal between date and time)
I believe the value itself represents GMT time. So the time from the image should look like 2023-04-15T11:04:44+00:00 (unless HA itself converts it to the local time zone which I don't believe it does)
weird data for fordpass_dieselSystemStatus
I'm sure it's not the proper format for json. Then what it should be?
timestamp issue, the same as described in point 2.
The text was updated successfully, but these errors were encountered:
michalk-k
changed the title
timestamps issues found in attributes are in wrong format
timestamp issues
Apr 15, 2023
I will add the device_class to that sensor in the next version, but the actual formatting is already T literal and then converted to local time using your local HA instance time.
All attributes are just raw sensor values from the Fordpass API I don't do any processing on dates as this is just extra data the user can use in templates if they so wish.
Agreed that shouldn't return that for the diesel sensor will have a look at that in the next version thanks.
I would like to report a few timestamp issues. I could report it separately but those share common problems. Changes I suggest will make reported values compliant with current HA standards.
sensor.fordpass_lastrefresh
device_class: timestamp
T
literal between date and time, for example:2023-04-15 13:04:33+02:00
)wrong format of timestamp attributes
timestamp
attributes found in entities are in the wrong format. It's American format with the date formatted asmonth-day-year
.To allow further processing the expected format is
year-month-day
.Please note, using the American format may lead to interpretation errors in other countries, for example, what date is 03-04-2023? is it 3rd April or 4th Match?
See the image below, the time of the last refresh is obviously correct (otherwise, but the timestamp attribute for ignition status has exchanged day and month values.
Also, I suggest making all timestamps ISO compliant (with
T
literal between date and time)I believe the value itself represents GMT time. So the time from the image should look like 2023-04-15T11:04:44+00:00 (unless HA itself converts it to the local time zone which I don't believe it does)
weird data for
fordpass_dieselSystemStatus
The text was updated successfully, but these errors were encountered: