Make calling update on child devices consistent and give control over whether to update the parent #1021
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.
This PR is normalising the behaviour of
update
acrossiot
andsmart
devices such that:update
can be called by consumers on child devices without them being surprised that it is a noop or partial for some devices and not for others.update_children
(renamedupdate_children_or_parent
) has the same default value ofTrue
across devices.smart
devices don't callupdate
on children ifupdate_children_or_parent
isFalse
.update_children_or_parent=False
so they just update their own module queries.update_children
as a kwarg retain the same behaviour and get a deprecation warning. (i.e.smart
ignores the parameter and always updates children)Currently Hubs do not support updates on children directly but this could be a good feature to implement in another PR to allow finer grained control for hubs with many attached devices.
Not to be merged until we're finished with 0.7.0.x patches