ratgdo / esphome-ratgdo

ratgdo for ESPHome
GNU General Public License v2.0
357 stars 108 forks source link

Obstruction While Closing Door Not Reported #276

Open LRomandine opened 6 months ago

LRomandine commented 6 months ago

Hardware: Liftmaster 8500W RATGDO 2.53i Not using dry contacts, just using the 3 wire install Home Assistant 2024.4.3

Issue: When the door is open, the sensors are blocked, and a door remote button (not through RATGDO) is pressed Liftmaster beeps and the light flashes a 10 times noting an error. The MyQ Android app reports the error. But the RATGDO does not output any way (that I can tell) to view the error or that the door remote button was pressed. Looking in the Home Assistant logbook it only shows that the obstruction was there and then cleared. The 'rolling code counter' does not increment and the 'openings' counter does not increment.

Screenshots of where I would expect logs ratgdo-no-error ratgdo-error-web

Expected Results: I would expect the logs or a sensor to show that the remote button was pressed but the sensors were blocked. I would like to create a Home Assistant alert similar to the one MyQ has for when this event occurs.

Other Notes: I can use Home Assistant to detect and alert when the door is closing, sensor is blocked, and door opens back up. But there is no way (currently) to detect the door could not start moving because the sensor was blocked due to this issue.

mulcmu commented 6 months ago

I have a forked version on my ratgdo with timer to close (TTC) work in progress. When I tried the close door with obstruction sensor blocked the gdo sends a 0x0a1 command.

[20:51:30][V][ratgdo:116]: cmd=0a1 (EXT_STATUS) byte2=00 byte1=0e nibble=1
[20:51:30][W][ratgdo:301]: TTC closing was interrupted!

So it looks like the gdo might provide this status but still need some work to decode the bits.