Some trouble with Fibaro FGS221

Setup, Configuration and Use Items & Sitemaps
1

Hi I have problem with new version FGS 221 (Fibaro Double Switch)
I don’t have problem with switch, but with survey energy. It doesn’t work
I use the same parameters what I have in fibaro dimmers and wallplugs
Has somebody this problem?

Switch P2_Biuro_Router “Router [%s]” (P2) { zwave=“79:1:command=SWITCH_BINARY” }
Switch P2_Biuro_Fibaro “Fibaro [%s]” (P2) { zwave=“79:2:command=SWITCH_BINARY” }
Number P2_Biuro_Router_Power “Aktualne zużycie: [%.1f W]” (P2,AKT_ENERGIA) { zwave=“79:1:command=sensor_multilevel” }
Number P2_Biuro_Router_Energy “Całkowite zużycie: [%.2f KWh]” (P2,CAL_ENERGIA) { zwave=“79:1:command=meter” }
Number P2_Biuro_Fibaro_Power “Aktualne zużycie: [%.1f W]” (P2,AKT_ENERGIA) { zwave=“79:2:command=sensor_multilevel” }
Number P2_Biuro_Fibaro_Energy “Całkowite zużycie: [%.2f KWh]” (P2,CAL_ENERGIA) { zwave=“79:2:command=meter” }

2

Why? This is a different device - it has updated firmware, and I know that some new Fibaro switches are using very different configuration. You should look in the node XML file - that’s what it’s there for. It will tell you what endpoints and command classes are supported.

3

I have second problem I don’t see node number 79 in /var/lib/openhab/zwave
All rest node XML files I have but not this device and also I see that in zwave binding section this module has grey colour.
What should I do?

4

I would get a debug log and display it with the log viewer to see what’s happening.

5

everything is ok. I had wrong zwave binding file. Now I have 1.9 version and work well