Sadly, not all bugs are found in beta’s

With the latest stable version of deCONZ, after a certain amount of time (I’m not sure how long), I can no longer access the Phoscon web interface. and this message appears :

This is not the page you are looking for
The file /pwa/index.html couldn’t be found.

(404 Not Found)

After a reboot, it works again for a while.

I have tried:

• clearing the cache
• incognito mode
• multiple web browsers
• using the IP address
• a complete system reinstallation

Control via Home Assistant and the rules are not affected

System :
deCONZ 2.32.5 on Raspberry Pi.

mf2105:

Are there no beta testers??

There are many beta testers

I restarted the Home Assistant Docker container several times, and deCONZ did not restart .

Is there a problem with the image provided by deCONZ ? Personally, I checked the MD5.

Seems deconz was update to 2.32.5 on the raspi after restart!? So I went thru the new posts here and I did…

1. sudo systemctl edit deconz.service and added https-port=0 :

[Service]
ExecStart=
ExecStart=/usr/bin/deCONZ -platform minimal --http-port=80 --https-port=0 --ws-port=8443 --auto-connect=1

2. Rebooted the raspi, the Alexa err msg was gone but still some devices not working 10 min after reboot.
3. So I did Very slow integration with Alexa - #111 by Franky

Thanks all for publishing your solution. @mimix (its not to point at you, pls. fwd): And again wondering about Dresden Elektronik like some others in this thread. New bugs in every new minor release? Are there no beta testers??

Home assistant : docker
DeCONZ 2.32.5 : raspberry pi 3 with the image provided by deCONZ

I just checked my 4th FLS-PP, this also has date code 20220105 - and consequently didn’t work either.

The F8 firmware was released last year exactly for this reason (color setting won’t work). I don’t have high hopes for a fix. That makes 3 FLS-PP heading to electronic waste for me, certainly not to be replaced by anything from Dresden.

The older one, which i was finally able to update to F8 was having ST Micro - ST25P40VP Flash memory

The newer one, still impossible to update having Renesas - AT25SF041 Flash Memory.

I reminded support for a new answer but i am still waiting for it…

One of the two does actually switch from green to yellow color after update, the yellow color blinks a few times, and at the end the firmware still reads as 0214.201000F5. The other of the non-working ones does not even switch to yellow after upgrade, it simply does nothing and version also keeps at 0214.201000F5.

One other FLP-PP with date code 20251007 and firmware F6 did upgrade successfully to F8.

Upgrading was first tried with Z2MQTT (didn’t work), then I re-joined them to a ConBee II and tried with deCONZ (same behaviour as @KipiKland).

Any help will be appreciated.

But I still see these errors popping up in the log, what does that mean? Again, everything works fine but I’m worried something is still not properly behind the scenes:
18:03:19:312 discovery for zombie 0x0017880108273B6C dropped, last try was 938 seconds ago

18:03:27:472 discovery for zombie 0x0017880108273B6C dropped, last try was 946 seconds ago

18:03:35:632 discovery for zombie 0x0017880108273B6C dropped, last try was 954 seconds ago

18:03:43:791 discovery for zombie 0x0017880108273B6C dropped, last try was 962 seconds ago

18:03:51:952 discovery for zombie 0x0017880108273B6C dropped, last try was 970 seconds ago

18:04:00:112 discovery for zombie 0x0017880108273B6C dropped, last try was 979 seconds ago

18:04:08:272 discovery for zombie 0x0017880108273B6C dropped, last try was 987 seconds ago

If you have time can you install deconz on a real PC without docker and use your last backup ?

But you can have restored an older backup without recent network key = You will need to re-include all your devices.

Can try Network lost issues · dresden-elektronik/deconz-rest-plugin Wiki · GitHub

This tool is able to restore old network setting but it have limits.

For information, devices data are stored on host, but network settings are stored on the gateway.

I was successfully using deCONZ with a ConBee II for many years with Home Assistant to integrate my Aqara sensors.

After updating some items, I still have my configuration but Phoscon is not showing any value updates for any sensor for any reason.

I had to update several items to due various reasons and are running Home Assistant’s newest version (e.g. Core 2026.3.1), deCONZ 8.7.0, Phoscon GW 2.32.5 & firmware 26720700 now.

I assume the issue appeared when I updated deCONZ from any old version (I assume it was any v6 or something like that) to the newest 8.7.0.

I also tried to restore an old Phoscon backup but it didn’t help. In the end it’s showing up values from months or years ago which are successfully forwarded to Home Assistant. But within Phoscon I don’t see any value update.

