Fibaro FGS-223 in electrical socket, controlling issues with C-7

[cinramn]

Hi, just got my C-7 to register my Fibaro FGS-223 using the erocm123 drivers.

I connected it to my electric socket only on q1:

According to the fibaro single socket video:

HomeKit Single Switch socket installation

I assigned the Fibaro fgs 223 driver to the device.
I see in device details:

• deviceType: 515
• zwaveSecurePairingComplete: true
• inClusters: 0x5E,0x86,0x72,0x59,0x73,0x22,0x56,0x32,0x71,0x98,0x7A
• zwNodeInfo: D3 9C 80 04 10 01 5E 86 72 59 73 22 56 32 71 98 7A 68 23 F1 00 25 5A 85 5C 70 8E 60 75 5B EF 26
• secureOutClusters: 0x26
• secureInClusters: 0x25,0x5A,0x85,0x70,0x8E,0x60,0x75,0x5B
• deviceId: 4096
• S2: 128
• manufacturer: 271

I've changed some settings and pressed save preferences. Only button that seems to work is configure, it gives me:

Current States

• numberOfButtons : 5
• needUpdate : YES

What does this needUpdate mean? is it the fibaro device?
I updated the zwave firmware in hub to latest, same with hub itself.

Pressing anything else refresh/on/off does nothing. I also see in logs:

dev:97 2020-08-17 10:44:47.618 debug Current value of parameter 29 is unknown
dev:97 2020-08-17 10:44:47.616 debug Current value of parameter 28 is unknown
dev:97 2020-08-17 10:44:47.615 debug Current value of parameter 59 is unknown
dev:97 2020-08-17 10:44:47.613 debug Current value of parameter 58 is unknown
dev:97 2020-08-17 10:44:47.611 debug Current value of parameter 57 is unknown
dev:97 2020-08-17 10:44:47.610 debug Current value of parameter 55 is unknown
dev:97 2020-08-17 10:44:47.608 debug Current value of parameter 54 is unknown
dev:97 2020-08-17 10:44:47.606 debug Current value of parameter 53 is unknown
dev:97 2020-08-17 10:44:47.605 debug Current value of parameter 51 is unknown
dev:97 2020-08-17 10:44:47.603 debug Current value of parameter 50 is unknown
dev:97 2020-08-17 10:44:47.601 debug Current value of parameter 44 is unknown
dev:97 2020-08-17 10:44:47.600 debug Current value of parameter 43 is unknown
dev:97 2020-08-17 10:44:47.598 debug Current value of parameter 42 is unknown
dev:97 2020-08-17 10:44:47.596 debug Current value of parameter 41 is unknown
dev:97 2020-08-17 10:44:47.595 debug Current value of parameter 40 is unknown
dev:97 2020-08-17 10:44:47.593 debug Current value of parameter 20 is unknown
dev:97 2020-08-17 10:44:47.592 debug Current value of parameter 18 is unknown
dev:97 2020-08-17 10:44:47.590 debug Current value of parameter 17 is unknown
dev:97 2020-08-17 10:44:47.587 debug Current value of parameter 16 is unknown
dev:97 2020-08-17 10:44:47.583 debug Current value of parameter 15 is unknown
dev:97 2020-08-17 10:44:47.578 debug Current value of parameter 13 is unknown
dev:97 2020-08-17 10:44:47.574 debug Current value of parameter 12 is unknown
dev:97 2020-08-17 10:44:47.572 debug Current value of parameter 11 is unknown
dev:97 2020-08-17 10:44:47.570 debug Current value of parameter 10 is unknown
dev:97 2020-08-17 10:44:47.568 debug Current value of parameter 9 is unknown
dev:97 2020-08-17 10:44:47.566 debug Adding MultiChannel association group 1
dev:97 2020-08-17 10:44:47.555 debug Configuring Device For SmartThings Use

Think this is just after i've pressed save preferences.
Is there something that i have missed? I'm very new to all this.

Cheers

EDIT:
Seems like reporting is working at least:
dev:97 2020-08-17 11:40:40.863 debug MeterReport: MeterReport(meterType: 1, precision: 2, scale: 0, size: 4, meterValue: [0, 0, 0, 0], rateType: 1, deltaTime: 0, previousMeterValue: []) : Endpoint: null
dev:97 2020-08-17 11:26:55.868 debug MeterReport: MeterReport(meterType: 1, precision: 1, scale: 2, size: 2, meterValue: [0, 0], rateType: 1, deltaTime: 0, previousMeterValue: []) : Endpoint: null

[njanda]

Just wondering if you followed the instructions here;

Fibaro FGS-223

Hi Guys, I'm 90% through porting everything over to Hubitat, but im running into dramas with the DH for the FGS-223. using all the current DH's around, I can only get it to operate the first relay, or none at all. Has anyone got (or wish to port) a DH from ST? it was working fine on ST before A lighting strike blew up my ST hub I will say though, that the speed difference here in AUS (comparing to ST) is lightning fast! (no pun intended) TIA

Especially.......
thing to note is that you must install the metering switch driver first
Then the driver creates two virtual switches that control the two relays.
Then ignore the ‘parent’ device and use the two switches.
Tagging @ericm

[cinramn]

I had both drivers installed before i manage to get my hub to find the device. Then i was clicking randomly everywhere
In the end i manage to select the FGS driver to the device and there was no S1 or S2, then when i clicked save preferences the S1 and S2 appeared under it.

Question is though, am i using it wrong? i do not have S1 or S2 wired. I just want to control it to be on or off.

Z-wave sees the device just fine:

[njanda]

Can you come back to the main Device page and then enter just S1 or just S2 and activate either one ?
Sorry I’m no experience with such a device.

[bobbles]

Mine do not work on a C7 hub.
Work fine on my C3 and C5.
This has been documented in other threads.
@ericm did modify his driver for this device as the security settings were incorrect after the latest update.
I still couldn't get it to work though. I have 2 x 223s that are now useless on the C7.

[cinramn]

Thanks for sharing your experience, so typical me to get the "wrong" device from start. Hopefully he got some time to look into this. Sadly my experience here is very limited to help out in the driver code.

[ericm]

Mentioned in another thread, but I believe a Hubitat firmware update fixed this. Everything working for me.

[cinramn]

Ah ok, i bought some 213 and replaced the 223. But the 223 will be used for a lamp switch and not an outlet. So will test when i got that sorted out.

Cheers

[bobbles]

@ericm

Mentioned in another thread, but I believe a Hubitat firmware update fixed this. Everything working for me.

Would you mind confirming the revision of your driver. I just tried on a 223 that I just paired and it will not define the child devices.
Thanks.

EDIT:
Got it working OK. Just need to wait for the child devices to define. Takes a while for some reason. Now working OK. Thanks again.

[djh_wolf]

mine won't refresh the status of either child, unless manually refreshed (c7 hub).