home-assistant[bot]
commented
4 hours ago Hey there @dknowles2, mind taking a look at this issue as it has been labeled with an integration (schlage) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `schlage` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign schlage` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
schlage documentation schlage source (message by IssueLinks)
The problem
The "locked" or "unlocked" status is "updating" every 30 seconds, causing any automation based on state change to fire every 30 seconds. Also I cannot use the "previous state" to filter because it is always null.
As a workaround I am capturing the state change in node-red and saving the state in a global variable so that I can check it each time.
If I open the actual lock in HA I can see the "last change" actually reset to "now" every 30 seconds.
What version of Home Assistant Core has the issue?
core-2024.10.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
schlage
Link to integration documentation on our website
https://www.home-assistant.io/integrations/schlage
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response