I've got a bunch of Fibaro FGS 223 double switches, and I'm using @ericm 's driver which is great (this and Eric's driver for the Fibaro Dimmer 2 are the ones to use I think).
However, I've just discovered some very weird behaviour.
They switch on OK, but they then need two off commands to actually switch off.
This is true whether pressing the physical switch), or sending the command from HE.
If it happens from the physical switch, does this suggest it's an issue in the firmware? (though I don't remember this happening when these were running under ST, but I had much bigger problems with ST, so this level of issue would likely have gone un-noticed)
The fact that it happens from HE as well as the switch suggests to me that it's not an issue with the definition with the switch type - I've flicked the driver to "Z wave tweaker" and checked that param 20 is zero.
Weirder still, after sending the 1st "off" from HE, (which does not switch the lights off), if I then send an "on", the lights switch off (this results in motion lighting routines switching the lights off as you walk in to the room!).
I have 7 of these, and I think it's happening on all of them. I've checked the log behaviour on two, and it's identical.
And so to the logs:
Driving from HE, this is one "on" followed by two "off"s:
The event log for the metering child device only shows the succesfull command, though it does seem to trigger a further power report:
Now the same, using the physical switch:
And on to the SUPER weird behaviour - from HE, "on", then "off", then "on":
The return value of SwitchBinaryReport seems to be pointing to something....
Has anyone spotted this before or got any ideas?
It's annoying, but liveable with the switches, but it makes the motion lighting routines unusable - I could code round the issue and write my own routines for these, but I'd like to fix the root cause if I can.
Eric - if you spot this, and think it might be a driver issue, or fixable within the driver, I'm happy to have a go at tweaking the code with any guidance, or to test any alterations (I can code, though have not (yet) got in to Groovy, or writing drivers)