Fibaro Motion Sensor FGMS-001 cannot set associations

Hi

I have a Fibaro Motion Sensor FGMS-001 v3.2 I am trying to set up a group 2 association with a Fibaro Dimmer 2 module in my Kitchen.

The Motion Sensor is included in to Vera OK and also securely I believe, as it says exchanged security keys.

The Dimmer 2 module is also in secure mode.

When I try and setup the association group I am unable to configure the motion sensor, it always gets stuck on “Setting User Association”.

I have tried unpairing and repairing the motion sensor. I’ve tried resetting the motion sensor back to factory. I have even restored a Vera backup and the Z-Wave network from yesterday.

No matter what I try its not working.

I am seeing this in the log file.

got CAN <0x75f70520>
01 02/11/20 15:50:26.744 ZWaveSerial::Send m_iFrameID 227 type 0x0 command 0x13 got repeat failure 24 iNumFailedResponse 1 time 78744 start time 78715 wait 2000 m_iSendsWithoutReceive 0 <0x76370520>
01 02/11/20 15:50:26.788 got CAN <0x75f70520>
01 02/11/20 15:50:26.788 ZWaveSerial::Send m_iFrameID 229 type 0x0 command 0x16 got repeat failure 24 iNumFailedResponse 1 time 78788 start time 78759 wait 2000 m_iSendsWithoutReceive 0 <0x76370520>
01 02/11/20 15:50:26.788 ZWaveJobHandler::SendDataAbort failed <0x76370520>
01 02/11/20 15:50:26.789 ZWaveNode::GetNonce node 90 cannot send request, abort (nil) <0x76370520>
01 02/11/20 15:50:26.789 ZWaveNode::EncryptFrame m_iFrameID 226 cannot get nonce node 90 command class 0x85 command 0x1 <0x76370520>
02 02/11/20 15:50:26.789 ZWaveSerial::Send m_iFrameID 226 type 0x0 command 0x13 sent ok - can’t encrypt <0x76370520>
01 02/11/20 15:50:26.789 ZWJob_SendData::Run done/fail job job#18 :assoc set 90grp 2 dev:409 (0x2bdb740) N:90 P:13 S:7 Id: 18 took 88 ms method 2 to node 90 command 133/1 failed 5 retries 0 of 0 <0x76370520>
01 02/11/20 15:50:26.790 ZWJob_SendData::Run job job#18 :assoc set 90grp 2 dev:409 (0x2bdb740) N:90 P:13 S:7 Id: 18 to node 90 command 0x85/0x01 failed 0/0 or Quit 0 <0x76370520>
01 02/11/20 15:50:26.790 ZWJob_SendData::JobFailed job#18 :assoc set 90grp 2 dev:409 (0x2bdb740) N:90 P:13 S:7 Id: 18 Priority 13 <0x76370520>
02 02/11/20 15:50:26.790 ZWJob_ConfigureNode::ChildChanged aborting job#4 :conf_jh#90 dev:409 (0x18bb2a0) P:14 S:5 Id: 4 for job#18 :assoc set 90grp 2 dev:409 (0x2bdb740) N:90 P:13 S:7 Id: 18 <0x76370520>
04 02/11/20 15:50:26.791 <0x76370520>
02 02/11/20 15:50:26.791 Device_Basic::m_eConfigured_set device 409 was -2 now 0 zw aborting <0x76370520>
06 02/11/20 15:50:26.792 Device_Variable::m_szValue_set device: 409 service: urn:micasaverde-com:serviceId:HaDevice1 variable: Configured was: -2 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0x121dcd0/NONE duplicate:0 <0x76370520>
04 02/11/20 15:50:26.793 <0x76370520>
04 02/11/20 15:50:26.794 <0x76370520>
01 02/11/20 15:50:26.794 ZWJob_SendData::Run job job#18 :assoc set 90grp 2 dev:409 (0x2bdb740) N:90 P:13 S:3 Id: 18 device 409 node 90 Aborting without requee after 0 retries <0x76370520>
01 02/11/20 15:50:26.864 got CAN <0x75f70520>
02 02/11/20 15:50:26.864 ZWaveSerial::Send m_iFrameID 231 got a CAN – Dongle is in a bad state. Wait 1 second before continuing to let it try to recover. <0x76370520>

