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
I recently added in a new automation based on the state of a binary motion sensor (setup via ESPHome) - when the automation is enabled the state changes of the binary sensor do not seem to be written to the logbook at all. As soon as I disable the automation the state changes are written to the log book without issue. I only added this automation in after the upgrade to 2024.2.1 so I'm uncertain if this does or doesn't work in previous versions.
More Info screen for the sensor with the automation enabled:
More Info screen for the sensor with the automation disabled:
What version of Home Assistant Core has the issue?
core-2024.2.1
What was the last working version of Home Assistant Core?
Did some additional investigation today (turned recorder debug logging on) - and it would appear that the recorder is receiving the state changes (when the automation is enabled):
The problem
I recently added in a new automation based on the state of a binary motion sensor (setup via ESPHome) - when the automation is enabled the state changes of the binary sensor do not seem to be written to the logbook at all. As soon as I disable the automation the state changes are written to the log book without issue. I only added this automation in after the upgrade to 2024.2.1 so I'm uncertain if this does or doesn't work in previous versions.
More Info screen for the sensor with the automation enabled:
More Info screen for the sensor with the automation disabled:
What version of Home Assistant Core has the issue?
core-2024.2.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
recorder
Link to integration documentation on our website
No response
Diagnostics information
config_entry-esphome-7bfff552c359cc3bf3d43c090039aa83 (1).json
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: