-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
esp8285 reboot due to incorrect API or wireless timeout #3472
Comments
You don't read, don't you? |
I don't appreciate your passive aggressive nature there. Yes, I do read, and I scoured the internet for two days and tried all sorts of things before putting this issue up - even then, I checked the existing issues first. I am new to esphome, but I am not new to the development process and lodging issues. Once you're over grandiosity, could you please actually assist or indicate what I missed? Thank you. |
It seems there is some aggression ongoing, so I only reference this issue #1 . |
Hm. Do you see anything special on this link? |
Thanks - will remove this and move it now. I legit did not see that when I posted last night! |
I do not, I did not last night. It may have not loaded the whole page, or it could have been because I had too many tabs open, but it was an honest mistake and there is no need for the attitude. |
I have a pile of Espressif MCU's connected to ESPHome within HA. Everything latest.
I've found that the ESP8285 crashes every 15-30 mins, and I narrowed that down to either a Wifi or API timeout. Setting both to 0s works fine.
The YAML I am using now is
However it'd be great to actually not have to set these, as they are not actually timing out. My AP does not show it disconnecting until after the reboot, and when I watch the logs everything is working fine until the API says read error on the 15 or 30 min mark, then it reconnects a few seconds later. So it seems like the timeout is not being counted correctly.
After the unexpected reboot (I can recreate and get verbose logs if required), the status LED is blinking every ~1 second and the emergency wifi AP is enabled, even though it's also joined again in STA mode.
The text was updated successfully, but these errors were encountered: