Fibaro Relays

[leonchue]

Just checking, have you tried learning with the latest UCM/Zwave 7.031 version?

[leonchue]

Btw, what is your Z-Wave module version? Version 3.22 and above fixed a bug that identify multi-channel devices wrongly. See Z-Wave manual (page 15) for more details.

[lwillerton]

Hi

Z-wave Chip Type 2
Z- wave chip version 1
Z-wave controller type bridge
Z-wave module info 2.40. Looks like this could be the problem then

UCM version 7.031

[ident]

That is a bug in the Zwave module itself, not the UCM/Zwave firmware
It needs a replacement of the plug in module as the upgrade cannot be done by Comfigurator.
You can return the plugin Zwave module to us for upgrade

[lwillerton]

Hi All

I have purchased another fibaro 2 x 1.5w module and again I am having difficulty getting comfort to recognise both switches on the device.

I have removed it from the installation location around 5 meters away and temporally wired it less than a meter away from the comfort z-wave aerial. I have made sure the output is on when including it in to the network by connecting a lamp.

Vera detects both switches on fibaro and I am able to switch both output on and off, unfortunatly when I go through the include process for comfort it only detects as a basic node.

I am running firmware 7.031 and z-wave module 3.52.

Any suggestions.

 

[juwi_uk]

I\'ve had that too in the past and doing a learn again would usually work.
I\'d say also make sure your primary controller has good battery power but in your case this is Vera so not applicable. 
I think moving a switch is not a good idea in ZWave architecture because it will confuse the mesh network comms which otherwise know the relative position of all nodes in the network.  Removing the device for the the network first would need to be done before you move it.
J 

[lwillerton]

Hi Julian

 

Good to hear from you again.

The reason for moving the module closer to comfort is I just wanted to try and get it detected by comfort as a multichannel node. If I ruled out the distance issue I thought I would be able to remove from the network and go through the process again.

I have gone through the following several (20 - 40 if not more) times.

1.       Removed the fibaro module from vera thus the network and reinstall then learned in comfort.

2.       Removed  comfort from the network and reinstalled

3.       Removed comfort from the network, rest the ucm to factory default and reinstalled.

4.       Tried putting another z-wave module between comfort and the new fibaro module and repeat 1 - 3

5.       Moved fabrio from the installed location to within ½ a meter of comfort z-wave controller and repeat 1 – 3

During this process above the 2 fibaro 2 x 1.5w module I have working stopped and detected as basic nodes again, however,  as soon as I switched both sets of lights on and reinstalled (learned)  they detected as multichannel switches in comfort and worked ok again

I guess all I can do now is order another fibaro 2x1.5w module and try again. The only thing that makes me feel this is not going to work is the fact vera has always detected both switches of the fibaro module and been able to switch both outputs on and off, even in the original and intended location.

To be honest I will give it another hour today just to see if I can get it working.

Best Regards

Lee

[juwi_uk]

Hi
Have to say I\'ve been through these steps before too but usually it has just been a case of doing a learn again and not changing anything on the remote/vera or switch side. 
It seems when Comfort cant properly identify the node it sets it as basic. when the learn does work though all is ok.
J
 
 

[ident]

Could it be that the Fibaro switches are with the old firmware that does not report as multichannel, as reported by Julian a few months back?

[juwi_uk]

The old firmware was in my Remotec primary remote and not anything to do with the Fibraro firmware.