I have a 2.5i using secplus1 (with 888LM). I've found that the obstruction sensor occasionally gets tripped while the door is in motion when wiring the ratgdo in the standard configuration (passing the obstruction sensor through the board). This causes the door to reverse when closing sometimes.
I'm not sure why this is happening, but to work around this, I've wired the obstruction sensor directly to the opener as before. I was happy to see the "obstruction from status" feature already implemented so there is no loss of functionality (in fact, I find this to be a more accurate configuration since I now can monitor the opener's view of the obstruction sensor).
I had to dig around in the source code but finally figured out how to enable this feature:
ratgdo:
input_obst_pin: none
It would be great to provide this in the documentation or troubleshooting guide as an alternative wiring and configuration for folks who have an unreliable connection (or would prefer to monitor the status in this way). Thanks!
I have a 2.5i using secplus1 (with 888LM). I've found that the obstruction sensor occasionally gets tripped while the door is in motion when wiring the ratgdo in the standard configuration (passing the obstruction sensor through the board). This causes the door to reverse when closing sometimes.
I'm not sure why this is happening, but to work around this, I've wired the obstruction sensor directly to the opener as before. I was happy to see the "obstruction from status" feature already implemented so there is no loss of functionality (in fact, I find this to be a more accurate configuration since I now can monitor the opener's view of the obstruction sensor).
I had to dig around in the source code but finally figured out how to enable this feature:
It would be great to provide this in the documentation or troubleshooting guide as an alternative wiring and configuration for folks who have an unreliable connection (or would prefer to monitor the status in this way). Thanks!