For devices with 'queryState' set, we read state after write. #999
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.
As per the discussion in #939 some devices (like my AduroSmart lights) don't send device updates. To properly know the state of the device after we set it, we can issue a get command. This change will always do that for devices that have
queryState
set to true.I decided to implement it like this, in a more generic way. This works fine for me. If you approve this PR, I'll submit one to actually include
querystate
for the device. The other option is to just make a few converters for this device and setreadAfterWriteTime
for those - I've tried that and that also works fine. Let me know if you prefer that and I'll make a PR accordingly,