-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contact Status Reversed #23
Comments
Same issue with a Z-Wave Sensative Strip (Window contact sensor). However, iOS Home App reports the sensor as OPEN (shall be CLOSED). |
Are you in the latest homebridge-openHAB? I ran into the same problem yesterday and saw there was a bug in the code. Updating tho the latest version fixed it. |
Thanks @gijoecool ! That was indeed the problem. I thought I was running the latest version (0.1.32) but that was not the case (0.1.31). I was using npm to install homebridge-openhab as stated in the documentation: |
I also had to switch to the dev version, time for a new release? |
Can someone provide step-by-step instructions on updating the homebridge-openhab plugin to 0.1.32? I have the same problem with iOS Home displaying contact status reversed. Pretty green here and currently have it working with 0.1.31 but when I try to install the newer version, Homebridge no longer starts up and I ultimately have to restore the SD card (RaspberryPi) with a backup to get things working again. |
I'm monitoring some dry contacts my Omni using the openHAB omnilink binding. When a window is open, it shows as "contact detected" in Home and "Contact: YES" in Eve while the status shows as "open" in openHAB. Maybe it's just semantics but it seems like "contact detected" and "YES" are closer in meaning to "close" than "open". Is there a way to reverse the status display in homebridge-openHAB?
Update 1:
I checked the behavior against other contacts I have in HomeKit/homebridge and they report "contact detected/YES" when window/contact is closed.
The text was updated successfully, but these errors were encountered: