Alarm state format

Problem

In #47 alarm state format was changed from unix timestamp to formatted string which is nice and makes it more readable. But I think it should also include time zone because it’s a local time.

Before March 28 I live in UTC and can’t check this but Sweden uses CET and I believe if in template editor in developer tools you try this, these timestampts won’t be equal:

Converted timestamp: {{ as_timestamp(states("sensor.<google_home_name>_alarms")) }}
Fire time: {{ state_attr("sensor.<google_home_name>_alarms", "alarms")[0]["fire_time"] }}

This makes it harder to use state in automations.

Solution

Add time zone to TIME_STR_FORMAT. %z should be compatible with ISO datetime format. It should look like 2021-03-04 13:41:04+0100

[leikoilja]

Both of those sounds really nice. Let’s split those into two issues. One to sort the alarms, another to fix the state format. The tricky part with alarms is that they can be single or repetitive, that integration does not cater for yet(#25). Let’s keep this issue to fix state to provide ISO time, we ll keep local_time for UI references and remove utc time 😃

[KapJI]

But anyway adding time zone to local_time is a good idea, this can save people from figuring out why their timestamp is wrong 😃 Also in this case I don’t see why to keep date_time_utc. fire_time and local_time should be enough.

Probably local_time without time zone can be useful for UI but I think sensor should only provide data and lovelace cards can render it the way they prefer.

For example, standard sun.sun or last_triggered attribute in automation use fully qualified ISO format. As well as popular weather.darksky.