From ee853f35feec48326975f8cf5cea1db44a333f68 Mon Sep 17 00:00:00 2001 From: DubhAd Date: Sun, 17 Jun 2018 11:03:03 +0100 Subject: [PATCH] Promoting timezone issue to warning (#5552) Given the long standing bug with the alert component - where the timezone in HA differs from the timezone of the OS when starting HA it either fires rapidly, or very slowly - promoting this to a warning. See [this bug](https://github.com/home-assistant/home-assistant/issues/13609) and [this thread](https://community.home-assistant.io/t/error-alert-component/56242) which reminded me about it. --- source/_components/alert.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_components/alert.markdown b/source/_components/alert.markdown index 4c59259cde3..e1af527f5f2 100644 --- a/source/_components/alert.markdown +++ b/source/_components/alert.markdown @@ -16,7 +16,9 @@ The `alert` component is designed to notify you when problematic issues arise. F Alerts will add an entity to the front end only when they are firing. This entity allows you to silence an alert until it is resolved. +

When using the `alert` component, it is important that the time zone used for Home Assistant and the underlying operating system match. Failing to do so may result in multiple alerts being sent at the same time (such as when Home Assistant is set to the `America/Detroit` time zone but the operating system uses `UTC`). +

### {% linkable_title Basic Example %}