Inovelli Blue series flooding Zigbee network

After some experimenting, I prefer disabling the values in Z2M rather that in HA. Example Z2M config for disabling all the extra entities: Zigbee2Mqtt Inovelli Config · GitHub

I have 28 switches installed now and am starting to see a slowdown. Going to try to this and see if it helps.

Is there a place we can go to see what each of these mean?

Also, is there a faster way to do this than one by one?

For your code, is it just a matter of copying it and putting it in the z2m configuration.yaml file that I’m currently using in my instance?

You will need to restart Z2M after copying and if you have an existing device_options: section in your configuration.yaml then you will need to merge it.

1 Like

OK so I did this for the 28 switches I’ve installed and I’ve noticed significantly less zigbee network traffic in logs. Also, my devices to seem more responsive.

So the winning combination seems to be disabled most entities (like I showed above) and setting these under the Reporting tab for each switch (wish it wasn’t a one by one process).

Hi group,
Any progress or updates from anyone experiencing this?

I’m trying to build a mesh with ~46 blue switches and about 75 Juno Connect Tunable wafers.
First 30 devices, things go fine. Then slowly I see more and more issues trying to add devices. By the time I’m at 70 devices, I can’t seem to add any additional devices reliably and I get severe network instability through home assistant).

I will say that groups and binding set up as the network is built work flawlessly (leading me to believe a coordinator/traffic issue).

I was having issues with the Sonnoff itead ZBDongle-E version. So I swapped it to the skyconnect usb dongle I have on hand (and tried to rebuild the mesh from scratch). This seems better, but I still have:

  1. Severe issues adding devices as the device count goes up.
  2. Black Box messages in Home assistant that my network has issues. Transmission tried 3x, failed, Network busy

Any input or thoughts. I realize it’s a big mesh, but I would think this should all work.

You could create a Hubitat app to update multiple switches at once based on parameter ID. The app would send a zigbee ‘SetPrivateCluster’ command. :slight_smile:

1 Like

I’m running Home Assistant :confused:

I’m not as familiar with HA, but I would assume they have a similar way to build an “extension / app” to do the same thing.

1 Like

I don’t run a large network of Zigbee devices, but I saw this new firmware update for coordinators mentioned performance improvements on large networks: Release Z-Stack_3.x.0_coordinator_20221226 · Koenkk/Z-Stack-firmware · GitHub

Thanks to @nathanfiscus who posted the recommendation in another thread.

This will remove the duplicate attribrutes in all the entities. Just uncheck the box for “Home Assistant legacy entity attributes” then submit. After you must do a complete Home Assistant restart. Only restarting Z2M will not work.

1 Like