ratgdo / esphome-ratgdo

ratgdo for ESPHome
GNU General Public License v2.0
308 stars 75 forks source link

Commands suddenly stop working #233

Open Daniel-dev22 opened 2 months ago

Daniel-dev22 commented 2 months ago

I have a lift master with 2.0 security and it seems that I need to restart the garage door opener for ratgdo to control it after awhile. I installed ratgdo and it was working fine but then it stopped, I can see it knows if the light is on and I can turn it on/off but no motion detections are coming through or can the door be controlled. If unplug and replug the garage door opener itself suddenly it works.

Rebooting the ratgdo doesn't help either.

The only thing of note in the logs I just saw was

[17:11:17][W][ratgdo_secplus2:309]: Discard incomplete packet, length: 10

Daniel-dev22 commented 2 months ago

I did a power cycle of the gdo during this log.

I also noticed that ratgdo restarted a few times in the logs as if it panicked as I was trying to turn the light on or query status and it's failing. As soon as I unplugged the gdo the logs lit up with activity.

logs_ratgdov25i-4b0938_logs (2).txt

Now it appears it's unreachable but it's still on the network. It's as if it's in safe mode after a boot loop?

Daniel-dev22 commented 2 months ago

So now it's connected but I can't open or close the garage door, or query openings. But it reports when the door is 100% open and 0% open when I open it manually.

cgbale commented 2 months ago

I'm experiencing these symptoms as well. I get random notifications that the door is open when it's not, and I'm unable to control the door.

Here's what I found in the log when this problem occurs: 20:57:47 | [D] | [ratgdo:095] | Door state=CLOSED 20:57:48 | [D] | [ratgdo:204] | Light state=OFF 20:57:48 | [D] | [ratgdo:210] | Lock state=UNLOCKED 20:57:48 | [D] | [ratgdo:095] | Door state=CLOSED 20:57:49 | [D] | [ratgdo:204] | Light state=OFF 20:57:49 | [D] | [ratgdo:210] | Lock state=UNLOCKED 20:57:49 | [D] | [ratgdo:095] | Door state=CLOSED 20:57:49 | [D] | [ratgdo:204] | Light state=OFF 20:57:49 | [D] | [ratgdo:210] | Lock state=UNLOCKED 20:57:50 | [D] | [ratgdo:095] | Door state=CLOSED 20:57:50 | [D] | [ratgdo:204] | Light state=OFF 20:57:50 | [D] | [ratgdo:210] | Lock state=UNLOCKED 20:57:51 | [D] | [ratgdo:095] | Door state=CLOSED 20:57:51 | [D] | [ratgdo:204] | Light state=OFF 20:57:51 | [D] | [ratgdo:210] | Lock state=UNLOCKED 20:57:51 | [W] | [api.connection:104] | : Connection closed 20:57:51 | [D] | [api:102] | Accepted 192.168.10.30 20:57:51 | [D] | [ratgdo:095] | Door state=CLOSED 20:57:52 | [D] | [ratgdo:204] | Light state=OFF 20:57:52 | [D] | [ratgdo:210] | Lock state=UNLOCKED 20:57:53 | [E] | [json:041] | Could not allocate memory for JSON document! Requested 440 bytes, largest free heap block: 440 bytes 20:57:53 | [D] | [ratgdo:095] | Door state=CLOSED 20:57:53 | [D] | [ratgdo:204] | Light state=OFF 20:57:53 | [D] | [ratgdo:210] | Lock state=UNLOCKED 20:57:53 | [D] | [ratgdo:095] | Door state=CLOSED 20:57:53 | [D] | [ratgdo:204] | Light state=OFF 20:57:53 | [D] | [ratgdo:210] | Lock state=UNLOCKED 20:57:54 | [D] | [ratgdo:095] | Door state=CLOSED 20:57:54 | [D] | [ratgdo:204] | Light state=OFF 20:57:54 | [D] | [ratgdo:210] | Lock state=UNLOCKED 20:59:16 | [D] | [button:010] | 'Sync' Pressed. 20:59:19 | [W] | [ratgdo_secplus1:059] | Triggering sync failed actions. 20:59:33 | [W] | [ratgdo_secplus1:059] | Triggering sync failed actions. 20:59:40 | [W] | [ratgdo_secplus1:059] | Triggering sync failed actions.

slappula commented 2 months ago

I have a double garage with two RATGDOs. Garage Openers are Security 1.0+. I had them installed for about six weeks with no issues. Then, I updated both of them with ESPHome. One worked fine, the other started acting very weird. It quit sending notifications and would only open or close from Firmware page or Home Assistant sporadically. I ended up pulling it down and doing a clean install (connecting directly to my computer). After that, it has worked fine for several days (and after another ESPHome firmware update). This doesn't get to the root of the problem, but it solved my issues.