Skip to content
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

Slow or No Response from Web Interface #266

Open
jmrobinsgithub opened this issue Feb 16, 2025 · 3 comments
Open

Slow or No Response from Web Interface #266

jmrobinsgithub opened this issue Feb 16, 2025 · 3 comments

Comments

@jmrobinsgithub
Copy link

I am running 1.8.4. My issue seems similar to [hectcastro] in Issue 252, but I do have Sec+ 2.0.

The web interface does not always respond, when it does, I get a spinning circle most of the time. The device does not normally respond to pings and when it does has 200-300ms response times. I tried flashing with the esphome firmware via USB and the webinterface for that was very responsive and consistently responded to pings with 4ms response. This tells me it's not my wifi/network. I have also moved the ratgdo as far from the opener as the leads will allow.

Then I put the homekit firmware back on and same symptoms. It will not allow me to rejoin to my home in homekit (yes, I removed all the device from the home). My phone sees the device, tries to add to the home, times out after several minutes, not visible in Apple Home, but once the webpage does load, the ratgdo thinks it's connected.

It's hard to get the logs to load over wifi, but when they did, it's full of crashes. The log went up to 255 with this data.
Messages logged immediately before last system crash...
Server upTime: 0 days 00 hrs 00 mins 00 secs
Crash information recovered from EEPROM
Crash # 1 at -1 ms
Restart reason: 255
Exception (255):
epc1=0xffffffff epc2=0xffffffff epc3=0xffffffff excvaddr=0xffffffff depc=0xffffffff

esp-web-tools-logs 16feb.txt
esp-web-tools-logs (2).txt
Garage Door 1BEEB6 Logs.pdf

Image
@jmrobinsgithub
Copy link
Author

I have since tried rolling back to 1.8.3 and am still unable to get it to join Homekit again.

@jmrobinsgithub
Copy link
Author

After rolling back to 1.8.3, I tried 4-5 times and was eventually able to get it to connect to homekit. So it is now working, but something seems off that it would take that many attempts.

@jmrobinsgithub
Copy link
Author

While I have been able to get it to connect to HomeKit, it goes unresponsive all the time. Would the WiFi changes introduced in 1.8.1 cause any of this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant