deCONZ - Official thread

Will there be any other update past 7.0.0 I still cannot update it without losing my dimmer switches and HA reminds me often to update to 7.0.0.

Hi everyone.
The upcoming Shelly Gen 4 devices will support Zigbee - will there be support for Shelly devices in Deconz? Anybody aware of this?

My use case would be to use a Shelly Gen4 as a button-dimmer to control a deconz light via Zigbee directly.
(I know there I could use the Shelly via Wifi, then control a Zigbee light through Home Assistant, but dimming is much easier directly with deconz…).

Thank you

Documentation is now up on the Shelly KB: Shelly 1 Mini Gen4

Promising :slight_smile: :

  • Press 5 consecutive times to switch the Device from Matter firmware (default) to Zigbee.
  • Press 3 consecutive times to put the Device in Zigbee inclusion mode. The Device stays in this mode for 2 minutes and you can find it in the Home Automation platform through the Zigbee Hub.

Sry for the late reply, i used this ddf Aqara smart smoke detector - JY-GZ-01AQ · Issue #5864 · dresden-elektronik/deconz-rest-plugin · GitHub

Please can anyone help.

I cannot get past 6.23.0

When 7.0.0 was released all my hue dimmer switches no longer responded.

I tried my best to update tried changing blueprints for them to respond and nothing happened they just became unresponsive until rolling back to 6.23.0

I’ve come home from work tonight to notice that 8.0.0 was available and I thought I’d give it a bash and updating.

Backed up and after the update the switches just like before no longer respond to turning on lights after button presses.

I’ve again had to fall back to 6.23.0.

thanks for the report – I am in the same situation as you for v7 with Hue Wall Switch Modules. There is no deConz version update between the v7 and v8 version of the add-on. That’s where the problem lies. Hue works ok in version 2.27 of deConz itself, and there is a problem with 2.28. 2.29 is in beta and i hope that that will solve the issue.

1 Like

So do you think this is a Hue issue rather than Deconz?

I stopped using the Hue Bridge when I migrated to ConbeeII and never really looked back.

Hmm…I have two Hue switches and no issues with version 7. I stopped the phoscon config and watch for the events. That works as expected

Thanks

So are you using any blueprints for using the switches to ensure they dim?

It’s odd that the upgrades stop my switches from responding yet rolling back restores them

It’s not a Hue issue. As far as I can tell it’s a DeConz issue, but the coordinator software, which is on version 2.2x.

The upgrade from v7 to v8 is for the add-on which allows for communication between HA and the coordinator software (plus a bunch of other things). The coordinator software did not change in this upgrade.

On the DeConz issue tracker in GitHub a problem appeared with some Hue switches and is claimed to be resolved in the version 2.27 coordinator software. But for me there is a problem on upgrade. Maybe it would be enough to re-add the devices, but this means opening up my light switches…

1 Like

Great response appreciated it and I understand completely.

I have mounted my dimmers over switches so I really don’t want the hassle of adding lights back that have already been paired.

From your research what do you think resolves it for us?

Thank you

Hi there,
i got a problem with onboarding a Tuya flower sensor (Zigbee Version) like this from AliExpress

I have a HA Setup with the CONBEE II Stick and use it for ~ 25 Devices since a few years.

Now i want to add the flower sensor, but i dont get it working.

At the DeConz Dashboard i start the pairing mode for new sensors:


After this i pressed the pairing button on the sensor for a few seconds till it starts to flash blue.
After ~2 sec the flashing stops and the led lights up continuously for ~3 seconds. then the led will turns off.

There is no successfully paired message and the Dashboard will not show the new sensor.

If i check the DeConz Log, i can see the pairing (i think it is, please correct me if im wrong):

172.30.32.2 - - [18/Apr/2025:22:03:06 +0200] "GET /api/6A8B2E5FC1/sensors?_=1745006526910 HTTP/1.1" 200 15767 "http://192.168.2.40:8123/api/hassio_ingress/uFxb-NbxvF3rRlf4y8fRNLL5muTjDLWeXY5kAc2A9o0/pwa/devices-sensors2.html?_v=8af8975ffa0c93c20a8c5db60e99f4a70b44c8c5,3,5,22&gwid=00212EFFFF053E81" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0"
172.30.32.2 - - [18/Apr/2025:22:03:06 +0200] "GET /api/6A8B2E5FC1/sensors/new?_=1745006526911 HTTP/1.1" 200 32 "http://192.168.2.40:8123/api/hassio_ingress/uFxb-NbxvF3rRlf4y8fRNLL5muTjDLWeXY5kAc2A9o0/pwa/devices-sensors2.html?_v=8af8975ffa0c93c20a8c5db60e99f4a70b44c8c5,3,5,22&gwid=00212EFFFF053E81" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0"
172.30.32.2 - - [18/Apr/2025:22:03:07 +0200] "GET /api/6A8B2E5FC1/sensors/new?_=1745006526912 HTTP/1.1" 200 32 "http://192.168.2.40:8123/api/hassio_ingress/uFxb-NbxvF3rRlf4y8fRNLL5muTjDLWeXY5kAc2A9o0/pwa/devices-sensors2.html?_v=8af8975ffa0c93c20a8c5db60e99f4a70b44c8c5,3,5,22&gwid=00212EFFFF053E81" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0"
172.30.32.2 - - [18/Apr/2025:22:03:07 +0200] "GET /api/6A8B2E5FC1/sensors/new?_=1745006526913 HTTP/1.1" 200 32 "http://192.168.2.40:8123/api/hassio_ingress/uFxb-NbxvF3rRlf4y8fRNLL5muTjDLWeXY5kAc2A9o0/pwa/devices-sensors2.html?_v=8af8975ffa0c93c20a8c5db60e99f4a70b44c8c5,3,5,22&gwid=00212EFFFF053E81" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0"
172.30.32.2 - - [18/Apr/2025:22:03:08 +0200] "GET /api/6A8B2E5FC1/sensors/new?_=1745006526914 HTTP/1.1" 200 32 "http://192.168.2.40:8123/api/hassio_ingress/uFxb-NbxvF3rRlf4y8fRNLL5muTjDLWeXY5kAc2A9o0/pwa/devices-sensors2.html?_v=8af8975ffa0c93c20a8c5db60e99f4a70b44c8c5,3,5,22&gwid=00212EFFFF053E81" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0"
         ...     (0xA4C138A115488B3F / 0x7E48)