Here’s the deCONZ log. In the end it’s continuing with the 172.30.32.2 errors frequently but I stopped to copy them at some point to not blow up this post. I hope somebody can help what’s going wrong and how to solve it. Thanks in advance!

Log:
[09:22:41] INFO: Bosch OTA update is disabled.

[09:22:41] INFO: IKEA OTA update is disabled.

[09:22:41] INFO: OSRAM/LEDVANCE OTA update is disabled.

s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

cont-init: info: running /etc/cont-init.d/firmware.sh

[09:22:41] INFO: Path | Serial | Type

------------------±------------±--------------

/dev/ttyACM0 | DE2217886 | ConBee_II

cont-init: info: /etc/cont-init.d/firmware.sh exited 0

cont-init: info: running /etc/cont-init.d/nginx.sh

cont-init: info: /etc/cont-init.d/nginx.sh exited 0

cont-init: info: running /etc/cont-init.d/novnc.sh

cont-init: info: /etc/cont-init.d/novnc.sh exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun deconz (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

services-up: info: copying legacy longrun websockify (no readiness notification)

[09:22:41] INFO: Websockify waiting for VNC to start

s6-rc: info: service legacy-services successfully started

[09:22:42] INFO: Starting VNC server (local - yes)…

[09:22:42] INFO: Starting websockify…

WebSocket server settings:

• Listen on 127.0.0.1:5901

• 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

[09:22:45] INFO: deCONZ waiting for VNC to start

[09:22:46] INFO: Starting the deCONZ gateway…

[09:22:46] INFO: Starting discovery script…

libpng warning: iCCP: known incorrect sRGB profile

libpng warning: iCCP: known incorrect sRGB profile

[09:22:46] WARNING: Database not found at /data/.local/share/deCONZ/zll.db, trying alternative path…

[09:22:46] WARNING: Existing API key invalid (HTTP 404), will try to create a new one…

[09:22:46] WARNING: No API key found – trying to create a new one…

parse error: Invalid numeric literal at line 1, column 34

[09:22:46] INFO: Starting Nginx…

2026/03/14 09:22:46 [notice] 147#147: using the “epoll” event method

2026/03/14 09:22:46 [notice] 147#147: nginx/1.22.1

2026/03/14 09:22:46 [notice] 147#147: OS: Linux 6.12.47-haos-raspi

2026/03/14 09:22:46 [notice] 147#147: getrlimit(RLIMIT_NOFILE): 1024:524288

2026/03/14 09:22:46 [notice] 147#147: start worker processes

2026/03/14 09:22:46 [notice] 147#147: start worker process 350

09:22:46:115 /data/.local/share/dresden-elektronik/deCONZ/config.ini exists and is writeable

09:22:46:115 /data/.local/share/dresden-elektronik/deCONZ/zll.db exists and is writeable

09:22:46:144 COM: use stable device path /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2217886-if00

09:22:46:164 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2217886-if00 / serialno: DE2217886, ConBee II

09:22:46:164 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt

09:22:46:270 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/

09:22:46:699 DDF enabled for Gold status

09:22:46:699 parent process s6-supervise

09:22:46:699 gw run mode: normal

09:22:46:699 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version

09:22:46:700 sd-card cid: 035344534433324785ffffffff015800

09:22:46:702 DB sqlite version 3.42.0

09:22:46:703 DB PRAGMA page_count: 50

09:22:46:703 DB PRAGMA page_size: 4096

09:22:46:703 DB PRAGMA freelist_count: 0

09:22:46:703 DB file size 204800 bytes, free pages 0

09:22:46:703 DB PRAGMA user_version: 10

09:22:46:703 DB cleanup

09:22:46:703 DB create temporary views

09:22:46:909 DB skip loading sensor Feuchtigkeitsensor 13, handled by DDF Water leak sensor (SJCGQ11LM)

09:22:46:910 DB skip loading sensor Bad 10, handled by DDF Open/close sensor (MCCGQ11LM)

09:22:46:910 DB skip loading sensor Esszimmer 4, handled by DDF Open/close sensor (MCCGQ11LM)

09:22:46:910 DB skip loading sensor Sam 12, handled by DDF Open/close sensor (MCCGQ11LM)

09:22:46:910 DB skip loading sensor Schlafzimmer 11, handled by DDF Open/close sensor (MCCGQ11LM)

09:22:46:910 DB skip loading sensor SH Arbeitsraum 6, handled by DDF Open/close sensor (MCCGQ11LM)

09:22:46:910 DB skip loading sensor Wohnzimmer 3, handled by DDF Open/close sensor (MCCGQ11LM)

09:22:46:910 DB skip loading sensor Haustuer 2, handled by DDF Open/close sensor (MCCGQ11LM)

09:22:46:910 DB skip loading sensor Gaeste-WC 5, handled by DDF Open/close sensor (MCCGQ11LM)

09:22:46:910 DB skip loading sensor Aussentemperatur 7, handled by DDF Temperature and humidity sensor (WSDCGQ11LM)

09:22:46:910 DB skip loading sensor Aussentemperatur 8, handled by DDF Temperature and humidity sensor (WSDCGQ11LM)

09:22:46:911 DB skip loading sensor Aussentemperatur 9, handled by DDF Temperature and humidity sensor (WSDCGQ11LM)

09:22:46:911 [INFO] - Timezone read is ‘Etc/UTC’

09:22:46:911 [INFO] - Environment variable TZ found: Europe/Berlin…

09:22:46:911 Started websocket server on 0.0.0.0, port: 8081

09:22:46:912 [INFO] - Found file containing button maps. Parsing data…

09:22:46:921 [INFO] - Button maps loaded.

09:22:46:922 found node plugin: /usr/share/deCONZ/plugins/libde_rest_plugin.so - REST API Plugin

09:22:46:922 found node plugin: /usr/share/deCONZ/plugins/libstd_otau_plugin.so - STD OTAU Plugin

09:22:46:937 LightNode 1: Configuration tool 1 added

09:22:46:947 DEV found DDF for 0x00158D00047C2BC6, path: /usr/share/deCONZ/devices/xiaomi/lumi_sensor_wleak_aq1.json, result: 1

09:22:46:947 DEV found DDF for 0x00158D0004ABD07E, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq11lm_openclose_sensor.json, result: 1

09:22:46:948 DEV found DDF for 0x00158D00053E80A0, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq11lm_openclose_sensor.json, result: 1

09:22:46:948 DEV found DDF for 0x00158D0004AAEDB6, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq11lm_openclose_sensor.json, result: 1

09:22:46:949 DEV found DDF for 0x00158D00053E7D67, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq11lm_openclose_sensor.json, result: 1

09:22:46:949 DEV found DDF for 0x00158D00052D54A1, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq11lm_openclose_sensor.json, result: 1

09:22:46:950 DEV found DDF for 0x00158D00053FE093, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq11lm_openclose_sensor.json, result: 1

09:22:46:950 DEV found DDF for 0x00158D00053FD679, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_mccgq11lm_openclose_sensor.json, result: 1

09:22:4172.30.32.2 - - [14/Mar/2026:09:23:52 +0100] “GET /pwa/index.html HTTP/1.1” 200 114528 “http://192.168.178.20:8123/api/hassio_ingress/MES6MuUJxiSP0TNXcWo0rarPmsJyCXiSQfskLgV-mOs/ingress.html” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.2 Safari/605.1.15”

172.30.32.2 - - [14/Mar/2026:09:23:52 +0100] “GET /pwa/library/js/snap.svg-min.js?25252354839= HTTP/1.1” 200 82497 “http://192.168.178.20:8123/api/hassio_ingress/MES6MuUJxiSP0TNXcWo0rarPmsJyCXiSQfskLgV-mOs/pwa/index.html” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.2 Safari/605.1.15”

Would really like to get Dresden Elektronik’s view on this.

As I see it, what is basically required to get KAJPLATS to work in deconz (and subsequently in API/Phoscon) is a capability to assign a ddf to the physical address (MAC) of the bulb. Or, somehow manipulate deconz to override the bulb’s manufacturer and device IDs, based on the physical address, before it maps a device to a ddf. The latter would probably be more suitable for the API.

IDK how Dresden’s take on this is. But to protect their customer’s investments made in deconz coordinated zigbee networks, they could consider this as a feature request to how deconz works.

deviceID: 269 = color, 268 = color temp

    {
        fingerprint: [
            {
                // https://github.com/Koenkk/zigbee2mqtt/issues/30211#issuecomment-3660923636
                modelID: "",
                manufacturerName: "",
                hardwareVersion: 1,
                dateCode: "",
                softwareBuildID: "",
                zclVersion: 8,
                applicationVersion: 0,
                endpoints: [
                    {ID: 1, profileID: 260, deviceID: 269, inputClusters: [0, 3, 4, 5, 6, 8, 768, 4096], outputClusters: []},
                    {ID: 242, profileID: 41440, deviceID: 97, inputClusters: [], outputClusters: [33]},
                ],
            },
        ],
        model: "KAJPLATS_RGB",
        vendor: "IKEA",
        description: "KAJPLATS color/white spectrum light",
        extend: [m.light({colorTemp: {range: [153, 555]}, color: true})],
    },
    {
        fingerprint: [
            {
                // https://github.com/Koenkk/zigbee2mqtt/issues/30211#issuecomment-3696471655
                modelID: "",
                manufacturerName: "",
                hardwareVersion: 1,
                dateCode: "",
                zclVersion: 8,
                applicationVersion: 0,
                endpoints: [
                    {ID: 1, profileID: 260, deviceID: 268, inputClusters: [0, 3, 4, 5, 6, 8, 768, 4096], outputClusters: []},
                    {ID: 242, profileID: 41440, deviceID: 97, inputClusters: [], outputClusters: [33]},
                ],
            },
        ],
        model: "KAJPLATS_CT",
        vendor: "IKEA",
        description: "KAJPLATS white spectrum light",
        extend: [m.light({colorTemp: {range: [153, 454]}})],
    },

For the API, it’s sure, it will be not possible, without model ID and manufacture name.
For deconz alone IDK, I think the application will not ask for thoses missing attribute if you don’t ask for them, so on zigbee side I don’t think it will be a problem.

But if you try to include a new device, the application will try to include this one too and you can have problems during the inclusion.

JulioVargas:

So issue is that deCONZ is returning some remembered value from some time in the past after a service restart, which happens to not be the most recent value before it went offline. Then sensor reconnects and things return to normal.

Yes exactly, I have another user whith the same issue (he don’t make poll, but ask for value at start), probably nothing to see, but you are using docker or classic OS ?

On my side I m using websocket, so I have only new value.

And looking your graph, the green line go to 23°C at restart, long time you haven’t this value, IDK why deconz have stored this one.

Here you have save databse delay

#define DB_HUGE_SAVE_DELAY  (60 * 60 * 1000) // 60 minutes
#define DB_LONG_SAVE_DELAY  (15 * 60 * 1000) // 15 minutes
#define DB_SHORT_SAVE_DELAY (1 *  60 * 1000) // 1 minute
#define DB_FAST_SAVE_DELAY (1 * 1000) // 1 second

But I have another question, if value are changing, why the last updated date is 6 days …
Can you share the complete device json ?

Smanar:

Even if the device disconnect, you can poll the API and have values.

Yes - I have a trigger in Zabbix that fires if value has not changed for 4h, this alerts me when sensor has dropped off. The “reachable” value in API takes a lot longer to change, hence using this trigger.
So issue is that deCONZ is returning some remembered value from some time in the past after a service restart, which happens to not be the most recent value before it went offline. Then sensor reconnects and things return to normal.

Even if the device disconnect, you can poll the API and have values.

I have a question about this topic

I just bought a second hand conbee II. But i dont know which firmware the main conbee is working on.

I work with proxmox and Z2M in a container. I want to migrate the container to another pve with using the new stick.

Do I really need the new firmware on the main stick?
Can I stop Z2M, insert the new bought stick and can I use this one then in another computer as the same coordinator?

Smanar:

so 6 days without report generaly mean battery issue.

Perhaps it’s not clear, but it’s nonsense, it was definitely reporting data because I am polling it from deCONZ API with Zabbix, this is in the graph.

But yes the jump is strange ^^.
Devices can take 1 hours before making their first real report (if temperature don’t move), idk what is the defaut value at start. But it’s strange you have all sensors starting to send report at exaclty same time, around 21h20, for me it’s not real reports.

Reading values from PWA API with Zabbix.

If I restart deCONZ [because of issues with Home Assistant, see other threads], the temperatures jump around implausibly:

Every temperature has suddenly jumped. The pressure and humidity behave the same.
Is this likely to be a deCONZ issue, or is it the sensors?

Der Datenpunkt deConz Gateway: alive steht auf false.

Ich kann meine Lampen etc. zwar noch steuern, aber die Rückmeldung dauert mehr oder weniger lang.

Was ich bisher versucht habe:

• Firmware update auf V2.32.5
• Firmware downgrade auf V2.31.2 Firmware 26720700
• WebSocket Port überprüft = 443
• Zigbee Kanal mehrmals gewechselt
• API erneuert
• Container/Instanz neu gestartet
• Datenpunkte der Instanz Verbindung gelöscht
• ioBroker Instanz zeigt 3x grün an)

Was kann ich noch machen, damit die die Verbindung wieder auf true wechselt?

Justin31415:

but I have an automation that transitions between colors as a mood light

And if you disable it ?

Because on logs you can see if the device is spammed, so it can be unresponsive, but you don’t need to re-include it to make it back.

You can see logs using the GUI, help/debug view, you can see something usefull with flag info+info_l2+error+error_l2.
More powerfull flags are APS+APS_l2 but not sure you will be able to understand message.

How do I check the logs. Happy to follow any existing posts, but a search turned up nothing much on the forum about this device.