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.
It may also be that your fgs214 doesn’t work well with associations.
I have 2 fibaro fgs223 and only one of them works with associations and they are 2 meters away from each other
Good evening Mariano. Since you have the keyfob you know how to send it in key lock. Setting parameters 1 and 2 I was not successful.
Hi @GiacomoF
Sorry, I forgot to answer you.
I haven’t been able to get lock mode to work either.
Hi
Is anyone able to let me know how to install this driver? I’ve had a frustrating weekend trying to set up an old Fibaro Dimmer 2, and this looks amazing and could really help!
Many thanks in advance.
Hi @gileshoughton
What edge driver are you using for dimmer2, the stock Z-Wave Switch?
I assume so. It’s the one labelled ‘Fibaro Dimmer 2 (ZW5)’ in the graph API portal. It only lets me set some parameters (e.g. leading vs trailing edge), but not minimum and maximum values, etc.
I think you are referring to a groovy DTH and this is for when using an Edge driver
I think you are right. I’ve just been researching and assumed I was already on Edge but looks like that migration hasn’t started yet. I’m not sure I really want to remove and re-add all my devices yet to get them early.
When I do get migrated, will this driver just be available or do I need to install it in some way?
Yes the driver will be in my shared channel
I’m trying this on a Zooz Zen34. I installed the driver, but when I select the Z-Wave Device Config Mc driver it just goes to a blank screen and never changes. I tried removing and adding the driver with the same result.
This is a known issue with the lastest app update. All we can do is wait for ST to fix it
Link to topic
How do I download this driver?
You can ignore my question. I found it.
This is a nice looking tool. I am trying to use it to get and set association groups. For some reason it doesn’t seem to be working. I see in the SmartThings cli logs that the command is being sent, but then I do not see any results. Also, when I do a scan of the groups I see all the groups “get” commands be sent, but not the response. Not sure if this is related, but after the group scan is performed an event is attempted, but there is an error.
Edit: I think it is a SmartThings bug. If I add the device with S2 then the tool works great. If I add the device and fail S2 (so that it down grades to non-secure) then the commands are not being sent correctly. Strange thing is that it seems to only be the association group commands that are not being sent correctly. Basic, Config, Multi-level, etc work just fine.
S2 affects associations; I think it’s the first Z wave feature that breaks backwards compatibility. Anyway, you cannot associate two devices that are not at the same security level. So you can’t associate an S2 level security device with one that isn’t at that level. My guess is that’s what’s blocking it, not a bug, although I could be wrong.
Hi @erocm1231
This error is a bug, which tried to update the state of the Command_Action capability with a 2 sec delay and was set to the wrong place. It does not affect the operation since it does not interrupt the execution of any function as it is the last instruction of the function.
It’s already fixed in this version
───────────────────────────────────────────────────
Name Z-Wave Device Config Mc
Version 2022-11-18T10:55:51.048242575
───────────────────────────────────────────────────
The driver uses the default libraries with these versions:
--- @type st.zwave.CommandClass.Association
local Association = (require "st.zwave.CommandClass.Association")({ version= 3 })
--- @type st.zwave.CommandClass.MultiChannelAssociation
local MultiChannelAssociation = (require "st.zwave.CommandClass.MultiChannelAssociation")({ version= 4 })
Use the default command constructor.
I don’t know if this will work for all devices.
With the ones I tried, fibaro FGS-223, FGR-212 and fibaro keyFob it works fine.
One of the devices, which is further away from the Hub, does not always respond with the same data for the association groups. Some times respond for 4 groups, others for 2 groups or all 5 groups
I think this device is wrong, but it could also be that messages are lost.
In another model that is closer and is also the repeater of the other, it always works well.
Today I tried with device that I think is bad and for single association in the CLI it gives Ok transmission, but it does not send the association data to driver.. Other day some time ago it works for single association too.
2022-11-18T11:41:29.977056279+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: ac895f6b-9e11-4a96-83a6-c4b8f175422b [20] (Luz Escalera)> sending Z-Wave command: {args={grouping_identifier=0}, cmd_class=“ASSOCIATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x00”, src_channel=0, version=1}
2022-11-18T11:41:29.998329946+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(876a9d7b) queued for radio transmission: CC:Association, CID:0x02
2022-11-18T11:41:30.003567946+00:00 PRINT Z-Wave Device Config Mc <<<< new Group_number: 0
2022-11-18T11:41:30.021320946+00:00 DEBUG Z-Wave Device Config Mc Luz Escalera device thread event handled
2022-11-18T11:41:30.030527279+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: ac895f6b-9e11-4a96-83a6-c4b8f175422b [20] (Luz Escalera)> sending Z-Wave command: {args={grouping_identifier=1}, cmd_class=“ASSOCIATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x01”, src_channel=0, version=1}
2022-11-18T11:41:30.040719279+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(d58237a0) queued for radio transmission: CC:Association, CID:0x02
2022-11-18T11:41:30.051480946+00:00 PRINT Z-Wave Device Config Mc <<<< new Group_number: 1
2022-11-18T11:41:30.056710279+00:00 DEBUG Z-Wave Device Config Mc Luz Escalera device thread event handled
2022-11-18T11:41:30.070325279+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: ac895f6b-9e11-4a96-83a6-c4b8f175422b [20] (Luz Escalera)> sending Z-Wave command: {args={grouping_identifier=2}, cmd_class=“ASSOCIATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x02”, src_channel=0, version=1}
2022-11-18T11:41:30.093990613+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(d6d0e2b3) queued for radio transmission: CC:Association, CID:0x02
2022-11-18T11:41:30.099450613+00:00 PRINT Z-Wave Device Config Mc <<<< new Group_number: 2
2022-11-18T11:41:30.111406279+00:00 DEBUG Z-Wave Device Config Mc Luz Escalera device thread event handled
2022-11-18T11:41:30.120356613+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: ac895f6b-9e11-4a96-83a6-c4b8f175422b [20] (Luz Escalera)> sending Z-Wave command: {args={grouping_identifier=3}, cmd_class=“ASSOCIATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x03”, src_channel=0, version=1}
2022-11-18T11:41:30.136970613+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(fcfde0fe) queued for radio transmission: CC:Association, CID:0x02
2022-11-18T11:41:30.142351946+00:00 PRINT Z-Wave Device Config Mc <<<< new Group_number: 3
2022-11-18T11:41:30.162788613+00:00 DEBUG Z-Wave Device Config Mc Luz Escalera device thread event handled
2022-11-18T11:41:30.181328946+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(876a9d7b) transmit status: TRANSMIT_COMPLETE_OK
2022-11-18T11:41:30.203811613+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: ac895f6b-9e11-4a96-83a6-c4b8f175422b [20] (Luz Escalera)> sending Z-Wave command: {args={grouping_identifier=4}, cmd_class=“ASSOCIATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x04”, src_channel=0, version=1}
2022-11-18T11:41:30.217725946+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(01bfb84a) queued for radio transmission: CC:Association, CID:0x02
2022-11-18T11:41:30.241547279+00:00 PRINT Z-Wave Device Config Mc <<<< new Group_number: 4
2022-11-18T11:41:30.254056946+00:00 DEBUG Z-Wave Device Config Mc Luz Escalera device thread event handled
2022-11-18T11:41:30.262890613+00:00 INFO Z-Wave Device Config Mc <ZwaveDevice: ac895f6b-9e11-4a96-83a6-c4b8f175422b [20] (Luz Escalera)> sending Z-Wave command: {args={grouping_identifier=5}, cmd_class=“ASSOCIATION”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“\x05”, src_channel=0, version=1}
2022-11-18T11:41:30.277369946+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(28fdbd61) queued for radio transmission: CC:Association, CID:0x02
2022-11-18T11:41:30.291347946+00:00 PRINT Z-Wave Device Config Mc <<<< new Group_number: 5
2022-11-18T11:41:30.296754946+00:00 DEBUG Z-Wave Device Config Mc Luz Escalera device thread event handled
2022-11-18T11:41:30.351106946+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(d58237a0) transmit status: TRANSMIT_COMPLETE_OK
2022-11-18T11:41:30.505888613+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(d6d0e2b3) transmit status: TRANSMIT_COMPLETE_OK
2022-11-18T11:41:30.715662946+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(fcfde0fe) transmit status: TRANSMIT_COMPLETE_OK
2022-11-18T11:41:30.925652280+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(01bfb84a) transmit status: TRANSMIT_COMPLETE_OK
2022-11-18T11:41:31.515923947+00:00 TRACE Z-Wave Device Config Mc Z-Wave command(28fdbd61) transmit status: TRANSMIT_COMPLETE_OK
For multi-channel association, sometimes it reports 4 groups and other times 5
Something I noticed with this driver if you use it for a Lock it will remove the lock from being displayed in the Smart Lock Guest Access app once you switch back to the Zwave Lock driver.
Anyone has successful setup on associate a ZooZ Zen71 binary switch to a ZEN30 double switch to control the relay?
I set at the source (Zen71), at Group 2. I put the Node ID of Zen30. When I choose Single Channel, it only affects the Dimmer part. Changing to Multi Channel, set End node of 0, also affects the Dimmer. I tried many different end nodes without luck. The CLI shows that however I change the end node, ZEN30 always receive request to the Dimmer.
Any help would be appreciated.
Hi @vinhtantran
I’m not familiar with zooz devices, but the stock driver assigns enpoint 0 to the dimmer and enpoint 1 to the relay.
First you have to see in the documentation which association group of the sending device sends the on-off commands. Group 2?
Then you should assign the sending group on-off, the node and the enpoint 1 in multichannel association of the receiver device
