deCONZ - Official thread

Configuration Zigbee
3594

Deconz devs are currently investigating the add-on issue

1 Like
3595

Hi manup from dresden elektronik here,

I’m trying to recreate the issues seen in #3323.

The mentioned missing OTA download script was brought back in the last deCONZ beta version (but I’d propose to remove calling this from the add-on since the script is highly outdated and not useful anymore).

I think the 404 seen in the screenshots of the PR might be a browser/nginx cache thing but not actual problem with the new deCONZ version, but to verify this I need to be able to test it and build the add-on.

Right now the the biggest issue is that I can’t get the add-on to be build locally for testing after trying for hours, there are various described approaches in the docs, but so far none worked. Any ideas how to build/test deCONZ add-on locally would be highly appreciated.

3 Likes
3596

Hi Manup, thank you for picking this up! :+1:
Hopefully no reaction doesn’t mean no one contacted you (directly) to help you?
I wish I could help you, but unfortunately I don’t have any knowledge about it.
Let’s hope this will be solved soon.

1 Like
3597

I haven’t received input yet. But magical things happened in my lokal VirtualBox HA OS setup, my last test was trying to install deCONZ v2.24.2 via a personal add-on repository https://github.com/manup/ha_addons_test/tree/main/deconz

I thought this didn’t work since the installation spinner was going on “forever” and later a installation failed message appeared saying to check super visor logs, which seem to be empty (or I looked at the wrong logs).

However the add-on with the new deCONZ version did eventually install. And I can now debug with that version. Currently also trying to install the same setup in the company Proxmox HA setup so developers of the Phoscon App can have a closer look directly.

3 Likes
3598

Small update, I think we found the remaining issues now in our test setup.
We’ll make some final tests tomorrow and then prepare a fixup release v2.24.3 which can be bumped into the official channel.

image
image1263×682 79.1 KB

7 Likes
3599

v2.24.3

Repository: dresden-elektronik/deconz-rest-plugin · Tag: v2.24.3 · Commit: 601da43 · Released by: manup

Changes

  • Fix Phoscon App Home Assistent add-on login and Ingress support.

Back ported fixes from v2.25.0-beta and v2.25.1-beta

  • Fix missing bash scripts in .deb package.
  • Fix missing deCONZ start menu icon on Linux.
  • Improved application based source routing.
  • Fix filter ZGP command duplication filtering when more than one frame counter is on air
  • Fix wrong sign applying config/offset to state/measured_value #7389
  • Stop unnecessary attribute read requests for many Philips/Signify devices #7384
  • Restore parse functions for maufacturername and modelid #7405
  • Fix LIDL smart plug consumption value multiplier #7361
  • Speed up first time loading of DDF for former legacy lights #7446
  • Fix generated scene names #7461
  • Force classic join/re-join for devices #7497
    —

Hopefully the Home Assistant Add-on: deCONZ will be release soon. :partying_face:

3 Likes
3600

Awesome! Good job solving the addon issue

1 Like
3601

Cool! Awesome job fixing the bugs! Is it possible to update now or do we have to wait for HA to release it first?

3602

Waiting in excitement. good job with the trouble shooting.

3603

Hi,

i don’t know if I’m in the right place. Recently I have the problem that the Conbee in Home Assistant with deCONZ Addon and integration no longer gets a connection to a ZigBee channel. It is also not possible to change channels. I always get in the deCONZ addon log:

17:04:01:194 Connection to network could not be re-established try=1
17:04:02:008 COM: /dev/serial/by-id/usb-dresden_elektronik_ConBee_III_...
17:04:06:443 Attempt to reconnect to the network try=2
17:04:11:443 Attempt to reconnect to the network try=3
17:04:13:006 COM: /dev/serial/by-id/usb-dresden_elektronik_ConBee_III_...
17:04:16:443 Connection to the network could not be re-established try=4
17:04:21:444 Connection to the network could not be re-established try=5
17:04:26:443 Failed to reconnect to the network try=6
17:04:27:007 COM: /dev/serial/by-id/usb-dresden_elektronik_ConBee_III_...

I can reproduce the problem in an unraid Home Assistant VM and with a Raspberry 4. Both with Conbee 2 and Conbee 3 and an existing Home Assistant installation as well as with a completely new installation.

There are no errors in the log files of Home Assistant itself. Only in the log of the deCONZ addon. I have also tested several USB ports without success. I am using Home Assistant 2024.1.5 and unfortunately I don’t know what else I can do. Resetting the Conbee doesn’t help either. Does anyone here have any ideas?

3604

On Windows 11 with deCONZ and Phoscon APP all is working fine. The Probleme is only with Home Assistant.

3605

I’m not sure, but I think, that Conbee III is not supported. Addon is still one year old version and we are waiting for a newer one.

3606

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.

3607

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.

3608

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.

3609

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.

3610

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
3611

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

3612

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

Cheers!

/Robban

For feature requests of the integration post an issue at pydeconz github

I’m on Github Sponsors if you appreciate my work.

1 Like
3613

FYI:
Hopefully this will finally result in a new release (after several months) of the HA deCONZ addon. :thinking:

=======================
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 and config/externalsensortemp for Bosch thermostat II #7517
2 Likes