Amount of nodes on one Razberry

[kenneth]

Hi
Does anyone know, how many nodes I can connect on one Razberry? I have read somewhere around 200 nodes...
I am planning to by a lot of AEON Multisensor nodes, that can monitor light, motion, temperatur, tampering, humidity and UV. If each node meassures 6 parameters, can I then only have 200 / 6 = 33 nodes on one razberry?

Kind regards from Kenneth

[PoltoS]

You can include up to 231 Multisensor in RaZberry. Means 231*6 parameters will be available.

[klaasjoerg]

Hi PoltoS,
which leads me to a little next performance question.

I do currently have 236 Elements appearing in the UI on my raspberrypi3.
(around 110 physical devices, sensors, switches etc.) and certain ones already deactivated.

Among the fact that I have a load avg. of around 1 (>90% cpu load) I get very often get UI "response timeouts" and waiting for refresh until the UI really appears.

So I am wondering if there is a known limit in a matter of CPU-Load.Mainly zway is causing the cpu-load.

Are there recommendations or tuning tipps to speed up zwave behaviour somehow or at least increase access limits/requests for the UI or such things?
I also deactivated already the log-level to lowest minimum to avoid unnecessary overheads.

Tweeks tuning tips available?

P.S. I am also running homebrigdge-zway, but that doesn't seem to cause much CPU load, as I already noticed.

[PoltoS]

Z-Wave core itself do not eat CPU. At least not more than 5% on a Pi 3. JS code might to that. Now the questions is how many apps do you have activated and what they are? May be it is worth to use JS debugger to profile your installation to see what is eating so much.

[klaasjoerg]

Well, I surely have around 30-40 apps/if-then-rules/scenes/influxdb etc. activated, but:

How would I easily "debug" what's causing the nearly 100% cpu-load? (...without deactivating each single app by app and look what happens...?)

[PoltoS]

Using JS debugger. There is node-inspector to debug JS code. https://forum.z-wave.me/viewtopic.php?f=3422&t=20387

[klaasjoerg]

Hey PoltoS, just a quick information back on this:

I didn't really found a easy way how to activate debugger to quickly see what it causing the slow down.
So I ended up simply deactivating app by app and looking at /bin/top process view.

Finally it seemed that the Astronomy module github.com/maros/Zway-Astronomy was part of the story. To double check, I re-activated the rest again forth and back and left it completely deactivated for now.

Don't know if the app is really causing this issue or something in the core/backend has been changed since January...
Till middle of January things have been fine, and since then cpu work load had more than doubled somehow.
Part of the story is surely the new hue-app that helps dealing with lots of philips hue bulbs, but that doesn't explain why astronomy app is also causing cpu load.... (viewtopic.php?f=3419&t=24012&hilit=hue&start=50#p66731)
Also 2.3.0. was released in January if I remember correctly...

Since I have lots of virtual hue device with the app now, I set the refresh rate to 60 minutes and will check if "cpu loads" is moving further more down again...