Hi All
Not sure if this has been answered.
I am running Deconz on HassOS 104.3 I recently upgraded from 102
Since the upgrade I have issues with random disconnections of my sensors for 15 seconds.
Below is the logs from the deconz logs
Remove websocket 172.30.32.1:43064 after error Unknown error
New websocket 172.30.32.1:57818 (state: 3)
I had an issue with upgrading and had to re-add all of my sensors to deconz.
I had a look and can’t see why it disconnects. Sometimes it does it once an hour, others it goes 18 hours before it does it.
I have some more information if anyone has any advise
I do notice that when the CPU goes from about 10% to around 30% it disconnects. Also if the CPU temperature increases as well (Usually runs about 56 C but can do to 65-70 when there is issues)
So something is causing home assistant to lose access to the deconz for 15 seconds.
I am running on a Pi 3 with SD card, which I have been doing for about 2.5 years without and major problems.
Did you ever figure this out?
I’m having the same problem. Deconz worked perfectly for months. A few weeks ago, I started seeing periodic disconnects of all sensors every ~30min for about 15-20 seconds. This is really annoying as door switches that happen to change state during these disconnects get really messed up (as they only report “on status change”).
I’m running deconz via Docker in a Raspberry Pi 3B with the ConBee II stick. I have not updated the deconz or ConBee firmware (just did now but issues are still there). I run HA in a different more powerful computer. I’ve kept HA update so it’s possible that one of those updates has caused the issue.
HI.
I can’t 100% remember, but I do recall around that time, there would be times when the CPU on the Pi would go to 70-80% and it would become unusuable, and I had to powercycle it.
I think not long after that, the SD card failed…
After that, I haven’t had it since.
I am planning on moving mine to a virtual machine on proxmox in the next couple of weeks. So I will see if it occurs again
Same here. I assumed that the WIFI or more precise a (WIFI) script that runs in the background (but whose name I forgot) was responsible for this.
So I switched off WIFI and wired the PI via ethernet.
Never ever had this problem again since.
In case anyone finds this in the future when trying to solve their issue: my problem was due to faulty wifi. In particular, one of the Eero beacons that the raspberry pi was connected must have been acting up. Resetting the Eero network solved the problem.