Add support for motion sensors #15
Merged
Conversation
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
webdeck
approved these changes
Jan 7, 2017
|
Forgot to update the readme and config sample though. I'll let you do it 😁 |
|
Done, and version bumped and published to npm - enjoy! |
|
Updated HBB and it reflects the new HB-Indigo as well as adding direct support in the plugin's Alias, Wrapper and Server devices for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allow Homekit to treat motion sensors as sensors. You might want to check around to see if I forgot something, but it seems to work really well with my sensors.
You have to close and reopen the Home app to see the statuses updated... but this seems to be the case for all devices.