Module association broken

[jiminy68 0]

Since 4.056 upgrade, I cannot manage to use association group.

 

I had an association set on a Fibaro Switch (FGS221) to turn on/off several lighs equiped with wallplug in my living room. It was working fine till the upgrade that introduce multichannel association.

 

I've tried many things from clearing the association and create in again in signle channel or multichannel, to soft reconfiguration off all module. No way, the wallplugs remain silent when I push the physical momentary switch (only the light linked to the module works).

 

I've tried to create other association in other room with no result either.

 

Do I missed something ?

 

Any help would be welcome.

 

Cheers

Jim

[sjauquet 16]

I have also searched hours why I had problems with association....

then I looked in the known bug of the 4.056....

Please login or register to see this image.

/emoticons/default_icon_curve.gif" alt=":-/" />

I hope they will solve this soon, it's very annoying

 

please have a look here: 

It's more for fgd 212 but it's probably related.

 

Please login or register to see this link.

[jiminy68 0]

Hi there and thanks for your input.

I've search the bug tracker on "association" and find a lot of issues, but I was unable to find one describing my problem. Can you give me the issue's id you are talking about.

Is the whole association mechanism broken in 4.056 ?

Cheers

Jim

[sjauquet 16]

Hi,

 

please see known issue, point 1:

 

Please login or register to see this link.

 

Altrough soft reconfiguration doesn't solve the problem..

[jiminy68 0]

Yep,

And since I'm trying to fix this issue, things are getting worse... I have items vanishing from the iphone app !

[petergebruers 1,268]

For the "disappearing" problem, please check "Controlled Device:" on the device's advanced page, it's reset after soft reconfiguration in 4.056 and older. And check user permissions too, if you use them.

[jiminy68 0]

That was is... Controlled device was reset to "other device". Setting it back to proper assignment brought back my lights in every rooms. Thanks.

[jiminy68 0]

So to make it short, there is no way to have association working on HC2 with firmware 4.056 ?

Correct me if I'm wrong.

[petergebruers 1,268]

I'll setup a test this evening with 4.057 if you want me to... To be clear... you use S1 or S2 to associate with a fib plug?

[jiminy68 0]

Thanks, that's nice. Yes I'd love to know if association will be back in the next version.

This is correct, I'd like to use either S1 or S2 to turn on/off its main light and at the same time auxiliary lights piloted with wall plugs.

[petergebruers 1,268]

It works. Nothing special to report. But I'll describe the test in detail, maybe some small but significant difference exists between my test and your situation.

I start on a "FGS221 Switch 2x1,5kW EU" version 2.1.

I check the associations, and they are default, meaning all 3 groups have only "1" = controller as destination.

I Click on group 1 and pick a wall plug. The exact device type is: "FGP111 Plug" version 22.22. If you look carefully, you might think that's a typo, because these plugs are known as "FGWP" and not "FGP", but I copy/pasted it from the GUI. This suggest to me that I am using a new template for my devices.

The wall plug is 3 meters straight line away from the relay, so it fulfills the requirement to be "in direct range". I click in the "S" column and at the left of the screen the Z-Wave Node ID is added to the "1".

I repeat that for group 2 and plug #2. Save. The status window displays "Received association report from group 3".

It simply works... S1 switches on the module & the plug in synchrony. Idem S2.

Just for fun I also set an association from the wall plug to the relay. That works too. Edit: my wall plug version can only do "S" association, so association with S1 but not S2.

Maybe 4.057 solves your problem... But to be honest, I did not have issues with the previous version.

Anyway, feel free to ask if you have more questions!

[sjauquet 16]

here is the response from fibaro support:

 

Dear Sir,

We have tested some of dimmers to make same situation as you have in your HC.
I remember that you have added these dimmers in security mode, and it is reason
why you cannot make associations to other devices. 
You should add them in normal mode and then you will be able to set associations.

Kind regards,

 

I asked them for more information about this security mode, but no response at the moment.

 

I added the fgd 212 using my phone and/or the web interface as always, nothing special...

Who knows how I can choose to disable security mode ?

I disabled security stuffs in the parameter 27 (so not secure) after inclusion, but this changed nothing.

 

Does someone have an idea please ?

[j.nowacki 5]

here is the response from fibaro support:

 

Dear Sir,

We have tested some of dimmers to make same situation as you have in your HC.

I remember that you have added these dimmers in security mode, and it is reason

why you cannot make associations to other devices. 

You should add them in normal mode and then you will be able to set associations.

Kind regards,

 

I asked them for more information about this security mode, but no response at the moment.

 

I added the fgd 212 using my phone and/or the web interface as always, nothing special...

Who knows how I can choose to disable security mode ?

I disabled security stuffs in the parameter 27 (so not secure) after inclusion, but this changed nothing.

 

