ratgdo out of sync with door position (open vs. closed)

[NukeThemTillTheyGlow]

ratgdo 2.5i with 2.57 ESPHome. One of three, other ESPHome is fine, 3rd is MQTT (also fine).

I noticed late last night that HAOS is showing the garage door as open, when its physically closed. MYQ app shows it closed too. Too late to mess with it, so I go to bed. This am, check door. Its closed, been closed all night. HAOS/ESPHome shows door open. web ui for that device shows it open. Door is closed.

Not sure how they got out of sync. Other than getting ladder out and pulling power to it to reset, how can I reset? When I look at the HAOS/ESPHome UI, I have options for "toogle door", "restart", "sync" and more, but I can't find any documentation that describes what they do and/or what I should be doing in this situation. Same for the device web ui.

What should I do/try?

[PaulWieland]

Just to confirm you are using the ESP Home firmware with a security + 2.0 opener?

Sec+ 2.0 sends out the current door status every 5 minutes or so which would normally prevent the scenario you are describing. Can you please share the log from ESP Home?

[NukeThemTillTheyGlow]

Just to confirm you are using the ESP Home firmware with a security + 2.0 opener?

Sec+ 2.0 sends out the current door status every 5 minutes or so which would normally prevent the scenario you are describing. Can you please share the log from ESP Home?

Yes, Security 2.0. 8550W GDO. Thats what I thought was the case with the sync. Log attached.
logs_ratgdov25i-e5ec77_logs (1).txt

[PaulWieland]

Can you click the query status button and paste the log?

12:03:38	[D]	[button:010]	'Query status' Pressed.
12:03:38	[D]	[number:012]	'Rolling code counter': Sending state 230.000000
12:03:38	[D]	[ratgdo:210]	Status: door=OPEN light=OFF lock=UNLOCKED

[NukeThemTillTheyGlow]

[12:07:47][C][improv_serial:032]: Improv Serial:
[12:07:52][D][button:010]: 'Query status' Pressed.
[12:07:52][D][number:012]: 'Rolling code counter': Sending state 2994.000000
[12:07:56][D][esp8266.preferences:238]: Saving preferences to flash...
[12:07:56][W][component:214]: Component preferences took a long time for an operation (0.06 s).
[12:07:56][W][component:215]: Components should block for at most 20-30ms.
[12:08:26][D][button:010]: 'Query status' Pressed.
[12:08:26][D][number:012]: 'Rolling code counter': Sending state 2995.000000
[12:08:31][D][esp8266.preferences:238]: Saving preferences to flash...
[12:08:31][W][component:214]: Component preferences took a long time for an operation (0.06 s).
[12:08:31][W][component:215]: Components should block for at most 20-30ms.

[PaulWieland]

The GDO isn't responding. Does it respond to door/light commands?

[NukeThemTillTheyGlow]

The GDO isn't responding. Does it respond to door/light commands?

Light yes, works on and off. Only have down arrow and when I press that nothing happens. Proper status is displayed in MyQ app. So I opened the door via MyQ app, door opened. Door controls didn't change in HAOS, but when I pressed the down arrow the door closed, but arrow remained down and up greyed out. I recorded the log of all of this and attached.
logs_ratgdov25i-e5ec77_logs (3).txt

Is there a way to reboot the ratgdo? I don't want to just start clicking things I don't understand.

[NukeThemTillTheyGlow]

Couple of things:

1. I tried the "restart" button in the device web UI and that didn't seem to do anything. Door down, but button in HA shows only down arrow/up arrow is greyed out.
2. I glance at HA notifications and now I'm seeing this message " GDO_Denali sync failed
   Failed to communicate with garage opener on startup; Check the GDO_Denali Rolling code counter number entity history and set the entity to one number larger than the largest value in history. ESPHome devices"

FYI, the current rolling code value line from the web ui is:

Rolling code counter | 3138 codes | 0  268435500 -- | -- | --

Should I make that edit/change with the rolling counter number?

3. HA said there was a ESPHome update and I applied it. Now getting notice to update both of my ESPHome ratgdo devices from 2023.12.5 to .6.

Should I go ahead?

[mariusmuja]

