Fibaro FGS-223

dragner · March 25, 2020, 1:40pm

Yes, I already had the two drivers installed FG223 and Metering Switch Child Device before to Include the device.

The strange thin is than everything seems to work perfectly, the Child devices receive the notification of the physical changes of the switch. But If I try to on/off from the child device it has like a big lag.

bobbles · March 25, 2020, 1:57pm

Not sure what to suggest. Mine is working OK.
Maybe try a z-wave repair to see if things clean up.

dragner · March 25, 2020, 4:51pm

Tried also without result, also exclude& include and reseting the FGS223

bobbles · March 25, 2020, 5:02pm

I really don't know what else to suggest apart from removing everything and starting over again making sure both drivers are installed before you pair the z-wave device to the hub.

With mine I can open a dashboard page instance and the child driver page.
Watching both windows I can turn on and off in either window and the other one shows the change within 1 second.
Sorry I could not be more helpful.

dragner · March 26, 2020, 8:17am

I tried with the oficial Fibaro Switch than should be compatible, with the same results, I think than the issue is not in the driver, it's on the device, the hub or zwave network, I will do more tests.

nigelmwilliams7 · June 7, 2020, 9:17am

Hi all

I am cross posting this to see if anyone else is experiencing this -

The main issue I am observing is Dashboards not reflecting current status as well as Groups (where they are setup to show any on as on).

Any ideas?

jonathan.rostron1969 · June 7, 2020, 11:29am

Hi,
I have just checked mine and am having similar symptoms. I have two of these switches and both are making similar reports in the logs. Also, on the devices page for the device, when I switch on, it is clearly operating the lights, but there is no indication in the log that the light has operated and also the switch status remains off. I am also using ericm123's drivers and metered child devices. Just noted that in the release log for 2.2.1 the following:

All Z-Wave drivers: switchBinarySet and switchMultilevelSet commands will replace basicSet for devices that support the switchBinary and or switchMultilevel classes, this is a requirement of Z-Wave certification.

Looking at the driver, there are a number of basicSet commands used, so I assume this is the problem. Not sure how to go about replacing them, though.

bobbles · June 7, 2020, 1:44pm

Same happening for me too.

Seeing this in the logs for the child devices. (EP-1 & 2).

Tagging @ericm.

bobbles · June 7, 2020, 3:01pm

Folks.
To resolve this go into the driver code and change all instances of multichannelv3 to multichannelv4.

This fix is courtesy of @christi999 .

nigelmwilliams7 · June 7, 2020, 4:19pm

Perfect thank you @bobbles for replying and thanks to @christi999.
Where did you find this solution please @bobbles?

bobbles · June 7, 2020, 4:22pm

Christi999 has re-released his driver for the Fibaro implant.
I decided to take a look at it and in his notes he mentioned it was updated to make it work with the last update.
I asked what he did, tried on the 222 and 223 drivers and it did the trick.

jonathan.rostron1969 · June 7, 2020, 6:09pm

Worked for me, thanks.

imbeta · August 4, 2020, 6:25pm

I am having issues with the update of the swich state when using the wall switch.

It works without problems from the device page, on and off, and the state updates in the dashboard accordingly.

However, if when the light is on, I switch it off from the wall switch, the light in the dashboard and the switch state remains ON. If I switch it off from the device page or the dashboard, the state updates to OFF and the light remains off.

EDIT: If switch on and off from the wall, it updates well in the dashboard, it only fails when switch on from the dashboard and off from the wall. The switch in the dashboard remains ON.

9999341 · August 19, 2020, 5:19am

Hi,
After last system update 2.2.2.X All fibaro switches stopped working for me.
I took the latest version (15 Aug 20) but the new version

has a bug that no handling multichannelv4, anyway - I fixed it.
The activation is not working, so If I click in the driver on Turn Off it shes in the log the ChildOff, but it is not performed and nothing happens. the same occur if I click on the child in the dashboard.
Any assistance?

bobbles · August 19, 2020, 6:19am

Are you on 2.2.2.xx or 2.2.3.xx which is the latest update.
On the latest I have found that Fibaro devices that use custom drivers no longer work correctly.
They either do nothing or do turn on and off but do not update status.
I have 5 which no longer work on the C7 but are ok on my C3.

9999341 · August 24, 2020, 10:14am

@Cobra , I have the C3/C4 but it doesn't work. Using the latest driver. (and latest HE)
I analyzed the problem and here are my findings:

GrumpyTeddy · September 28, 2020, 8:04am

I've said it before and I'll say it again.... You're a legend, mate. The bug with the status not updating and dashboard switches bugging out has been driving me crazy for months. I finally got round to looking into the problem and this right here was the issue. Updated the code to "multichannelv4" and bam! fixed!

nigelmwilliams7 · December 3, 2020, 9:37am

Hi all
Over the weekend I updated the metering child device handler as @cjcharles0 has updated for home automation platforms.
I am assuming the simple changes to this are not the cause of the issues I am now experiencing.
I have a C5 running 2.2.4

Although the switches are working, there are debug messages appearing in the Live Log -

Also the state of the child devices is not updating, and can only be state synced using the Refresh button on the child device screen. This is having a side effect of the effective use of Groups...

Is anyone else experiencing these issues with Fibaro FGS-223s using @ericm device handlers ?

cjcharles · December 3, 2020, 10:28am

If youre talking about the child update so it is detected as a light then yes I did make that change, but that doesnt explain your issue.

I have a C7 hub and have been having a number of issues with my FGS222 and FGS224 devices (I skipped the FGS223 model for some reason, and had slightly different issues on each of the 2.2.4 firmware versions!).

I think Ive solved most of them now for my devices, and they might work with the 223 model if you can't get your device handler working. A fair few of the issues seem to be caused by the switch from multichannelv3 to multichannelv4 (driven mainly by Hubitat firmware I think) - have you changed all references in the device handler from v3 to v4 already?

nigelmwilliams7 · December 3, 2020, 10:55am

@cjcharles I wasnt inferring at all that the change has caused. Just explaining why I updated.

I am looking at the fgs223 device handler and have changed as you suggest -
def zwaveEvent(hubitat.zwave.commands.meterv4.MeterReport cmd, ep=null) {
def zwaveEvent(hubitat.zwave.commands.multichannelv4.MultiChannelCapabilityReport cmd)
def zwaveEvent(hubitat.zwave.commands.multichannelv4.MultiChannelCmdEncap cmd) {

private encap(cmd, endpoint) {
if (endpoint) {
zwave.multiChannelV4.multiChannelCmdEncap(destinationEndPoint:endpoint).encapsulate(cmd)
} else {
cmd
}
}

and the state is still not being updated.
I see there are loads of other V1 & V2 commands in the device handler also.
Do these need to be updated?

Where is this all documented so I can debug issues more effectively in future?