From fefe90a9300a14a790ad0af0b87b314882ac94df Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Wed, 20 Apr 2022 14:12:22 -1000 Subject: [PATCH] Fix typo in EVENT_TIME_CHANGED blog post (#1300) --- blog/2022-04-20-saying-goodbye-to-event_time_changed.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/blog/2022-04-20-saying-goodbye-to-event_time_changed.md b/blog/2022-04-20-saying-goodbye-to-event_time_changed.md index d7e1a3ca..d5e42cbb 100644 --- a/blog/2022-04-20-saying-goodbye-to-event_time_changed.md +++ b/blog/2022-04-20-saying-goodbye-to-event_time_changed.md @@ -8,9 +8,9 @@ With Home Assistant Core 0.113, we began transiting to using the asyncio event l With 2022.5, we are excited to announce that this process is now complete. The legacy `time_changed` event, also known as `EVENT_TIME_CHANGED` is no longer fired every second. Integrations that listen for all events no longer need to filter out `EVENT_TIME_CHANGED`. Integrations that run in a separate thread may see slight performance benefits since they will no longer be awakened every second. -With the previous implementation, consumers would subscribe to the `timed_changed` event and check the time every time it fired to see if it was a match. This pattern led to many callbacks where most of the time, the callback would reject the event and continue receiving callbacks until the desired time was reached. +With the previous implementation, consumers would subscribe to the `time_changed` event and check the time every time it fired to see if it was a match. This pattern led to many callbacks where most of the time, the callback would reject the event and continue receiving callbacks until the desired time was reached. -If your custom integration is still relying on listening for `timed_changed` events, it will need to transition to using one of the built-in event helpers, which are, in most cases, a one-line drop-in replacement. For more information, please review the [integration +If your custom integration is still relying on listening for `time_changed` events, it will need to transition to using one of the built-in event helpers, which are, in most cases, a one-line drop-in replacement. For more information, please review the [integration documentation on listening for events](https://developers.home-assistant.io/docs/integration_listen_events#tracking-time-changes).