Problem:
All of my devices that were set up under the Phoscon / deconz gateway are unresponsive in HomeKit.
The Homebridge log (currently version 2.0.2) regularly shows:
[deCONZ] warning: 192.168.178.42 config: request 1: connect ECONNREFUSED 192.168.178.42:80
[deCONZ] warning: {IP adr. same as above, due to forum posting restrictions}: connect ECONNREFUSED {same as above} - retrying in 60s
Everything was working fine before. However, I was getting “ECONNREFUSED” error messages even before updating Homebridge to 2.x.
The configuration for the Homebridge-deCONZ plugin is:
{
“name”: “deCONZ”,
“noResponse”: false,
“stealth”: false,
“hosts”: [
“{same as above, due to forum posting restrictions}”
],
“platform”: “deCONZ”
}
Adding a port entry in the config file, such as 4530, 8080, or 8090, does not solve the problem.
I can access the Phoscon GW’s graphical interface at “http://homebridge.local:4530/pwa …”. I can see all my devices there. The GW is displayed in the top right corner with the IP address “{same as above, due to forum posting restrictions}”.
In the Phoscon app on the iPhone, my gateway appears at {same as above, due to forum posting restrictions} and suddenly another one at {Link: due to forum posting restrictions} “ten.ninety-nine.two.thirty-eight” as “undefined.” I have no idea where the second gateway suddenly came from.
In the Homebridge terminal, I get the following information:
pi@homebridge:/var/lib/homebridge $ sudo systemctl status deconz
● deconz.service - deCONZ: ZigBee gateway – REST API
Loaded: loaded (/lib/systemd/system/deconz.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/deconz.service.d
└─override.conf
Active: active (running) since Tue 2026-05-12 16:42:43 CEST; 2 days ago
Main PID: 165829 (deCONZ)
Tasks: 7 (limit: 3927)
CPU: 1h 52min 39.253s
CGroup: /system.slice/deconz.service
└─165829 /usr/bin/deCONZ -platform minimal --http-port=4530 --ws-port=4531
May 12 16:42:43 homebridge systemd[1]: Started deconz.service - deCONZ: ZigBee gateway – REST API.
May 12 16:42:43 homebridge deCONZ[165829]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-pi’
May 12 16:42:43 homebridge deCONZ[165829]: libpng warning: iCCP: known incorrect sRGB profile
May 12 16:42:44 homebridge deCONZ[165829]: This plugin does not support propagateSizeHints()
May 12 16:42:44 homebridge deCONZ[165829]: This plugin does not support propagateSizeHints()
May 12 16:42:44 homebridge deCONZ[165829]: This plugin does not support propagateSizeHints()
pi@homebridge:/var/lib/homebridge $ ^C
pi@homebridge:/var/lib/homebridge $
“https://phoscon.de/discover” does this:
id “XYZ”
internalipaddress “{IP adr. same as above, due to forum posting restrictions”
macaddress “XYZ”
internalport 4530
httpsport 443
name “Phoscon-GW”
publicipaddress “–.–.–.–”
But to change the configuration of the Homebridge-deCONZ plugin to “{IP adr. same as above, due to forum posting restrictions:443,” do the following:
[deCONZ] warning: {IP adr. same as above, due to forum posting restrictions:443 config: request 1: socket hang up
[deCONZ] warning: {IP adr. same as above, due to forum posting restrictions:443: not a deCONZ gateway - retrying in 60s
What the heck is broken here, and how can I fix it?
If there isn’t a simple 
solution, I’m willing to delete everything from Phoscon / deconz. But please don’t mess up my Homebridge installation (currently running Raspberry Pi OS Lite (Debian) Bookworm on a Raspberry Pi 4 4 GB, Model B, Rev. 1.2, c03112). And how do I get it reinstalled? Using hb-config?
Yes, I know, after that I’ll have to reconnect all my devices to Phoscon deCONZ.
Please help. 