Fix incorrect handling of openState in Contact Sensor #1061
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.
♻️ Current situation
The Contact Sensor has three states:
open
,close
, andtimeOutNotClose
1.timeOutNotClose
indicating that the door/window has been open for an extended period. However, in the current implementation, thetimeOutNotClose
state is not handled correctly, causing the state to be incorrectly updated toclose
.💡 Proposed solution
I modified the handling so that
timeOutNotClose
behaves the same asopen
state, and I created a private function for shared handling to prevent future bugs.⚙️ Release Notes
➕ Additional Information
Testing
Reviewer Nudging
Footnotes
https://github.com/OpenWonderLabs/SwitchBotAPI/tree/main?tab=readme-ov-file#contact-sensor-1 ↩