FGS-222 Dual Relays not working

mike.maxwell · August 13, 2020, 9:07pm

well yeah, we have to start someplace, Fibaro makes a wide range of devices, several of which aren't available in US frequencies (we can still acquire them obviously) so I'm not in a position to guess which ones aren't working correctly on a C7.

I literally have no way of knowing who's using what user driver with what Fibaro device and why...

amithalp · August 13, 2020, 9:27pm

Hi Mike,
Looking at the full product line of Fibaro makes me realize they do have a lot....
Fibaro are popular in Europe and I would suggest starting with the most common (to my best knowledge) which are - Fibaro Roller Shutter 3, Fibaro Double Switch and Fibaro Dimmer 2.
Hope it makes sence to you.
Thanks

mark.cockcroft · August 14, 2020, 8:31am

Just noticed this on a 223 , why does a z-wave device need a zigbee id?

**

No*te: This handler requires the "Metering Switch Child Device" to be installed.
Copyright 2016 Eric Maycock
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
in compliance with the License. You may obtain a copy of the License at:

 http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
for the specific language governing permissions and limitations under the License.
Fibaro FGS-223 Dual Relay
Author: Eric Maycock (erocm123)
04/25/2017 - Fix for combined energy & power reports & switch endpoints showing correct info.
04/18/2017 - This handler requires the Metering Switch Child device to create the multiple switch endpoints.
*/

Berthoven · February 11, 2021, 4:54pm

Sorry to awaken an old thread.
I just upgraded the hub to latest firmware (2.2.5.131) - although I'm not on C7 yet.

I think this has caused issues with my Fibaro dual relays. (I have an FGS-222 and an FGS-223)
Even though the relays seem to work, I believe its not tracking state of the switch.

Fibaro FGS-222 Double Relay Switch
(Author: Robin Winbourne)

On & Off commands work (on parent and child devices)
Status no longer being updated (on parent or child devices)
Toggle command no longer works - presumably because this relies on status- No
I dont have any hard wired switches
No device events being reported since the upgrade

Fibaro Double Switch 2 FGS-223
(Author: Eric Maycock (erocm123))

On & Off commands work (on parent and child devices)
Status no longer being updated (on parent or child devices)
Toggle command no longer works - presumably because this relies on status
Hard wired switches both work normally (S1 & S2)
No device events being reported since the upgrade

The fact that the upgrade seems have caused this gives me hope that its a software issue.
I know these devies arent natively supported in HE, but Fibaro seems a big-name brand to suddenly have to give up on.

Any suggestions ?
Thanks
Rob

Berthoven · February 11, 2021, 5:39pm

Update 1:
I've resolved the issue with the FGS-223 at least.
Seems that I just needed the latest driver code changes from Github. (Dec 20)
Thank you Chris Charles.

Update 2:
Looks like I've also resolved the FGS-222 issue (fingers crossed).
I compared the driver code on my hub with the the thread below - and also the version on GIthub.
Seems that the version that @bobbles posted in the thread is updated (multiChannelV3 to multiChannelV4) - and this version appear to work.
Does this mean @Robin version on Github is out of date ?

cjcharles · February 18, 2021, 11:42pm

@Berthoven - Ive been making a few changes to my FGS-222 handler to fix some bugs I was seeing, do you want to give them a quick test and see if they fix your issues?

github.com

cjcharles0/Hubitat/blob/master/drivers/fibaro-fgs-222/fibaro-fgs-222-dth.groovy

/**
 *  
 *	Fibaro FGS-222 Double Relay Switch Device Type - For use on Hubitat
 *  
 *	Author: Eric Maycock and Robin Winbourne, updated by Chris Charles
 *	Date: 2018-03-24
 */
 
metadata {
definition (name: "Fibaro Double Relay FGS-222", namespace: "erocm123", author: "Eric, Robin and Chris") {
capability "Switch"
capability "Relay Switch"
capability "Polling"
capability "Configuration"
capability "Refresh"
capability "Zw Multichannel"

attribute "switch1", "string"
attribute "switch2", "string"

This file has been truncated. show original

Berthoven · February 19, 2021, 12:05am

Hi
I can give it a try, sure. Will let you know.
However, I had eventually resolved the issue I was having using a version of the driver that was on the thread above. The main difference was the change to multiChannelV4, so I'd assumed that was the issue). I see your new version has lots of interesting changes (did a quick diff).

cjcharles · February 19, 2021, 12:11am

I think Ive only just found Robin's version of the handler, but I made some of the original changes with him back in the ST days, so not sure how I ended up with the version I have.....

Most of the changes were written to support the FGS-224, however recently I had some zwave problems and this code managed to fix some of those problems, hence I thought I would roll it out to my other Fibaro handlers. Mainly related to whether you have a secure pairing or not.

There is one more change I want to make, around using the built in Hubitat component switch (child) as opposed to the metering switch from Eric (so it is easier to install), but would be interested in your feedback at this point if you dont mind.

cjcharles · February 21, 2021, 7:18pm

@Berthoven - I have now uploaded the full set of changes for this device handler and it seems to be working well for me. It now uses the built in child/component device switch handler, so does not need you to install the metering switch from Eric.
Would love to hear your thoughts.
Thanks

igor.lehotan · February 22, 2021, 6:25am

Tested today. Works like a charm. Child devices created, device is reporting back its manual state change to HE. Thanks for great job!

Edit: after testing, I have only one remark. Switch 1 is updated immediately, switch 2 needs to be polled to get its state updated. Would it be possible to fix that?

cjcharles · February 22, 2021, 11:45am

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....?

igor.lehotan · February 22, 2021, 8:27pm

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.

cjcharles · February 23, 2021, 1:15am

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!

igor.lehotan · February 23, 2021, 12:20pm

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.

cjcharles · February 23, 2021, 12:24pm

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....

igor.lehotan · February 23, 2021, 12:32pm

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.

Berthoven · February 23, 2021, 1:37pm

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.

cjcharles · February 23, 2021, 5:25pm

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...

hendrec · September 7, 2022, 12:02pm

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.

cjcharles · September 8, 2022, 11:34pm

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....