Closed DHandspikerWade closed 3 months ago
Same as #112573
Not a bug.
The value of the remaining
attribute has never updated while the timer
entity is active.
This sounds related to my issue... I have an issue with ESPHome not getting subscription updates for the timer attributes despite other entities receiving an initial attribute update upon subscribing even if the entity attribute has not changed. Are you sure this isn't a bug with HA? I have raised the issue with ESPHome in case it is an ESPHome issue.
Update: Ignore my comment, I had an issue in my own code which stopped it working. 🤦
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
Using the "remaining" attribute on timer entities does not update. With an initial value of 50 minutes and after running for over 10 minutes, dashboard tiles and refreshing the state display in developer tools still shows 50 minutes. Entity card shows the correct time.
What version of Home Assistant Core has the issue?
core-2024.3.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
timer
Link to integration documentation on our website
https://www.home-assistant.io/integrations/timer/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
Timer was started via a
timer.start
service call. I let the timer run for over ten minutes without change.