Obstruction sensor issues

[robotron-smith]

Behavior

With the ratgdo wired in, all functions work in homekit (and with hardware controls), EXCEPT the 'door close' function

When attempting to close the door, it starts down the track for about 1/2 second, then flashes the light and stops as when there is an obstruction

Note that this happens when trying to close the door by any means

• Firmware web page
• Homekit
• wall button
• arrow button on opener itself
• opener remote

In addition to the light flashing, the up and down arrows on the unit flash as well, which indicate a short or missing motion sensor

Troubleshooting so far:

• Disconnected ratgo and re-wired as original, in case something had actually misaligned the detectors, or if there was a coincidental break/failure : GDO functioned as expected -- opened and closed without issue

• Assuming it was a wiring issue, I trimmed all of the wires to reduce the chance of a short or cross-wire induction.

The reason I think this is a firmware issue and not anything else:

• I re-flashed the ratgdo with the latest firmware for HomeAssistant, reconnected the unit, and the issue did NOT occur : all functions operated as expected

• I flashed AGAIN with the latest Homekit firmware, rewired the unit, and the issue re-appeared.

To be clear on that point: I thought it might be a voltage issue or the like, but the issue disappeared when switching to the Home Assistant firmware, and re-appeared when switching back to the Homekit firmware

I am happy to provide pics, or logs , or anything else that might help!

ratgdo info:
hardware : 2.52
firmware : homekit v0.11.0

GDO info:
Liftmaster 1D7675 w/Yellow learn button

[jgstroud]

Does HomeKit report the door is obstructed? This is strange because the obstruction sensor logic was copied almost exactly from the mqtt firmware. Your reasoning does seem to point to something in the firmware though.

[jgstroud]

I wonder if this is possibly related to #119.

[jgstroud]

@robotron-smith This is odd. The code in the HA firmware and HK firmware are nearly identical as we just copied their implementation. It's a long shot, but we fixed a bunch of memory issues. I wonder if you could try again with the HK firmware and report back if you still have the same issues. I'll review and see if anything new was added in the HA firmware and see if we are missing a patch.

[walking]

have the same issue with version 1.6.0. Everything works well with version 1.4.3, but when I upgrade to 1.5.0, I start to encounter problems. For example, in HomeKit, it keeps showing "closing" even when the door is already closed. So, I upgraded to 1.6.0. This issue is fixed in 1.6.0, but now, almost every time I open the door, it reports an obstruction and opens the door again. I downgraded it to 1.4.3 and it's solved

If I disconnect the ratgdo, the door works fine, even with the wires connected, so there is no contact issue between them.

[jgstroud]

"almost every time I open the door, it reports an obstruction and opens the door again."

I don't understand this comment. Do you mean when you close the door? Can you attach logs?

[jgstroud]

Did you have the obstruction problem in 1.5.0? The obstruction code was tweaked in 1.6 to filter out spurious detections. Really need logs to understand what is going on. You can viewlogs.sh script or monitor the logs in the javascript console.

[walking]

"almost every time I open the door, it reports an obstruction and opens the door again."

I don't understand this comment. Do you mean when you close the door? Can you attach logs?

You are right, my bad. When I close the door. It even closes completely, but it opens again because of obstruction... but there is nothing.

I reinstalled 1.5.0 and it looks good right now. Having some issues with the homekit status (it shows as "closing" when the door is already closed and I need to touch on it to update the status) but no problem with the obstruction report.

I would need to reinstall 1.6.0 to check the logs... and I'm not very confident... my garage door stayed open for some time while I was away from home because I didn't realize it detected a false obstruction...

[jgstroud]

1.6.0 fixed a problem with the wrong status being reported in HomeKit. But I'm really curious about this obstruction regression and would like to try and fix it. If you could load 1.6.0 and capture the logs, that would be fantastic. Then you could revert back to the build that works for you until I can release a fix.

[dkerr64]

@robotron-smith and @walking please test with v1.7 (tagged as pre-release so you need to check that box on the firmware update dialog).

[rcabell]

I'm also seeing this exact same behavior with v1.7.0 and a Sec+ 1.0 opener. Light control, sensors, locking, and opening door work fine. If I try to close the door by any means (Home app, device web app, physical controllers) the door moves for less than a second and then the light blinks as if there's an obstruction (web interface / HK do not show an obstruction). Only way to close the door is to hold down the button on the 889LM until the door completely closes.

Changing over to the ESPHome firmware and using Home Assistant to re-export the device to HomeKit works just fine.