"Internal" time wrong

sender · May 5, 2020, 8:16pm

I used this initially:

but then I used this:

But the last time the sensor was tripped was 20:22, thus for me 2 hours ago…

petro · May 5, 2020, 8:17pm

it doesn’t round.

sender · May 5, 2020, 8:18pm

so you mean in 4 minutes from now, at my time 22:22 it will say “2 hours ago”?

EDIT: yes it does:

petro · May 5, 2020, 8:18pm

yep, that’s what will happen.

sender · May 5, 2020, 8:21pm

Ok thank you for your help.

As a moderate user I must say that this is not very handy/understandable/user friendly/clear/whatever comes to that :-). I just want to see “my time” stuff in hass and not a UTC timezone that for me in this location make no real sense… I think this must be aware to the “awesome guys” that make hass?

I would really like to see events and tripped times to my timezone. That not a dumb question is it?

petro · May 5, 2020, 8:25pm

I understand where you’re coming from, but it’s only confusing because of the way that your device is implemented. Anyone who want’s a special time displayed in the interface from a device goes through this and there is 9000 different ways people want to view their time. Some people want AM PM, some people only want minutes, some people want it spelled out… see where this is going?

For example, my motion sensors do not have a special attribute called ‘last_tripped_time’. They just turn on and off. HA handles the times by using the last_updated and last_changed state object properties. (giving you the ability to use the last_changed secondary row). Your sensor is unique because it doesn’t do that. Apparently when your sensor trips, it doesn’t send an update to the main state, effectively making last_changed or last_updated useless.

sender · May 5, 2020, 8:27pm

Sorry, I don’t see where you are going :-). time is time, nothing fancy is it? I don’t care about AM/PM, written or sung, but I DO care about the correct ZONE. Nevertheless, thank you and I hope it will be picked up in the future.

petro · May 5, 2020, 8:28pm

Yes, but you seem to not understand. The more-info page is showing you unaltered attributes. It (home assistant) does not know it’s a time. So it keeps it unaltered. That’s up to the user to make use of the attribute.

If that is coming straight from your device, then your device needs to use the local timezone. And if thats something that you can’t set, then you can make a request to the integration to put that time in local timezone. Or do what everyone else does and convert the time. There’s a number of threads that cover how to do that. Here’s one:

sender · May 5, 2020, 8:31pm

Ok I see now that I don’t know what I don’t know. I’ll read on. thanks again!

sender · May 15, 2020, 9:50am

Hi, another question regarding this topic…

what if I wanted this:

Tried this:

    sensors:
      car_last_tripped:
        friendly_name: "Last Motion in BMW"
        value_template: "{{ state_attr('switch.motion_sensor_5_1493', 'last_tripped_time') }}"
        device_class: timestamp
      hal_voorkant_afdak_last_tripped:
        friendly_name: "Last Motion Voordeur"
        value_template: "{{ state_attr('binary_sensor.sensor_hal_voorkant_beweging', 'last-changed') }}"
        device_class: timestamp

But clearly I have not yaml knowledge

Mariusthvdb · May 15, 2020, 10:20am

you must have an error there in the logs… use last_changed instead, and use it like this:

{{ states.binary_sensor.sensor_hal_voorkant_beweging.last_changed }}

you cant template last_changed using the states() method

sender · May 15, 2020, 11:50am

yes, seems to work now, thank you!

Mariusthvdb · May 15, 2020, 11:56am

sure, welcome.

you should understand why though, so read up on this: https://www.home-assistant.io/docs/configuration/state_object/

last_changed isn’t an attributes you can call using state_attr()

sender · May 15, 2020, 12:01pm

Hi, read it. but I do not understand what you mean with
last_changed isn’t an attributes you can call using state_attr()

Mariusthvdb · May 15, 2020, 12:09pm

using state_attr() you can reference all attributes of the state.

in your case eg:

states.binary_sensor.sensor_hal_voorkant_beweging.attributes.name
states.binary_sensor.sensor_hal_voorkant_beweging.attributes.icon

which you can also write as

state_attr('binary_sensor.sensor_hal_voorkant_beweging','name')

this is also explained here: https://www.home-assistant.io/docs/configuration/templating/#states

be sure to read the yellow Warning bit, as it will help you write safer templates.

if you want to see which attributes are available for you entity, just throw this at the template editor:

{{states.binary_sensor.sensor_hal_voorkant_beweging.attributes}}

you’ll notice ‘last_changed’ isnt listed. because it is no ‘attribute’.

petro · May 16, 2020, 12:48pm

ArcherNE · May 19, 2020, 2:07am

On a RaspPi 3, HassOS 3.13

{{ utcnow() }}
{{ now() }}
{{ utcnow().astimezone() }}
{{ now().astimezone() }}
{{ utcnow().tzinfo }}
{{ now().tzinfo }}
{{ now().astimezone().tzinfo }}

I get

2020-05-19 01:53:12.396476+00:00
2020-05-18 20:53:12.396624-05:00
2020-05-19 01:53:12.396790+00:00
2020-05-19 01:53:12.398530+00:00
UTC
America/Chicago
UTC

Any idea why the astimezone() are all messed up?

petro · May 19, 2020, 4:50pm

check out this

nonyhaha · May 28, 2020, 6:42am

Hello Everybody!
Looks like I have a similar issue with time settings. I think you are all running in circles not finding the correct issue.
I say this because:
I am running home assistant supervised in an esxi VM. Installed using 3.13 vmdk image.
Since I installed it a few days ago, I have had a lot of problems, by losing access to the server. I saw it was losing its ip address.
So after reading a lot of topics, I found that the timestamps in supervisor logs are of by 3 hours.
This time delay will F*** up the dhcp renewal from my router (pfsense vm) and after the minimum lease time of 2 hours, the home assistant machine loses its IP and I have to power cycle it. Simple reset will not solve the issue.

Now, I would like to ask you if there is any way to correct this issue. It is driving me crazy, and until now I did not manage to find a way to set the supervisor time/timezone.

Thank you,
And here is my original topic on this forum: Hassio on esxi losing IP address - HA supervised
And here is the issue on Github: https://github.com/home-assistant/operating-system/issues/684

rpw · November 12, 2022, 3:16pm

Version	core-2022.2.3
Installation Type	Unknown
Development	false
Supervisor	false
Docker	false
Virtual Environment	false
Python Version	3.9.10
Operating System Family	Windows
Operating System Version	8.1
CPU Architecture	AMD64
Timezone	America/Chicago