Thanks. Thats super weird, there is nothing different between endpoint 1 and endpoint 2 in the code.
When do you miss the automatic state update? When you press the wall switch, press the parent device button, press the child device button....?
I have 3 fgs222 relays. On all of them, switch 2 is not updated once not controlled by HE = controlled by physical switch, or by automatic turn off by relay itself. Once switch 1 is changed, switch 2 status is updated as well. But if only switch 2 is changed, HE will not record this status change.
Thanks Igor, much debugging later I was able to reproduce it and eventually fix it. I think there is something funky in the way the association groups are configured causing some reports not to send. Can you update to the version on latest GitHub above, and then set all 3 association groups to false, finally press configure. Hopefully this gets everything working at last!
Ok, tested proposed solution with a updated latest driver, configured all groups to "false" and besides the S2 is not reporting its state back, niether S1 
. I will try to pair FGS as a new device to HE and will see what happen.
Thats super weird, do you see nothing in Live Logging at all when pressing the wall switch?
Also just to confirm you have a C7 hub? And the device is paired with no security (I dont believe S0/S2 work with the FGS-222). Im semi tempted to try and arrange a team viewer session or something so I can see what is going on and how it might behave differently from my end.
What are your configuration settings/parameters? Can send me in PM to avoid spamming others perhaps....
I added another FGS222 and its the same. I can see only updates in logs once S1 is controlled. If S2 switch is used, log is empty.
Tested it here too now. (note I dont have C7 hub)
All seems to work ok for me.
Created the child devices fine.
The relay isnt connected to a physical switch, I only ever use HE commands to control it.
State appears to be reflected in the parent regardless of where or how I trigger it.
If I use S2 child to turn on one child, the parent state appears to update ok.
I use the Mirror app to have other lights follow the parent state of the FGS-222.
Every now and again they seem to miss a state change, but that was happening irrespective of what driver I used on the FGS-222. Havent had time to try and figure out what causes that yet.
Thanks for that.
It was the physical switch bug that I fixed today (another small change in the GitHub version to solve it) which I guess isn't a problem for you given what you say.
Despite that I'm not sure how it would miss a state change digitally as I haven't seen that problem myself (the auto off timers don't do state changes very reliably, but otherwise it seems good for me with this afternoon's version).
Happy to have a more detailed look if you send me your configuration details by PM and I can try to recreate. Perhaps the solution for you is to actually set the association groups correctly, rather than using an app to mirror state...
I'm moving my to HE (from Smartthings) and have many of the FGS-222 relays and therefore very grateful for your driver.
I'm using your driver.
The driver works well, apart from that I have the same issue as @Berthoven. I also don't have any buttons attached and control the devices with webCore only.
While S1 updates the state of the child and parent devices, S2 fails to update the status of the S2 child device and the status of S2 in the parent. Switching S1 updates both children (i.e. if S2 is out of sync, switching S1 refreshes S2's status if it got out of sync) and the parent.
I see the same if I switch S2 from within the device setup page in HE.
I was wondering if you or anyone has find a solution to this issue?
I tried Robin's older driver, but that fails to update the status of the parent and children.
Edit: I suppose it is important to note that I use the FGS-222 as a "momentary switch" (to control my Somfy curtain motors.
Thank you.
Can you paste your settings here so I can try and emulate the problem here? (a screenshot would be fine)
I expect the problem will be to do with association groups as I have seen similar problems on other device handlers, so we might need to do some debugging to see what it says after that.
Might also be worth setting the first and second association group to true, then saving, configure, wait. Then reverse the change and see if the behaviour improves at the end or even at the midpoint.
EDIT: Definitely give the association group option a go as I realise they are never set without this action. Even though the Fibaro docs say this should be false, it may need setting once anyway....
Thank you for your response.
I have tried what you suggested (on 2 of the devices), but they still display the same behaviour.
Example of settings:
Some more info that may help troubleshoot the issue. One of the FGS-222's is working fine (i.e. updating the status when turning S2 off.) The settings of this one is:
Could parameter 14 (Toggle vs Momentary) be the culprit?
The device data of this relay:
- deviceType: 515
- zwaveSecurePairingComplete: true
- inClusters: 0x5E,0x86,0x72,0x59,0x73,0x22,0x56,0x32,0x71,0x98,0x7A
- secureOutClusters: 0x26
- secureInClusters: 0x25,0x5A,0x85,0x70,0x8E,0x60,0x75,0x5B
- deviceId: 4096
- S2: 128
- manufacturer: 271
It joined the network with S2 security.
The data of the version not updating S2, differ slightly:
- deviceType: 514
- inClusters: 0x72,0x86,0x70,0x85,0x8E,0x60,0x25,0x27,0x7A,0x73
- zwNodeInfo: D3 9C 00 04 10 01 72 86 70 85 5C 8E 60 25 27 7A 73 EF 25 60 68 23
- outClusters: 0x25,0x60
- deviceId: 4098
- MSR: 010F-0202-1002
- manufacturer: 271
This one joined the network with no security. (None).
Wait, you have an FGS222 which joined with S2 security? I didnt even know that was possible as I didnt think it supported S2.... (S0 perhaps but even that is missing from my units...) Definitely the same version? Not a 224? I'll have a look at the deviceTypes/ID and see if I can find any more information from Fibaro on them.
S2:128 is S0
You had me worried there, but I checked - definitely FGS222. I'll report back if I notice anything else of significance. Thanks
Weird. All of those settings match mine and Im not having any problems....
Can you install the Basic Zwave Tool, swap the device handler for the device temporarily, then run the 'Get Association Report' command. Should look a bit like the below
[dev:235]2022-09-11 11:27:19.386 [info]AssociationReport- groupingIdentifier:5, maxNodesSupported:0, nodes:[]
[dev:235]2022-09-11 11:27:18.860 [info]AssociationReport- groupingIdentifier:4, maxNodesSupported:0, nodes:[]
[dev:235]2022-09-11 11:27:18.360 [info]AssociationReport- groupingIdentifier:3, maxNodesSupported:1, nodes:[]
[dev:235]2022-09-11 11:27:17.859 [info]AssociationReport- groupingIdentifier:2, maxNodesSupported:5, nodes:[]
[dev:235]2022-09-11 11:27:17.366 [info]AssociationReport- groupingIdentifier:1, maxNodesSupported:5, nodes:[1]
dev:2892022-09-11 16:01:12.045 infoAssociationReport- groupingIdentifier:5, maxNodesSupported:0, nodes:[]
dev:2892022-09-11 16:01:11.455 infoAssociationReport- groupingIdentifier:4, maxNodesSupported:0, nodes:[]
dev:2892022-09-11 16:01:10.866 infoAssociationReport- groupingIdentifier:3, maxNodesSupported:1, nodes:[]
dev:2892022-09-11 16:01:10.276 infoAssociationReport- groupingIdentifier:2, maxNodesSupported:5, nodes:[]
dev:2892022-09-11 16:01:09.687 infoAssociationReport- groupingIdentifier:1, maxNodesSupported:5, nodes:[1]
dev:2892022-09-11 16:00:31.127 infoConfigurationReport- parameterNumber:43, size:1, value:0
dev:2892022-09-11 16:00:30.819 infoConfigurationReport- parameterNumber:42, size:1, value:0
dev:2892022-09-11 16:00:30.511 infoConfigurationReport- parameterNumber:41, size:1, value:0
dev:2892022-09-11 16:00:30.202 infoConfigurationReport- parameterNumber:40, size:1, value:0
dev:2892022-09-11 16:00:29.894 infoConfigurationReport- parameterNumber:39, size:2, value:2
dev:2892022-09-11 16:00:26.775 infoConfigurationReport- parameterNumber:33, size:1, value:0
dev:2892022-09-11 16:00:26.466 infoConfigurationReport- parameterNumber:32, size:1, value:0
dev:2892022-09-11 16:00:26.156 infoConfigurationReport- parameterNumber:31, size:1, value:0
dev:2892022-09-11 16:00:25.849 infoConfigurationReport- parameterNumber:30, size:1, value:0
dev:2892022-09-11 16:00:18.227 infoConfigurationReport- parameterNumber:16, size:1, value:0
dev:2892022-09-11 16:00:17.918 infoConfigurationReport- parameterNumber:15, size:1, value:0
dev:2892022-09-11 16:00:17.610 infoConfigurationReport- parameterNumber:14, size:1, value:0
dev:2892022-09-11 16:00:17.301 infoConfigurationReport- parameterNumber:13, size:1, value:0
dev:2892022-09-11 16:00:14.176 infoConfigurationReport- parameterNumber:7, size:1, value:0
dev:2892022-09-11 16:00:13.868 infoConfigurationReport- parameterNumber:6, size:1, value:0
dev:2892022-09-11 16:00:13.561 infoConfigurationReport- parameterNumber:5, size:2, value:22
dev:2892022-09-11 16:00:13.253 infoConfigurationReport- parameterNumber:4, size:2, value:22
dev:2892022-09-11 16:00:12.947 infoConfigurationReport- parameterNumber:3, size:1, value:1
dev:2892022-09-11 16:00:12.079 infoConfigurationReport- parameterNumber:1, size:1, value:0
dev:2892022-09-11 16:00:07.892 traceconfigurationGet command(s) sent...
dev:2892022-09-11 15:59:57.767 infoVersion Report - FirmwareVersion: 2.02, ProtocolVersion: 3.52, HardwareVersion: null
I discovered something else:
With the settings above, S2 does not update. I changed the switch type Toggle (from Momentary), but that did not make a difference. If I change Parameters 4 and 5 to "10" (milliseconds), the S2 status updates automatically.
Please see this thread to continue the discussion about this driver:
