Light, motion and lock remotes status not updating.

[jschafermo]

I received two Ratgdo boards and installed them on my two Chamberlain openers a couple days ago. All hardware and wiring are identical on both openers. One Ratgdo works perfectly with instant status updates, the other one does not. My problem Ratgdo will update the light status after approximately five minutes which I believe the opener sends updates at this interval. I can toggle the light from the web interface or Esphome and the light will toggle instantly with a status update. If I toggle the light from the wall controller, the light will toggle, but the status will not change for a few minutes. The light status updates instantly when the door is opened or closed. No status update happens with motion detection and lock remotes while using the wall controller. It appears anything triggered by the wall controller is not being captured by the Ratgdo board. Looking at the logs, events are logged for everything except when triggered by the wall controller. I log the following every now and then:

10:11:42 | [W] | [component:214] | Component preferences took a long time for an operation (0.06 s).
10:11:42 | [W] | [component:215] | Components should block for at most 20-30ms.

As a quick test, I swapped Ratgdo boards on the openers. The problem transferred with the board swap. Currently, both Ratgdo boards are wired using red, white and black connections and powered by USB. Not using passthrough or dry contacts.

Tested obstruction detection, status will update instantly on both boards. While testing the obstruction sensor, I discovered if an obstruction was detected, the light status would update when using the wall controller. The status update takes a couple seconds, not instantly as the working Ratgdo.

With more testing, door position is not being reported as the door is opened and closed. On the working Ratgdo, the door position is published roughly every 4%.

I re-flashed the Ratgdo board with the problem, but this didn't resolve my issue.

Not knowing how light, motion and lock status change works, not sure what to try next.

Any suggestion would be appreciated.

Thanks

[mulcmu]

The component blocking warning isn't an issue. What happens if you leave the ratgdo hardware installed but just swap the ESP board between setups?

[jschafermo]

The component blocking warning isn't an issue. What happens if you leave the ratgdo hardware installed but just swap the ESP board between setups?

My version of Ratgdo have ESP boards which can't be removed. I can only swap the entire Ratgdo and ESP.

Thanks

[mulcmu]

I didn't realize rev 2.5 had ESP integrated, that would make it a bit difficult to swap. Based on the logs from here it looks to me like the garage door is pulling the red line to ground low enough to trigger a logic low on the board with the issue, however the wall control transmissions are not pulling the red line down low enough.

I'd visually inspect the board to see if there is any crust or poor solder joints that might be the culprit. It seems to me you've isolated the problem down to a hardware problem on the ratgdo board.

[jschafermo]

I didn't realize rev 2.5 had ESP integrated, that would make it a bit difficult to swap. Based on the logs from here it looks to me like the garage door is pulling the red line to ground low enough to trigger a logic low on the board with the issue, however the wall control transmissions are not pulling the red line down low enough.

I'd visually inspect the board to see if there is any crust or poor solder joints that might be the culprit. It seems to me you've isolated the problem down to a hardware problem on the ratgdo board.

I will check the ratgdo closer to see if I spot any problems. From everything I've been able to do, I believe I have a defective ratdgo board. I wanted to check to see if there was anything else I could try. My other ratgdo board works great on both openers.

I appreciate your help!

Thanks

[mariusmuja]

Yeah, sounds like the data line is not pulled low enough to reliably triggering the mosfet on the board that's not working.

A mosfet threshold voltage decreases a bit with the rise in temperature, so one thing you could try is to get the temperature of the board that's not working slightly higher (maybe place it near the garage light bulb and use an incandescent bulb). If it starts working fine it would confirm this hypothesis.

[jschafermo]

Yeah, sounds like the data line is not pulled low enough to reliably triggering the mosfet on the board that's not working.

A mosfet threshold voltage decreases a bit with the rise in temperature, so one thing you could try is to get the temperature of the board that's not working slightly higher (maybe place it near the garage light bulb and use an incandescent bulb). If it starts working fine it would confirm this hypothesis.

I will try warming the board to see if it makes a difference.

Thanks!

[jschafermo]

So far, warming of the board hasn't helped. I will try a few more times to see if the Ratgdo starts responding correctly.

Thanks again for your help!

[MrSt1k]

