I haven’t tested it much since I only have 2 Z-wave devices with groups and one doesn’t work very well.
The normal procedure for Association groups is:
change the driver on the device to be configured. You will NOT lose any routine or scene, when you finish and return to the driver they will all be recovered as they were. Let’s hope they don’t change it again.
It will open in the last profile used and if it is the first one, the fingerprint information profile will open.
In setting preferences choose the “Device association Group scan” profile. The device will have to be closed and reopened to display the new profile. If it is the first time it is used, it may be necessary to clear the cache of the app.
By default it starts at group 0 and ends at 10, but you can choose others up to 255. There are devices that do not answer when they do not find more enabled groups, but other devices such as the fibaro FGS-223, always answer with the information of the group 1. Therefore repeated groups can be seen. Then you can repeat the search until the number before the group 1 repeated
Press the execute action button:
It gives us information on the maximum nodes allowed and how the nodes are configured.
When the node coincides with the Hub node, it marks it " * Hub Node * ". This group should not be touched unless it is wrong.
We can take a picture of how everyone is.
If we already know which group we want to configure:
Select the profile in preferences: “Device association Group configure”. You will have to close the device and reopen it to display the new profile. If it is the first time it is used, it may be necessary to clear the cache of the app.
Enter the Association Group number to configure
Select if you are going to configure to send commands to a single or Multi-Channel device
Select “Get” and press the execute action button
Show association group information
Insert the Network Node value of the device to link in Hexadecimal format. (You can see it in the CLI)
If it is a multi-channel device, insert the End point number (0 to 127) to which the command will be sent
Select “Set” and press the action button. It will send it and 2 seconds later it will read it and show the result.
To remove One Node from an association group, follow the steps above and select “Remove One Node” and press the action button. It will delete it and 2 seconds later it will read it and show the result.
To remove all nodes from an association group, follow the steps above and select “Remove All Nodes” and press the action button. It will delete it and 2 seconds later it will read it and show the result.
Used this driver the other day to change an option on a Aeon multi 5 and it worked a treat, I told the tec support at Aeon and he was well impressed too.
That last tool is really cool, where can i find that driver? (It looks like Z-Wave Tweaker but for Edge drivers). Parameter 5 set to 2 would use Binary Sensor Report which would make sense to me. Definitely keep me in the loop
Good evening. I am trying to associate a fibaro Keyfob with the fibaro 214. In the Keyfob I insert the driver, then I select the profile device association group, and here I insert the group 2 and the node address (B9) of the fibaro 214, node endp a 0, set single channel device. When I give the set command it executes it and passes in get showing me the association. Finished restoring the keyfob driver. When the button that sends the command to group 2 is pressed, the fibaro 214 does not execute any command. Where am I wrong?
The configuration change might still be queued on the hub. Did you check the user manual for the device to see if there’s something you need to do to wake it up to accept the configuration change?
See the community FAQ:
And from the user manual for this device:
Waking up the device:
The KeyFob needs to be woken up to receive information about the new configuration from the Z-Wave controller, like parameters and associations. Use 1st menu position (white) or click and simulta- neously to wake up the device.
It is a good idea to check the user manual for any batterypowered Z wave device if you are going to make configuration changes to see what steps you need to follow.
I’m stuck. the Keyforb sends the command and receives ok from the fibaro 214 (it is a relay), but this does not go from off to on. If I turn off the fibaro 214 the Keyforb rightly emits first orange then red light. if I turn on the fibaro 214, the Keyforb first emits orange then green light (it sent the command and arrived at its destination)
It also didn’t turn on and off on the first try, I had to send several commands until the association had to be established correctly in the zwave network.
Once it worked the first time it was instantly working every time I sent an on or off command.
I also verified that the parameter 29 of the keyFob had the value 4095, which is equivalent to sending all the commands of the 6 buttons in security mode
Check to make sure that both devices are added to your network with the same security level. As of the new S2 security framework, Zwave association does not work between devices with different security levels.
You may also need to check the parameters for the keyfob.