-
Notifications
You must be signed in to change notification settings - Fork 115
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
Obstruction Status Always "On" in HomeKit #280
Comments
And what is the obstruction status showing in ESP Home? |
Also, how are you connecting the ESPHome firmware to HomeKit? (There are a few different ways to do it.) |
And I have thrice verified the wiring is correct and nothing is shorted out (unless its shorted somewhere along the lengthy sensor wire). Multi metered all the connections to be sure. |
I've been messing around with various wiring setups and still no luck. Any ideas on the software side of things? |
From my testing, in my set up this only happens when I introduce HomeKit (either homekit firmware, or with ESP and a homekit bridge). a) ratgdo-homekit firmware, obstruction detected and I cannot close the door. b) ratgdo-esphome firmware, this works better with no obstructions until I connect HASS to homebridge. When I delete homebridge and reboot the system the obstruction is gone. So for whatever reason as soon as Homekit is introduced (even with the same wiring) it flags an obstruction. |
Description
I am experiencing an issue where the "Obstruction" status is always "On" in HomeKit, causing it to report an issue even when there is nothing blocking the door. Despite this, the door operates normally with remotes, wall button, HomeKit, or the ratgdo web UI. When the sensor is actually obstructed, it functions correctly in all modes (won’t close).
Environment
Steps to Reproduce
Observations
Additional Information
Please let me know if any further information or diagnostic steps are needed.
Thank you!
The text was updated successfully, but these errors were encountered: