Fibaro FGS221 -> FGS223 exchange Problem

Hi,

I have a quite complicated problem:

1. what I changed:
I had to exchange an old FGS221 switch with a new FGS223 Switch because the old one had a hardware defect.
2. What the function should be
On the Fibaros, the first switch (S1) is and was used to control a direct load and trigger an action in Indigo to switch some slave Hue devices as well.
The second (S2) switch was used just to trigger an action group to switch some lamps in another room.
Unfortunately the new FGS223 has different association groups for S1 and S2 and lifeline. The lifeline group is the only one automatically set to device1 (Indigo)
But the second switch (s2) doesn't send anything to the lifeline.
So I set association group 4 which is the on/off group for S2 to device 1 (indigo) as well. Now I get on off commands when I switch S2 but unfortunately Indigo doesn't distinguisch between S1 und S2 and always behaves as if I would have switched S1.

I hope I could explain the problem properly so that anyone else can understand my problem.

Am I doing something wrong or is indigo just misinterpreting the commands?
Any help would be appreciated.
Cheers
Wilhelm

Hi Wilhelm

Stick a Zwave Watcher on your new Fibaro and press S1/S2 a couple of times so we can see it.

Peter


Sent from my iPhone using Tapatalk Pro

Code: Select all

 S1 On:
   Z-Wave                          received "Esstisch" status update is on
   Trigger                         Esszimmer ein
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 09 00 04 00 AC 03 25 03 FF 84
   Sent Hue Lights                 "Vitrine" on to 100 at ramp rate 0.0 sec.
   Sent Hue Lights                 "Sideboard über Türschalter" off at ramp rate 0.0 sec.
   Z-Wave                          received "Esstisch" power load to 23.4 W
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 0E 00 04 00 AC 08 32 02 21 32 00 EA 00 00 98
   Z-Wave Watcher Debug            Raw command sent (Node 172): 01 0A 00 13 AC 03 32 01 00 25 15 4A (True)
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 10 00 04 00 AC 0A 32 02 21 44 00 00 00 00 00 00 18
   Z-Wave Watcher Debug            Raw command sent (Node 172): 01 0A 00 13 AC 03 32 01 10 25 16 59 (True)
   Z-Wave                          received "Esstisch" power load to 23.2 W
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 0E 00 04 00 AC 08 32 02 21 32 00 E8 00 00 9A
   GreenSky MQTT Bridge            Hifi-Turm Power set to 39.1 W
   GreenSky MQTT Bridge            Fernseher Power set to 0.0 W
   GreenSky MQTT Bridge            Albert Power set to 1.0 W
   GreenSky MQTT Bridge            Kühlschrank Power set to 52.0 W


Code: Select all

S1 Off: 
   Z-Wave                          received "Esstisch" status update is off
   Trigger                         Esszimmer aus
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 09 00 04 00 AC 03 25 03 00 7B
   Sent Hue Lights                 "Vitrine" off at ramp rate 0.0 sec.
   Z-Wave                          received "Esstisch" power load to 0.0 W
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 0E 00 04 00 AC 08 32 02 21 32 00 00 00 00 72
   Sent Hue Lights                 "Sideboard über Türschalter" on to 100 at ramp rate 0.0 sec.
   GreenSky MQTT Bridge            Rechenzentrum Power set to 105.0 W
   Z-Wave                          received "Temperatur 2. OG" sensor update to 27.2 °C
   Z-Wave Watcher Debug            Raw command sent (Node 172): 01 0A 00 13 AC 03 32 01 00 25 17 48 (True)
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 10 00 04 00 AC 0A 32 02 21 44 00 00 00 00 00 00 18
   Z-Wave Watcher Debug            Raw command sent (Node 172): 01 0A 00 13 AC 03 32 01 10 25 18 57 (True)
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 0E 00 04 00 AC 08 32 02 21 32 00 00 00 00 72
   Trigger                         Ausgeschaltet
 

S2 On and S2 off send absolutely nothing, when standard associations are active.

When I set assotiation group 4 to device 1

Code: Select all

 Z-Wave                          added association of "001 - Indigo Z-Wave Interface" to "Esstisch" group 4
   Z-Wave Watcher Debug            Raw command sent (Node 172): 01 0B 00 13 AC 04 85 01 04 01 25 29 C2 (True)
   Z-Wave Watcher Debug            Raw command sent (Node 172): 01 0A 00 13 AC 03 85 02 04 25 2A C5 (True)
   Z-Wave                          retrieved group 4 associations: [1]
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 0C 00 04 00 AC 06 85 03 04 05 00 01 DB


Code: Select all

S2 Off:
   Z-Wave                          received "Esstisch" status update is off
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 09 00 04 08 AC 03 20 01 00 74
   Trigger                         Esszimmer aus
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 09 00 04 00 AC 03 20 01 00 7C
   Sent Hue Lights                 "Vitrine" off at ramp rate 0.0 sec.
   Sent Hue Lights                 "Sideboard über Türschalter" on to 100 at ramp rate 0.0 sec.
   GreenSky MQTT Bridge            Albert Power set to 1.0 W
   GreenSky MQTT Bridge            Kühlschrank Power set to 51.0 W


Code: Select all

S2 On:
   Z-Wave                          received "Esstisch" status update is on
   Trigger                         Esszimmer ein
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 09 00 04 08 AC 03 20 01 FF 8B
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 09 00 04 00 AC 03 20 01 FF 83
   Sent Hue Lights                 "Vitrine" on to 100 at ramp rate 0.0 sec.
   Sent Hue Lights                 "Sideboard über Türschalter" off at ramp rate 0.0 sec.
   GreenSky MQTT Bridge            Rechenzentrum Power set to 98.4 W
   Z-Wave Watcher Debug            Raw command sent (Node 172): 01 0A 00 13 AC 03 32 01 00 25 2D 72 (True)
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 10 00 04 00 AC 0A 32 02 21 44 00 00 00 00 00 00 18
   Z-Wave Watcher Debug            Raw command sent (Node 172): 01 0A 00 13 AC 03 32 01 10 25 2E 61 (True)
   Z-Wave                          received "Esstisch" power load to 22.5 W
   Z-Wave Watcher Debug            Raw command received (Node 172): 01 0E 00 04 00 AC 08 32 02 21 32 00 E1 00 00 93


To explain:
"Esstisch" is device 172 , the main device. That S2 triggers anction for S1 is the problem
The secondary switch is called "058 Relay switch 2" which I also added a watcher on, but that one is never triggered

Ok so it looks like everything is doing what it “should”, though not what you want.

Try changing param 36/37 to eg 10 and 250 instead of 0 and 255, and possibly change association to group 5 instead of 4 so that you receive multi-level commands instead of basic on/off commands.

Then in Indigo, change your trigger to receive dimming commands (or a custom Zwave pattern) for S2.

(I can’t recall if Zwave Scene Controller differentiates dim commands but I should be able to add that later)


Sent from my iPhone using Tapatalk Pro

Ok so it looks like everything is doing what it “should”,

Well that is subject to interpretation.

First of all I think that S2 states isn‘t sent to the lifeline association is a firmware bug.

Second I think it‘s not correct that indigo reacts to the S2 messages exactly the same as to the S1 messages as it‘s a 2 Channel device with 2 different relais and inputs.

What you are suggesting might be a workarround, but I really don‘t like to mess arround just because the standard is not working properly.
Thanks for your help.
Cheers
Wilhelm

BTW Your suggestion to use the dimmer association will not work in my setup, because I use a second FGS in another location to be able to switch from another room. (I think this might be called „Multiway switching“ in English)

What i was doing to set S2 on the corresponding other FGS by association. to make them work together.

Zwave has a feature called endpoints.

If a device supports two or more features, eg a weather unit that has wind, rain, sun etc, each of those “bits” of the device can/will be different endpoints.

If wind sends “I am on” then it is encapsulated into a larger command with both the “On” and the “Wind” identified. Indigo reads the message and can differentiate whether it’s Wind or Rain that is on.

Fibaro has chosen not to make S1/S2 or O1/O2 into different endpoints, so therefore it is not possible to identify whether S1 or S2 sent the On command. Therefore what I said is true, whether you agree or not - the Zwave commands are being sent and received accurately, doing as they “should”.

Now, the other side of the coin is that Fibaro has also implemented Scene commands. If you enable them, you can determine which button S1/S2 was pressed as each sends a different ID to the lifeline. Scenes don’t support on/off, they support single/double/triple tap and/or hold/release.

At the end of the day it’s up to you how you implement them. I’m not sure I follow how your multi-way comes into this; the 2nd Fibaro switch can have different triggers to behave how it used to, than the new triggers for the new FGS using scene or dim commands.

Peter




Sent from my iPhone using Tapatalk Pro

[matt (support)]

This particular device is problematic / finicky in how it has to be configured, however based on some other user reports it is possible to get it broadcasting the S2 endpoint command correctly. See this forum thread for the details.

Thanks Matt,

that did the trick.
Thanks for keeping track of all those problems.

Cheers
Wilhelm