Well I tried creating a dummy z-wave device driver (a Walli like substitute) and put the flag to false, but using it to include a Heat-it switch still resulted in S2 secure. So I cannot confirm the default is true for S2.
The documentation states it should be set to true to force locks to S2 and refuse unsecure. A useless feature IMO because it wiil include S2 if it can. So as I read it the one and only flag left cannot be used to force anything unsecure.
I appreciate that. But there are also topics about people not understanding why associations won’t work, and this is a major cause. That also needs a lot of explaining.
For me: I’ve had to send in Homey three times for repairs/investigation which usually meant one to two weeks no Homey. That would have kept me in the dark, if not for KAKU direct connections of buttons to the lights. But Athom could not fix my KAKU issues (Homey going deaf for 433Mhz after a while until a Homey reboot).
So I spent a ton of money on 18 fibaro dimmers/switches and 18 wall remotes to replace the KAKU that wasn’t reliable (had been reliable for years with Homewizard and ICS-2000). All are linked with associations so I can control my lights when Homey should fail me. Except for a new combo that cannot be linked anymore because of the S2 security being enabled on a wall remote and not the Fibaro dimmer. So I am more than a little annoyed.
I sent in a request to Athom explaining my predicament, but as always on feature requests, no reponse.