Invalid timestamp

Describe the bug

I was getting “Unavailable” on v.1 on alarms and timers but now get “Invalid Timestamp” on v1.1.0

Version of the integration

V1.1.0

Glocaltokens Version (Underlying package)

Add pip information here.

Logs

2021-03-25 20:15:37 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2021-03-25 20:15:43 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform meross_cloud is taking over 10 seconds.
2021-03-25 20:16:37 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: google_home
2021-03-25 20:16:47 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2021-03-25 20:16:47 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2021-03-25 20:16:47 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2021-03-25 20:16:47 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2021-03-25 20:16:47 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2021-03-25 20:16:47 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2021-03-25 20:16:47 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.

Debug log

logger:
  default: debug
  logs:
    custom_components.google_home: debug

Add your debug logs here.

[leikoilja]

Thank you, @KapJI, for taking a look at this. I would rather go with your 2nd proposal and use UNAVAILABLE just as you mentioned mobile app sensor uses 😃 That way we would still keep device class that enables sensors to be used in automation and blueprints without problems (there are some nice popular blueprints out there that filter devices by device_class being DEVICE_CLASS_TIMESTAMP (see this PR)

[craigmcgowan]

To hopefully better explain the “Invalid Timestamp” issue.

Previously, an _alarms or _timers entity would display as “Off” or “On” depending on if any were set.

However, they now try to display as a formatted timestamp. So now show as “In 7 hours” if a timer/alarm is set (Rather than just “On”). If no alarm/timer is set they display as “Invalid Timestamp” (Rathe than just “Off”)

Please see below

I hope that clears it up.

Personally speaking, the alarm/timer entities contain the set alarms/timers in an array, I think the entity itself should just show “Yes” or “No” as per original functionaliy.

Thank you for your hard work.

P.S. Also notice your version number has been dropped to 0.0 in my screenshot above, I think it used to show. Ive now updated to v1.1 and it doesnt show.