-
Notifications
You must be signed in to change notification settings - Fork 34
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
Writing Ephome is prone to death #5789
Comments
There are currently two types of crashes,
I hope there is a mechanism to prevent complete death, |
Can a long press continuous click mode be added to a pin port to trigger a reset function. |
The problem
It's very easy to die, which means I have to dismantle my socket. If I want to upgrade it in,
it needs to be soldered, The operation is very complicated
which is very painful for me. There are two reasons why it dies directly because I changed the configuration. The socket light is not on, nor does it display hotspot WiFi. There is also one light that is on, but I scanned the port and did not find that the web service was created. I hope there is a mechanism to prevent it from dying, otherwise it will be very painful for me. In addition, there is a mechanism that is newly flashed in, and I usually need WE. If it is not accessed for a long time for the first time, it will automatically restore to the initial state. I remember filling in the static IP, and then the IP and WiFi are not in the same network segment. How does it recognize conversions in this situation?
Which version of ESPHome has the issue?
2024.3.0
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2024.12.3
What platform are you using?
ESP8266
Board
other
Component causing the issue
misc
Example YAML snippet
The text was updated successfully, but these errors were encountered: