ratgdo out of sync with door position (open vs. closed) #174
Comments
|
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. |
|
Can you click the query status button and paste the log? |
|
|
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. Is there a way to reboot the ratgdo? I don't want to just start clicking things I don't understand. |
|
Couple of things:
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?
Should I go ahead? |
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. |
|
Yeah, might be the same issue then. If it starts working again once the weather warms up, that will confirm it. |
|
@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? |
|
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. |
|
@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... |
|
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. |
2.5i |
|
Checked temp with ir thermometer. 34.5 F |
|
I applied the ESPHome updates to both ratgdos and results are the same, one works, the other one doesn't. |
|
Since you have two of them, can you swap the control boards to see if the issue follows the ratgdo board or stays with the GDO? |
Not a bad idea. It's supposed to warm up a little over the next two days, then drop down again. Let me see if I can swap them today or tomorrow. If I understand the situation correctly, the garage door opener isn't updating the ratgdo with the right status info for the door and its state/location? |
|
I sincerely doubt this is a temperature related issue, but lets see... |
|
reset the break for the garage ceiling plugs in an effort to see if a power cycle of the GDO might help. Nothing changed. Then again, both ESPHome ratgdo's are connected to battery backed up openers, so that really didn't fully test out. The MQTT/non battery backed up ratgdo/opener combo works great. I'm going to go out and swap them shortly. |
It might be worth trying to disconnect the battery too to fully reset the GDO. |
|
After removing the 3.3V tap, the responses from the GDO look good now, so that was potentially the issue it in my case... I say just potentially, because I remember that when I tested with the 2.5i board a couple days ago I powered it from a USB charger, not from the 3.3v tap and the GDO responses still looked bad... There's a second confounding variable: before removing the 3.3V tap I was probing around on the GDO board (while on top of a ladder) and I manager to short the 12V bus to the 3.3V bus 😬 . The GDO stopped working and I was sure I completely fried the board. After a quick look with the a thermal camera, I noticed that the embedded wifi board was overheating (indicating a short inside it) and since I had nothing to loose I ripped off the wifi board and the GDO board started working again. So now with two less power drain sources on the 3.3V rail (the embedded wifi board and the esp), the GDO responses look nice and sharp, so there you go @NukeThemTillTheyGlow , you just need to rip out the embedded wifi board... Here's a pic of the carnage: |
Probably, for me it was correlated with the temperature drop, but correlation is not causation... Maybe it was borderline working fine for months and the temperature change just pushed it over the edge. |
|
Houston I have a problem! This was the first GDO I installed a ratgdo on of the 3 total I have and I struggled a bit with the wiring at first. I took the red/white wire from the wall control (I think its the 880LMW) and inserted it into the red/ctrl port on the upper left of the ratgdo and then 3 wires from the ratgdo blk/obst, wht/GND, red/ctrl to the GDO in positions blk, left most white, red respectively. Thats worked fine until this current issue. But on ratgdo's 2 and 3, I just ran red, white and black wires between the ratgdo & GDO to keep it simple. So I test power off/battery out, that doesn't change anything. So first think I notice when I climb up to swap ratgdo's is that I have the 4th wire (red/ctrl) in the top corner of the ratgdo and I decide to clean that up first to keep everything the same. Now I get error message on wall control display saying "press the push bar to activate control". I do that.. long pressed, short presses, etc and nothing happens. Now wall control doesn't sync up/work for GDO. I can use MyQ app and it works fine. ratgdo still doesn't work other than to close the garage door if its in the up position, up arrow doesn't illuminate at all if down. I have to make sure I get wall control back working or wife will kill me. Any suggestions?? |
|
The "press the push bar to activate control" happens because you removed power/battery from the GDO and the wall panel needs to "pair" with the GDO again. They exchange some messages when you press the button for the first time. The fact that the button doesn't pair actually fits with the symptoms ratgdo was showing, that it cannot read responses from the GDO. Before you power cycled the GDO the button was working because it didn't need to receive anything from the GDO, it was just sending the button/light presses, motion events. Now it needs to read the pair request to respond to it and it cannot do it. All this indicates that something is wrong with the GDO...
If none of that works, probably there's something wrong with the GDO board and you might need to replace the board (cheaper than replacing the GDO). I was joking before, but if you get there, you have nothing to loose by ripping out the embedded wifi card like I did, just in case it was the one causing the issue. |
Great minds think alike! So, here's what I've done do far:
Your comments make sense related to there being an issue with core functionality of the GDO, but the MyQ app will open and close the GDO. |
The issue is only with the GDO not sending messages on the wire correctly (would be interesting to put an oscilloscope on the wire to see what the signal looks like). The MyQ app talks to the GDO over wifi, not wireline messages involved (so yeah, that would stop working if you rip out the embedded wifi card... ). |
|
By the same logic, if you have a keypad, car remote, etc, those communicate with the GDO over radio and should be still working. |
|
Wife just left with her car which has the remote in it...I'll try to check that out later. But sure is sounding like the GDO has an issue vs. the ratgdo. |
Other people reported having issues with openers with battery backup, can you confirm when you get the new board and install it that it solved the issue? |
|
I sure will. Looks like Fedex is having issues so now board is delayed again, will not get until Monday. I'm leaving for a work trip Tue morning, so I will work on it Monday night |
|
New board arrived today (Finally!) and I just installed it. Good news, the wall control panel powered up and paired on the first try. But I'm trying to get the initial setup of the GDO completed and I'm getting error 4-2 on the display indicating excessive force to life the door. I am working to diagnose and fix it now. Other good news was that the ratgdo is alive and indicates the door being in a differnt position (closed) and will work the lights on and off, but can't open the door as the GDO is not letting it, just like it won't on the keypad until error 4-2 is cleared. So progress! |
|
You need to set the open-closed limits on the door: There's two up & down buttons and a black rectangular button in between them. Press the black button until the up button flashes. Now keep the up button pressed (the door will open) until the door gets to the desired open position. You can release/press to fine-tune the position. When at desired open position press the black button to set the open limit and now the down button will flash. Repeat the same for the closed position. Press the black button again to set the closed limit. Now the up button will flash again, a single press will open the door to test the up limit. Then the down button will flash and a single press will close the door to test the closed limit. |
Thank you! I just found the install manual and just read about how to do it, your directions are spot on. Going back to the garage now to fix. Then when wife gets home, reprogram remote and then finally reset up MyQ...as I have not deployed the HAOS app and appropriate dashboard/controls for her and my kids yet. This GDO acted as both a MyQ GDO as well as hub for the 3rd/old GDO via upgraded keypad/wall control. I need to go back and find out/remember how to set that all up again. |
|
Setup complete! Ratgdo fully functional again! |
|
Good news and it's good to have confirmation that a GDO board replacement fixes the issue. To double check, the board replacement was model/version 050DCTBFMC? |
|
Now getting 4-3 excessive closing force errors. Will reprogram. Myq setup worked fine, but not able to get oldest gdo to be detected during myq process. That mqtt ratgdo works fine |
I did another reset/setup on the travel and got it right this time. handheld and myq openers setup and working. Need to get the exterior keypad over the weekend done. and also get the 3rd gdo to join the myq config. But GDO Brain Transplant complete! |
Yes, its a 050DCTBFMC, that is copied/pasted right from the liftmaster order. |
|
Not sure if anyone is still following this, but I also just completed a GDO brain transplant with the 050DCTBFMC board. It was pretty straight forward and my RATGDO is now functioning as expected. It's been warmer than usual so the true test will be when the temps really dip again. I didn't hook this board to MyQ, I had the other ones blocked from internet access anyway and I've had the wife using HomeAssistant. Now to get all my automatons dialed in. Thank you @NukeThemTillTheyGlow for being the first brain surgeon. |
@hellboyfishman You're very welcome. I'm in a similar situation as you...it got warmer and I'm curious to see what happens when/if we get back down to single digits. Its also odd how the Lifetmaster 3 button remotes (8xxMax) are so flaky with working with that door now Program one via wall control panel, it works fine to open/close, but then get in wifes car just outside the door and its hit or miss. changed battery in it, etc. I want to cut wife and kids over to super simple HA app for their iPhones, but need to solve for the requirement of getting them on the home network when outside of the house. Other update is I found out that the 3rd opener I have, very old/20 years/original to house when we build it, was supported with ESPHome/Security 1.0 support. So yesterday took down the ratgdo, reflashed it to ESPHome/Sec 1.0 and it works great. Now to address the remote issue, the random light coming on the newest liftmast GDO..I think its the wall panelm its the original one from the opener that I replaced the board in.....but I moved it over to the other opener to see if it was the board or the wall control.. I think someting it wrong. |
Did you by chance add or change to LED bulbs when you started having remote issues? When I switched over to LED bulbs, my first brand of LEDs would kill or interfere with all my remotes, including factory installed remotes in our vehicles. |
We will be back down in the 20s and 30s overnight in the next week or so, I plan on testing the light immediately when I wake up in the morning to see how that is functioning. I will say that the thing I had the most issues with on the old board, outside of light updates, was "opening" status. Even as it warmed up into the 20s and 30s the RATGDO would most often only report opened, closing, and closed status. Since the swap I always get an opening status which is great because that's how I prefer my alerting automatons to trigger. I have reprogrammed 2x 3 button remotes for vehicles and 1 keypad and so far so good, I'm crossing my fingers on that one now. Also, I know this was another $100 to chamberlain but in the long run, I feel like it was worth it for the 10 min process to swap it and get off their cloud crap. |
Another possibility is interference from a 5V wall wart bring used to power the RATGDO. When I installed my RATGDO, remote openers became very unreliable. If I unplugged the wall wart, all worked OK. I wasn’t surprised since wall warts are notorious RFI generators. I moved the RATGDO and wall wart to a sidewall of the garage and ran a longer cable from it to the GDO. Remotes started to work properly again. The new arrangement had the added advantage of allowing access to the RATGDO without needing to use a ladder. |
|
I have a very similar issue to this, but when hitting the query openings or status buttons, they will not return a response when my garage is below 50 degrees Fahrenheit. During this time, if I open or close my garage door while using the wall button or a remote control, the Apple Home and Home Assistant app will be out of sync. Things stay in sync if I use the Apple Home or HA app exclusively. While the apps are out of sync, I can still use them. If the garage door is open but the apps report it's closed, I can select the button to open it, and it will go through the motions as if it were opening the door. Then, if I hit the close button, the garage door will indeed close, and things will be in sync again. These past few weeks have had many cold nights, dropping the temps in the garage below 50. When the out-of-sync issue happens, and I leave it that way on purpose, during the day when the garage warms to over 50 degrees, all the sudden, I'll get a notification that my garage door has either opened or closed (depending on the state it was in) and the apps will all the sudden become in sync again with the actual state of the door. I never lose communication with the ratgdo as I've been monitoring it consistently since I've noticed the out-of-sync issue. When the temps are above 50 in the garage, I never have a sync issue, and I can hit the query openings/status buttons with 0% failure. Is this also indicative of the GDO board itself as the issue and needs to be replaced? |
This sure sounds like the issue some of us have been facing. If you want to delay buying the $100 mainboard, there's one more step you can try in order to confirm that is the issue, when it is out of sync, turn on the light on the GDO using the wall button, leave the light on for a while (10-30 min) and see if the status updates automatically. I believe that leaving the light on warms the board enough to update it properly. |
|
never thought of that, can try tonight. |
|
@arrisfe, can you also test @jschafermo's hypothesis above. Are you using LED light bulbs on the GDO, and if so what happens if you unscrew the light bulbs?
|
|
Hey @mariusmuja, yes, I do have an LED bulb on the board side of the GDO, but the other side with the battery still has a normal bulb in it. I've had this LED bulb in for a long while now and have not noticed any issues with my remotes. I installed my Ratgdo device at the end of January (LED has been in for a much longer time). I did see the post about the LED bulb and did remove it from the system temporarily, but that did not resolve the issues I was having when it was below 50 degrees. Thanks for bringing this up, actually, as now I will switch the bulbs as the LED doesn't generate much heat at all, so I'll need the regular bulb closer to the GDO board for the test tonight. |
|
@hellboyfishman, sure enough, this worked. This morning, the garage was in the low 40s, and pressing the query openings/status buttons were unresponsive. I turned on the light via the wall button and left it on for 10 minutes. The query openings/status buttons were returning responses again. At this point, I need to decide whether to swap out the GDO board. I'm not left with a good feeling that I can completely trust the door's status at this point w/ratgdo, though, so I may have to stick with the MyQ app (unfortunately), as it's always 100% accurate. |
To be honest, the swap was not that hard. If you are at all technically inclined it shouldn't take very long at all. My only guess is that the MyQ cloud doesn't rely on the line events that the RATGDO does, that's probably the only reason we all haven't required warranty replacement of our boards. |
Yea, I don't have an issue with performing the swap out. The issue for me comes down to relying on the actual state of the door for security and home automation reasons. If i have to second guess the apps only to fall back to the MyQ app for assurance, then why bother. I can replace the GDO board now, but who's to say how long before the issue starts to happen again, or worse yet, in a different form? |
True, I've only had mine in for a handful of weeks at this point, but it has been rock sold down to 20 degrees in my garage. For me the 100 was money well spent. I do also have a camera in my garage so I can always visually double check status, but it has been a non issue for me since replacing the board. If a year from now it goes to crap, I can hope there's another option on the market for GDO that has a local API I can switch to. |
|
Just received my RATGDO and installed it. Couple of issues:
I have tried restarting the RATGDO few times without much luck. Ran the query opening command and this is output: Time level Tag Message Can someone help me? |
|
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?
The text was updated successfully, but these errors were encountered: