RATGDO - GDO, GDC Sensor Behaviour

I recently installed a RATGDO device on a Liftmaster garage door opener. Installation was straight forward and easily achieved. Once installed, I modified one of my NodeRed flows to utilize the “binary_sensor.garage_overhead_door” expecting the sensor to report on when the door was open or closed. Unfortunately the flow failed to work properly as the “binary_sensor.garage_overhead_door” sensor doesn’t report a steady state. It flips between “door was opened” and “door was closed” at approximately 2 second intervals.

Here’s a copy of my log during the time the garage door was opened then closed;

Garage - Overhead Door was closed
9:51:39 AM - 3 hours ago
Garage - Overhead Door was opened
9:51:32 AM - 3 hours ago
Garage - Overhead Door was closed
9:51:32 AM - 3 hours ago
Garage - Overhead Door was opened
9:51:32 AM - 3 hours ago
Garage - Overhead Door was closed
9:51:32 AM - 3 hours ago
Garage - Overhead Door was opened
9:51:31 AM - 3 hours ago
Garage - Overhead Door was closed
9:51:31 AM - 3 hours ago
Garage Door Motor turned off
9:51:28 AM - 3 hours ago
Garage Door Door was opened
9:51:28 AM - 3 hours ago
Garage - Overhead Door was opened
9:51:25 AM - 3 hours ago
Garage - Overhead Door was closed
9:51:25 AM - 3 hours ago
Garage - Overhead Door was opened
9:51:23 AM - 3 hours ago
Garage - Overhead Door was closed
9:51:23 AM - 3 hours ago
Garage - Overhead Door was opened
9:51:22 AM - 3 hours ago
Garage - Overhead Door was closed
9:51:22 AM - 3 hours ago
Garage - Overhead Door was opened
9:51:19 AM - 3 hours ago
Garage - Overhead Door was closed
9:51:19 AM - 3 hours ago
Garage - Overhead Door was opened
9:51:18 AM - 3 hours ago
Garage - Overhead Door was closed
9:51:18 AM - 3 hours ago
Garage - Overhead Door was opened
9:51:17 AM - 3 hours ago
Garage - Overhead Door was closed
9:51:17 AM - 3 hours ago
Garage Door Motor turned on
9:51:16 AM - 3 hours ago
Garage Door Door is opening
9:51:15 AM - 3 hours ago
Garage Door Light turned on
9:51:15 AM - 3 hours ago
Garage - Overhead Door was opened
9:51:15 AM - 3 hours ago
Garage Door Button turned off
9:51:14 AM - 3 hours ago
Garage Door Button turned on
9:51:14 AM - 3 hours ago

EDIT: Has anyone else experienced a similar issue. if so, how did you correct it?

Bump I’m still having this issue. Is anyone else having this issue?

Have you tried using the state of the cover.* entity? This appears to be providing reliable status for my automations (albeit outside of NodeRed).

On my RATGDO v2.5i, I do not see any binary sensor entity that would appear to indicate the status of the garage door. There are numerous binary sensors created that appear to serve other purposes.

Yes, that’s what I used to get the lights/garage door working the way I wanted. What I’m concerned about now are repeated messages being logged in HA’s log file when the door is open for a prolonged period of time. Timing between messages is about two seconds. If I open the garage door for an hour or so while I’m cleaning the car, there could be as many as 3600 messages logged.

I am not seeing this sort of activity in my HA, ESPHome, or RATGDO logs.

Did this only start when you created the Flow in NodeRed?

The NodeRed flow I’m using existed prior to installing RATGDO on the garage door. The flow was triggered via the MyQ integration. After installing RATGDO the MyQ integration was removed and the NodeRed trigger was replaced with a trigger from RATGDO. Should I try disabling the NodeRed flow to see if the excessive stops?

NOTE: I thought the issue may have been related to limit settings on the GDO. I reset the limit positions but the messages continue to flow.

I would be surprised if a NR flow could cause this, but it may be worth a shot. Other options may be to try classic debug strategies like restarting HA, disabling the RATGDO integration, and perhaps even reinstalling the RATGDO firmware and integration. Ordinarily, at this point, posting to the Github page about the problem would be advisable, but it does not seem that it has an Issues section; as great as RATGDO is at what it does, the lack of support may be a challenge.

Also, are you using the MQTT or ESPHome firmware?

Your looking at the old repo.

See:

1 Like

I’m using ESPHome firmware.

I thought of re-flashing the RATGDO so I guess that will be my next step. I won’t be able to do so until after this weekend. I’ll post results once completed.

Thanks for you thoughts.

Thank you for the link. I’ll have a look through the issues to see if there’s anything close to what I’m seeing.

Noticing that repository is MQTT-specific. Here is one for ESPHome:

Thanks. I found that as well. I’ve posted an issue there.