The status updates for on/off and dimming are by far improved with your device handler, so itās a good start.
Let me know if you want me to test something else!
UPDATE: With your DTH the Dimmer 2 actuallyt DO report the correct status when physically triggering the switch as well. It seem to work about 9 out of 10 times, sometime getting stuck in the incorrect state. But this is miles better than before, when the status was never updated when using the switch physically. Im starting to see the light in the tunnel over here
ā¦now if the Fibaro EU Plugs could only get the same treatment
@steven.green, is there any particular reason, why only the Double Switch 2 has this code only? Shouldnāt all the other DHs force the groupingIdentifier? (Seeing the issue, that for some reason these devices do use MultiChannel encapsulation. Or is it just a matter of the Zwave inclusion by ST, where multichannelassociation set some incorrect way? I am just guessingā¦)
def zwaveEvent(physicalgraph.zwave.commands.multichannelassociationv2.MultiChannelAssociationReport cmd) {
def cmds = []
if (cmd.groupingIdentifier == 1) {
if (cmd.nodeId != [0, zwaveHubNodeId, 1]) {
log.debug "${device.displayName} - incorrect MultiChannel Association for Group 1! nodeId: ${cmd.nodeId} will be changed to [0, ${zwaveHubNodeId}, 1]"
cmds << zwave.multiChannelAssociationV2.multiChannelAssociationRemove(groupingIdentifier: 1)
cmds << zwave.multiChannelAssociationV2.multiChannelAssociationSet(groupingIdentifier: 1, nodeId: [0,zwaveHubNodeId,1])
} else {
logging("${device.displayName} - MultiChannel Association for Group 1 correct.","info")
}
}
if (cmds) { [response(encapSequence(cmds, 1000))] }
}
Wait for ST to come back with a proper solution. I am happy that I could help temporarily.
But this issue has some underlying reason probably, what needs to be identified and fixed.
None of these devices should use MultiChannel encapsulation by default, this is something new. And they shouldnāt report from sourceEndPoint 1, and should not report to destinationEndPoint 1, I believe.
I am not a zwave guru, but it doesnāt seem to be right.
Hey I can confirm your device handler is also working for me on my fibaro dimmer 2.
When I switched status on the app and at the switch on the wall it updates immediately.
Yes. I have multiple Fibaro Switch 2 devices and they all behave the same. From the packaging: āSingle Switch 2 FGS-213 ZW5 v3.2ā
These devices have been installed for a couple of years now as Iāve been using other controllers: OpenHAB/HASS/Indigo Domo (using Aeon Z-Stick) SW based ones and Homey HW based one. I do have a few Fibaro Dual Switch 2 too and Iām confident in telling them apart.
The three Fibaro Switch 2 devices Iāve been testing with are all connected in the simplest way possible. A single momentary switch on S1 and one fixture on Q, as in the first diagram shown:
The Fibaro Switch 2 devices were factory reset before included in ST so all settings (except 20. Switch Type that I changed to Momentary) should be the default values.
Sorry for replying before reading the full thread.
@GSzabados I too can confirm that your DH works WAY better for my Fibaro Dimmer 2 devices. Feedback is way quicker both when using the app and the physical switches.
The Fibaro handlers were written by Fibaro (a long time ago).
On our side, weāve since incorporated some default association (and multi-channel association) code into our device join process, largely to eliminate having to include this kind of boilerplate in every DTH.
Thanks - if I do that it doesnāt seem to show status of the physical switch, but does work properly for smartthings controlled in the app, my use case needs to know physical switch state, did you see the same?
No sorry mine works with the physical switch and the app and updates status nearly instantly, maybe you should try excluding your switch and reset it completely.