C-7 and S0

🛎️ Get Help
61

Apparently not.. I’m looking into why the SDK isn’t picking up the new value

3 Likes
62

@bcopeland

Trying to learn the Zwave technology better. I have a switch (Inovelli) that offers S0, S2-0, S2-1 and I select all three, does that mean if I setup an association with a bulb which is S0 only, the switch will communicate with highest S2-1 with the hub and then use S0 with the bulb? I am not sure I understood some of the other comments above. Inovelli and other claim in order to have an association with a bulb that only supports S0, the switch must also and only use S0 during the inclusion process? Can you please add some clarification to this.

Also I have been told Hubitat is having issues with S0 included devices, has the latest Hubitat firmware on C-7 model fixed this issue?

63

I cannot speak for Bryan but after many community discussions in which he and other staff participated the following seems likely:

  • S0 is an older security protocol it is not recommended to use it unless needed for "border" devices like locks. The reason for this is it is very "chatty" and can potentially bog down communications with the hub. This is true for all versions of the hub not just the C-7.

  • The HE firmware is fine for S0 edit: there may be some issues with some devices!!! - One of the big issues though is the 700 Series spec requires S0 capable devices be paired as S0 and not unauthenticated not with "no security". The only way to pair those devices with no security at this point is to use a "secondary controller".

  • There do appear to be some issues with the current HE firmware and certain newer S2 devices and S2 authentication. Whether these require device firmware updates or HE updates or both remains to be seen.

In general pairing with no authentication security seems to be the best way to go for now - this is only my take though others may have different opinions.

4 Likes
64

I think you mean to say "pairing with no security" as the best way to go, as opposed to saying pairing with "no authentication" or "unauthenticated" which are terms used for S2 Unauthenticated pairing. :slightly_smiling_face:

4 Likes
65

Good catch! Edited my post to reflect reality for once.. :crazy_face:

5 Likes
66

Very old topic, I know. I thought I would add something. I have a bunch of Fibaro door and window sensors (FGDW-002). They will not pair without S0 security. I think I found a workaround that's quite easy (for this product anyway). Change parameter 3 (it's 1 byte) to 0. The default is 3. This parameter, according to the manual, determines if the device sends encrypted communications or not. It is still paired as S0, but when it sends communications to the hub, I think they are unencrypted now. I do not have a sniffer to prove it, but I changed the parameter on one sensor and it no longer overwhelms the network if I rapidly "open and close" it.

Just posting in case someone comes by like I did desperate for a solution that doesn't involve replacing them all.

Manual - https://manuals.fibaro.com/wp-content/uploads/2023/05/FGDW-002-EN-T-v1.3.pdf

5 Likes
67

That's a great idea, I had one fibaro Dimmer 2 still paired in s0 because it's hard to reach, and it also has a parameter like that and I changed it. Never thought of that!

2 Likes