Back when we got the last supervisor update I had a LOT of problems with my deconz, I lost devices, the network was very unstable.
So I was quite hesitant with upgrading to the new OS 5.11 and the Deconz update that was just rolled out.
One thing that was in the Deconz 2.9.3 was that the ‘IKEA range extender’ was better supported and recognized, in some version the naming of them differed, it also has a lot of IKEA updates (I had my led drivers flashing quite a bit).
So I hesitated, but went through with the update yesterday, and it completed without any problems. Only thing I had to do was to activate my smoke sensors which were marked as offline (they check in very rarely), I then went through the very few sensors, activated them, and they updated nicely.
It has been a very reassuring experience, very painfree, and much better than the supervisor update.
Thanks for this positive feedback, I’ve forwarded it to the developers, don’t underestimate the energy that comes with a happy post. It’s nice to not only get feedback when stuff is not working, even though it is important to know.
When things go smoothly, which are not simple updates (even though they look like it for us plain folks) credits are due, and this was a very solid effort.
Oh well, trees doesn’t grow into the heaven I guess.
I’ve had a ton of problems the last day, I think that there have been a lot of device updates for the zigbee devices, because they just show themselves as connected, but aren’t really, some of them has acted really weird.
I’ve gotten most back online, by just ‘rebooting’ them with a power off/on, but my heiman sirens had to be disconnected, I’m currently waiting for them to run out of power so they are properly reset.
I also had to hack one of my IKEA led drivers so that it would accept a 12V strip, instead of the original 24V.
But this has nothing to do with the deconz itself, rather that devices gets updates, and suddenly weirds up.
It seems that the firmware and deconz have changed quite a bit in the way they present themselves. Previously the IKEA controller would present a light entity if it was paired to a bulb directly, so that you could turn on / off the controller and it would turn on / off all the lights it was paired with, that is no longer possible it seems. This has given quite a few headaches here (and seriously dropping WAF).
It has nothing to do with the add-on, in the way that it is only packaged software, but too bad that deconz has made all these changes and not really warned about them.
Hi @Robban
My deconz is going to hell at the moment, everything is jumping off the network, even very reliable IKEA bulbs are loosing connections, everything is going to sh…
I’ve tried posting it to the deconz page: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/4416 as frustrations are rising here, the zigbee network is almost useless.
I’m not sure who is updating the add-on, but could you nudge the appropriate person to update the deconz to suggested version 26670700 ?
That is a firmware version, not deconz. You can easily change the firmware on a any PC, no need to have the add-on updated for this.
It is not officially supported to update the Conbee firmware using the add-on, there are some longstanding issues leading to bricking the device and a reset and new firmware flashed from a separate deconz instance.
Ahh, ok, got it, @Robban
I think I’ve found a big part of the problem.
The deconz addon exits on itself, without any warning:
This is the log file from the last part:
2021/02/16 21:12:37 [error] 1182#1182: *44575 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: _, request: "GET /api/31857C7F46/sensors/new?_=1613505658774 HTTP/1.1", upstream: "http://127.0.0.1:40850/api/31857C7F46/sensors/new?_=1613505658774", host: "homeassistant.fribert.dk:8123", referrer: "https://homeassistant.fribert.dk:8123/api/hassio_ingress/nI9J4nKKn6-ajjWEPdU61TCh--GN6TbTeKg23lcb6nk/pwa/devices-sensors.html?_v=940837265b655b13c7c5e2fbabb4935025ca4c1b,1,2,21&gwid=00212EFFFF051F1A"
172.30.32.2 - - [16/Feb/2021:21:12:37 +0100] "GET /api/xxx/sensors/new?_=1613505658774 HTTP/1.1" 502 184 "https://homeassistant.fribert.dk:8123/api/hassio_ingress/xxx-ajjWEPdU61TCh--xxx/pwa/devices-sensors.html?_v=940837xxxxxxx13c7c5e2fbabb4935025ca4c1b,1,2,21&gwid=00212EFFFF051F1A" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Firefox/85.0"
2021/02/16 21:12:37 [notice] 318#318: signal 15 (SIGTERM) received from 307, exiting
2021/02/16 21:12:37 [notice] 1182#1182: exiting
2021/02/16 21:12:37 [notice] 1182#1182: exit
2021/02/16 21:12:37 [notice] 318#318: signal 14 (SIGALRM) received
2021/02/16 21:12:37 [notice] 318#318: signal 17 (SIGCHLD) received from 1182
2021/02/16 21:12:37 [notice] 318#318: worker process 1182 exited with code 0
2021/02/16 21:12:37 [notice] 318#318: exit
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
In exit
[s6-finish] waiting for services.
Closing socket listening at 127.0.0.1:5901
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting
After doing a restart, it stops again:
21:16:03:325 New websocket 172.30.32.1:57142 (state: 3)
21:16:04:288 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2139528-if00 / serialno: DE2139528, ConBee II
21:16:04:653 device disconnected reason: 4, index: 0
[21:16:05] WARNING: Your direct VNC access is not protected!
[21:16:05] INFO: Starting VNC server (local/no)...
In exit
2021/02/16 21:16:05 [notice] 317#317: signal 15 (SIGTERM) received from 307, exiting
2021/02/16 21:16:05 [notice] 1179#1179: exiting
2021/02/16 21:16:05 [notice] 1179#1179: exit
2021/02/16 21:16:05 [notice] 317#317: signal 17 (SIGCHLD) received from 1179
2021/02/16 21:16:05 [notice] 317#317: worker process 1179 exited with code 0
2021/02/16 21:16:05 [notice] 317#317: exit
Closing socket listening at 127.0.0.1:5901
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Both of them is a SIGTERM from ‘307’ whatever that is?
I updated to the latest deconz addon version earlier today, and unfortunately now I’ve seen the addon stop in the last hour. I have an automation that alerts me when this happens. I’ve started it again and the network has come back up very quickly, and everything seems fine again, but it’s a bit of a concern.
Hi @jdbrookes
Thanks for chiming in, I’m seeing the problems progress over the last couple of days, and it is very frustrating, and the family (wife in particular) is NOT happy, I can’t blame here, I’m equally frustrated over the state of this.
I’ve created a case here, feel free to update it with logfiles, comments etc.
I don’t have the original log file I’m afraid so I’m not sure why it stopped the first time. It hasn’t stopped again in the last few hours but we’ll have to see overnight. Otherwise deconz has been running very well the last few months.
Darned, this has been a horrible experience. It’s not the addon part, its the deconz itself.
After going to the 2.09.03 everything was fine, but then the devices started getting updates.
We haven’t had stable lighting in 2 weeks, the family is going crazy, and taking me with them.
For some reason, every light has had updates, which has made them go flashing while updating, and gone haywire after the update.
It also meant that my hacked 12V IKEA led drivers didn’t want to light up, until they were ‘updated’ with a lower resistor.
The heiman sirens have lost the connection completely, but can’t be removed from the network, which makes all the sensors go crazy, as the heiman sirens has both 220v and battery backup, they seem to prefer them as routers. So almost all the sensors are gone off the grid.
Now I’m waiting for the battery to depleat in one of the sirens, so I can toss it, and then reestablish a hopefully more stable network after that.