Having to push the button twice: association weirdness

Hi all,

I have two Fibaro DImmer 2 modules, module A and module B.
Module A dims load 1 through S1 (double push button).
Module B dims load 2 through S1 (single button).
I associated S2 of Module A to dim load 2 on module B.

However, it seems that whenever I turn on load 2 with module B, I need to push S2 on module A twice to turn the load off. The desired behavior is that I need to push only once.

I think it has to do with the fact that S2 on Module A has its own "state". In the example above, I think that the first push brings S2 to the ON state, and then the second push actually turns the load off. How do I fix this?

Below more info on the two devices.

Z-Wave Syncing - started for "1 Wastafel Dimmer" This is module A
Z-Wave Syncing - retrieved module neighbors list: 2, 3, 5, 27, 32, 34, 35, 36, 37, 38, 39, 41, 43, 44, 47, 48, 49, 50, 51
Z-Wave Syncing - assigning return route to "042 - 1 Wastafel Dimmer"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Dimmer Switch (FGD212) - 01021000
Z-Wave Syncing - retrieved protocol version 4.24, app version 3.05
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Mulitlevel Switch : Dimmable Power Switch (04 : 11 : 01, base 26)
Z-Wave Syncing - retrieved command classes: 20v1 60v4 22v1 26v3 86v1 27v1 7Av1 72v1 8Ev1 70v1 71v1 32v3 73v1 75v1 56v1 98v1 59v1 31v4 5Av1 5Ev1 85v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming, security
Z-Wave Syncing - retrieved multi-endpoint types: 1:(11 : 01), 2:(11 : 01)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 20 86 26 85 59 8E 32 31 71], 2:[5E 20 86 26 85 59 8E]
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - retrieved group 2 associations: [1]
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - retrieved group 4 associations: []
Z-Wave Syncing - retrieved group 5 associations: [43]
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - group 2 association to interface already exists (skipping)
Z-Wave Syncing - retrieved parameter 20 "Switch type" is 0 "Momentary"
Z-Wave Syncing - retrieved parameter 28 "Enable scene commands" is false
Z-Wave Syncing - retrieved parameter 23 "Enable double-click to full brightness" is true
Z-Wave Syncing - retrieved parameter 9 "Power up to last known state" is true
Z-Wave Syncing - retrieved parameter 26 "Enable 3-way switch mode" is false
Z-Wave Syncing - retrieved parameter 1 "Minimum value" is 11
Z-Wave Syncing - retrieved parameter 2 "Maximum value" is 53
Z-Wave Syncing - retrieved parameter 7 "Local dim delta" is 1
Z-Wave Syncing - retrieved parameter 8 "Local dim timer" is 5 * 10 milliseconds
Z-Wave Syncing - retrieved parameter 5 "On/Off dim delta" is 1
Z-Wave Syncing - retrieved parameter 6 "On/Off dim timer" is 1 * 10 milliseconds
Z-Wave Syncing - retrieved parameter 50 "Power report threshold" is 10 %
Z-Wave Syncing - retrieved parameter 52 "Periodic power reports" is 3600 seconds
Z-Wave Syncing - complete

Z-Wave Syncing - started for "1 Badkamer Dimmer" This is module B
Z-Wave Syncing - retrieved module neighbors list: 2, 3, 5, 19, 27, 32, 34, 35, 36, 37, 38, 39, 41, 42, 44, 46, 47, 48, 49, 50, 51
Z-Wave Syncing - assigning return route to "043 - 1 Badkamer Dimmer"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Dimmer Switch (FGD212) - 01021000
Z-Wave Syncing - retrieved protocol version 4.24, app version 3.05
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Mulitlevel Switch : Dimmable Power Switch (04 : 11 : 01, base 26)
Z-Wave Syncing - retrieved command classes: 20v1 60v4 22v1 26v3 86v1 27v1 7Av1 72v1 8Ev1 70v1 71v1 32v3 73v1 75v1 56v1 98v1 59v1 31v4 5Av1 5Ev1 85v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming, security
Z-Wave Syncing - retrieved multi-endpoint types: 1:(11 : 01), 2:(11 : 01)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 20 86 26 85 59 8E 32 31 71], 2:[5E 20 86 26 85 59 8E]
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - retrieved group 2 associations: [1]
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - retrieved group 4 associations: []
Z-Wave Syncing - retrieved group 5 associations: []
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - group 2 association to interface already exists (skipping)
Z-Wave Syncing - retrieved parameter 20 "Switch type" is 0 "Momentary"
Z-Wave Syncing - retrieved parameter 28 "Enable scene commands" is false
Z-Wave Syncing - retrieved parameter 23 "Enable double-click to full brightness" is true
Z-Wave Syncing - retrieved parameter 9 "Power up to last known state" is true
Z-Wave Syncing - retrieved parameter 26 "Enable 3-way switch mode" is false
Z-Wave Syncing - retrieved parameter 1 "Minimum value" is 6
Z-Wave Syncing - retrieved parameter 2 "Maximum value" is 82
Z-Wave Syncing - retrieved parameter 7 "Local dim delta" is 1
Z-Wave Syncing - retrieved parameter 8 "Local dim timer" is 5 * 10 milliseconds
Z-Wave Syncing - retrieved parameter 5 "On/Off dim delta" is 1
Z-Wave Syncing - retrieved parameter 6 "On/Off dim timer" is 1 * 10 milliseconds
Z-Wave Syncing - retrieved parameter 50 "Power report threshold" is 10 %
Z-Wave Syncing - retrieved parameter 52 "Periodic power reports" is 3600 seconds
Z-Wave Syncing - complete

Hi Mark -

I am doing EXACTLY the same thing as you, throughout my entire house. Same protocol version 4.24 , same app. version 3.05 (although I do not know exactly what these version numbers mean). I have 24 Fibaro FGD212 Dimmers 2 and with almost every one of them I use the secondary momentary button to send an On/Off/Dim signal to another dimmer in the house. This was my way of avoiding all the additional electrical wiring and still have "hotel switch" functionality. I too have done this by setting group 5 association to the desired remote dimmer.

I compared all my settings to yours and they are identical, except for parameter 50, which is only the power report threshold. I have that set to 1%.

In my house, all this works flawlessly. I had one dimmer only that did not want to send an association message out to it's 'friend'. After I swapped that out, the replacement dimmer worked fine too.

In my case, sometimes I do need to press twice, but that usually happens if I click too fast, or if the button did not make proper contact physically. I suspect that a few of my wall switches contain some dust, a left-over from the construction work....

So: I cannot tell you where things are off in your case. I can tell you that your exact settings work in my situation. More that happy to help you trouble-shoot his by comparing notes/settings/etc and as we're in the same country and speak the same language, drop me a pm if you want. We can then post the resolution here once found.

A few things come to mind though:
- Have you tried another combination of master/slave dimmers, ie by associating S2 of module B to control load 1 on module A?
- I don't think that 3.05 actually is the firmware version. If not mistaking, I did upgrade my dimmers to 3.5 with the Fibaro Home Center (HC2) which has been collecting dust here since a few years. If you need a firmware update and you don't own a HC2: happy to help with that.

Hope this helps,
Ronald

I found the solution to this problem.

It turns out that the remote dimmer A has a separate state for S2. If I'd turn the lights on with dimmer B, the state of A-S2 would still be "OFF". Pressing S2 once would change that state to "ON" (but the light is already on so it looks like nothing happens). Only pressing a second time would change the state to "OFF" and send a message to the associated dimmer B, which turns off the light.

Solution: the separate state needs to be updated to whatever change is made on dimmer B. I defined a trigger that would update the brightness of A-S2 to the changed brightness of B-S1, and presto! it works.

This solution is not fully association-based and thus requires the server to do something smart, but that's why Indigo is running anyway!

Thanks for this.

Have just discovered the same issue.

Dimmer 2 S2 associated with Group 4/5 to a older dimmer module. Double press needed if states on devices don't match.
As you describe - ON -> OFF (Associated Device OFF) nothing, would need another press to go from Off --> ON (Associated device now ON)

Have set trigger in Indigo to update the S2 Device in indigo to whatever the linked device state is to fix issue.

I would believe it should be possible with Association only???

Glenn


Dimmer 2 Device - S2 should be controlling

Code: Select all

Indigo Z-Wave Version: 7.4.1
Node ID: 153
Model: Dimmer Switch (FGD212)
Model ID: 01023000
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 4.24
Application Version: 3.05
Model Definition Version: 2
Library Type: 3
Class Name: Dimmable Power Switch
Class Hierarchy: 04 : 11 : 01
Command Class Base: 26
Command Versions: 20v1 85v1 86v1 71v1 8Ev1 56v1 98v1 59v1 5Av1 5Ev1 60v4 22v1 26v3 27v1 72v1 70v1 31v4 32v3 73v1 75v1 7Av1
Encryption Status: Supported but not Enabled
Multi-Endpoint Types: 1:(11 : 01), 2:(11 : 01)
Multi-Endpoint Classes: 1:[5E 20 86 26 85 59 8E 32 31 71], 2:[5E 20 86 26 85 59 8E]
Multi-Instance Counts: - none -
Features: routing, beaming, security, energyMeter
Neighbors: 8, 9, 10, 11, 29, 35, 36, 37, 42, 43, 44, 46, 47, 48, 51, 52, 55, 93, 116, 148, 149, 151, 152, 154, 155
Associations: 1:[1] 2:[1] 3:[] 4:[52] 5:[52]
Config Values: 1:2 2:99 5:1 6:1 7:1 8:5 9:1 50:10 20:0 23:1 52:3600 26:0 28:0