Anyone know how to fix it ?

Thanks

Is it awake?

Open the back and triple click the button. Perhaps

C

1 Like

I wish it was that simple, I have been pressing the button 3 times a lot haha

Well it was worth an ask!

C

1 Like

Its the same if I try and setup an association group 4 as well. It just never configures the association set.

Their manual states a triple click of the B button. With my ZOOZ motion sensors, I found it effective to bring them right next to the Vera and wake them up. Sometimes reloading luup and waking up the device once reloads has helped me too.

Thanks. I have also tried with the motion sensor virtual sat on top of the Vera unit very close.

Sometimes just waiting a little while for the device to automatically wake up by itself works as well. Very tedious to configure battery powered devices.

Hi

Can someone explain how the default value for Parameter 18 is a value of 15 ?

When the options are 0,1,2,4 and 8

image

Looking at my target device I want to add in to the motion sensors association group 2. A Fibaro Dimmer 2 module, under its Advanced - Variables - NodeInfo I see this with S’es which I believe mean that the Dimmer 2 module was included in Secure Mode:

20S,22,26S,27S,31,32,56,59,5aS,5e,60S,70S,71,72,73,75S,7a,85S,86,8eS,98,

Also looking at the Fibaro motion sensors NodeInfo, it also looks to be in secure mode.

20S,22,30S,31,56,59,5aS,5e,70S,71S,72,73,7a,80,84S,85S,86,8eS,98,9cS,

I have changed Parameter 18 to a value of 0 for “none of the groups sent as secure”

And I then tried to add group 2 again and add the Fibaro Dimmer 2 module in to that association group.

But the same thing happens Vera doesn’t configure the motion sensor and it gets stuck on “Setting User Association”

Not sure if Vera support are operating or just really busy I emailed them about this issue and another issue including Sensative strips, but haven’t had a response as yet. Have to wait a while longer I guess.

