deCONZ stopped working for me -> 502 Bad Gateway

On my Synology NAS I have a Conbee II stick and was using it using the Deconz/Phoscon Addon. It used to work fine-ish before. So I have a Zib-Bee Button that worked quite well. Then I added a temperature sensor and I was able to read it’s values in the Phoscon Web-UI, but not home-assistant. Wasn’t sure why. Today I saw that there was an update to the add-on, so I intalled that.
But since then I can’t even login to the web-ui any more. It only gives me a 502 - Bad Gateway

Current logs from the add-on are those:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] firmware.sh: executing... 
[11:50:14] INFO: GCFFlasher V3_13 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyACM0     | 0x1CF1 | 0x0030  |            | ConBee II 
[cont-init.d] firmware.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] novnc.sh: executing... 
[cont-init.d] novnc.sh: exited 0.
[cont-init.d] done.
[09:50:16] INFO: Running the IKEA OTA updater...
[services.d] starting services
[services.d] done.
[09:50:16] INFO: Starting udevd...
[09:50:16] INFO: Running the deCONZ OTA updater...
[11:50:16] INFO: Websockify waiting for VNC to start
[09:50:16] INFO: Running the OSRAM LEdvance OTA updater...
[11:50:16] INFO: Waiting for device...


[09:51:16] INFO: Starting Nginx...
[11:51:16] INFO: Starting websockify...
2020/08/30 09:51:16 [notice] 324#324: using the "epoll" event method
2020/08/30 09:51:16 [notice] 324#324: nginx/1.14.2
2020/08/30 09:51:16 [notice] 324#324: OS: Linux 4.4.59+
2020/08/30 09:51:16 [notice] 324#324: getrlimit(RLIMIT_NOFILE): 524288:1048576
2020/08/30 09:51:16 [notice] 324#324: start worker processes
2020/08/30 09:51:16 [notice] 324#324: start worker process 1332
WebSocket server settings:
  - Listen on 127.0.0.1:5901
  - Flash security policy server
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from 127.0.0.1:5901 to 127.0.0.1:5900
2020/08/30 09:51:52 [error] 1332#1332: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: _, request: "GET /pwa/index.html HTTP/1.1", upstream: "http://127.0.0.1:40850/pwa/index.html", host: "192.168.1.9:8123", referrer: "http://192.168.1.9:8123/api/hassio_ingress/00wSTa-sBK6f0x1ySE-d2ft4zn0NHyWeh8VhgtPu48c/ingress.html"
172.30.32.2 - - [30/Aug/2020:09:51:52 +0000] "GET /pwa/index.html HTTP/1.1" 502 184 "http://192.168.1.9:8123/api/hassio_ingress/00wSTa-sBK6f0x1ySE-d2ft4zn0NHyWeh8VhgtPu48c/ingress.html" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.2 Safari/605.1.15"
2020/08/30 09:51:59 [error] 1332#1332: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: _, request: "GET /pwa/index.html HTTP/1.1", upstream: "http://127.0.0.1:40850/pwa/index.html", host: "192.168.1.9:8123", referrer: "http://192.168.1.9:8123/api/hassio_ingress/00wSTa-sBK6f0x1ySE-d2ft4zn0NHyWeh8VhgtPu48c/ingress.html"
172.30.32.2 - - [30/Aug/2020:09:51:59 +0000] "GET /pwa/index.html HTTP/1.1" 502 184 "http://192.168.1.9:8123/api/hassio_ingress/00wSTa-sBK6f0x1ySE-d2ft4zn0NHyWeh8VhgtPu48c/ingress.html" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.2 Safari/605.1.15"
[11:53:16] FATAL: No device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1962646-if00 found!
2020/08/30 09:53:16 [notice] 324#324: signal 15 (SIGTERM) received from 309, exiting
2020/08/30 09:53:16 [notice] 1332#1332: exiting
2020/08/30 09:53:16 [notice] 1332#1332: exit
2020/08/30 09:53:16 [notice] 324#324: signal 17 (SIGCHLD) received from 1332
2020/08/30 09:53:16 [notice] 324#324: worker process 1332 exited with code 0
In exit
Closing socket listening at 127.0.0.1:5901
2020/08/30 09:53:16 [notice] 324#324: exit
[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.

So it’s complaining about not finding the stick?!? Not sure why that would be… It did find the stick 30 minutes ago before I did the update and it told me the correct values for e.g. my temperature sensor…

Also in the HA logs I found the following relevant info:

Config entry for deconz not ready yet. Retrying in 5 seconds
11:59:33 – config_entries.py (WARNING) - Die Nachricht ist zum ersten Mal um 11:51:21 aufgetreten und erscheint 11 mal
Error connecting to deCONZ gateway at 172.30.33.0
11:59:33 – deCONZ (ERROR) - Die Nachricht ist zum ersten Mal um 11:51:21 aufgetreten und erscheint 10 mal

(The IP of the deCONZ gateway seems a bit strange?!?)

Anyway… how can i debug the problem and fix it… Did any of you encounter the problem as well?
Any ideas are greatly appreciated! :slight_smile: thank you

I now uninstalled and then re-installed the deCONZ integration, and still the problem with the Bad Gateway persists…

Does anybody have any idea?

Yesterday I installed the first time the deCONZ integration and got also the Bad Gateway. Somewhere else I found a note to wait a few seconds (15) before clicking on the Phoscon button. That worked for me, but no idea why

@d.brauer I found my solution here:


Cheers