Controlled device

Code: Select all

Node ID: 52
Model: Dimmer Switch (FGD211)
Model ID: 0100300A
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 3.52
Application Version: 2.02
Model Definition Version: 8
Library Type: 3
Class Name: Dimmable Power Switch
Class Hierarchy: 04 : 11 : 01
Command Class Base: 26
Command Versions: 20v1 85v1 26v1 27v1 8Ev1 70v1 72v1 73v1 7Av1 86v1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, beaming
Neighbors: 2, 3, 7, 8, 9, 10, 11, 12, 14, 15, 16, 29, 35, 36, 37, 38, 42, 43, 44, 46, 47, 48, 51, 54, 55, 56, 58, 59, 60, 72, 74, 93, 95, 101, 107, 108, 112, 139, 140, 143, 145, 148, 151, 152, 153, 154, 155
Associations: 1:[1] 2:[] 3:[1]
Config Values: 8:1 9:5 10:1 11:1 12:99 13:2 14:0 15:1 16:1 17:0 18:0 41:0
   

Further to my reply. Thought might need Indigo (Device 1) in Group 4 & 5 for the created device S2 to be updated...

Code: Select all

Indigo Z-Wave Version: 7.4.1
Node ID: 153
Model: Dimmer Switch (FGD212)
Model ID: 01023000
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 4.24
Application Version: 3.05
Model Definition Version: 2
Library Type: 3
Class Name: Dimmable Power Switch
Class Hierarchy: 04 : 11 : 01
Command Class Base: 26
Command Versions: 20v1 85v1 86v1 71v1 8Ev1 56v1 98v1 59v1 5Av1 5Ev1 60v4 22v1 26v3 27v1 72v1 70v1 31v4 32v3 73v1 75v1 7Av1
Encryption Status: Supported but not Enabled
Multi-Endpoint Types: 1:(11 : 01), 2:(11 : 01)
Multi-Endpoint Classes: 1:[5E 20 86 26 85 59 8E 32 31 71], 2:[5E 20 86 26 85 59 8E]
Multi-Instance Counts: - none -
Features: routing, beaming, security, energyMeter
Neighbors: 8, 9, 10, 11, 29, 35, 36, 37, 42, 43, 44, 46, 47, 48, 51, 52, 55, 93, 116, 148, 149, 151, 152, 154, 155
Associations: 1:[1] 2:[1] 3:[] 4:[52, 1] 5:[52, 1]
Config Values: 1:2 2:99 5:1 6:1 7:1 8:5 9:1 50:10 20:0 23:1 52:3600 26:0 28:0

Unfortunately adding Indigo/Device 1 to Group 4 & Group 5 - Indigo still doesn't update ever when the S2 switch is pressed.

Indigo is receiving Z-wave commands, copied below... Just the device never updates

Back to issue with double pressing.

Below is the raw Z-wave received and sent (so is being received)
153 - S2 is the switch in question.
First is me turning on/off within Indigo.
Next is manually turning on/off - you can see the Wadrobe (Spelling!) associated device responding.
The S2 Node ID 153 Switch 2 - device never updates.

Matt any thoughts - it seems some is missed being detected???

Code: Select all