got CAN <0x75f70520>
01 02/12/20 14:24:02.238 ZWaveSerial::Send m_iFrameID 512 type 0x0 command 0x13 got repeat failure 24 iNumFailedResponse 1 time 160238 start time 160209 wait 2000 m_iSendsWithoutReceive 0 <0x76370520>
01 02/12/20 14:24:02.282 got CAN <0x75f70520>
01 02/12/20 14:24:02.282 ZWaveSerial::Send m_iFrameID 514 type 0x0 command 0x16 got repeat failure 24 iNumFailedResponse 1 time 160282 start time 160253 wait 2000 m_iSendsWithoutReceive 0 <0x76370520>
01 02/12/20 14:24:02.282 ZWaveJobHandler::SendDataAbort failed <0x76370520>
01 02/12/20 14:24:02.282 ZWaveNode::GetNonce node 90 cannot send request, abort (nil) <0x76370520>
01 02/12/20 14:24:02.283 ZWaveNode::EncryptFrame m_iFrameID 511 cannot get nonce node 90 command class 0x85 command 0x1 <0x76370520>
02 02/12/20 14:24:02.283 ZWaveSerial::Send m_iFrameID 511 type 0x0 command 0x13 sent ok - can’t encrypt <0x76370520>
01 02/12/20 14:24:02.292 ZWJob_SendData::Run done/fail job job#55 :assoc set 90grp 2 dev:408 (0x2b99dc0) N:90 P:13 S:7 Id: 55 took 93 ms method 2 to node 90 command 133/1 failed 5 retries 0 of 0 <0x76370520>
01 02/12/20 14:24:02.293 ZWJob_SendData::Run job job#55 :assoc set 90grp 2 dev:408 (0x2b99dc0) N:90 P:13 S:7 Id: 55 to node 90 command 0x85/0x01 failed 0/0 or Quit 0 <0x76370520>
01 02/12/20 14:24:02.293 ZWJob_SendData::JobFailed job#55 :assoc set 90grp 2 dev:408 (0x2b99dc0) N:90 P:13 S:7 Id: 55 Priority 13 <0x76370520>
02 02/12/20 14:24:02.293 ZWJob_ConfigureNode::ChildChanged aborting job#41 :conf_jh#90 dev:408 (0x2bd9088) P:14 S:5 Id: 41 for job#55 :assoc set 90grp 2 dev:408 (0x2b99dc0) N:90 P:13 S:7 Id: 55 <0x76370520>
04 02/12/20 14:24:02.294 <0x76370520>
02 02/12/20 14:24:02.295 Device_Basic::m_eConfigured_set device 408 was -2 now 0 zw aborting <0x76370520>
06 02/12/20 14:24:02.295 Device_Variable::m_szValue_set device: 408 service: urn:micasaverde-com:serviceId:HaDevice1 variable: Configured was: -2 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0x126c470/NONE duplicate:0 <0x76370520>
04 02/12/20 14:24:02.296 <0x76370520>
04 02/12/20 14:24:02.297 <0x76370520>
01 02/12/20 14:24:02.297 ZWJob_SendData::Run job job#55 :assoc set 90grp 2 dev:408 (0x2b99dc0) N:90 P:13 S:3 Id: 55 device 408 node 90 Aborting without requee after 0 retries <0x76370520>
01 02/12/20 14:24:02.338 got CAN <0x75f70520>
01 02/12/20 14:24:02.338 ZWaveSerial::Send m_iFrameID 517 type 0x0 command 0x13 got repeat failure 24 iNumFailedResponse 1 time 160338 start time 160309 wait 2000 m_iSendsWithoutReceive 0 <0x76370520>
02 02/12/20 14:24:04.393 ZWaveSerial::GetFrame 0x7636f8f0 timed out now 1 m_listGetFramePending 1 <0x76370520>
02 02/12/20 14:24:04.393 ZWaveJobHandler::SendDataAbort got m_iFrameID 0 <0x76370520>
01 02/12/20 14:24:04.394 ZWaveNode::GetNonce node 90 cannot send request, abort (nil) <0x76370520>
01 02/12/20 14:24:04.394 ZWaveNode::EncryptFrame m_iFrameID 516 cannot get nonce node 90 command class 0x84 command 0x8 <0x76370520>
02 02/12/20 14:24:04.394 ZWaveSerial::Send m_iFrameID 516 type 0x0 command 0x13 sent ok - can’t encrypt <0x76370520>
01 02/12/20 14:24:04.394 ZWJob_SendData::Run done/fail job job#42 :Wakeup done 90 dev:408 (0x2dffa88) N:90 P:102 S:7 Id: 42 took 2096 ms method 2 to node 90 command 132/8 failed 5 retries 0 of 0 <0x76370520>
01 02/12/20 14:24:04.395 ZWJob_SendData::Run job job#42 :Wakeup done 90 dev:408 (0x2dffa88) N:90 P:102 S:7 Id: 42 to node 90 command 0x84/0x08 failed 0/0 or Quit 0 <0x76370520>
01 02/12/20 14:24:04.395 ZWJob_SendData::JobFailed job#42 :Wakeup done 90 dev:408 (0x2dffa88) N:90 P:102 S:7 Id: 42 Priority 102 <0x76370520>
04 02/12/20 14:24:04.396 <0x76370520>
01 02/12/20 14:24:04.396 ZWJob_SendData::Run job job#42 :Wakeup done 90 dev:408 (0x2dffa88) N:90 P:102 S:3 Id: 42 device 408 node 90 Aborting without requee after 0 retries <0x76370520>
06 02/12/20 14:24:05.101 Device_Variable::m_szValue_set device: 408 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: AgiInfo was: X now: X #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x76970520>
06 02/12/20 14:24:05.102

it’s binary representation
1+2+4+8 =15 so all groups are sent as secure.

1 Like

I then tried adding an old Duwi dimmer module in to the Fibaro Motion Sensors group 2 instead.

