-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
device regularly becomes unresponsive for several minutes #246
Comments
How often does this happen? Can you plug in and capture the serial logs? Also, have you disabled the Home Assistant "api:" on your firmware, since you aren't using Home Assistant? The device will automatically reboot if it cannot connect to Home Assistant after 15 minutes by default. https://esphome.io/components/api.html To disable the api, you will need to compile your own firmware with ESPHome. You'll need to install ESPHome itself somewhere and then create a device .yaml for the ratgdo and compile and flash that new firmware. Here's what the device .yaml could look like:
|
I did not edit any yaml files or build my own firmware, I just flashed it from https://ratgdo.github.io/esphome-ratgdo/ (choosing "security + 2.0" and "ratdgo v2.5x"). I do see messages about it rebooting in the log on the web UI, however the nonresponsive periods are much more frequent than that, e.g. just in the last half hour it was unresponsive from 8:29-8:31, 8:33-8:40, 8:43-8:44, 8:46-8:48, 8:50-8:51 and 8:54-8:55. I'll see about getting serial logs. Might have to go buy a really long USB cable first. |
This is probably because the ESP Home firmware is rebooting because it's not connected to HA. |
But doesn't that reboot only happen every 15 minutes? The nonresponsive periods happen way more frequently than that, and their duration varies a lot too. |
I attached the ratgdo to a Raspberry Pi so I could capture serial logs while the ratgdo was attached to the opener. Some things that stood out to me:
which correspond to times that the ratgdo becomes unresponsive to pings. |
I have this issue too... Curious if you've found any resolution. For now I've dialed my |
Haven't found a solution/workaround. Since it happens so frequently, starting shortly after boot, rebooting often wouldn't really help me much either, since then I'd just be waiting for it to finish its reboot and reconnect to the network. |
On a whim I tried updating the firmware again (from 2024.4.2 to 2024.5.0) and it is so much worse now. The web interface isn't even usable anymore: every time I reload the page it takes over a minute to load just a partial mostly-empty page, another minute or more for the actual information to load, and the ratgdo is unresponsive to pings for most of this time. |
this sounds similar to an issue I'm seeing with a couple devices running the homekit firmware. curious if you disconnect the device from the GDO if it becomes responsive again. in those cases just disconnecting from the gdo made it suddenly become fully responsive again. |
Yeah i've been having this issue too. It constantly disconnects where as it used to be really stable. Its not rebooting. In the logs I see a disconnect and then reconnects in a short time. |
I also been troubleshooting this issue - glad to find this thread as I’ve been pulling my hair out. Anyone make any progress resolving? |
I just set up a ratgdo today and was seeing the json error message followed by a reboot. It was crashing so often it warned it was going into safe mode. I was testing it with combinations of remotes and Home Assistant commands and it would crash after almost every open/close cycle.
Removing |
I'm using the ratgdo 2.53i standalone, not integrated with any home automation setup. I flashed it with the ESPHome firmware and have a script that polls the REST API every few seconds to get the current state and automatically close the door when it's been accidentally left open.
What I'm noticing is that the ratgdo frequently stops responding, sometimes only briefly, sometimes for minutes at a time.
ping
ing the device shows the same behavior: it'll regularly stop responding to pings for up to a few minutes, then resumes, and these interruptions coincide with the REST API becoming nonresponsive.I can ping the GDO itself as well as other devices on the same Wifi access point (I have a dedicated AP in the garage) without issue.
(as I was typing the above, it stopped responding again and stayed unresponsive for 6 minutes)
The text was updated successfully, but these errors were encountered: