The new beta version v2.32.2 is just released, I hope this fixes the crashes but I can’t test with Alexa.
hey,
the crashes still happen. no changes in behavior in the beta.
hey,
just pulled the latest container image. seems like the restart-problem is solved?!
haha, spoken of the container crashed again. this time after round about 25 minutes. error message stays the same:
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
I think i found the reason why the deconz is permanently crashing. my home assistant was mass generating websessions on the deconz webinterface.
I migrated the deconz to kubernetes now and everythings looking better. no more crashes and no more unwanted web-sessions are created.
but alexa is still not working correctly. I can see the devices in the alexa app but they are all not responsive. Still testing with kubernetes…
Hola.
Thanks to all your work I was able to setup a docker container with nginx reverse proxy. After hours off troubleshooting nearly everything works fine now. My ioBroker deCONZ Adapter connects via Websocket Port 8444 - the port that offers nginx for the real 8443 Port offers by deCONZ. Alexa works nearly as fast as bevore the summer. But… Alexa didn’t find new Devices. And there are a lot of new devices to find.
Also, when I go to the deCONZ https adresse I only get an “502 - Bad gateway”. Can someone help please. Where is the error?
To make a long story short:
No port-blocking, no nginx, just reconfigured deconz to ws-port=8443 and everything worked.
Ok, so that’s the the results of many hours of testing, since i was was only some hours per year on the raspi before (debian 12, iobroker with decoonz instance), I’m not able to drill down to the kernel:
-Alexa-App: Changing alexa-skill to iobroker.assistance and reconnected it
-raspi: After “repair” of deconz didn’t work in (m)any ways I un- and re-installed deconz (lasted beta 2.32.1) and … nothing changed, same shit as before. Then I worked with MS Copilot and got this script below.
Then I changed the port for iobroker instance of deconz to ws=8443 and every worked again!
#!/bin/bash
echo "=== Korrigiere Rechte für /run/user/1000 ==="
sudo chmod 700 /run/user/1000
echo "=== Erstelle systemd-Unit für deCONZ ==="
sudo tee /etc/systemd/system/deconz.service > /dev/null <<EOL
[Unit]
Description=deCONZ Zigbee Gateway
After=network.target
[Service]
ExecStart=/usr/bin/deCONZ -platform minimal --http-port=80 --ws-port=8443 --auto-connect=1
Restart=on-failure
User=pi
WorkingDirectory=/home/pi
Environment=DISPLAY=:0
[Install]
WantedBy=multi-user.target
EOL
echo "=== Lade systemd neu ==="
sudo systemctl daemon-reload
echo "=== Aktiviere Autostart ==="
sudo systemctl enable deconz
echo "=== Starte deCONZ-Service ==="
sudo systemctl start deconz
echo "=== Status anzeigen ==="
sudo systemctl status deconz --no-pager
And to say it in clear words: @Mimiix i’m very dissapointed from Dresden Elektronik. More than 4 months and no solution at all an average user can apply.
1 Like
Hi, not sure why you tag me. As far I can see, Dresden is trying their best and they can’t replicate it. Great to see you have it fixed 
tbh, if youre running your own zigbee gateway at home, you must be able to use the content of this forum to fix this. there are enough solutions postet here.
If not, you should consider to swap your zigbee gateway to an amazon echo or something like this
I’ve added another fix for the networking code, this mainly affects browsers but might also be relevant for Alexa API access. https://github.com/dresden-elektronik/deconz-lib/commit/3d98f564b424d5ecbb301ef6e0aa8e6cb77dd33f
Will be part of the upcoming v2.32.3-beta.
1 Like
Hi manup, this all is for deconz - for Raspbee only? I am using Conbee II on a Qnap in a container. Same issue here since August. I am also very dissapointed and checking other Zigebee hub’s. Sooner or later i will change or is there some hope that this will be fixed for Christmas?
There are already severl ways to fix this described here, also for your qnap docker as automated compose
marcus, did you try to add new devices via alexa app? My deconz setup is now very responsiv for alexa, with the nginx reverseproxy - but it is not possible to add new devices.
So yeah…, I was actually about to say “yes,” because after I added the nginx extension to my deCONZ Docker on September 27th, everything was working fine. Since then I’ve added 2 Zigbee powerswitches, a motion sensor, and a light without any problems.
I just tried adding another light now, and it doesn’t work anymore. The last motion sensor I added to Alexa was on October 31st, 2025 (For Halloween), the light a few days before, and it was still working then. So it looks like Amazon has changed something again since that date.
So of course I’m coming back to you and hoping for a quick fix.
We are all currently considering switching to an alternative because the current situation has been ongoing for months and is by no means acceptable. For months, very little has happened, and everyone feels quite abandoned and disappointed by how little Dresden Elektronik seemed to care about the acute issues until just a few days ago. Other local devices work without problems, so it seems to be something very specific to Phoscon.
Yeah, nothing happened for four months. After two months there was a first solution with nginx that someone figured out on their own. That’s pretty embarrassing on Dresden’s side. On the other hand, it looks like Amazon keeps changing things so the Hue 3rd-party integration stops working again. Considering that Amazon keeps tweaking stuff and Dresden keeps working at the same slow pace, this probably won’t go anywhere. The Hue emulation was honestly the nicest way to connect things to Alexa. With Z2MQTT it’s way more work.
From DEs activities on GitHub, I take that they are working on a fix for the next stable release!?
Hello everyone,
after reading this topic with 97 messages, I wanted to summarize: the --ws-port=443 for Alexa has changed to --ws-port=8xxx, and the --http-port apparently has as well, but this is not yet known. Since this is necessary for device discovery, port 80 no longer seems to work. deCONZ v2.32.x have many changes to http(s)/ws and should not be used by inexperienced users. For a quick solution, deCONZ v2.31.2 with adjusted ports should be used. Port forwarding (nginx) is not necessary, but it’s not a problem either.
Alexa’s ports have been changed and dresden elektronik can’t do much about it at the moment. Alexa works very well for me because I’ve been using --ws-port=8xxx for a while now. So the Hue API v1 is still supported, and I hope it will be for a long time.
I understood the problem.
However, Dresden Elektronik sold the Conbee II with seamless Alexa integration. Addressing the issues with such a delay does not reflect well on the company. Phoscon could be provided with an account and an Alexa app could be released that connects to the account and makes the devices available in Alexa again. I realize that all of this would cost money. But then please be upfront about the fact that Alexa integration will probably no longer be available because Amazon has changed the system so much. And stop advertising Conbee and Alexa on the website. With all due respect, Dresden Elektronik’s approach is not exactly transparent.