Z-Wave S2 authentication / High network load

[Fac3]

I was an installation last Friday, we deployed among others seven Flush Thermostat 2, but only these were added by S2 Authentication.

Since then there are huge delays in Z-Wave network. User opens venetian blinds, and module opens the venetian blind 30 minutes later.

We use a second generation Homey there, but not Pro, nor Bridge version. Is it possible that S2 causes this huge delays in the Z-wave network?

Is it possible to add Qubino Thermostat 2 modules without S2?

You can see that S2 devices communicates a lot compared to uncecured ones, and Tx error is quite hight at some.

[DirkG]

@Fac3

Is it possible that S2 causes this huge delays in the Z-wave network?

I also have some devices with S2 Authenticated included, but can’t notice any delays.
Nevertheless, devices included with S2 Authenticated cause higher traffic.

@Fac3

Is it possible to add Qubino Thermostat 2 modules without S2?

Yes, please have a look at this thread:

[APP][Pro] UnZ-Cure (add z-wave devices unsecure)

Add Z-wave devices unsecure Z-wave associations are a very important. The main reason is that if Homey isn’t working for some reason, the lights can still be controlled. As of version 7.0, Homey supports more z-wave security levels. That is great for locks and such, but not so much for z-wave associations, because associations need the same security level for both associated devices in order to work. As not all devices support the same security level, and Homey picks the security level based …

@Fac3

You can see that S2 devices communicates a lot compared to uncecured ones, and Tx error is quite hight at some.

I have 5 MCO Home MH7-WH included unsecure. Compared to other devices included unsecure, the Rx value is disproportionately high, e.g. 500 to 75,000. However, I have no Tx error.

[Fac3]

Thanks! I’m gonna check that article.