[REQUEST] User selectable Z-wave security levels in order for associations to work

[Edwin_D]

PARTLY solved, Thanks @TagePP for the tip. I created and tested an app that was insprired on the previous Walli workaround. This app will allow you to add other z-wave devices unsecure using your temporary fix. I do not expect Athom to accept this in their store, but it is available in the community store. If you know how to do a CLI install, you can get the source from Github too.

[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 …

By the way

@TagePP

Furthermore we recommend not to use associations but to use flows instead.

That is a really stupid recommendation to follow, though I can imagine Athom would want that.

I had the good fortune to have to send Homey in for investigation more than once. Each time Homey was away for more than a week. Also, if Homey dies on you then Homey pro isn’t easy to buy as stock is limited or absent due to the shortages in chips. I was really happy that I could still turn the lights on and off when Homey was not there to execute flows.

So if you do not mind that you cannot control your lights is Homey has problems then: by all means. But if you are like me and you want to prevent the WAF dropping well below zero: go for associations if you can.