22:00:29:701 ZCL attribute report 0xA4C138A115488B3F for cluster: 0x0000, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
22:00:29:824 FP indication 0x0104 / 0xEF00 (0xA4C138A115488B3F / 0x7E48)
22:00:29:824                       ...     (0xA4C138A115488B3F / 0x7E48)
22:00:29:947 FP indication 0x0104 / 0x0000 (0xA4C138A115488B3F / 0x7E48)
22:00:29:947                       ...     (0xA4C138A115488B3F / 0x7E48)
22:00:29:947 ZCL attribute report 0xA4C138A115488B3F for cluster: 0x0000, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
22:00:30:843 FP indication 0x0104 / 0x000A (0xA4C138A115488B3F / 0x7E48)
22:00:30:843                       ...     (0xA4C138A115488B3F / 0x7E48)
22:00:31:336 FP indication 0x0104 / 0xEF00 (0xA4C138A115488B3F / 0x7E48)
22:00:31:336                       ...     (0xA4C138A115488B3F / 0x7E48)
22:00:31:921 DB SELECT manufacturername FROM nodes WHERE mac LIKE '04:cd:15:ff:fe:5d:54:49%' COLLATE NOCASE: _TZ3210_r0xgkft5
22:00:38:920 send permit join, duration: 0
22:00:39:072 Search sensors done
22:00:40:658 Websocket disconnected 127.0.0.1:59662, state: 0, close-code: 1000, reason: 
22:00:42:193 New websocket 127.0.0.1:35214 (state: 3) 
22:00:45:468 Websocket disconnected 127.0.0.1:35214, state: 0, close-code: 1000, reason: 
22:00:53:073 ZCL attribute report 0x04CD15FFFE5D5449 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
22:01:12:029 ZCL attribute report 0x04CD15FFFE5D5449 for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
22:01:52:855 Invalid admin password hash
22:01:53:651 Invalid admin password hash
22:01:56:171 created username: 6A8B2E5FC1, devicetype: Phoscon#B2304x1288
22:01:57:361 New websocket 127.0.0.1:44910 (state: 3) 
22:02:06:122 Websocket disconnected 127.0.0.1:44910, state: 0, close-code: 1000, reason: 
22:02:07:238 New websocket 127.0.0.1:46490 (state: 3) 
22:02:27:921 send permit join, duration: 65
22:02:30:246 ZCL attribute report 0xA4C13851510BB3AF for cluster: 0x0001, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
22:02:36:921 DB SELECT manufacturername FROM nodes WHERE mac LIKE '04:cd:15:ff:fe:5d:54:49%' COLLATE NOCASE: _TZ3210_r0xgkft5
22:02:46:921 DB SELECT manufacturername FROM nodes WHERE mac LIKE '04:cd:15:ff:fe:5d:54:49%' COLLATE NOCASE: _TZ3210_r0xgkft5
22:02:56:921 DB SELECT manufacturername FROM nodes WHERE mac LIKE '04:cd:15:ff:fe:5d:54:49%' COLLATE NOCASE: _TZ3210_r0xgkft5
22:03:02:766 ZCL attribute report 0x00158D0002C8DC1B for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
22:03:02:797 ZCL attribute report 0x00158D0002C8DC1B for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
22:03:02:803 ZCL attribute report 0x00158D0002C8DC1B for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
22:03:06:920 DB SELECT manufacturername FROM nodes WHERE mac LIKE '04:cd:15:ff:fe:5d:54:49%' COLLATE NOCASE: _TZ3210_r0xgkft5
22:03:07:121 0xA4C138A115488B3F 0x7E48 nwk changed to 0xAB9B
22:03:07:146 device announce 0xA4C138A115488B3F (0xAB9B) mac capabilities 0x80
22:03:07:146 set fast probe address to 0xA4C138A115488B3F (0xAB9B)
22:03:07:146 FP indication 0x0000 / 0x0013 (0xA4C138A115488B3F / 0xAB9B)
22:03:07:146                       ...     (0xA4C138A115488B3F / 0xAB9B)
22:03:07:146 device announce 0xA4C138A115488B3F (0xAB9B) mac capabilities 0x80
22:03:07:146 DEV Tick.Join: event/device.anounce
22:03:07:146 DEV Tick: fast poll 0xA4C138A115488B3F, mac capabilities: 0x80
22:03:08:020 [1] get node descriptor for 0xa4c138a115488b3f
22:03:08:020 ZDP get node descriptor for 0xAB9B
22:03:08:216 FP indication 0x0000 / 0x8002 (0xA4C138A115488B3F / 0xAB9B)
22:03:08:216                       ...     (0xA4C138A115488B3F / 0xAB9B)
22:03:08:216 ZDP indication search sensors 0xA4C138A115488B3F (0xAB9B) cluster 0x8002
22:03:08:216 ZDP indication search sensors 0xA4C138A115488B3F (0xAB9B) clear timeout on cluster 0x8002
22:03:08:222 [2] get active endpoints for 0xa4c138a115488b3f
22:03:08:222 ZDP get active endpoints for 0xAB9B
22:03:08:449 FP indication 0x0000 / 0x8005 (0x172.30.32.2 - - [18/Apr/2025:22:03:08 +0200] "GET /api/6A8B2E5FC1/sensors/new?_=1745006526915 HTTP/1.1" 200 32 "http://192.168.2.40:8123/api/hassio_ingress/uFxb-NbxvF3rRlf4y8fRNLL5muTjDLWeXY5kAc2A9o0/pwa/devices-sensors2.html?_v=8af8975ffa0c93c20a8c5db60e99f4a70b44c8c5,3,5,22&gwid=00212EFFFF053E81" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0"
172.30.32.2 - - [18/Apr/2025:22:03:09 +0200] "GET /api/6A8B2E5FC1/sensors/new?_=1745006526916 HTTP/1.1" 200 32 "http://192.168.2.40:8123/api/hassio_ingress/uFxb-NbxvF3rRlf4y8fRNLL5muTjDLWeXY5kAc2A9o0/pwa/devices-sensors2.html?_v=8af8975ffa0c93c20a8c5db60e99f4a70b44c8c5,3,5,22&gwid=00212EFFFF053E81" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0"
172.30.32.2 - - [18/Apr/2025:22:03:09 +0200] "GET /api/6A8B2E5FC1/sensors/new?_=1745006526917 HTTP/1.1" 200 32 "http://192.168.2.40:8123/api/hassio_ingress/uFxb-NbxvF3rRlf4y8fRNLL5muTjDLWeXY5kAc2A9o0/pwa/devices-sensors2.html?_v=8af8975ffa0c93c20a8c5db60e99f4a70b44c8c5,3,5,22&gwid=00212EFFFF053E81" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0"
172.30.32.2 - - [18/Apr/2025:22:03:10 +0200] "GET /api/6A8B2E5FC1/sensors/new?_=1745006526918 HTTP/1.1" 200 32 "http://192.168.2.40:8123/api/hassio_ingress/uFxb-NbxvF3rRlf4y8fRNLL5muTjDLWeXY5kAc2A9o0/pwa/devices-sensors2.html?_v=8af8975ffa0c93c20a8c5db60e99f4a70b44c8c5,3,5,22&gwid=00212EFFFF053E81" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0"
172.30.32.2 - - [18/Apr/2025:22:03:10 +0200] "GET /api/6A8B2E5FC1/sensors/new?_=1745006526919 HTTP/1.1" 200 32 "http://192.168.2.40:8123/api/hassio_ingress/uFxb-NbxvF3rRlf4y8fRNLL5muTjDLWeXY5kAc2A9o0/pwa/devices-sensors2.html?_v=8af8975ffa0c93c20a8c5db60e99f4a70b44c8c5,3,5,22&gwid=00212EFFFF053E81" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0"

i think the problem is here:

22:01:52:855 Invalid admin password hash
22:01:53:651 Invalid admin password hash

Does any one know how to handle this issue?

I opened the sensor to check for serial numer or something else:


Model: ZT5
Product Number: 2.01.03.01547
Seriel Number: 10018552001475
FCC ID: 2ANDL-ZT5

My Gateway (Version 2.28.1) is running the Firmware Version 26720700

Just to flag that there is a new version od deConz add on — 8.1.0, which contains the new version of deConz — 2.29.5. This then comes with a new version of firmware for Conbee III, which must be upgraded separately.

I have installed all these and my Hue Wall Switch Modules work for the first time since deConz add on 6.23.

2 Likes

Thanks I’ll give it a shot

Are you updating the add on first?

Ah just to add it seems like all is back to normal and I’m fully up to date

Thanks

Since I updated to 2.29.5 my cpu load rose from 2 to 4%. So I reverted the update and I’m back to normal. Anyone else experienced this?