The panel has stopped working and is not visible on the network. #3228
Replies: 7 comments 15 replies
-
Beta Was this translation helpful? Give feedback.
-
|
Do you remember from which ESPHome builder version have you updated from? |
Beta Was this translation helpful? Give feedback.
-
|
ESPHome Device Builder |
Beta Was this translation helpful? Give feedback.
-
A serial flash is usually very good to recover from this state… but it is quite a work 😩 |
Beta Was this translation helpful? Give feedback.
-
|
How complicated is this procedure? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I already do this 2-3 times. Nothing changed after that |
Beta Was this translation helpful? Give feedback.
-
|
I replaced the panel, bought a new one, and after a week it's the same. After a week, the panel stopped responding and lost its connection to the network. This time, I didn't disconnect it from the power supply so that I could better describe what was happening. I tried to reset it, but after going to the reset option page, the button lights up blue, but the panel does not reset. The mechanical buttons do not work either. The only thing I noticed is that when validating the code, I get this warning: |
Beta Was this translation helpful? Give feedback.
-
|
Could you please share here the yaml you have used to flash that panel? Please remove sensitive info before sharing. |
Beta Was this translation helpful? Give feedback.
-
|
I don't change the yaml: |
Beta Was this translation helpful? Give feedback.
-
|
When I got home, the screen still wasn't communicating, but it was still working. I checked the settings, etc., but everything looked OK. I decided to do a hard reset, and unfortunately, as with the previous display, it didn't start up. I have absolutely no idea what is going on. Two panels won't start up, and three more are waiting because I'm afraid to reprogram them. |
Beta Was this translation helpful? Give feedback.
-
|
So, I know this is a bit complex task, but would be possible to connect your panel via serial (the same you used for boot) and try to collect the logs via serial? That will most likely show what your panel did right before crashing. |
Beta Was this translation helpful? Give feedback.
-
|
LOG form panel: |
Beta Was this translation helpful? Give feedback.
-
|
Ok, looks like it is crashing when starting the WiFi. Most likely some issue from the upstream (ESPHome itself). I would expect these symptoms from a power failure, when starting the WiFi system (which takes lots of power)… Could you please try adding this to your panels yaml? wifi:
power_save_mode: HIGH |
Beta Was this translation helpful? Give feedback.
-
|
I collected the logs with a USB-TTL adapter connected. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, right. The device was powered by the TTL at that moment then. So please try adding this to your yaml then (in addition to the one from my previous message): switch:
- id: !extend screen_power
restore_mode: ALWAYS_OFFWith this your panel should have a chance to start WiFi before the screen is powered, so you should have a chance to collect more logs and hopefully get to the cause of the issue preventing the boot when powered by mains. 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, it didn't help. The panel still couldn't connect to Wi-Fi. |
Beta Was this translation helpful? Give feedback.
-
|
It looks all right… 😩 |
Beta Was this translation helpful? Give feedback.
-
|
I seem to have run into a similar problem. I tried to update the firmware to the latest version (don't recall exact version, sorry, it was like a couple of weeks ago), and apparently something went amiss. When I got downstairs later to check the panel it had stuck in the boot screen, failing to contact wifi. I pressed the on-screen reboot several times, to no avail. A bit unsure on how to proceed, I let this be (much to my family's chagrin) until I could read a bit more on how to reset the NSPanel. After a day or so, the panel was completely blank, and the hardware buttons do not work anymore. I've tried power cycling the NSPanel by the fuse it's connected to, but nothing changes. Did anyone get a solution to this? Should I consider it bricked? |
Beta Was this translation helpful? Give feedback.
-
A serial flash always fixes this kind of issue, but with the information you have it's hard to understand what caused that. 😞 |
Beta Was this translation helpful? Give feedback.
-
|
My family is kind of mad at me since we can't turn on the lights in the hallway. :) I've ordered a replacement nspanel to get the light working again, but then I can presumably spend some time to see if it is possible to tease something useful out of the soft-bricked one. If I disconnect it from the wall mount and attaches a serial, should I look for logs, or just reflash it? |
Beta Was this translation helpful? Give feedback.
-
|
The logs via serial are usually more complete, however, it is a different setup and you may not see the same issue. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I think I bricked my panel. But maybe someone else had a similar problem and it turns out that's not the case. I was updating the framework to ESP-IDF and unfortunately something went wrong. At first, the panel went into a boot loop, then it started up, only to eventually stop turning on altogether. At the moment, I can't see it on the network, let alone in ESPhome as active. I did the updates via a cable connection to make sure everything went smoothly. Below is my code.
I'm totally out of ideas for what I could have screwed up.
Beta Was this translation helpful? Give feedback.
All reactions