The Duwi is not included in to Vera in secure mode. Yet the same thing happens again, Vera cannot configure the motion sensor and setup the association group and gets stuck on “Setting user association”.

Should be simple to setup according to this guide. :cry:

I’ve decided I hate Z-Wave motion sensors they are a pain in the arse to setup. I still had no joy setting the association in the UI7 web GUI and still no reply from Vera support on email.

So I reached out to Vesternet and their technical support manager Martyn kindly gave me some insight. Here is what he said:

Nice to hear from you!

I took a quick look at your thread on the Vera forum and based on the log files Vera is having trouble carrying out the initial security exchange that occurs when it needs to communicate with a secure device.

You can see this from the “cannot get nonce” and then the subsequent “can’t encrypt” messages.

Unfortunately these types of problem can be tricky to troubleshoot, but usually what’s happening is that other devices attempt to communicate with Vera at the same time, which interrupts that initial security exchange.

In the first instance, I would suggest trying to see if you can repeatedly and consistently get the device to wake up (by triple-clicking the B-Button) while observing the log files. You really want to be able to see that whole process complete without interruption and error before going further.

The other problem is that it’s difficult to know when to wake a battery powered device up when trying to set Associations from Vera, because typically you click Save in the Vera UI and then it does a whole bunch of stuff (perhaps restarting the LUUP engine and sending a boat load of commands out on the Z-Wave network at the same time).

What you can do, is try and send the Association command directly using raw Z-Wave LUUP calls from the LUUP test window.

This can still be tricky to get the timing right, but doing it this way you can at least watch the logs until a quiet period before you click the “go” button on the LUUP test window and then triple-click the B-Button on the device with reasonably accurate timing.

luup.call_action(‘urn:micasaverde-com:serviceId:ZWaveNetwork1’,‘SendData’,{Node=‘91’,Data=‘133 1 2 85’},1)

91 - Motion Sensor Z-Wave Node ID
133 - Association Command Class
1 - Set
2 - Group you want to use
85 - Dimmer 2 Z-Wave Node ID

Please let me know if that helps?

NOTE: The NodeID is the altid in Vera on the devices Advanced page.

I ran the LUUP command:

luup.call_action(‘urn:micasaverde-com:serviceId:ZWaveNetwork1’,‘SendData’,{Node=‘91’,Data=‘133 1 2 85’},1)

And the Dimmer 2 module started turning on the lights when motion was detected and off again after the default 30 second time out, so the association was set and working !

The direct association set between the two devices using this command method, doesn’t make the configured association information appear under “Device Options” and the “Associations” section of the UI7 GUI though, that is all still blank.

image

Here is what Martyn said about that:

Yeah you won’t see anything there because that’s just a LUUP variable that Vera uses internally. Sending raw Z-Wave command bypasses that.

You can check on the Advanced -> Variables tab and look for “AssociationGet” and “ConfiguredAssoc”, the first is what Vera “got” from the device, so they are what have been set and the latter is what Vera has stored internally and is what drives the Associations section on the UI.

My “ConfiguredAssoc” was empty as expected, however I don’t have a “AssociationGet” field listed at all on the Motion Sensor.

If you want to delete the association:

Change the Set (1) to a Remove (4):

luup.call_action(‘urn:micasaverde-com:serviceId:ZWaveNetwork1’,‘SendData’,{Node=‘91’,Data=‘133 4 2 85’},1)

Get Association:

You can also send a Get (2) to check what it’s set to, but you’d need to interpret the reply from the log.

These are my current device parameters set on the Fibaro Motion Sensor.

I bought this Fibaro Motion Sensor to replace a Neo CoolCam one that said it was Z-Wave Plus but wasn’t included in to Vera in Secure Mode and therefore the Neo CoolCam couldn’t control the Fibaro Dimmer 2 that was also in Secure Mode via direct association.

I did have the Neo CoolCam controlling the Dimmer 2 via PLEG logic for a while, but found it wasn’t fast enough and instant like direct association is.

Best Home Automation shopping experience. Shop at getvera!

© 2020 Vera Control Ltd., All Rights Reserved. Terms of Use | Privacy Policy