Hello,
has anyone managed to get the Fibaro Universal Binary Sensor to work with v2? When I add it it ends up as a basic z-wave device and I can’t get the Input 1 or Input 2 to change state in Homey.
Yes, works fine here with Homey 2.0.1 and Fibaro app 2.1.19
Sorry for this question, did you install the Fibaro app? And if yes, which version are you running? Maybe tell us the Product Id.
All of my double switchs 2 installed 9 months ago correctly update the device status when manually changed at the wall.
The one switch I repaired on 2.0.1 (and is added as insecure) does not update its state correctly. When where your switches installed @David_K ?
Yes, maybe it’s actually just like you said. I’ve noticed once or twice out of sync state on single switch. Then I’ve installed fibaro app update 2.1.19 and after that I can reproduce the error only on double switch 2 on S2 on device that was repaired after v2 like you said.
Ok, as long I’m not the only one. I’ve sent issue report to athom. Thnx for confirmation @Jamie
It looks like the Product Id (258) of your unit is not included.
Since this app was written by Athom, I would report this issue here: https://support.athom.com/hc/requests/new
They pretty good in adding a new product Id.
May I ask you in which country you are using your Homey? Different regions have different z-wave frequencies hence, different product IDs for the same type of product.
Thank you! I will report this to Athom. I am usine my Homey in Sweden.
Interesting! Sweden has the same z-wave frequency as the whole Europe so your Universal Binary Sensor should have the Id already included… unless Fibaro has given it a new Id.
@Jamie Initially when FGS-223 issues surfaced fibaro app was updated to 2.1.17. We were then able to re-paird it again in homey. Before it was reporting error during device pairing. A day after Athom released 2.1.18. I don know what was different but I already had it paired and didn’t try to re-pair again on 2.1.18. Yesterday I tried just that. It’s again included in z-wave as insecure but after the routes settled (I left it for 15-20 minutes) it looks to me like states are updating now. I will test today a bit more.
EDIT: It really does seems to be updating correctly after re-pairing it on 2.1.18.
About two months ago I did mention and did make an issue to Athom about the RGBW switch not functioning perfectly.
If the swicht is set to a RGBW LED the general dimming is not including the White channel. (It even switching it off)
For that I did make a work around dimming the white channel separately.
But because the general dimming is first switching off the white channel, everytime I dim general, the white channel is going off for a moment and then controlled again by the separate white dim command.
Is somebody knowing this issue is still in progress?
The fixes are currently in the alpha channel, not sure when it is being pushed to beta/stable, @MatthewWaanders knows more.
Thanks
Does anyone know what the status is with fixing the tamper alarms ?
1 Like
How about the implementation of the new Fibaro Smart Implant?
Is the Universal Binary Sensor successor already supported by the Fibaro App??
If not, is there any plan to support the new Sensor?
It’s not yet supported I guess, looking at the app-page. Nice device 
You can do a feature-request:
Solution : Dual Switch 2 not reporting power .
Ok, I’ve done some research and found a couple of examples from other controllers on how they solved the dual switch 2 power reporting issues. (All of them seem to be solving it in a similar way).
I sent a support ticket into to Athom a couple of weeks ago but they never responded.
From what I can tell it requires that remove the group 1 association and add a mult-channel association.
The problem I have is I just don’t understand multi-channel groupings well enough to convert this into ‘homey . format’. 1 1.0 1.1? (guess?). Apparently with out the removal of the original association it wont work it is command class 133, but thats where I get lost.
Is there someone who can help me out?
Here are the demos of how to do it in each of the different controllers
Vera
luup.call_action('urn:micasaverde-com:serviceId:ZWaveNetwork1','SendData',{Node='20',Data='133 4 1 1'},1)
luup.call_action('urn:micasaverde-com:serviceId:ZWaveNetwork1','SendData',{Node='20',Data='142 1 1 0 1 1'},1)
Smartthings
zwave.associationV2.associationRemove(groupingIdentifier: 1, nodeId: zwaveHubNodeId)
zwave.multiChannelAssociationV2.multiChannelAssociationSet(groupingIdentifier: 1, nodeId: [0,zwaveHubNodeId,1])
OpenZwave
Manager::Get()->RemoveAssociation(homeID,nodeID, 1, 1, 0);
Manager::Get()->AddAssociation(homeID,nodeID, 1, 1, 1);
Links
what did i do 
@Jamie your guess was right with the option of 1.1 as association value in group 1, i can’t test that though for the switch 2’s, have nothing connected to my switch 2’s output so if you could test that 
2 Likes
I asked the support about there strategy to handle and acknowledge the tamper alarm, but they did not answer my questions. The only feedback I have got was:
We are currently investigating this issue and hope to fix it asap.
…
I have forwarded your suggestion to the development team.
So I hope they are working on it.
