Fibaro Dimmer 2, Triple click

Hardware Home Automation
1

Hi,

I have some Fibaro Dimmer 2 modules. What I’d like to do is use a triple click to turn off a number of lights. From what I understand from https://manuals.fibaro.com/dimmer-2/ (down at “28. Scene activation functionality”), when using the standard S1 input, which my light is connected to, I can’t use the triple click. Is that correct? I think the triple click on S1 is used for inclusion and exclusion.

Could I just connect my light to the S2 input instead? Is that possible? I guess I won’t be able to do inclusion and explusion via the regular switch, but will have to get out the module and uses the B button instead.

Does anyone know?

Thanks!

2

You do can use the triple click (and others) on S1, just param #28 needs to be set to enable scene functionality.
Or connect a second switch to S2.

3

I don’t have another switch there.

I did set parameter 28 to “Scene functionality enabled”, but when triple clicking, I don’t get a scene number. Only single and double click and holding/releasing give me scene numbers. :frowning:

That’s what I would expect when reading the manual though.

Unbenannt
Unbenannt.PNG820×727 45.6 KB

4

Do you have any other info so that using a triple click on S1 can trigger a scene?

5

It used to be 15 in older FGD versions.
Just enable zwave debugging, triple-click and watch for any messge on the scene channel.

6

Below the debug log entries for double and triple click. To me it looks like the controller isn’t getting the scene activation with the triple click, is it?

Double click:

[21:51:20] openhabian@openHABianPi:~$ tail -f /var/log/openhab2/openhab.log | grep ZWave
2018-04-15 21:51:29.375 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 05 04 2B 01 0E 00 D4
2018-04-15 21:51:29.379 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-04-15 21:51:29.382 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0A 00 04 00 05 04 2B 01 0E 00 D4
2018-04-15 21:51:29.384 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 04 2B 01 0E 00
2018-04-15 21:51:29.386 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Starting initialisation from DONE
2018-04-15 21:51:29.387 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@412134 already registered
2018-04-15 21:51:29.390 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - Received Scene Activation for Node ID = 5
2018-04-15 21:51:29.391 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - Scene Activation Set
2018-04-15 21:51:29.392 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - Scene activation node from node 5: Scene 14, Time 0
2018-04-15 21:51:29.393 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-04-15 21:51:29.395 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-04-15 21:51:29.396 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = SCENE_ACTIVATION, value = 14
2018-04-15 21:51:29.398 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:84f8a005:node5:scene_number to 14 [DecimalType]
2018-04-15 21:51:29.844 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 05 03 26 03 63 B2
2018-04-15 21:51:29.846 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-04-15 21:51:29.850 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 05 03 26 03 63 B2
2018-04-15 21:51:29.852 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 03 26 03 63
2018-04-15 21:51:29.855 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Starting initialisation from DONE
2018-04-15 21:51:29.857 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@412134 already registered
2018-04-15 21:51:29.860 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 5: Received SWITCH_MULTILEVEL command V3
2018-04-15 21:51:29.862 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 5: Switch Multi Level report, value = 99
2018-04-15 21:51:29.863 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-04-15 21:51:29.865 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-04-15 21:51:29.867 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_MULTILEVEL, value = 99
2018-04-15 21:51:29.869 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:84f8a005:node5:switch_dimmer to 100 [PercentType]
2018-04-15 21:51:34.866 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 05 06 31 05 04 22 01 53 B4
2018-04-15 21:51:34.869 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-04-15 21:51:34.873 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 00 05 06 31 05 04 22 01 53 B4
2018-04-15 21:51:34.876 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 05 06 31 05 04 22 01 53
2018-04-15 21:51:34.879 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Starting initialisation from DONE
2018-04-15 21:51:34.880 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@412134 already registered
2018-04-15 21:51:34.890 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 5: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V4
2018-04-15 21:51:34.891 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 5: Sensor Multi Level REPORT received
2018-04-15 21:51:34.893 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 5: Sensor Type = Power(4), Scale = 0
2018-04-15 21:51:34.894 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 5: Sensor Value = 33.9
2018-04-15 21:51:34.896 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2018-04-15 21:51:34.898 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2018-04-15 21:51:34.899 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 33.9
2018-04-15 21:51:34.901 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:84f8a005:node5:sensor_power to 33.9 [DecimalType]

Triple click:

[21:48:59] openhabian@openHABianPi:~$ tail -f /var/log/openhab2/openhab.log | grep ZWave
2018-04-15 21:49:33.463 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 20 00 49 84 05 1A 04 11 01 5E 20 86 72 26 5A 59 85 73 98 7A 56 70 31 32 8E 60 75 71 27 22 EF                           2B AC
2018-04-15 21:49:33.473 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-04-15 21:49:33.485 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 20 00 49 84 05 1A 04 11 01 5E 20 86 72 26 5A 59 85 73 98 7A 56 70 31 32 8E 60 75 71 27 22 EF                           2B AC
2018-04-15 21:49:33.491 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 05 1A                           04 11 01 5E 20 86 72 26 5A 59 85 73 98 7A 56 70 31 32 8E 60 75 71 27 22 EF 2B
2018-04-15 21:49:33.506 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Starting initialisation from DONE
2018-04-15 21:49:33.509 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@412134 alrea                          dy registered
2018-04-15 21:49:33.514 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=7, call                          back=153, payload=07 05 26 04 60 00 FF
2018-04-15 21:49:33.520 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, de                          st=255, callback=0, payload=84 05 1A 04 11 01 5E 20 86 72 26 5A 59 85 73 98 7A 56 70 31 32 8E 60 75 71 27 22 EF 2B
2018-04-15 21:49:33.523 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=153, expected=SendData, cancelled=false
7

Hi all,

Did you have some progress on this topic? I’m dealing with the same problem.
When I do a single or double tap, the scene number changes. Triple tap doesn’t give a new scene number.

Best regards,
Tamar

8

What progress are you expecting? If the device doesn’t send different scene numbers, then I’m not sure that the binding can do anything? Or maybe I misunderstand the issue?

9

Progress in the way of finding a reason why the switch doesn’t give a new scene number.
When using S2, a single, double and triple tap will all give a different scene number. Using S1 only the single and double tap will do that.
As Domoticz will activate a scene when a the triple tap on S1 is done, I was expecting a scene number in OH.

10

I don’t currently see how this is a binding issue, so I’m not sure what can be done. From the logs I see above, the device is not sending anything. If the device doesn’t send anything, then the binding can’t do anything either.

My guess is either the device doesn’t do this, or the device is not configured correctly, but the binding can’t solve these issues I think?

11

I agree on that. Maybe my expectation was too high. I was assuming that when S2 is sending something on single, double and triple tap, S1 will do that also on a triple tap (definitely when Domoticz “sees” the triple tap).

12

If Domoticz receives the message, then I guess it must be a configuration issue. I’d look through the parameters to see if there’s a way to enable it.

13

See manual on parameter #28. I also vaguely recall this was different in the past, maybe with the FGD-211 or earlier firmware versions.

14

I see…
I doesn’t understand why Domoticz sees the triple tap. It’s working for months here.
Currently I’m not using S2 so I guess my solution is to use S2 instead of S1 in OH and change parameter 29 to switch functionality.
Thank you all for your help!