#NCP entered failed state
1 messages · Page 1 of 1 (latest)
Alright so i'm just gonna make a thread for this. Checked overnight and, while 12.1 is mostly stable without that edit... I did have multiple dropouts between 2:24:13 AM and 2:50:30 AM overnight. I'm using my motion sensor history as a proxy for whether things are working because it can tell me how long it held a state for, and it's saying that after 4 hours, 44 minutes of being 100% fine, it cuts out multiple times, and then goes back to being fine for another 6 hours before I return to my basement.
Literally none of the RF producing things in the room were active during that period. As I mentioned previously, all my Zigbee stuff is in a single room in my basement, and I was not in that room overnight. Believe it or not, I don't have anything running on wifi that stays on overnight in this room other than my Switch, which I had actually turned entirely off last afternoon to troubleshoot this. The only wifi interference would be the signal from my router upstairs.
The only possible thing i can think of could be what you mentioned earlier about CPU usage, because 2 am is when google drive is scheduled to backup and then upload to gdrive.
Unfortunately I was not running debug mode overnight, so I don't have a log to give you of this incident.
https://github.com/home-assistant/core/issues/105705
This seems related to my issue, though it doesn't explain the middle of the night dropouts. I had it again today. Still on 12.1
So, I upgraded to 12.4 to see if it fixed this, it didn't, and then when I tried to restore to 12.1 with the backup that was automatically made... It completely screwed the entire HA installation to the point I can't even restore with one of my daily full backups.
I'm at the point where i'm now reinstalling raspbian from scratch so that I can reinstall HA supervised from scratch, restore from backup, and hope that works. Hoorayyy...
For the record I don't think the ZHA issue had anything to due with the nuke of HA (just real bad luck), but it does mean that a pretty big variable has now changed once this is back up and running.
On the bright side, at least i'm upgrading to debian 12
Will be following to see if you might be able to find the culprit. Seeing the same when upgrading past 12.1, 12.4 also not fixing things for me unfortunately
Number of restarts was getting ridiculous so decided to try and update to 1.0b3 and see if that would do anything. Not calling it fixed yet, but things are definitely performing way better. Will report back in a day or two when confident that the issue is fixed
Not a single issue since upgrading to 1.0b3 more then 48 hours ago. I’d give it a try and see if it helps for you as well @silent carbon
Very good to know
Currently upgrading to 1.0b4, since that's available. Will post up if it's stable!
So far so good!
idk if anyone's still monitoring this, but absolutely zero issues since I updated to 2024.1.X. Even that thing I mentioned about dropping out in the middle of the night is gone. Hell yeah.