Has anyone successfully implemented a direct association for the AEON Labs - WallMote Quad (ZW130-C)?
It functions seamlessly with scenes through Home Assistant, however, attempting a direct association to a device seems unfeasible. I maintain the “Action” button pressed to enable Wake mode, followed by configuring the association, but I consistently encounter an “Error while adding association” message.
Any ideas on how to resolve this issue?
Thank you!
2024-01-18T16:40:14.463Z CNTRLR « [Node 020] received wakeup notification
2024-01-18 17:40:18.108 INFO APP: GET /health/zwave 301 1.878 ms - 191
2024-01-18 17:40:28.699 INFO Z-WAVE: Calling api addAssociations with args: [
{ nodeId: 20, endpoint: 0 },
2,
[ { nodeId: 18, endpoint: null }, [length]: 1 ],
[length]: 3
]
2024-01-18 17:40:28.699 WARN Z-WAVE: [Node 020] Unable to add Node 18 to Group 2 of Node 20
2024-01-18 17:40:28.700 INFO Z-WAVE: Success zwave api call addAssociations false
The Fibaro FGBS222 is S2_Authenticated, but the “Wallmote Quad” is not S2_Authenticated because it does not support this feature.
As far as I know, it is possible to directly associate an S2_Authenticated Z-Wave device with one that is not S2_Authenticated and the association will operate at the lower security level supported by the devices involved… do you not agree?
Only in certain cases. In other cases both nodes must have the same highest granted security class. It looks like your device falls into the latter case.
If both devices support S2 Unauthenticated, you can use that and still take advantage of the encrypted communications. Otherwise you’re looking at both with no security.
Indeed, previously the Wallmount Quad was registered under “No security”, but after a few attempts, it has now been registered with “S0_Security”. I will try setting the FGBS222 to S0_Security as well and will inform you if it works.
