Aeotec Z-Stick 7 dropping packets/unstable network

Hey everyone,

I’ve searched this up but haven’t really found anything about it…

Basically I want to have a master switch which turns off/on all Fibaro Walli Dimmers at once. This looks simple enough in principle, except that when you do that, the networks gets overloaded because if has to send a command to every device. This means that many (around half) fail to receive the command due to dropped packets, and therefore become unavailable.

What is the recommended approach for this? Once the nodes become dead I have to ping them manually/wait so they become available again.

There’s a lot of missing information here. That’s not a lot of devices for the network to lock up.

What controller are you using and what firmware are you using? Are your devices using s2?

Where is your controller located? Are you using a USB extender?

1 Like

Hey, thanks for your reply. Sorry about that :slight_smile:

Controller is ZST10-700 (Aeotec Z-Wave Stick Gen7) running firmware v7.17.2 (with same SDK Version)

All the devices were added using no security into the network

Here is my network graph:

I have ordered a USB Extender, still waiting for it. The USB is plugged into the front IO of the case alone, which itself is located in the server closet, and I have removed the metal front panel.

(They have just undergone a heal, so the network should be as strong as it gets in its current state)

How big is your house? Two hops is not a good connection (unless the distances are very long). I suspect you are suffering from the, ahem, not very good range of the Aeotec Z-Stick 7.

1 Like

I’d say it’s decently big, I imagine the issue may be more related with the fact that it’s an older house and the walls are quite thick.

Hops are definitely gonna happen because it’s three stories…

Would a range extender help?

Utilizing S2 security, if your devices support it may help, it ends up having to send less packets.

1 Like

I thought it added more overhead. I’ll give it a shot, thanks!

That was a misunderstanding that propgrated somehow early on but it’s the opposite.

Repeaters would help. You can also check each device’s statistics to see its RSSI, and what device it talks to directly to determine where to add them or if they are needed for a specific device.

1 Like

Gotcha, thanks.

What would be a good floor for the RSSI where the connections is still solid, @Danny2100 ?

I would assume nothing over 90?

@firstof9 may be able to provide a better answer on that. I have a leak sensor the furthest from the controller with an RSSI of -69.

1 Like

As with wifi or any other radio devices you don’t want to see your RSSI go below -75 dBm.
Not to say that lower will not work, but it’ll definitely be bumping that radio power to max.

1 Like

Unless the devices are spaced very unevenly currently, why would a repeater help? A hop is a hop.

1 Like

From my experience, I’d suggest replacing the Z-Stick 7 with any other S2/SmartStart-capable controller. There seems to be a relatively consistent 15-30 dBm difference.

1 Like

They aren’t, maximum 5m I’d say. There are relatively thick walls in between though.

I’ve ordered a 2 repeater pack, and a SiLabs SLUSB001A. Let’s see what solution works better.

Thanks for all you guys’ help!

Any constantly powered node will act as a repeater. Separate repeaters really only help when you don’t have one of those in a certain area.

1 Like

Wait, what?? Can you shed more light on this?

1 Like

I don’t have all the details, but S2 utilizes the Supervision CC, this reduces the amount of packets needed.

Have a look and Google is your friend. I’m definitely curious as to what started the notion s2 increased overhead awhile back, I assume the belief was encryption = more overhead or something along those lines.

1 Like

S2 has less overhead than S0, but not less than nodes included without security.

1 Like

Except for the greater chance of needing to send extra GET requests for verification.

1 Like