Get alarm time from alexa

Configuration
1

Hello,

I try to grab the time of an alarm configured on my echo.
My goal is to get the time of the alarm to start my AC 1 hour before.

I use Alexa Media Player to get the data.
Example of the data I get from the parser :

“originalDate”: “2020-01-10”, “originalTime”: “06:45:00.000”, “personProfile”: null, “provider”: null, “rRuleData”: null, “recurrenceEligibility”: false, “recurringPattern”: “XXXX-WD”,

So the next alarm will be tomorrow morning a 6:45am local time (Montréal) of my echo.

The state of my sensor is : 2020-01-10T06:45:00+00:00
And I think HA think it’s GMT because on my lovelcace I see :

Alexa - Echo Dot Next Alarm in 12h but in Montreal right now it’s 13h30 so 6h45 is not in 12h but in 17h so 5h of error.

So I looked at the time of my HA : sensor.date_time = 2020-01-09, 13:39 sensor.time_utc = 18:40 sensor.date_time_iso = 2020-01-09T13:41:00

I can’t find any explanation why HA shows 5h of error
And if I try to use the data in node red I also have an error of 5h …

Any idea ?

2

If “2010-01-10” + “06:45:00.000” is supposed to be in EST, then the state of your sensor seems to be misinterpreting it, because “+00:00” means UTC, not EST. What is the HA config for that sensor?

3

Nothing …
It a sensor created by Alexa Media Player integration.
So i didn’t put anything in my config.

4

Well then it seems like it has a bug.

5

Yes.
I just see other bug report on github for timezone.

Anyway to correct the sensor in HA ? (sensor = sensor +5h) :slight_smile:

6

I don’t know anything about the Alexa Media Player integration. But you could always create a template sensor that calculates the correct time.

Out of curiosity, what do you get if you enter the following into the Template Editor:

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

America/Toronto
UTC

8

Did you check your logs? Are you getting a warning about your timezone not being set in alexa?

9

That might be your problem. The time zone setting in the OS, or docker, or whatever HA is running in, is set incorrectly.

10

if you’re interested…

    def _fix_alarm_date_time(self, value):
        import pytz

        if self._sensor_property != "date_time" or not value:
            return value
        naive_time = dt.parse_datetime(value[1][self._sensor_property])
        timezone = pytz.timezone(self._client._timezone)
        if timezone:
            value[1][self._sensor_property] = timezone.localize(naive_time)
        else:
            _LOGGER.warning(
                "%s does not have a timezone set. "
                "Returned times may be wrong. "
                "Please set the timezone in the Alexa app.",
                self._client.name,
            )
        return value
11

Mmmm … i use docker on ubuntu.

12

Do you run it with ... -v /etc/localtime:/etc/localtime:ro?

13

I see … i will check my log

14

Seems to be a common problem. But according to @petro’s post, looks like yet another time zone setting is coming into play that needs to be set right, too.

15

I can’t check right now because i don’t have access th the host machine.
But i use the stock configuration and image of hassio on docker …

16

when you setup ubuntu it asks you to put in your timezone. It’s separate from HA.

17

yes maybe but why when i display the HA time :
sensor.date_time = 2020-01-09, 13:39 sensor.time_utc = 18:40 sensor.date_time_iso = 2020-01-09T13:41:00
It’s correct …

18

But docker can have its own time zone setting, too, right??? (I don’t know. I never tried to use docker.)

19

Because HA has its own time zone setting.

There are at least these time zone settings in your scenario, and they should all be set correctly and agree:

Ubuntu
Docker
HA
Alexa App

20

I know … i checked my tzinfo on my ubuntu server and it was correct yesterday