i already switched off the dimming functionality by setting 172 to off.
so i use it as a switch only (just bought the dimmer for future readyness).
there is a switch type setting, which is already set to “momentary”, but i do not find a setting to only use one of the two sides of the switch.
Walli Controller is added as Generic Z-wave device, but i need to change some parameters value, like per.20. to 1 to create Association (linking devices) Walli Controller | FIBARO Manuals
Maybe this is possible in some way, but I don´t have no idea, how to achieve that.
Parameter can be changed via „Raw Configuration“. Don’t know if it’s possibility in the advanced settings of a „Generic Device“.
If not, you can do the raw configuration in Homey Developer → Z-Wave → Tools.
I’m having some problems with ‘Woonkamer Links’ & ‘Ivo kamer links’. Now I have submitted athom support ticket and they let me know to add the device again. Done this several times. Even had to keep the homey closer by means of a battery pack (never had this in the past). This is since the update to 7.1. Het zijn allemaal fibaro FGS-223 modules. Hence the question. Could it be the status ‘Secure (⨯)’? Whatever this may mean.
The devices must support the S2 security standard in order to be included “secure”. The security standard S0 is not supported by the current Homey firmware v7.1.3.
All Fibaro devices you mentioned only support the S0 security standard, so they are included as “unsecure”.
S2 is also an AES-128 encryption. Quote Aeotec Webseite: “S2 enhances Z-Wave Plus, Gen5, and Gen7 with an additional layer of AES 128-bit encryption of wireless signals coupled with pro-security grade UL 1023 compliance.”
I am not an in-depth Z-Wave and Internet expert, but from my point of view it is quite unlikely that a burglar would try to hack the Z-Wave network in a normal household in order to break in “more easily” or to deactivate the alarm system. The necessary effort is relatively high. Maybe the possible danger is higher in villas or commercial buildings, but there I would not use a Homey or radio-based devices.
An attack via the Internet is much easier in my view.
Homey includes all devices with S0 as unsecure, this is by design since Homey v7 as they had too many issues (too slow) with devices included as secure on S0 (especially battery devices).
Lots of users already used a workaround to include devices before as unsecure.
The developer of said app can still enable it for example for Z-Wave based locks but it will have to be enabled in the code of the app, it can’t be chosen by users.
Just an additional info. You can force a S2 device where a PIN is needed to include it as unsecured by using a wrong PIN. e.g. 00000. This could be necessary if you want to use associations.
Btw, there is already a request to Athom (Athom partially reads posts in the forum, but in principle does not respond to them) that it should be made possible for the user to choose during inclusion if a security standard should be used or not.
If you are also interested in this, then you can like the post.
First, both devices must be included with the same security standard, e.g. unsecure - insecure / S0 - S0 (only exists for already included devices before S2 was introduced) / S2 - S2.
Regarding S2 I’m not sure if S2 (Unauthenticated) works with S2 (Authenticated), but I guess it does.
So if the plug and the flood sensor have different security standards, then I don’t really need to explain anything further. Please let me know.
You can find infos about the security standard for example in Homey Developer Tools.
Go to Z-Wave and then you find a list of all your Z-Wave devices. On the right side of the table you can find infos about the Z-Wave security standard of each device:
Why I’m telling all the things about the security standard? Because you mentioned this:
And the code is used for devices that are included with the S2 (Authenticated) security standard. And if the flood sensor is included unsecure, then it doesn’t work.