Blinds #33
Blinds #33
Conversation
requires upgraded nhc2-hobby-api for Moving prop still needs some additional logic to differentiate between increasing and decreasing
|
Thank you, I have it working locally, would be nice to have it merged. |
|
Works nicely for me here, too. It looks like the pull check build errored due to it using the version of nhc2-hobby-api that doesn't have the Moving attribute added. |
|
Yes it does work the issue is that I can't publish a new version of nhc2-hobby-api to npm as the travis build isn't working: Unfortunately the maintainer of these two projects does not seem to be active anymore. I'm considering creating a fork so we can deploy new features again. |
|
Hi Everyone, I finally managed to port over both repositories to a new organisation. You can find the new repository here. https://github.com/openhomekit/homebridge-nhc2 @christophevg Since you were still active, if you are willing to contribute in the new org, contact me and I'll add you as a contributor. Please try out the new package (v3.0.0), blinds support should be working there (as good as we can for now). |
|
Hi @rubencallewaert I'll start with installing/testing/... and we'll see from there. |
Finished up support for all type of blinds offered by Niko.
(Direction is indeed an unsolvable issue, we should get in touch with Niko that they add a direction property on their events)
Most of the heavy lifting was already done by @christophevg thanks for that.
Apple homekit detects "moving" as a difference between target and current position.
closes #31
Up to date with master and tested on my own devices.
Depends on my other 2 PR's in the nhc2-hobby-api repo:
homebridge-nhc2/nhc2-hobby-api#17
homebridge-nhc2/nhc2-hobby-api#18