Hi Simon
That’s exactly what I’m experiencing. In some occasions, when pushing the physical switch I don’t hear the relay switching and therefore nothing happens.
However, in my case, some wall switches are really close to the wiring box and other are really far away…and the same behavior is happening on all of them.
As soon as I’ll get some logs I’ll share them here.
Have a nice day.
Eric
Thanks for this ongoing excellent work
I am going to be updating the device handlers for all my Fibaro Double Switches shortly
But first the Fibaro Single Switch in my hallway has been causing me problems. It has become very unpredictable.
I have physically removed it from the light switch to identify its.
It is a Fibaro Single Switch and has the zwave plus logo on the switch sticker.
So I am assuming it is a Fibaro Single Switch 2 Gen5. Right?
I think my issue is with the device handler and not the hardware. Simple physical tests.
I have a number of Fibaro Single Switch modules in the house and I have been adopting the zwave switch secure handler for these without issue.
But I do think this one in the hallway is the only zwave plus Gen 5.
So before I refit this fibaro, am I right in thinking this device handler is the right one for this switch?https://github.com/erocm123/SmartThingsPublic/blob/master/devicetypes/erocm123/fibaro-single-switch-2-fgs-213.src/fibaro-single-switch-2-fgs-213.groovy
Hi again
Does anyone know how to factory reset one of the Fibaro Single Switch 2’s please?
I cant get it to include into the zwave network
I would appreciate advice as this is frustrating
Hi Nigel
According to Fibaro’s official manual for the Switch 2:
Resetting the Switch 2:
1. Switch off the mains voltage (disable the fuse).
2. Remove the Switch 2 from the wall switch box.
3. Switch on the mains voltage.
4. Press and hold the B-button to enter the menu.
5. Wait for the visual LED indicator to glow yellow.
6. Quickly release and click the B-button again.
7. After few seconds the device will be restarted, which is signalled
with the red LED indicator colour.
Now, regarding my issue with both FGS-223 and FGS-213, I’ve finally managed to capture the event on the LiveLog:
3028554d-7015-473a-a6fa-ca12a0349500 21:53:31: debug Unhandled event MultiChannelCmdEncap(bitAddress: false, command: 1, commandClass: 32, destinationEndPoint: 0, parameter: [255], sourceEndPoint: 1)
3028554d-7015-473a-a6fa-ca12a0349500 21:53:31: debug SwitchBinaryReport: SwitchBinaryReport(value: 255) : Endpoint: null
3028554d-7015-473a-a6fa-ca12a0349500 21:53:13: debug MeterReport: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0], precision: 1, previousMeterValue: [0, 0], rateType: 1, scale: 2, scale2: false, scaledMeterValue: 0.0, scaledPreviousMeterValue: 0.0, size: 2) : Endpoint: null
3028554d-7015-473a-a6fa-ca12a0349500 21:53:12: debug Unhandled event MultiChannelCmdEncap(bitAddress: false, command: 1, commandClass: 32, destinationEndPoint: 0, parameter: [0], sourceEndPoint: 1)
3028554d-7015-473a-a6fa-ca12a0349500 21:53:12: debug SwitchBinaryReport: SwitchBinaryReport(value: 0) : Endpoint: null
3028554d-7015-473a-a6fa-ca12a0349500 21:53:02: debug MeterReport: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0], precision: 1, previousMeterValue: [0, 0], rateType: 1, scale: 2, scale2: false, scaledMeterValue: 0.0, scaledPreviousMeterValue: 0.0, size: 2) : Endpoint: null
3028554d-7015-473a-a6fa-ca12a0349500 21:53:01: debug SwitchBinaryReport: SwitchBinaryReport(value: 0) : Endpoint: null
I think one of the event logged at 21:53:12 is what’s causing the issue. Anyhow, I’m certain now that the device is receiving the signal from the physical switch.
Any idea about what could be causing the issue?
Thanks in advance!
Jorge
I have sorted including the switch.
The trick is, it to make sure switch S1 is left OPEN.
Then triple pressing the button works fine to both include and exclude 
Jorge
So helpful.
Later I am going to test using B-button to reset this switch after excluding it.
I will remember to make sure the switch connected to S1 remains open.
This tip was from our friends at Vesternet here in UK. Very helpful bunch
Good to know. That little gotcha is one I have never tripped over before.
FWIW I have never had to exclude before. A reset of the module followed by a Z-wave repair and delete any unfound devices seems also to do the trick.
@gbfabiani, did you manage to solve that problem with the button staying ‘TURNINGON’ state? I already had three double switches on my network that worked just fine. I added a new one which is the only one having this problem.
When I click the phone app button, I see the following in the log, but nothing else. Button stays in ‘TURNINGON’ state and the switch never turns on.
8:24:03 PM: debug childOn(16-ep2)
Other than that, the switch seems to be working using the wall switch buttons.
It become so complicate to me to find ways to get 100 available options working with Fibaro Relais/dimmers , than I finally gave up and buy a Fibaro controller.
I have more than 20 different Relais/dimmers home now and I was looking for simplicity and reliability.
Sorry, I didn’t go ahead using smarthub …
Regards
Giovanni
I fixed it myself after all. Removed, added, removed added, got annoyed, removed, added, gave up, removed, added… worked!
Hi.
Glad to hear you finally fixed it. Sadly, mine are still behaving the same.
However, today I’ve noticed that there is property called “button” (Within the parent device handler) that is sometimes showing the value “held” instead of “push”…I don’t know if that could be related with my issue.
Any advice on how to keep digging on this issue?
Thanks in advance.
Jorge
eric
Keep up the good work…I have just updated and my Fibaro Single/Double switch device handlers.
Thank you
Am I right in thinking we CANT differentiate physical switch changes from programmatic changes via CoRE and webCoRE?
I would appreciate your advice
Hello again
I finally managed to spent some time checking my problem within the LiveLog and I’ve noticed several things:
Unhandled event MultiChannelCmdEncap(bitAddress: false, command: 1, commandClass: 32, destinationEndPoint: 0, parameter: [255], sourceEndPoint: 1)
If I change the switch virtually (Using AT or the ST App), that line doesn’t appear at all (Blue labeled squared text).
After any virtual interaction with the switch, the following physical interaction always reports back the same status the switch already had. (If the switch was off, physically clicking on the switch will report back the off status again).
Finally, I’ve noticed all my logs have the Endpoint:null parameter, but I’m not sure if that’s alright or not.
Any idea about what’s causing it? Any help would be really appreciated.
Can I use this switch for 12volt? I want to try to open my garage door with it
Nope. You need the FGS-212 (Single) or FGS-222 (Double) Relays if you want to switch 12V devices.
Are you sure I see on my last search the only switch that support 12volt is rgbw dimmer fibaro the normal dimmer is 110-220
You can use the 212 because it has dry contacts. if you look at the wiring diagram you can see how it has a separate connection for the source power, which can be any voltage.
The relay is still powered by your mains, but you can switch any voltage up to 48V if I remember correctly.
If you want to power the relay with 12V, then the RGBW dimmer is indeed as far as I know, the only unit which can be powered by 12V. I suppose you will be able to use the RGBW dimmer as a switch if you want to.
The Fibaro Universal Binary Sensor has 2 potential free outputs and can be powered by 9-30v. It also has 2 potential free inputs you could use this to sense door open and door closed. Worth a look!
SIMON can you give the link with that info because in web site says
Power supply: 110-240 V AC, 50/60 Hz
