Fibaro motion 3.03 firmware, secure inclusion?

Devices & Integrations
1

Hello,

Just got a new fibaro motion sensor.

When included, SmartThings states that it was not zwave secure.

In the graph ide it shows as zwave_so_legacy

Is this correct?

I excluded it and then re-added, got the same results.

Firmware in SmartThings ide listed as model 2002 ver 3.03

Did I get an old one? Is thus the expected behavior?

2

That is correct, it is an older model device and does not support S2 security.

https://products.z-wavealliance.org/products/3467?selectedFrequencyId=2

1 Like
3

Thanks,

which line on that page shows it does not support secure?

Also, to be secure does the device need that barcode for inclusion? Or is that a different issue?

For devices that have the barcode, do you need to use the barcode for inclusion to get all the features and security?

4

Since it doesn’t say that it supports S2 security, it doesn’t. conformance statements that pre-date S2 don’t have a field for it.

In contrast, a newer device like the Aeotec multisensor will show the S2 classes:

https://products.z-wavealliance.org/products/4088

Also, to be secure does the device need that barcode for inclusion? Or is that a different issue?

Z wave devices that support S2 security will have the QR code, but you don’t have to use the QR code to get S2 security. It’s just a quicker way to pair it.

1 Like
5

under where the battery goes does it say ‘zwave plus’

6

Zwave plus was the fifth generation chip, but when it was first released it did not have S2 security. That was a separate feature added later.

image

S2 logo, although it isn’t always used

image

The QR code feature, smart start, was added even later. again, the logo isn’t always used.

image

But in any case, there are a lot of older Z wave plus devices that don’t support S2 security.

1 Like
7

yes, I was just curious if he had the regular zwave or the zwave plus version. I have over 20 of these eyeballs and they are definitely not S2.

1 Like