You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Detected that custom integration 'attributes' calls async_track_state_change instead of async_track_state_change_event which is deprecated and will be removed in Home Assistant 2025.5
#47
Open
antivirus68 opened this issue
May 12, 2024
· 3 comments
After updating to HA 2024.5 I got this WARNING in HA log.
2024-05-12 08:09:48.940 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'attributes' calls "async_track_state_change" instead of "async_track_state_change_event" which is deprecated and will be removed in Home Assistant 2025.5 at custom_components/attributes/sensor.py, line 221: async_track_state_change(, please create a bug report at https://github.com/pilotak/homeassistant-attributes/issues
The text was updated successfully, but these errors were encountered:
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:184
First occurred: 10:12:28 AM (1 occurrences)
Last logged: 10:12:28 AM
Detected that custom integration 'attributes' calls async_add_job, which is deprecated and will be removed in Home Assistant 2025.4; Please review https://developers.home-assistant.io/blog/2024/03/13/deprecate_add_run_job for replacement options at custom_components/attributes/sensor.py, line 216: self.hass.async_add_job(self.async_update_ha_state(True))
After updating to HA 2024.5 I got this WARNING in HA log.
2024-05-12 08:09:48.940 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'attributes' calls "async_track_state_change" instead of "async_track_state_change_event" which is deprecated and will be removed in Home Assistant 2025.5 at custom_components/attributes/sensor.py, line 221: async_track_state_change(, please create a bug report at https://github.com/pilotak/homeassistant-attributes/issues
The text was updated successfully, but these errors were encountered: