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 have updated to the latest available Home Assistant version.
I have cleared the cache of my browser.
I have tried a different browser to see if it is related to my browser.
I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.
Describe the issue you are experiencing
I have an automation that immediately turns off a toggle when it is turned on. Up until 2024.5.0 version, I could trigger the toggle in the UI and it would very quickly turned off. After this version, the toggle seems to not be updated anymore.
If I add a delay to my automation, then it works fine again.
Initially I thought this was related to core, but during my tests, it still worked well after HA was updated to 2024.5.0, and it only starts failing after I got the "there's a new frontend version" and I reloaded the scripts.
Describe the behavior you expected
As before, I expected the toggle to be immediately switched off after turned on.
Steps to reproduce the issue
Create a new Toggle Helper (e.g. input_boolean.toggle_1)
Open the entity window for the Toggle and turn it on. Up until 2024.5.0, the toggle would immediately turn off. Starting on this version, the toggle is not turned off anymore.
If you add a delay as the first step of the automation above, then everything works again.
...
What version of Home Assistant Core has the issue?
core-2024.5.1
What was the last working version of Home Assistant Core?
core-2024.4.4
In which browser are you experiencing the issue with?
Google Chrome 124.0.6367.119
Which operating system are you using to run this browser?
macOS Sonoma 14.4.1
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
This shows the behaviour I'm seeing: https://imgur.com/a/TNinCtD
The first 50 seconds show the previous behaviour, then the last 10 seconds is after the frontend is refreshed.
The text was updated successfully, but these errors were encountered:
After manual toggling the helper to ON:
-- the helper is still ON;
-- in logbook: a record "toggled by automation to OFF" is BEFORE a record "manually toggled to ON".
After F5:
-- the helper is OFF;
-- there is no record "toggled by automation to OFF" in logbook.
Turn the helper ON again:
After F5:
Turn the helper ON again:
After F5:
See no logic here:
-- a wrong sequence in logbook - "changed by automation" before "changed by user";
-- why the 1st record "changed by automation" disappeared;
-- why records "changed by automation" replaced by "turned off triggered by state..."
Checklist
Describe the issue you are experiencing
I have an automation that immediately turns off a toggle when it is turned on. Up until 2024.5.0 version, I could trigger the toggle in the UI and it would very quickly turned off. After this version, the toggle seems to not be updated anymore.
If I add a delay to my automation, then it works fine again.
Initially I thought this was related to
core
, but during my tests, it still worked well after HA was updated to 2024.5.0, and it only starts failing after I got the "there's a new frontend version" and I reloaded the scripts.Describe the behavior you expected
As before, I expected the toggle to be immediately switched off after turned on.
Steps to reproduce the issue
input_boolean.toggle_1
)...
What version of Home Assistant Core has the issue?
core-2024.5.1
What was the last working version of Home Assistant Core?
core-2024.4.4
In which browser are you experiencing the issue with?
Google Chrome 124.0.6367.119
Which operating system are you using to run this browser?
macOS Sonoma 14.4.1
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
This shows the behaviour I'm seeing: https://imgur.com/a/TNinCtD
The first 50 seconds show the previous behaviour, then the last 10 seconds is after the frontend is refreshed.
The text was updated successfully, but these errors were encountered: