The Conbee III is detected without errors. I have the same problem with Conbee II. Regardless of whether Home Assistant is running in a VM or directly with a Raspberry 4 (deCONZ 2.22.2). The problem also exists on an Unraid server with deCONZ Docker (deCONZ 2.24.3). My Conbee II and III currently only run without errors under Windows (deCONZ 2.25.1). Both Conbee have the latest firmware. I don’t know what to do.
With a deCONZ Image on Raspberry Pi 4 or VM both Conbee are working fine. The Problem is only with Home Assistant. The behavior must have changed since one of the last Home Assistant updates. I’m sure it worked before HA Update 2024.1.X. Something is blocking the Conbee at start from Home Assistant so that deCONZ or ZHA cannot use it or that the Conbee cannot set up a network.
There has been problems with the deconz Addon for years.
There are people having this problem all the time. The addon does not always see the serial port given by /dev/serial/by-id… links. It normally works with /dev/ttyACM0
If you have multiple usb serial devices using the ttyACM name it is unpredictable which is 0 and which is 1. Using deconz as addon is nothing but trouble and waiting for updates from upstream. I moved to a deconz running on a seperate debian machine so I can update from the vendors repo. Same with zwave-js, Unifi, and Zigbee2mqtt. I avoid using addons for anything from 3rd party. And I have much less trouble this way and more control.
Text editor addons, ssh, ESPHome makes sense as addons.
I have only one USB device, the Conbee. The deCONZ add-on is listed as an “Official add-on”. I therefore assume that these add-ons work correctly. I have no possibility to use “/dev/ttyACM0”. Home Assistant itself recognizes the Conbee via “/dev/serial/by-id” in the hardware overview, regardless of the deCONZ add-on. For me as normal user, this is not a fault of the deCONZ addon alone. It is a combination of Home Assistant and the USB detection “by-id”.
I know running deCONZ on a separate device works. I have tested this with a Raspberry Pi4 and the official deCONZ image. It works flawlessly. But I would like to save as many devices as possible and not outsource every service to external devices.
Hi folks,
I’m dealing with a sporadical problem of my IKEA switches (Remote Control N2 - the squared one with 4 buttons) in combination with the IKEA 35W LED-driver.
Setup: I’m running deconz with the PCBA from dresden-electronics on my Pi4 with about 40 devices - works fine since 2 years.
My remote control is within an own deconz-room together with the LED-driver and is requesting with push a specific scene (light brightness 10%).
Problem: sometimes, with pushing the button on the remote control, the light is not triggered. Pushing again is also not solving the problem. Waiting for about 30 or 40 seconds will heal the problem - but waiting to get the light working for halb an minute is not an option for me.
I immediatly saved the logs - can anybody tell me why the connection between those two devices is not working sometimes and how can I fix it?
Tank you!
21:28:59:412 0x60A423FFFEC5C7CA error APSDE-DATA.confirm: 0xE9 on task
21:28:59:413 max transmit errors for node 0x60A423FFFEC5C7CA, last seen by neighbors 316 s
21:29:02:821 [INFO] - Button 2002 - Remote Control N2, unicast to: 0x0000, endpoint: 0x01, cluster: ONOFF (0x0006), action: On, payload: None, zclSeq: 78
21:29:02:823 rule event /sensors/50/state/lastupdated: 0 -> 0
21:29:02:824 trigger rule 10 - Rule OFF
21:29:02:825 trigger rule 89 - Rule PUSHDIMDOWN_OFF
21:29:02:826 delayed group sending
21:29:02:852 delayed group sending
21:29:03:048 ZCL attribute report 0xF082C0FFFED2A010 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:29:04:136 [INFO] - Button 1002 - Remote Control N2, unicast to: 0x0000, endpoint: 0x01, cluster: ONOFF (0x0006), action: On, payload: None, zclSeq: 79
21:29:04:139 rule event /sensors/50/state/lastupdated: 0 -> 0
21:29:04:140 trigger rule 8 - Rule CALL_SCENE
21:29:04:141 trigger rule 82 - Rule PUSHDIMUP_ON
21:29:04:284 ZCL attribute report 0xF082C0FFFED2A010 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:29:05:679 [INFO] - Button 1001 - Remote Control N2, unicast to: 0x0000, endpoint: 0x01, cluster: LEVEL_CONTROL (0x0008), action: Move up (with on/off), payload: 0053, zclSeq: 80
21:29:05:681 rule event /sensors/50/state/lastupdated: 0 -> 0
21:29:05:683 trigger rule 83 - Rule PUSHDIMUP_START
21:29:05:928 ZCL attribute report 0xF082C0FFFED2A010 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:29:09:865 [INFO] - Button 1003 - Remote Control N2, unicast to: 0x0000, endpoint: 0x01, cluster: LEVEL_CONTROL (0x0008), action: Stop_ (with on/off), payload: None, zclSeq: 81
21:29:09:867 rule event /sensors/50/state/lastupdated: 0 -> 0
21:29:09:868 trigger rule 88 - Rule PUSHDIMUP_STOP
21:29:10:937 ZCL attribute report 0xF082C0FFFED2A010 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:29:15:504 0x50325FFFFEBF5898 error APSDE-DATA.confirm: 0xE9 on task
21:29:15:505 max transmit errors for node 0x50325FFFFEBF5898, last seen by neighbors 220 s
21:29:17:316 ZCL attribute report 0x00158D0002AFD8AB for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
21:29:17:804 0x60A423FFFEC5C7CA error APSDE-DATA.confirm: 0xE9 on task
21:29:17:805 max transmit errors for node 0x60A423FFFEC5C7CA, last seen by neighbors 335 s
21:29:18:008 max transmit errors for node 0x8CF681FFFE5179B2, last seen by neighbors 51 s
21:29:18:068 max transmit errors for node 0x8CF681FFFE5179B2, last seen by neighbors 51 s
21:29:18:128 max transmit errors for node 0x8CF681FFFE5179B2, last seen by neighbors 51 s
21:29:18:180 max transmit errors for node 0x8CF681FFFE5179B2, last seen by neighbors 51 s
21:29:18:236 max transmit errors for node 0x8CF681FFFE5179B2, last seen by neighbors 51 s
21:29:18:288 max transmit errors for node 0x8CF681FFFE5179B2, last seen by neighbors 51 s
21:29:30:592 [INFO] - Button 1002 - Remote Control N2, unicast to: 0x0000, endpoint: 0x01, cluster: ONOFF (0x0006), action: On, payload: None, zclSeq: 7
21:29:30:595 rule event /sensors/48/state/lastupdated: 0 -> 0
21:29:30:597 trigger rule 79 - Rule PUSHDIMUP_ON
21:29:30:598 trigger rule 87 - Rule CALL_SCENE
21:29:30:599 delayed group sending
21:29:30:832 ZCL attribute report 0x6C5CB1FFFEE014A8 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:29:30:903 0x3F44 seems to be a zombie recv errors 12
21:29:30:905 Node zombie state changed 0x8cf681fffe5179b2
21:29:31:143 discovery for zombie 0x2C1165FFFEB382FE dropped, last try was 188 seconds ago
21:29:32:583 discovery for zombie 0x8CF681FFFE5179B2 dropped, last try was 551 seconds ago
21:29:33:063 discovery for zombie 0x8CF681FFFE287114 dropped, last try was 342 seconds ago
21:29:33:544 discovery for zombie 0x0017880109A0E994 dropped, last try was 654 seconds ago
21:29:35:500 0x50325FFFFEBF5898 error APSDE-DATA.confirm: 0xE9 on task
21:29:35:501 max transmit errors for node 0x50325FFFFEBF5898, last seen by neighbors 240 s
21:29:37:812 0x60A423FFFEC5C7CA error APSDE-DATA.confirm: 0xE9 on task
21:29:37:813 max transmit errors for node 0x60A423FFFEC5C7CA, last seen by neighbors 355 s
21:29:45:052 ZCL attribute report 0x04CD15FFFE657EEE for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
21:29:45:948 Skip idle timer callback, too early: elapsed 948 msec
21:29:46:440 ZCL attribute report 0x8CF681FFFE5BAED5 for cluster: 0x0300, ep: 0x01, frame control: 0x38, mfcode: 0x0000
21:29:54:195 0x50325FFFFEBF5898 error APSDE-DATA.confirm: 0xE9 on task
21:29:54:196 max transmit errors for node 0x50325FFFFEBF5898, last seen by neighbors 259 s
21:29:56:508 0x60A423FFFEC5C7CA error APSDE-DATA.confirm: 0xE9 on task
21:29:56:509 max transmit errors for node 0x60A423FFFEC5C7CA, last seen by neighbors 373 s
21:29:56:616 ZCL attribute report 0x8CF681FFFE5BAED5 for cluster: 0x0008, ep: 0x01, frame control: 0x38, mfcode: 0x0000
21:30:00:381 [INFO] - Button 2002 - Remote Control N2, unicast to: 0x0000, endpoint: 0x01, cluster: ONOFF (0x0006), action: On, payload: None, zclSeq: 8
21:30:00:383 rule event /sensors/48/state/lastupdated: 0 -> 0
21:30:00:383 trigger rule 77 - Rule OFF
21:30:00:384 trigger rule 84 - Rule PUSHDIMDOWN_OFF
21:30:00:385 delayed group sending
21:30:00:544 ZCL attribute report 0x6C5CB1FFFEE014A8 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:30:01:736 [INFO] - Button 1002 - Remote Control N2, unicast to: 0x0000, endpoint: 0x01, cluster: ONOFF (0x0006), action: On, payload: None, zclSeq: 9
21:30:01:738 rule event /sensors/48/state/lastupdated: 0 -> 0
21:30:01:739 trigger rule 79 - Rule PUSHDIMUP_ON
21:30:01:740 trigger rule 87 - Rule CALL_SCENE
21:30:01:741 delayed group sending
21:30:01:756 delayed group sending
21:30:01:880 ZCL attribute report 0x6C5CB1FFFEE014A8 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:30:03:304 discovery for zombie 0x8CF681FFFE5179B2 dropped, last try was 581 seconds ago
21:30:03:812 [INFO] - Button 1001 - Remote Control N2, unicast to: 0x0000, endpoint: 0x01, cluster: LEVEL_CONTROL (0x0008), action: Move up (with on/off), payload: 0053, zclSeq: 10
21:30:03:813 rule event /sensors/48/state/lastupdated: 0 -> 0
21:30:03:814 trigger rule 78 - Rule PUSHDIMUP_START
21:30:03:950 ZCL attribute report 0x8CF681FFFE5BAED5 for cluster: 0x0300, ep: 0x01, frame control: 0x38, mfcode: 0x0000
21:30:04:076 ZCL attribute report 0x6C5CB1FFFEE014A8 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:30:04:503 0x604A seems to be a zombie recv errors 11
21:30:04:505 Node zombie state changed 0x50325ffffebf5898
21:30:05:024 [INFO] - Button 1003 - Remote Control N2, unicast to: 0x0000, endpoint: 0x01, cluster: LEVEL_CONTROL (0x0008), action: Stop_ (with on/off), payload: None, zclSeq: 11
21:30:05:027 rule event /sensors/48/state/lastupdated: 0 -> 0
21:30:05:028 trigger rule 80 - Rule PUSHDIMUP_STOP
21:30:09:068 ZCL attribute report 0x6C5CB1FFFEE014A8 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:30:16:304 0x60A423FFFEC5C7CA error APSDE-DATA.confirm: 0xE9 on task
21:30:16:305 max transmit errors for node 0x60A423FFFEC5C7CA, last seen by neighbors 393 s
21:30:16:504 0xD5CD seems to be a zombie recv errors 10
21:30:16:506 Node zombie state changed 0x60a423fffec5c7ca
21:30:17:145 ZCL attribute report 0x84B4DBFFFEF91AF7 for cluster: 0x0001, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:30:17:548 ZCL attribute report 0x04CD15FFFE657EEE for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
21:30:17:572 ZCL attribute report 0x04CD15FFFE657EEE for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
21:30:18:663 discovery for zombie 0x50325FFFFEBF5898 dropped, last try was 415 seconds ago
21:30:19:144 discovery for zombie 0x0C4314FFFEAC175C dropped, last try was 392 seconds ago
21:30:20:255 ZCL attribute report 0x0017880109A7C043 for cluster: 0x0001, ep: 0x01, frame control: 0x08, mfcode: 0x0000
21:30:33:544 discovery for zombie 0x8CF681FFFE287114 dropped, last try was 402 seconds ago
21:30:34:504 discovery for zombie 0x2C1165FFFEB382FE dropped, last try was 251 seconds ago
21:30:37:952 ZCL attribute report 0x04CD15FFFE657EEE for cluster: 0x0300, ep: 0x01, frame control: 0x18, mfcode: 0x0000
21:31:03:352 ZCL attribute report 0x04CD15FFFE657EEE for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
21:31:19:623 discovery for zombie 0x0017880109A0E994 dropped, last try was 91 seconds ago
21:31:22:399 ZCL attribute report 0x00158D000950DC45 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
21:31:22:425 ZCL attribute report 0x00158D000950DC45 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
21:31:22:467 ZCL attribute report 0x00158D000950DC45 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000
Conbee III is not supported in 2.22.2, support starts with 2.24,
Luckily it is released a week ago, including the ‘Fix Phoscon App Home Assistent add-on login and Ingress support.’, so lets hope the add-on will be updated soon.
FYI, I never experienced issues using the deConz add-on or UniFi on my Pi4. Had some stability things on the Pi3, but those where caused by hardware performance issues
Hello all!
Here comes another release log on Phoscon forum for the HA deCONZ integration
Development pace is a little slow at the moment as Im reworking one of my other integrations. Thankfully this integration is very stable and Im really happy with where it’s at for now. Even though I do have some things clean up as I’ve learned from the work on my other integrations.As
Here are the changes coming with Home Assistant 2024.2.0
- Support alternative model id of LIDL doorbell in deCONZ device triggers
- Fix lights reporting unsupported colormodes in deCONZ
Cheers!
/Robban
For feature requests of the integration post an issue at pydeconz github
I’m on Github Sponsors if you appreciate my work.
FYI:
Hopefully this will finally result in a new release (after several months) of the HA deCONZ addon.
=======================
v2.25.2-beta Pre-release
Contributors:
The following users have been contributing to this release. Thank you for that!
@BEskandari, @Smanar, @SwoopX, @Verteo, @andreas5232, @chbndrhnns, @ebaauw, @jmue, @manup, @noud-github, @retrography and @traschke
This release took a while to cook and address performance issues. If no new bugs are discovered the stable release should follow in two days.
Changes
Device Support
- DDF for Philips Signe floor lamp (4080248P9) #7562
- New
modelid
values for Hue smart button and Hue wall switch module #7567 - DDF add clone of Tuya temperature and humidy sensor (TZE200_locansqn) #7523
- DDF for Avatto TRV16 and TRV06 TRVs + add support for offset (_TZE200_TS0601) #7537
- DDF add Tuya water sensor clone (_TZ3000_kstbkt6a) #7549
- IKEA SOMRIG Shortcut Button support #7511
- DDF for Hue lightstrip plus (LCL006) #7521
- DDF for Xiaomi MHO-C401N temperature and humidity sensor #7528
- DDF for IKEA bulb E14 W opal 400lm #7527
- DDF Add support for Doorlock clone from Onesti Products AS #7534
- Add two new aliexpress manufacturers for Tuya TS0041 smart button #7520
- DDF for Osram Plug 01 #7522
- DDF for LIDL Livarno window blinds (Tuya) #7325
- IKEA Vallhorn motion sensor device request #7513
Enhancements
- Optimize idle timer and legacy device polling #7574
- Skip more legacy code for DDF devices #7571
- Optimize updatedLightNodeEndpoint() #7570
- Remove legacy FLS-PP (version 1) color XY quirk #7569
- DDF for Avatto TRV16 and TRV06 TRVs + add support for offset (_TZE200_TS0601) #7537
- Make Ikea Parasoll IAS Zone enrollment more robust #7560
Bug Fixes
- Fix macOS doesn’t auto connect to ConBee if already attached before starting deCONZ.
- Fix display of LQI values (note LQI text drawing is still slow).
- Fix regression from v2.24.1 that UI and Zigbee processing can become very slow with high CPU usage
- Fix battery spamming on Tuya smart button IH-663 #7509
- Fix CentraLite Motion Sensor-A detection #7565
- Fix non-functioning Aqara T1 open/close sensor #7559
- Fix setting
config/displayflipped
andconfig/externalsensortemp
for Bosch thermostat II #7517
Update available: deCONZ add-on 6.23.0
Bump deCONZ to 2.25.3
Just installed and working perfectly! One good news; I had in my installation 6 Aqara Temperature T1 sensors and these were working basically fine, with exception of one, that was unstable (periodically disappearing). I decided to add 3 more (eventually one to replace failing one), but for last few of days I was not able to add any of these new 3 sensors to deconz. After upgrade it took ~10 secs to recognize each of them almost instantly and add to my system! EXCELLENT ! ! !
I have several Xiaomi sensors , after restart of the addon, all entities are unavaible… the go to on/off state once there was a first movement
In previous update, after a restart of the addon, they kept the last state
After 2 days it looks stable and without any problems. New GUI, firmware has been updated.
Installing the new update (6.23.0) broke every sensor I had. Lights where working properly. I had to revert back to 6.22.0
Have you tried to make at search ? it will find them again. (Mine did)
that fixed it - and waiting a bit. Thanks a lot!
The 6.23 has a lot less CPU load for me. Went from 4% to 7% down to 1% to 2% load on my machine.
Yes, they obviously manged to execute the painting of the loi lines with less cpu usage. I always deactivated ir, which decreases the cpu usage by 3 to 4%. Now, I can let that activated
Would anyone know if it’s possible in DeConz to hide features of a light from HA?
I have a couple of tuya led controllers for RBGCCT and have connected them to cct only led strips. I would like to hide the rgb support.
The only way I think would be to make your own ddf to limit the functionality
Could you point me to a guide to how to do it?
Do I need to create a new DDF, or is it OK if I just edit the one that is loaded in deConz?