Update from MCV:Regarding power useage I was able to see it on the parent device but not on the children devices because they didn?t report power usage via Z-Wave.If you dont?t see any power usage on the parent device you might have an issue with wiring so you can check the device manual or contact Fibaro.Regarding instant status report on the inputs , our development team is currently working on it.You can try to remove the value 38 from Capabilities (and reload the engine) on the parent device as well as on the inputs and see if this will work.The issue with can?t detect device is also related to capabilities. The device reports that it support CC Switch Multilevel and Vera is using this command class to poll it instead of CC Switch Binary.Our development team will try to fix the issue but I don't have an ETA.

For me the capabilties were:Master211,156,1,4,16,1,L,R,B,RS,|34,37S,50:3,86,89,90S,91S,94,96S:4,112S,113:5,114,115,117S,122,133S,134,142S,152,

child 1211,156,1,4,16,1,L,R,B,RS,|37,38,50,89,94,133,134,142,239,

child 2211,156,1,4,16,1,L,R,B,RS,|37,38,50,89,94,133,134,142,239,

I removed the 38 and I will monitor behaviour

UPDATE1: Only Q1 channel is power monitored. The power is displayed on the master device.

UPDATE2: Removing 38 is not possible... It just comes back. In the meantime I received another mail:After you have removed 38 from Capabilites from both children did you also reload the engine after each removal ?You can exclude and re-include the device.Then on the parent and each children do the following : click on the ?>? button for each device , go to Advanced → Variables and under Capabilities remove the value 38 , go to New Service and hit Reload Engine.After the engine reloads hit Ctrl+F5 on your keyboard and check if 38 was removed.If this doesn?t work then we need to wait until the bug is solved.

So... wait for Vera...

UPDATE3:I have found a workaround for the can't detect device and Instant Status Report.You should remove value 38 from the parent device from the variable called MultiChCapabilites (then go to New Service and hit Reload Engine) and also remove value 38 from each child device (and also reload the engine , each time you remove it).(I removed it from Capabilities as there is no MultiChCapabilites in the childs)Also you should add the following service id , variable and value for both children and also Reload the Engine :urn:micasaverde-com:serviceId:ZWaveDevice1BasicSetCapabilities00=F0,FF=O0

Done and I will observe

« Last Edit: December 24, 2016, 07:13:36 am by Sender »

Logged

Good firmware is more important than good karma. (and this costed me lots of Karma)

HiThanks for the guide! I have now got the Child units to be able to control the switch but they don?t get an update wether the switch is on or off. I am rather new on the vera UI, is it possible for someone to explain a little bit more in detail regarding the following:"Also you should add the following service id , variable and value for both children and also Reload the Engine :urn:micasaverde-com:serviceId:ZWaveDevice1BasicSetCapabilities00=F0,FF=O0"

In my new service tab i have the following fields:"New Service""New Variable""New Value"

Hi you guys,I also have this problem that the second channel of the FGS-223-ZW5 v3.2 does not work. I tried the described solutions but with me it does not seem to work.I also have two of the predecessors of this switch, FGS-222-EN-A-v1.00, where one works fine, and the other one does have the same problems as described.The one that works fine though has manual switches connected and all other ones (old and new, that don't work) don't have manual switches connected, I only use the relays to switch on lamps.So, to me it seems that the connected manual switches have something to do with it, although it can be coincidence. I also had some troubles to get the devices of the new series connected to the network. I kept keeping messages like "Can't detect device" and "User configuration settings", although the devices seemed to work properly, except for the second channel.

If somebody could help me with this problem I would be much obliged, it seems to me a kind of 'configuration settings' problem.

The above described procedures will only work for FGS 223. To my knowledge the predecessors FGS 222 should not have any problems, unless it's some kind of initial configuration issue, in which case, support would be able to check this out and point you to the correct solution.

Don't forget to also enable customer care remote access in the initial email, so things will go faster.

HiThanks for the guide! I have now got the Child units to be able to control the switch but they don?t get an update wether the switch is on or off. I am rather new on the vera UI, is it possible for someone to explain a little bit more in detail regarding the following:"Also you should add the following service id , variable and value for both children and also Reload the Engine :urn:micasaverde-com:serviceId:ZWaveDevice1BasicSetCapabilities00=F0,FF=O0"

In my new service tab i have the following fields:"New Service""New Variable""New Value"

What shall I put into these fields?

Yes in that order

Logged

Good firmware is more important than good karma. (and this costed me lots of Karma)

I also cant get this to work with the procedure described above. I can control the children from the UI, but status reporting does not work. I cant believe how long it is taking for Vera to include this popular new device - 3 firmware versions on with all kinds of functionality included that I am pretty sure nobody will trust a Vera to manage (like security) and pretty much NO new device support.