Z-Wave Watcher Debug            Raw command sent (Node 153): 01 0A 00 13 99 03 32 01 10 25 66 1C (True)
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0E 00 04 00 99 08 32 02 21 32 00 00 00 00 47
   Z-Wave                          received "(U) - 153 - Master Bedroom Light" status update is off
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 08 99 03 20 01 00 41
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 00 99 03 20 01 00 49
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 08 99 04 26 01 00 01 42
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 00 99 04 26 01 00 01 4A
   Z-Wave                          received "(U) Master Bedroom Wadrobe" status update is off
   Z-Wave                          received "(U) - 153 - Master Bedroom Light" status update is on
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 08 99 03 20 01 FF BE
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 00 99 03 20 01 FF B6
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 08 99 04 26 01 FF 01 BD
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 00 99 04 26 01 FF 01 B5
   Z-Wave                          received "(U) Master Bedroom Wadrobe" status update brightness 100
   Z-Wave                          received "(U) - 153 - Master Bedroom Light" status update is off
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 08 99 03 20 01 00 41
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 00 99 03 20 01 00 49
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 08 99 04 26 01 00 01 42
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 00 99 04 26 01 00 01 4A
   Z-Wave                          received "(U) Master Bedroom Wadrobe" status update is off
   Z-Wave                          received "(U) - 153 - Master Bedroom Light" status update is on
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 08 99 03 20 01 FF BE
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 00 99 03 20 01 FF B6
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 08 99 04 26 01 FF 01 BD
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 00 99 04 26 01 FF 01 B5
   Z-Wave                          received "(U) Master Bedroom Wadrobe" status update brightness 100
   Z-Wave                          received "(U) Master Bedroom Wadrobe" status update is off
   Z-Wave                          received "(U) - 153 - Master Bedroom Light" status update is off
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 08 99 03 20 01 00 41
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 00 99 03 20 01 00 49
   Z-Wave                          received "(U) - 153 - Master Bedroom Light" status update is on
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 08 99 03 20 01 FF BE
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 00 99 03 20 01 FF B6
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 08 99 04 26 01 FF 01 BD
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 00 99 04 26 01 FF 01 B5
   Z-Wave                          received "(U) Master Bedroom Wadrobe" status update brightness 100
   Z-Wave Watcher Debug            Raw command sent (Node 153): 01 0A 00 13 99 03 32 01 00 25 70 1A (True)
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 10 00 04 00 99 0A 32 02 21 44 00 00 00 3E 00 00 13
   Z-Wave Watcher Debug            Raw command sent (Node 153): 01 0A 00 13 99 03 32 01 10 25 71 0B (True)
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0E 00 04 00 99 08 32 02 21 32 00 00 00 00 47
   Z-Wave                 

& later with Button press of S2 - turns of associated device.
Then trigger (Wardrobe off - when off, turn off the indigo S2 Dimmer-2 Device) runs to switch Indigo S2 device to matching

Code: Select all

 Z-Wave                          received "(U) Master Bedroom Main Light" status update is off
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 08 99 03 20 01 00 41
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 00 99 03 20 01 00 49
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 08 99 03 20 01 00 41
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 00 99 03 20 01 00 49
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 08 99 04 26 01 00 01 42
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0A 00 04 00 99 04 26 01 00 01 4A
   Z-Wave                          received "(U) Master Bedroom Wadrobe" status update is off
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 09 00 04 00 99 03 26 03 00 4D
   Trigger                         Duplicate Wadrobe Off
   Z-Wave                          sent "(U) Master Bedroom Main Light - Switch 2" off
   Z-Wave Watcher Debug            Raw command sent (Node 153 Endpoint 2): 01 0E 00 13 99 07 60 0D 01 02 26 01 00 25 BB AB (True)
   Z-Wave Error                    error trying to parse value (valsize 3 too large for packetsize 3)
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0C 00 04 00 99 06 31 05 04 22 00 CD B7
   Z-Wave Error                    error trying to parse value (valsize 3 too large for packetsize 3)
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0C 00 04 10 99 06 31 05 04 23 00 CD A6
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0C 00 04 10 99 06 31 05 04 23 00 CD A6
   Z-Wave Error                    error trying to parse value (valsize 3 too large for packetsize 3)
   Z-Wave Error                    error trying to parse value (valsize 3 too large for packetsize 3)
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0C 00 04 10 99 06 31 05 04 23 00 CD A6
   Z-Wave Error                    error trying to parse value (valsize 3 too large for packetsize 3)
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0C 00 04 10 99 06 31 05 04 23 00 CD A6
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0C 00 04 10 99 06 31 05 04 23 00 CD A6
   Z-Wave Watcher Debug            Raw command received (Node 153): 01 0C 00 04 00 99 06 31 05 04 22 00 CD B7
   piBeacon Warning                piBeacon WaterTank New;  sensor:ADS1x15;  sensorValue


[matt (support)]

I'm not sure I'm following everything above (you are doing lots of things and then I'm not sure which part of the Event Log snippets correspond with your actions), but in general I think you will have to do the original work around: create a Trigger that monitors the Device State of the responding module and have that mirror the state into S2 on the controlling module. I don't believe this module is going to send broadcasts to Indigo when S2 changes. If you make an association for S2 back to Indigo that is unlikely to work – the association commands don't include which input (S1, S2, etc.) initiated the command so there is no way for Indigo to know to update the S2 device state.

Thanks Matt.

Seems like the original solution is the best

Was seeming, at least to me, to be sending back to indigo on S2 presses - but on second thoughts presume those are the associated commands going out that indigo is picking up.

Glen


Sent from my iPad using Tapatalk