deCONZ - Official thread

Configuration Zigbee
3088

Thanks, I can no longer count the number of pairing attempts ;-). Followed the wiki as well. Both temp and door sensors work again after many attempts.

3089

My recommendation: Activate Source Routing. That helped to stabalize the network rapidly.
You can find it under the panels menu.

3090

Regarding the Source Routing; is it of benefit if most of the routers (bulbs) are randomly on and off?

3091

Hi, I don’t think so. The routers are permanently connected and exchanging “life signs” frequently.
What you can do is playing with the hops and the lqi level but if you have a quite good network (the map shows green and yellow in worst case like the picture provided above) you can start with lqi level 170 and max 4 hops. That are the paramenters I use and its rock stable. In case of still facing issue then reduce the lqi level.
Thats how my source routing map looks like:

image
image1240×714 137 KB

3092

Please tell me if I have understood correctly:

Source Routing means the coordinator specifies the route before sending a packet. Without Source Routing packets wander through routers until they hit the target.

3093

Yep, that’s my understanding as well

3094

thank you for your help

3095

This still happenes, would be great to get some assistance!

Thanks!

3096

Which version of core are you running? There was some dependency change in 2022.4.3 regarding ZHA dependency zigpy-deconz that removed startup delays. Make sure you run at least the mentioned version.

3097

Did you ever figure this out?

I would have assumed reconnecting to a temporarily disconnected zigbee device would be an automatic task of the controller…

1 Like
3098

in the end, I changed the controller to CP2652p

3099

Hi all! Beta phase of 2022.5 starts tomorrow, if you have the time I’d appreciate if you try it out since there are quite some changes under the hood to the deCONZ integration.

I have a very good test coverage both on the library as well as on the integration but there always seem to be situations I haven’t covered.

Cheers!
Robban

1 Like
3100

Hello all!

Another month comes with another release log on Phoscon forum for the HA deCONZ integration

The beta has been cut and I wanted to share what’s changed since last release.

Released with Home Assistant 2022.5.0

Same as last month I’m laying the groundwork by improved design and rework under the hood making sure to keep up to date with all architectural improvements continually ongoing with the Python language and Home Assistant.

Improve typing and enable strict typing of platform

Move imports based on pydeconz v88 refactorization

Other changes

pydeconz releases

Try the beta out and report any bugs you experience!

/R

4 Likes
3101

Great work. Highly appreciated. Thumbs up. :+1:

3102

Hi @Robban ,

Thank you to share the complete information. It’s huge change apparently. Actualy using standard add-on version and I can test the beta but I don’t know how to install this and also revert in case of big issues.
Another question link to this add-on, DDF file can be imported in the add-on in case the device is not yet implemented ?

Checking how to do for beta installation without breaking my HA install

3103

My changes are for the integration. So it would just be to change your core to follow the beta track.

Regarding the addon I can’t give much help as I don’t use it myself.

1 Like
3104

@Robban First thanks for the hard work. Most of these changes are below the hood. I looked through all of the links and I must admit I find it hard to understand any of these many PRs. And maybe I should not need to care.
But one is marked as breaking change - the “Migrate On/Off Output” lights to switch.
My Zigbee switches from Hue are reported as switches already today and I actually use the new Switch as X feature to turn them to Lights (used customize before).

What does this change to the end user? It is marked as breaking change. What is the corrective action the end user has to do with this breaking change and who does it affect?

1 Like
3105

Yeah this is mostly code quality improvements to continue to make it easier to build upon the library and keep maintenance low. I share it so people can see what changes are happening and for myself to remember when I did what. But there are probably not that many that are interested in it.

The breaking change is that certain binary power control units are reported as lights today but will be reported as switches tomorrow. Im not even sure there exist any device that report as this type “On/Off Output” but it’s still a breaking change so better to communicate it. So only the platform domain will change.

There are so much information in the deConz project that I stumble across things like this from time to time.

2 Likes
3106

1 user (Krocko) found an error in the beta blocking the integration from loading. It would be nice with at least a couple of more trying it out.

3108

I have some problems after restarting Home Assistant. I have the ConBee II stick (RaspBerry PI 4).

Everything was working but since a few days ago I have problems after rebooting Home Assistant that some automations doesn’t work that are using a zigbee button:

Logger: homeassistant.components.automation.start_chromecast_audio_pc
Source: components/automation/__init__.py:591
Integration: Automatisering (documentation, issues)
First occurred: 07:35:48 (1 occurrences)
Last logged: 07:35:48

Got error 'No deconz_event tied to device "Slimme knop 2" found' when setting up triggers for Start chromecast audio pc

When I deactivate and activate the automation in Home Assistant it works directly. Are there more people that have this problem?

I’m using:

  • Home Assistant 2022.5.1
  • ConBee II firmware: 26660700 (version 2.15.03 / 21-4-2022)