input_datetime timestamp is off by 18 minutes

[coolguymatt]

The problem

If I take the timestamp attribute of an input_datetime, and use a unix time converter, the time is off by 18 minutes.

For example:

6:00 EST is 11:00 UTC, but 11:18 UTC appears.

I spun up a fresh HA instance in docker to see if the same thing happens there, and it does:

Environment

• Home Assistant Core release with the issue: 2020.12.0 but I think I noticed it on 0.118 (after input_datetime is in UTC and not local time zone in 0.118 #43337 was resolved)
• Last working Home Assistant Core release (if known): 0.117
• Operating environment (OS/Container/Supervised/Core): OS and Container
• Integration causing this issue: input_datetime
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/input_datetime/

Problem-relevant configuration.yaml

input_datetime:
  both_date_and_time:
    name: Input with both date and time
    has_date: true
    has_time: true

Traceback/Error logs

Additional information

I think I was having this issue when #43337 was resolved but no one else said anything at that time, so I thought it was just something I was doing wrong. I am using America/Toronto time zone.

[probot-home-assistant]

input_datetime documentation
input_datetime source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as its been labeled with an integration (input_datetime) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[seanblanchfield]

I'm having the same problem since I upgraded today from Home Assistant 0.118.4 to Home Assistant Core 2020.12. However my timestamps are exactly 25 minutes too late in all cases.

I am located in Ireland, which is currently on UTC (e.g., both {{ now() }} and {{ utcnow() }} output the same value).

I'm including details here in case they are helpful tracking this down.

I have the following input_datetimes that I store the timestamp of motion events into.

• input_datetime.kitchen_motion_last_detected_time
• input_datetime.living_room_motion_last_detected_time
• input_datetime.hall_motion_last_detected_time
• input_datetime.landing_motion_last_detected_time
• input_datetime.stairs_toilet_motion_last_detected_time
• input_datetime.bathroom_motion_last_detected_time
• input_datetime.driveway_motion_last_detected_time
• input_datetime.garden_motion_last_detected_time

In each case, I have an automation like the following that stores the timestamp:

alias: Kitchen Record Motion
trigger:
  - platform: state
    entity_id: binary_sensor.kitchen_motion_sensor_motion
    to: 'on'
action:
  - service: input_datetime.set_datetime
    data:
      timestamp: '{{ now().timestamp() }}'
    entity_id: input_datetime.kitchen_motion_last_detected_time

After the upgrade, each of these input_datetimes are internally inconsistent, with the correct time stored in the year, month, day, hour, minute, second properties, but with an incorrect timestamp.

To illustrate this, here is the value of one of them from the Developer Tools template editor:

{{  states.input_datetime.kitchen_motion_last_detected_time }}
<template TemplateState(<state input_datetime.kitchen_motion_last_detected_time=2020-12-15 19:12:59; editable=True, has_date=True, has_time=True, year=2020, month=12, day=15, hour=19, minute=12, second=59, timestamp=1608061079.102465, friendly_name=Kitchen motion last detected time @ 2020-12-15T19:12:59.127531+00:00>)>

Note the time was 2020-12-15 19:12:59 and the timestamp value was 1608061079.102465.

Converting that timestamp back to ISO format in a python shell gives:

>>> datetime.datetime.fromtimestamp(1608061079.102465).isoformat()
'2020-12-15T19:37:59.102465'

As you can see, the timestamp in the input_datetime is 25 minutes later than the actual time stored in the other attributes.

The 25 minute difference is consistent across all the other input_datetimes. I've included similar template editor / python shell output below to demonstrate this.

---

Developer tools template editor:

<template TemplateState(<state input_datetime.kitchen_motion_last_detected_time=2020-12-15 19:20:11; editable=True, has_date=True, has_time=True, year=2020, month=12, day=15, hour=19, minute=20, second=11, timestamp=1608061511.092271, friendly_name=Kitchen motion last detected time @ 2020-12-15T19:20:11.117998+00:00>)>

Python console

>>> datetime.datetime.fromtimestamp(1608061511.092271).isoformat()
'2020-12-15T19:45:11.092271'

Timestamp is 25 minutes too late

---

Developer tools template editor:

{{  states.input_datetime.living_room_motion_last_detected_time }}
<template TemplateState(<state input_datetime.living_room_motion_last_detected_time=2020-12-15 19:15:19; editable=True, has_date=True, has_time=True, year=2020, month=12, day=15, hour=19, minute=15, second=19, timestamp=1608061219.076189, friendly_name=Living room motion last detected time @ 2020-12-15T19:15:19.092633+00:00>)>

Python console

>>> datetime.datetime.fromtimestamp(1608061219.076189).isoformat()
'2020-12-15T19:40:19.076189'

Timestamp is 25 minutes too late

---

Developer tools template editor:

{{  states.input_datetime.hall_motion_last_detected_time }}
<template TemplateState(<state input_datetime.hall_motion_last_detected_time=2020-12-15 18:59:04; editable=True, has_date=True, has_time=True, year=2020, month=12, day=15, hour=18, minute=59, second=4, timestamp=1608060244.313249, friendly_name=Hall motion last detected time @ 2020-12-15T18:59:04.419288+00:00>)>

Python console

>>> datetime.datetime.fromtimestamp(1608060244.313249).isoformat()
'2020-12-15T19:24:04.313249'

Timestamp is 25 minutes too late

---

Developer tools template editor:

{{  states.input_datetime.landing_motion_last_detected_time }}
<template TemplateState(<state input_datetime.landing_motion_last_detected_time=2020-12-15 19:00:22; editable=True, has_date=True, has_time=True, year=2020, month=12, day=15, hour=19, minute=0, second=22, timestamp=1608060322.885656, friendly_name=Landing motion last detected time @ 2020-12-15T19:00:22.901331+00:00>)>

Python console

>>> datetime.datetime.fromtimestamp(1608060322.885656).isoformat()
'2020-12-15T19:25:22.885656'

Timestamp is 25 minutes too late

---

Developer tools template editor:

{{  states.input_datetime.stairs_toilet_motion_last_detected_time }}
<template TemplateState(<state input_datetime.stairs_toilet_motion_last_detected_time=2020-12-15 18:29:09; editable=True, has_date=True, has_time=True, year=2020, month=12, day=15, hour=18, minute=29, second=9, timestamp=1608058449.077812, friendly_name=Stairs toilet motion last detected time @ 2020-12-15T18:29:09.087786+00:00>)>

Python console

>>> datetime.datetime.fromtimestamp(1608058449.077812).isoformat()
'2020-12-15T18:54:09.077812'

Timestamp is 25 minutes too late

---

Developer tools template editor:

{{  states.input_datetime.bathroom_motion_last_detected_time }}
<template TemplateState(<state input_datetime.bathroom_motion_last_detected_time=2020-12-15 12:49:18; editable=True, has_date=True, has_time=True, year=2020, month=12, day=15, hour=12, minute=49, second=18, timestamp=1608038058.43889, friendly_name=Bathroom motion last detected time @ 2020-12-15T15:04:00.634062+00:00>)>

Python console

>>> datetime.datetime.fromtimestamp(1608038058.43889).isoformat()
'2020-12-15T13:14:18.438890'

Timestamp is 25 minutes too late

---

Developer tools template editor:

{{  states.input_datetime.driveway_motion_last_detected_time }}
<template TemplateState(<state input_datetime.driveway_motion_last_detected_time=2020-12-15 18:25:27; editable=True, has_date=True, has_time=True, year=2020, month=12, day=15, hour=18, minute=25, second=27, timestamp=1608058227.418247, friendly_name=Driveway motion last detected time @ 2020-12-15T18:25:27.435940+00:00>)>

Python console

>>> datetime.datetime.fromtimestamp(1608058227.418247).isoformat()
'2020-12-15T18:50:27.418247'

Timestamp is 25 minutes too late

---

Developer tools template editor:

{{  states.input_datetime.garden_motion_last_detected_time }}

<template TemplateState(<state input_datetime.garden_motion_last_detected_time=2020-12-15 18:44:10; editable=True, has_date=True, has_time=True, year=2020, month=12, day=15, hour=18, minute=44, second=10, timestamp=1608059350.11338, friendly_name=Garden motion last detected time @ 2020-12-15T18:44:10.148678+00:00>)>

Python console

>>> datetime.datetime.fromtimestamp(1608059350.11338).isoformat()
'2020-12-15T19:09:10.113380'

Timestamp is 25 minutes too late

---

[balloob]

Thanks for all the feedback.

This sucks because I thought that I had covered all cases in this test https://github.com/home-assistant/core/blob/dev/tests/components/input_datetime/test_init.py#L648

Will take a look.