@NukeThemTillTheyGlow

Should I make that edit/change with the rolling counter number?

From the symptoms you describe above, ratgdo is able to transmit to the garage opener, so the rolling code is ok. The problem is that it's unable to receive the opener responses, so it thinks it's in an incorrect state (door open, when in fact it is closed, etc). Because of this the up/down arrows are not going to work correctly. The toggle door button should continue to work correctly because it doesn't depend on the state of the door, it behaves the same a pushing the button on the wall.

I have noticed something similar for my opener since the weather got very cold, the signal from the opener got "worse", it would not bring the power/data line to (or close to) zero when sending a response, but only to 2-4V and the low threshold looks "noisy". This causes an issue that it doesn't reliably trigger the RX mosfet and the response cannot be read correctly. In my case, if leaving the light on the opener on for some time, the signal from the opener got better and ratgdo started being able to read responses again.

I don't if it's the same for you, it might be just my opener that has an issue, but the symptoms are the same: ratgdo is able to send commands, is able to received motion events from the wall panel, but is not able to receive responses form the opener. Did the temperature also got colder where you are since the issue began?

In my case, I got it to work more reliably by putting a voltage divider between the power/data line and ground at the gate of the RX mosfet.

[NukeThemTillTheyGlow]

@NukeThemTillTheyGlow

Should I make that edit/change with the rolling counter number?

From the symptoms you describe above, ratgdo is able to transmit to the garage opener, so the rolling code is ok. The problem is that it's unable to receive the opener responses, so it thinks it's in an incorrect state (door open, when in fact it is closed, etc). Because of this the up/down arrows are not going to work correctly. The toggle door button should continue to work correctly because it doesn't depend on the state of the door, it behaves the same a pushing the button on the wall.

I have noticed something similar for my opener since the weather got very cold, the signal from the opener got "worse", it would not bring the power/data line to (or close to) zero when sending a response, but only to 2-4V and the low threshold looks "noisy". This causes an issue that it doesn't reliably trigger the RX mosfet and the response cannot be read correctly. In my case, if leaving the light on the opener on for some time, the signal from the opener got better and ratgdo started being able to read responses again.

I don't if it's the same for you, it might be just my opener that has an issue, but the symptoms are the same: ratgdo is able to send commands, is able to received motion events from the wall panel, but is not able to receive responses form the opener. Did the temperature also got colder where you are since the issue began?

In my case, I got it to work more reliably by putting a voltage divider between the power/data line and ground at the gate of the RX mosfet.

Interesting. I meant to mention that it'd been very cold here the past for days. Was 7F this am here and my garage isn't heated, so I assume it was in the low teens inside. Sounds like it could be the GDO being cold too. hhmmmm, the other ESPHome ratgdo is on a different model Liftmaster GDO and is working fine as is the MQTT on the very old (20 yr) builder grade Chamberlain GDO.

[mariusmuja]

Yeah, might be the same issue then. If it starts working again once the weather warms up, that will confirm it.

[PaulWieland]

@mariusmuja which version of the control board did you notice this on?

@NukeThemTillTheyGlow which version of the control board are you having the issue with?

[mariusmuja]

@PaulWieland

The board I originally made myself, I never went up the ladder to swap it with a ratgdo board. When this happened I did swap it with a ratgdo v2.5i and the behaviour was the same.

[mariusmuja]

@PaulWieland My case is quite possible just an issue with my GDO, the signal from the GDO was looking quite "bad" on the oscilloscope (unfortunately I didn't save an image). I'm pulling 3.3v power from the GDO, today I'll open it up and remove that, it's possible that noise introduced by the esp board on the power rail causes issues or the esp is pulling more power than that rail can provide. I know of people reporting decreased remote range when taping into the 3.3v GDO power...

[PaulWieland]

Yes the wrong internal 3.3v supply can cause issues if there isn't enough overhead available. I found a rock solid source on my model, there are many logic boards out there. I've tested in extreme temperatures and have never seen an issue.

[NukeThemTillTheyGlow]

@mariusmuja which version of the control board did you notice this on?

@NukeThemTillTheyGlow which version of the control board are you having the issue with?

2.5i