Ok, to make it a bit clearer.
Amongst some Aquara switches I use two of these Hue switches:
I configured them here:
But since Version 6.16 that doesn’t work anymore. Even I’m not able to catch an event in HA since then as it might have been my alternate solution to create an automation on order to copy the normal behavior.
But since 6.16 as well, I have this picture instead:
Here:
I can add my lights an then I can simply switch them on and off but I’m not able to manage the scenes.
There is a scene editor available at that stage but its deactivated and will not help anyway as all my scenes are already defined.
That’s my issue and finally to answer your question: Yes, I work with Phoscon 
So you are using a native deCONZ feature directly between the hue dimmer and the lights and Home Assistant is not involved with this at all.
I do not use that - all mine are doing functions through HA automations reacting on events so that is why I will not see this problem
It is nice to be made aware of the problem here on the HA forum. But to get support for this kind of problem it is best to subscribe to the deconz forum and raise the issues there. This is where the deconz developers are and where the Dresden Elektronik staff are. The traffic on that forum is low compared to the HA forum so it is easy to follow
OK thanks, I will do that
I’ve mentioned to the devs that there are multiple users experience issue with 2.19.1. Preferably you report unique issues separately to help getting this fixed
already opened an issue in the phoscon thread on GitHub
Great! Github is the proper place
Same for me, Deconz was crashing a few seconds after startup.
I had a backup for Deconz 6.15.0, and after restoring this version things started to work again.
I’ve now disabled the auto-update feature to avoid those issues in the future.
Hello!
About a couple of months ago I set up a zigbee network at my house based on Home Assistant and deCONZ.
I use a Con Bee II coordinator and a lot of SONOFF ZBMINI Zigbee Smart Switch.
The first month everything worked well, but now every day something from ZBMINI becomes unavailable in the Home Assistant interface.
In the logs, the device is marked as a zombie.
Only a physical reboot ZBMINI helps to restore work.
What can be done in this situation?
Vendor: dresden elektronik
Product: Con Bee II
Version: 2.19.01 / 19.09.2022
Firmware: 26780700
deCONZ log
07:34:37:790 05 RSSI dB (?) 169 (0x00A9)
07:34:37:791 64 lift 0 (100%)
07:34:37:792 64 smoke/gas density 0 (0x00)
07:34:37:793 08 unknown 4386 (0x1122)
07:34:37:794 07 unknown 0 (0x0000000000000000)
07:34:37:795 09 unknown 2816 (0x0B00)
07:34:41:021 GW firmware version is up to date: 0x26780700
07:34:46:440 discovery for zombie 0x00124b0024c5d97d dropped, last try was 127 seconds ago
07:34:56:999 discovery for zombie 0x00124b0024c5d97d dropped, last try was 137 seconds ago
07:35:00:839 discovery for zombie 0x00124b0024c195ac dropped, last try was 274 seconds ago
07:35:08:082 0x00124B0024C1A0B4 error APSDE-DATA.confirm: 0xE9 on task
07:35:12:783 0x00124B0024C1F82B error APSDE-DATA.confirm: 0xE1 on task
07:35:15:473 0x00124B0024C1A5BB error APSDE-DATA.confirm: 0xE9 on task
07:35:20:999 discovery for zombie 0x00124b0024c5d97d dropped, last try was 161 seconds ago
07:35:34:439 discovery for zombie 0x00124b0024c195ac dropped, last try was 307 seconds ago
07:35:44:520 discovery for zombie 0x00124b0024c5d97d dropped, last try was 185 seconds ago
07:35:48:359 discovery for zombie 0x00124b0024c195ac dropped, last try was 322 seconds ago
07:35:54:807 0x00124b0026b6cb90 found group 0xFFF0
07:36:00:052 0x00124b0024c1a5bb found group 0xFFF0
07:36:04:572 0x00124b0022675c37 found group 0xFFF0
07:36:45:960 discovery for zombie 0x00124b0024c5d97d dropped, last try was 246 seconds ago
07:36:48:840 discovery for zombie 0x00124b0024c195ac dropped, last try was 16 seconds ago
07:37:02:279 discovery for zombie 0x00124b0024c5d97d dropped, last try was 263 seconds ago
07:37:09:800 0x00124b0024c136e9 found group 0xFFF0
07:37:18:163 0x00124B0026B6CB90 error APSDE-DATA.confirm: 0xE9 on task
07:37:22:920 discovery for zombie 0x00124b0024c195ac dropped, last try was 50 seconds ago
07:37:47:142 ZCL attribute report 0x00124B0022676DEE for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
07:37:47:631 ZCL attribute report 0x00124B0022674990 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
07:37:47:762 ZCL attribute report 0x00124B0022675C37 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
07:37:48:157 ZCL attribute report 0x00124B0022679F0F for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
07:37:48:273 ZCL attribute report 0x00124B0022676976 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
07:37:56:039 discovery for zombie 0x00124b0024c5d97d dropped, last try was 316 seconds ago
07:38:16:199 discovery for zombie 0x00124b0024c5d97d dropped, last try was 337 seconds ago
07:38:23:355 0x00158D000757E793 error APSDE-DATA.confirm: 0xE1 on task
07:38:40:692 ZCL attribute report 0x00158D000757E793 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
07:38:40:693 0x00158D000757E793 extract Xiaomi special attribute 0xFF01
07:38:40:694 03 Device temperature 33 °C
07:38:40:695 05 RSSI dB (?) 165 (0x00A5)
07:38:40:696 64 lift 0 (100%)
07:38:40:697 64 smoke/gas density 0 (0x00)
07:38:40:698 08 unknown 4386 (0x1122)
07:38:40:699 07 unknown 0 (0x0000000000000000)
07:38:40:700 09 unknown 2816 (0x0B00)
07:38:41:020 GW firmware version is up to date: 0x26780700
07:38:44:520 discovery for zombie 0x00124b0024c195ac dropped, last try was 132 seconds ago
07:38:50:759 discovery for zombie 0x00124b0024c5d97d dropped, last try was 371 seconds ago
07:38:57:479 discovery for zombie 0x00124b0024c195ac dropped, last try was 145 seconds ago
07:38:59:879 discovery for zombie 0x00124b0024c5d97d dropped, last try was 380 seconds ago
07:39:09:479 discovery for zombie 0x00124b0024c195ac dropped, last try was 157 seconds ago
07:39:14:759 discovery for zombie 0x00124b0024c5d97d dropped, last try was 395 seconds ago
07:39:15:054 0x00124b0024c1f6df found group 0xFFF0
07:39:28:119 0x00124B0024C19EFD error APSDE-DATA.confirm: 0xE9 on task
07:39:36:359 discovery for zombie 0x00124b0024c5d97d dropped, last try was 417 seconds ago
07:39:43:079 discovery for zombie 0x00124b0024c195ac dropped, last try was 190 seconds ago
07:39:50:315 0x00124b0026b6c8fd found group 0xFFF0
07:39:55:793 ZCL attribute report 0x00158D0006EBDDD2 for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
07:39:55:794 0x00158D0006EBDDD2 extract Xiaomi special attribute 0xFF01
07:39:55:795 03 Device temperature 29 °C
07:39:55:796 05 RSSI dB (?) 169 (0x00A9)
07:39:55:797 64 lift 0 (100%)
07:39:55:798 64 smoke/gas density 0 (0x00)
07:39:55:799 08 unknown 4386 (0x1122)
07:39:55:800 07 unknown 0 (0x0000000000000000)
07:39:55:801 09 unknown 2816 (0x0B00)
07:39:56:999 discovery for zombie 0x00124b0024c195ac dropped, last try was 204 seconds ago
07:40:20:520 discovery for zombie 0x00124b0024c195ac dropped, last try was 228 seconds ago
172.30.32.2 - - [30/Oct/2022:07:40:36 +0500] "GET /ingress.html HTTP/1.1" 304 0 "http://192.168.165.5:8123/core_deconz" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36"
07:40:54:119 discovery for zombie 0x00124b0024c195ac dropped, last try was 261 seconds ago
07:40:54:599 discovery for zombie 0x00124b0024c5d97d dropped, last try was 60 seconds ago
07:41:10:919 discovery for zombie 0x00124b0024c5d97d dropped, last try was 76 seconds ago
07:41:24:359 discovery for zombie 0x00124b0024c195ac dropped, last try was 292 seconds ago
07:41:51:079 remove dead link for (46DC, B2D6)
07:41:54:599 discovery for zombie 0x00124b0024c195ac dropped, last try was 322 seconds ago
07:41:55:079 discovery for zombie 0x00124b0024c5d97d dropped, last try was 120 seconds ago
07:42:24:680 remove dead link for (8B2A, 257F)
07:42:41:020 GW firmware version is up to date: 0x26780700
07:42:47:134 ZCL attribute report 0x00124B0022676DEE for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
07:42:47:627 ZCL attribute report 0x00124B0022674990 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
07:42:47:779 ZCL attribute report 0x00124B0022675C37 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
07:42:48:157 ZCL attribute report 0x00124B0022679F0F for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
07:42:48:279 ZCL attribute report 0x00124B0022676976 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
07:42:58:630 ZCL attribute report 0x00124B002520125C for cluster: 0x0001, ep: 0x01, frame control: 0x18, mfcode: 0x0000
07:42:59:165 Bind response success for 0x00124b002520125c ep: 0x01 cluster: 0x0000
07:42:59:399 discovery for zombie 0x00124b0024c5d97d dropped, last try was 185 seconds ago
07:43:11:722 ZCL attribute report 0x00158D00047BAE9C for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
07:43:11:723 0x00158D00047BAE9C extract Xiaomi special attribute 0xFF01
07:43:11:724 01 battery 3015 (0x0BC7)
07:43:11:725 03 Device temperature 28 °C
07:43:11:726 04 unknown 5032 (0x13A8)
07:43:11:727 05 RSSI dB (?) 19 (0x0013)
07:43:11:728 06 LQI (?) 4294967296 (0x0100000000)
07:43:11:729 08 unknown 518 (0x0206)
07:43:11:730 0a Parent NWK 0 (0x0000)
07:43:11:730 64 on/off 0
07:43:12:839 discovery for zombie 0x00124b0024c195ac dropped, last try was 37 seconds ago
07:43:22:919 discovery for zombie 0x00124b0024c5d97d dropped, last try was 208 seconds ago
07:43:26:760 discovery for zombie 0x00124b0024c195ac dropped, last try was 51 seconds ago
07:44:00:057 0x00124b0024c19efd found group 0xFFF0
07:44:04:588 0x00124b0024c5d502 found group 0xFFF0
07:44:10:440 discovery for zombie 0x00124b0024c195ac dropped, last try was 94 seconds ago
I have a dresden ConBeeII stick running on a generic x86 box with a USB extension cable. It is no longer reporting RSSI and LQI.
Should I assume that the ConBee II stick is no longer working properly?
Sorry. This thread is for deCONZ users. You seem to be using using ZHA.
Hello all!
Time flied this month as we’re closing in on first Wednesday of the month comes another release log on Phoscon forum for the HA deCONZ integration
Here are the changes coming with Home Assistant 2022.11.0
Continuing the rewrite of the UniFi integration I get a lot of inspiration on how to improve and expand on deCONZ as well so there are gains to be seen in the future! I will try to do some small improvements at the very least with next release as well, but my prio is on UniFi for some more time. My main hope is that deCONZ will improve stability so I can implement proper support for the Hue Tap Dial Switch.
Cheers!
/Robban
- Improve sensor entity descriptions
- Improve binary sensor entity descriptions
- Add presence duration number entity by scop
- Device trigger for Lidl Silvercrest button by Jeinwag
For feature requests of the integration post an issue at pydeconz github
1 Like
But it doesn’t seem that somebody is interested in that 
Sorry! I’m not part of that support structure. Hope you get some support soon!
Which github odjur is it?
There are multiple similar threads as well as github issues. I pointed out in the dev channel that more people are affected by similar peoblems. Don’t know if that will help escalate anything though
Hi Kenneth, I’d prefer to manage the Hue Switches from HA as well as I do with all my other switches.
But I have difficulties to catch the events these button are sending.
The event listener in the developer tools doesn’t show an event when I press the buttons.
Can you help me out with the event code I have to listen to?
Hi, interestingly I detected today that for this dimmer swith, I added some lights in the new switch editor, I have an entity in HA:
That turns to on/off according to the button press.
The swith is shown as a group! weird
This is normal
When you create a group of lights/switches in Deconz, Deconz create a light entity for the group and this gets loaded by Home Assistant.
Deconz automatically suggests creating a group when you add a dimmer. The idea is that you add a dimmer to a room and then most users of Deconz (as a stand alone product) will want it to control all lights in a room. It is well through of by Dresden Elektronik
There are no entities create for a remote control in HA. A dimmer cannot be on or off. It sends momentary events when you press or release a button and or hold it down.
To see the events go to Developer Tools.
Then in Listen to Events at the bottom half you have to type “deconz_event” and click the Start Listening
And then you see the events when you press the buttons on the dimmer.
Note that clicking the link on the right only add deconz_event to the event data at the top for sending events. It would actually be better user friendly UI if it also populated the listener field.
But you have to type “deconz_event” manually
The name of the device sending the events is the name you gave the device in Phoscon. And the events are 4 digit codes that are predictable and easy to use.
Thanks Kenneth,
that’s exactly what I did. Ok then its clear that the hue switch doesn’t send events for the time being. Let’s see if that can be repaired.