Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amount of devices / Routing #331

Closed
Jaxon77 opened this issue Sep 3, 2018 · 8 comments
Closed

Amount of devices / Routing #331

Jaxon77 opened this issue Sep 3, 2018 · 8 comments
Labels
stale Stale issues

Comments

@Jaxon77
Copy link

Jaxon77 commented Sep 3, 2018

Fisrt of all i want to thank you for your work to make such a project possible.
Right now i am a little bit confused. As i started to migrate to the CC2531 the amount of possible direct connected devices was 43. Now we landed at 15 devices. As i now have >60 (xiaomi)devices in my house, i am not sure if this is still a good solution for me, because it requires a lot of routers and i haven't got any use for the devices with routing function. So i'd have to use CC253X for that.
Does anyone else have such an amount of devices running without problems?

Am i right that every router extends the max devices about 10 so that i have to connect 5 additional routers to get 60 possible devices?

Would it be better to have one more router as needed (in my case 6) so that the clients can connect to another router if one dies?

Would it even be possible to plug all of these CC253X routers into one usb hub if there is no need to extend the range with it?

Is there any chance that the limitation of 15 devices gets elevated in future and does this limitation also apply to the CC2530 or other devices?

At least: is there any listing which devices act as router or is it as easy as "every devices with a permanent external power supply acts as a router"?

In hope to get some clearification,
Jack

@baerengraben
Copy link

baerengraben commented Sep 3, 2018

Hi
I had the same question. I'm running a system with > 25 Xiaomi Devices (Door/Window-Sensors). It needed a lot of patience to got this running. But it runs now:
ioBroker/ioBroker.zigbee#37 (comment)

For now I'm unsure if I would run > 60 Devices this with this solution. I would probably run > 60 Devices with several Xiaomi-Hubs and block the Xiaomi-Hub via firewall to "call home".

Am i right that every router extends the max devices about 10 so that i have to connect 5 additional routers to get 60 possible devices?

Yes. A router extends the max devices like that.

Is there any chance that the limitation of 15 devices gets elevated in future and does this limitation also apply to the CC2530 or other devices?

As far as I learned, there is a Memory-Limit on those cheap devices. I wouldn't count on a lot more Devices in the future (if there will be a new firmware at all).

hope this helps

@ben423423n32j14e
Copy link

Z-Stack 3* support is apparently being worked on which should massively increase the number of devices to 120 if I am not mistaken.

#211

@subzero79
Copy link

It is possible apparently using zigbee-shepherd to force devices to join through a router. If you manually do that, then is possible to have more devices with the current cc2531 as coordinator. Process is described #252 (comment)

Unfortunately zigbee2mqtt has not implemented that join process yet. So apparently will have to work the zstack 3.0.

@lolorc
Copy link
Contributor

lolorc commented Sep 4, 2018

Koenkk/zigbee-shepherd@0e4f387 is it supposed to fix joining through a router or does it need more from zigbee2mqtt ?

@Jaxon77
Copy link
Author

Jaxon77 commented Sep 4, 2018

@baerengraben your apprach is to span multiple zigbee networks instead a big one with routers is a
nice approach, but i think i'll stick with a second xiaomi gateway until there is a robust Z-Stack 3x. Thanks for the info @ben423423n32j14e.

@lolorc
Copy link
Contributor

lolorc commented Sep 24, 2018

@Koenkk I've seen you've reverted "Allow joining through specified device.", is there something wrong with it ?

@Koenkk
Copy link
Owner

Koenkk commented Sep 25, 2018

@lolorc It didn't work (caused exceptions)

@stale
Copy link

stale bot commented Nov 24, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale issues label Nov 24, 2018
@stale stale bot closed this as completed Dec 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale issues
Projects
None yet
Development

No branches or pull requests

7 participants