-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zha switch schedule update state #16621
Merged
balloob
merged 2 commits into
home-assistant:dev
from
Adminiuga:zha-switch-update-state
Sep 21, 2018
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't do this, and neither should we change
self._state
. We depend onattribute_updated
to push the state change to usThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not entirely sure relying on
attribute_updated
is a proper channel for this kind of state updated, especially when we're triggering the change.We do send a ZCL command and we do know the transmission hasn't timed out, in other words device has acknowledge reception of the command.
The problem with
attribute_updated
it relies on attribute reporting configuration, so if for whatever reasonzha.configure_reporting()
was unsuccessful, this makes the switch unusable, as I never can change the state (because the feedback loop throughattribute_updated
is broken) even though I can control the switch and switch can successfully receive my commands.attribute_updated
channel is more for externally originated events, like user toggling the switch from the button on the actual physical device.@rcloran what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also want to implement
attribute_updated()
method forfan.zha.ZhaFan
class, because it is nice for HA state to be in sync with the actual state of the device, since the fan is often operated externally from the remote/wall switch.I'd like to understand why it is fundamentally wrong with updating
self._state
in the service calls and inattribute_updated()
method. Both are executed in the event loop, so there shouldn't be any race conditions. I'm not always getting attribute report triggering theattribute_update()
with King of Fans zigbee fan, so relying solely onatribute_updated()
to updateself._state
would likely render Fan inoperable from HA