sensor.next_alarm_time shows "unavailable" while there is an alarm set in Garmin Connect about home-assistant-garmin_connect HOT 6 CLOSED

I will have a look, thanks for report

from home-assistant-garmin_connect.

Fixed in version 0.2.16

from home-assistant-garmin_connect.

For me this works properly with v0.2.3, some things with timestamps was fixed in there.

from home-assistant-garmin_connect.

Not sure if that is related, but for me this error came up after the recent updates. Now the log is full with the following error occuring every 5 minutes:
ValueError: Sensor sensor.next_alarm_time has a state class and thus indicating it has a numeric value; however, it has the non-numeric device class: timestamp

from home-assistant-garmin_connect.

I just installed this integration for the sole purpose of feeding my watch's next alarm time into HA. After installation, all sensors worked except next alarm, which showed "unavailable" even though I had an alarm set. I added another alarm for a different time, and the new one showed up. I removed the new one and the sensor reverted to unavailable. I turned off my old alarm, sync'd with the GC app, and waited 5 minutes, then turned the alarm back on and sync'd and 5 minutes later still nothing changed. I then just deleted that old alarm and created an identical one in its place. Now it shows up in HA.

My summary is that it seems like there is something with old or existing alarms that prevents them from being exposed to the integration. Deleting them and creating new ones seems to be the resolution.

from home-assistant-garmin_connect.

I've been using the next alarm for an automation for some months. On Thursday after upgrading home Assistant to 2023.05.3 the next alarm entity is missing.
Alarm is set. All other entities are available.

from home-assistant-garmin_connect.