Homey Community Forum

Homey Zigbee - limit of 20 battery powered devices

Line> -----------------------------------------

For those who doesn’t understand: i draw a line here. Let’s stop nagging and start being useful.
Next off-topic posts will be deleted without further notice. Reactions to this post will also be deleted.That includes posts where we have to make a statement first to go on-topic again after that. If you have any problems with that please feel free to PM me or any other moderator.

1 Like

It’s strange that your mesh does not use your routers. I believe the limitation is not 20 battery powered devices in total, but 20 battery powered devices per router/coördinator.

My developer page does show zigbee using the routers (ocassionally). Have you tried rebuilding the zigbee network already?

From what I know (also from other sources), the SoC has a 20-device limit, no matter if those are battery-powered or not (there might be a slight variation between controllers, but it’s 20-ish).

1 Like

I’m sorry, battery powered or not is indeed not relevant.

What I was trying to say, is that the limitations encountered by the TS are most likely caused due to the fact that all his devices are directly connected to Homey. Therefore, the network (and the limitation) is not expanded. Or, as the source you provided states this:

“Definitely not! Example given: the default Zigbee2mqtt CC2531 firmware indeed supports 20 devices connected directly to the coordinator. However, by having routers in your network the network size can be extended.”

1 Like

I am also faced with the same limitation of 20 zigbee devices:

  • I have a XIAOMI v2 gateway but it does not act as a router.
  • I also have a HUE gateway but I understood from lisatn other posts on the forum that he builds an independent zigbee network.
  • I have a ZIGATE (zigbee USB key) but I can not add it to HOMEY.

Last solution: https://www.ikea.com/en/fr/p/tradfri-signal-amplifier-10400408/

I hope this product will help to overcome this limitation (material since dependent SOC?)
Do you see another solution?

i use Philips hue bridge for all Philips motion sensors, dresden elektronik strips.
for the rest of motion sensors, innr lamps and hue lamps, I use homey.
each room has now. min. 3 sensors.

first time, that this works how it should :slight_smile:

maybe there is a better working solution? but it works for me :slight_smile:

I’m working with count downs start and adjust
flow:

maybe this will solve your issues also

Do you have any proper routers? Such as an Ikea or hue light bulb connected directly to Homey? Or a Zigbee smart wall plug connected directly to Homey? The bridges from Hue (for example) are intended to be used as a coördinator, the same as Homey, not as a router. The mesh-network should only have one coördinator, but can have multiple routers. Each router (and the coördinator) can hold up to 20 devices (give or take).

I recognize that I did not think of pairing the HUE bulbs directly to Homey, they are always connected to the HUE bridge. (the functionality and ergonomics are the same?)
The only devices I can use as a router are the IKEA TRADFRI signal repeaters (answer tonight after work;))

OK, I’m curious to see if that has any effect. A good way to test how your zigbee mesh is set up, is checking https://developer.athom.com/
You’ll have to wait a minute, as the mesh-network needs to load in order to show on your screen. You’ll see something like this. This is a screenshot of (a part of) my zigbee mesh.


The developer site shows which devices are a router or an endpoint. It also shows the route, based on the little coloured blocks with the number inside.

Result: it works but only for new devices added :cry: i have to appair again all my Xiaomi devices

edit: I have:

  • reset zigbee - restarted homey
  • add 3 ikea repeaters
    -re-paired my xiaomi devices

and guess what? it works !!!

Thank you very much for the insights as I am planning to deploy ZigBee sensors in combination with Heimdall, this is very useful material here.
However because I am new to the community, I would have some questions to raise and I am sorry if it was already addressed in some groups of discussion.
1- Did anyone test what happens when you have a power cut ? Because I guess using extenders you couldn’t really control throughout the mesh network could be an issue. Does it reconfigure correctly ? Any possibility to say the device should act as router or not ?
2- Using devices such as Lamps or sockets acting as extenders is also an issue if you cannot control their functions isn’t it ?
3- What could be recommended as best practice to deal with this type issue, for instance using UPS also for the ZigBee extenders ? Disconnecting the lamps and sockets in a flow activating the surveillance mode ?, etc.
Please could we list somewhere all recommendations to make it more secured ?
Many thanks in advance for your feedbacks :wink:

Hi Arvlux,

1- if the power of homey is cut then you can no longer control the devices that are paired on it. However, when the power returns, all devices are operational again (with some exceptions)

2- Indeed it is the risk but point number 3 answers

3- I think of your need: connect homey to a UPS in case of power failure. However, if you have a lot of very distant zigbee devices, you should also plan to redundant the power of your zigbee repeaters otherwise there is a risk that they will no longer communicate with homey during the power outage.

1- if the power of homey is cut then you can no longer control the devices that are paired on it. However, when the power returns, all devices are operational again (with some exceptions)
2- Indeed it is the risk but point number 3 answers I think of your need: connect homey to a UPS in case of power failure. However, if you have a lot of very distant zigbee devices, you should also plan to redundant the power of your zigbee repeaters otherwise there is a risk that they will no longer communicate with homey during the power outage.

Le ven. 24 janv. 2020 à 09:28, Hervé via Homey Community Forum athom@discoursemail.com a écrit :

Hi Guy56,
Many thanks for the confirmation for the way to go, sounds logical :wink: Did you implement it ? What about removing a device playing role of extender like a lamp or power socket, could we remove it from the Zigbee mesch by command in a workflow ?

Then it is a generic zigbee issue when it’s in a specific hardware setup (SoC/Memory/etc) as described…

Thats not the mesh layout, thats the routing list.
Look at the post made earlier: )

Something cannot be both generic and specific :stuck_out_tongue:

To clarify: it’s not a generic Zigbee issue because the limit isn’t imposed by the Zigbee standard.

Ye i know both the meaning of that word and the sentence as a whole. and the insights of this “issue”. and again, read my post, never said it was a generic flaw across the board. Just a common limitation in specific hardware environments. (As earlier stated).
If its easier for you just put in “hardware environment” in the specific-part if the sentence. And generic you can change to general/common, then perhaps the sentence get simplified when someone isnt used to eng.

in dutch ill guess its same as algemeen / gemeenschappelijk…
Iam not Dutch, used google for that part.

2 Likes

Don’t be patronizing.

No worries i wasnt, just explained, to prevent misunderstandings.

Then it’s a good thing I never said it’s the mesh lay-out. However, it’s my understanding that, based on the routes, you can work out how your mesh is set-up. So in my post, the ikea light bulb is used to pass on the messages between the aqara motion sensor and homey. Are you telling me that’s false?

1 Like