Thank you for working with us on this.
We currently don’t have this specific device on hand to reproduce the issue on the Homey side. If possible, could you please try again to add the device into Homey, and after the attempt fails, generate a diagnostics report and send it to us. Here are the steps:
- Open the Homey mobile app or access Homey via web.
- Navigate to More → Apps → select the “EasyLighting App / driver” for your device.
- Tap the gear icon (Settings) next to the App.
- In the settings, select “Create Diagnostics Report”.
- The system will package the Homey logs + EasyLighting App logs into a report file. Please send that file or the report ID back to us.
For your reference, our current configuration is:
"zwave": {
"security": ["none"],
"manufacturerId": 816,
"productTypeId": [ 512 ],
"productId": [ 53250 ]
}
Additional configuration options you can also try:
If you’re comfortable with making adjustments, you could try the following two alternative configurations:
"zwave": {
"manufacturerId": [ 816 ],
"productTypeId": [ 512 ],
"productId": [ 53250 ],
"secure": [ "S0" ],
"requireSecure": true
}
or
"zwave": {
"manufacturerId": [ 816 ],
"productTypeId": [ 512 ],
"productId": [ 53250 ],
"secure": [ "S0" ],
"requireSecure": false
}
These two options will attempt pairing in secure mode S0—one forcing secure, the other allowing non-secure as fallback.