Does someone have an idea please ?

 

Security mode is a special mode of operation in Z-wave. It assures encrypted communication and higher degree of robustness. However it slows down communication, and due to many additional frames being send it can disturb flow of information in entire network if too many nodes are included in security mode. So the key is to keep number devices using this to minimum, and reserve it only for crucial devices - like locks, gate openers, smoke sensors etc. Device added in secure mode can only send associations to other devices included as secure but all our devices that can use this mode have parameters, that allow them to disable encrypted communication in given association groups. And that is exactly what support agent meant.

Option to add device as secure or not is shown below "add device" button, as a check box, but many devices do not have security, therefore they will be included as usual, even though check box is ticked.

[CopyCatz 4]

here is the response from fibaro support:

 

Dear Sir,

We have tested some of dimmers to make same situation as you have in your HC.

I remember that you have added these dimmers in security mode, and it is reason

why you cannot make associations to other devices. 

You should add them in normal mode and then you will be able to set associations.

Kind regards,

 

I asked them for more information about this security mode, but no response at the moment.

 

I added the fgd 212 using my phone and/or the web interface as always, nothing special...

Who knows how I can choose to disable security mode ?

I disabled security stuffs in the parameter 27 (so not secure) after inclusion, but this changed nothing.

 

Does someone have an idea please ?

I think they mean the option "Add in security mode if device supports it", but I just tested it, makes no difference. For me there clearly seems to be a bug in the HCL 4.057 beta; not a single device has a multichannel association check box present and all my plugin modules do not have a single channel association check box. Which sucks because I cannot control them anymore using the second button on my tkbhome wall switch. It worked in v3..

[sjauquet 16]

Ok, I think I found something.

At first I added my new FGD 212 with the add device button from my smartphone.

It's very convenient because you name the device once and the 4 zwave devices are renamed and put in the related room in one operation.

But association was broken.

 

Now I removed it once again and added it with the phone interface and nowhere there is a secure option to be seen.

Association was still broken.

 

I removed it once again (btw, I'm at ID 1926 now

Please login or register to see this image.

/emoticons/default_icon_curve.gif" alt=":-/" /> )

And then added it trough the web interface, without checking secure mode (I never did)

Now association is working again, at least between fgd 212 and wallplug or FGD 211, (not with my 3 other fgd 212)

I will test tomorrow between two fgd 212 (but I have to exclude and include an other fgd 212)

[petergebruers 1,268]

Clever detective work! Thanks for sharing!

[sjauquet 16]

Ok, after removing and adding one more fgd 212 (trough the web interface) Association works between two fgd 212 modules.

 

@j.nowacki

 

So three conclusion:

1) Association is broken in security mode

2) add device from mobile phone broken as it adds the device in security mode without asking for.

3) I've lost 8 hours with this problem

Please login or register to see this image.

/emoticons/default_icon_curve.gif" alt=":-/" />

 

Small bug:

Added two fgd 212 for testing the association problem.

But until next reboot, the fgd-212 added are with properties isLight = False (but declared in "controlled device" as "lightning" in the web interface)

After a reboot, the value of isLight is now "true"

[sjauquet 16]

Hi, @j.nowacki

Can you confirm this or Do I have to submit a bug (I prefer not)

[j.nowacki 5]

Ok, after removing and adding one more fgd 212 (trough the web interface) Association works between two fgd 212 modules.

 

@j.nowacki

 

So three conclusion:

1) Association is broken in security mode

2) add device from mobile phone broken as it adds the device in security mode without asking for.

3) I've lost 8 hours with this problem

Please login or register to see this image.

/emoticons/default_icon_curve.gif" alt=":-/">

 

Small bug:

Added two fgd 212 for testing the association problem.

But until next reboot, the fgd-212 added are with properties isLight = False (but declared in "controlled device" as "lightning" in the web interface)

After a reboot, the value of isLight is now "true"

 It is not a bug in association mechanism, it is desired feature that devices included as secure can only send commands to other secure devices - this can be adjusted with parameters.

Default inclusion as "secure" through mobile device is something worth considering indeed.

Also light property is known bug in current Beta.

 

If you do not see boxes for multichannel associations please give these devices a soft reconfiguration - and of course make sure device can accept them. If there is no association checkbox in single channel column even after reconfiguration that means devices does not have any association group - which is possible. It is kind of a miss, since device can be controlled even in such case - so the problem is in displaying them. It was passed as a bug to developers.

[sjauquet 16]

 It is not a bug in association mechanism, it is desired feature that devices included as secure can only send commands to other secure devices - this can be adjusted with parameters.

 

I tried many times and many ways with disabling security features in the fgd 212 parameters but it was not working also. (for devices included with mobile app, so in security mode)

Also it was not working between my 4 fgd 212 included in secure, they were not able to command each others.