I too have what started as one device with the exact same behavior. One of three devices (also a version 2.5) installed on three identical garage doors would not report door opening or closing position. Tripping the obstruction sensor would trigger the reporting of the door to the correct open/closed position. The other two work perfectly.

After reflashing the device and checking the wiring multiple times, I concluded it must be a problem with the Ratgdo board and ordered another. Installing the second device (version 2.5i) yielded the same results. I have run out of ideas and will be watching this discussion hoping that a solution is foud.

[jschafermo]

I too have what started as one device with the exact same behavior. One of three devices (also a version 2.5) installed on three identical garage doors would not report door opening or closing position. Tripping the obstruction sensor would trigger the reporting of the door to the correct open/closed position. The other two work perfectly.

After reflashing the device and checking the wiring multiple times, I concluded it must be a problem with the Ratgdo board and ordered another. Installing the second device (version 2.5i) yielded the same results. I have run out of ideas and will be watching this discussion hoping that a solution is foud.

Have you swapped a working Ratgdo board to the non-working opener? When I swap Ratgdo boards between my two openers, the problem follows the problem Ratgdo board.

I will try a new Ratgdo board soon.

[MrSt1k]

I have tried a new, unused board and, while it was not a known good board, the problem seemed to stay with the opener. I will try to swap it with a good board/opener tomorrow and report back… On Thursday, January 4, 2024, 8:41 PM, jschafermo ***@***.***> wrote: I too have what started as one device with the exact same behavior. One of three devices (also a version 2.5) installed on three identical garage doors would not report door opening or closing position. Tripping the obstruction sensor would trigger the reporting of the door to the correct open/closed position. The other two work perfectly. After reflashing the device and checking the wiring multiple times, I concluded it must be a problem with the Ratgdo board and ordered another. Installing the second device (version 2.5i) yielded the same results. I have run out of ideas and will be watching this discussion hoping that a solution is foud. Have you swapped a working Ratgdo board to the non-working opener? When I swap Ratgdo boards between my two openers, the problem follows the problem Ratgdo board. I will try a new Ratgdo board soon. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[MrSt1k]

After swapping the boards on a working opener with a non-working opener, I can confirm the problem with mine is with the opener.

It is a mystery what the problem is though. It worked briefly after changing out CFL bulbs and I thought maybe they were causing interference, but the problem returned. I swapped out the wall controls without any luck. I connected the wall control with new wires without any luck.

It has mysteriously started working again, so I'm not messing with it anymore. The only other possibilities seem to be the safety sensors or their wires, or the board in the opener itself.

[jschafermo]

An update to my problem. I received my replacement Ratgdo board and installed it on the problem opener. Happy to report my problem is resolved and the sensors on both doors update immediately and working correctly.

Thanks for the help!

[ue-cthompson]

I am also having this issue. I have the latest board, 2.53. I guess the only way to find the issue is to buy another board?

[hellboyfishman]

Somehow my other account was marked as spam, so I'm reposting this, hopefully you can all see it:

I am also having this issue. I have the latest board, 2.53. I guess the only way to find the issue is to buy another board?

I can say, from my experience, don't buy another board. I just spent time installing a replacement (this one is a 2.53i vs the 2.5i I had) and it is the same result. I'm starting to suspect an issue with the GDO itself not reporting. Light and door status aren't updating, but motion and obstruction are reporting. I can toggle the door but the status just won't update, I'm not getting the 5 min poll events either.

I guess at least this one always says the door is closed vs the 2.5i that said it had been open for the past week.

Also I get this message every time I reboot the device:

Failed to communicate with garage opener on startup; Check the ratgdo main Rolling code counter number entity history and set the entity to one number larger than the largest value in history. ESPHome devices

Quick edit, after cycling the door it now thinks it is open again. I give up, unless anyone else has ideas on where to go from here. At this point I'm wondering if the battery backup in the GDO is causing any issues. I'm tempted to just disconnect it for a while to see.

[mariusmuja]

There have been several people reporting issues on GDOs with battery backup (DC motor). I suspect the first models of the logic boards in these GDOs have an issue where when transmitting it doesn't fully bring the data line to ground and ratgdo cannot receive the messages transmitted. There's also a case where the wall button was not receiving messages from the GDO (was not pairing after a GDO restart).