[SOLVED] Fibaro Dimmer 2 Scene Activation

drc · July 26, 2019, 7:42pm

Hi,

My Fibaro Dimer 2 (FGD-212) is working as expected locally and remotely through openhab, but I cannot pull through the Scene ID. Things I’ve done so far:

Enabled Parameter 28 (Scene Activation Functionality)
Added controller to association groups 1 and 2
Bound Scene channel to Number Item on System:Default (and other variants)
Enabled debugging on console and watched for state changes

The item never updates and nothing appears in the log. All configuration has been done through PaperUI. Running Openhab 2.5.0 snapshot with an Aeotec Z-Stick Gen5.

Thanks for any suggestions

mstormi · July 26, 2019, 8:12pm

If the item does not appear in events.log your channel link is bad. Here’s how it’s done in .items file:

Number Szenenschalter_Empore "Szenenschalter Empore" <switch> (Szenen) { channel="zwave:device:xxxxxxxx:node58:scene_number" }

Have you enabled zwave debugging ? Is there a message being sent ?

drc · July 26, 2019, 8:23pm

New item:

Number   Dim2_Test  "Test" <switch> (light)  {channel="zwave:device:e562eb0b:node5:scene_number" }

Events.log output when dimmer 2 switched on using local switch, using manually defined item as described:

2019-07-26 21:14:43.091 [vent.ItemStateChangedEvent] - ZWaveNode005FGD212Dimmer2_Dimmer1 changed from 0 to 12
2019-07-26 21:14:44.918 [vent.ItemStateChangedEvent] - ZWaveNode005FGD212Dimmer2_Dimmer1 changed from 12 to 0

Looks like just the standard brightness message on the dimmer channel.

I did enable zwave debugging and watched for the channel but nothing came through.

Updates from paper ui apply, but they have no effect:

2019-07-26 21:25:29.394 [nt.ItemStatePredictedEvent] - Dim2_Test predicted to become 10
2019-07-26 21:25:29.395 [vent.ItemStateChangedEvent] - Dim2_Test changed from 13 to 10

mstormi · July 26, 2019, 8:43pm

?? You cannot “watch for a channel” but for the device ID only. (I’m not talking about events.log - zwave debugging generates zwave messages in openhab.log)
You should have seen at least the dimming related messages (status updates) when you hit the button.
If you didn’t, your device setup/associations are not ok and you need to fix this first.

Note if you only have a switch on S1 input then only the fast triple click will generate a scene_number command/event. Single or double click or hold won’t generate scene numbers.

drc · July 26, 2019, 8:59pm

Output of openhab.log when turning the dimmer on and off:

2019-07-26 21:55:09.393 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 08 05 07 60 0D 01 01 20 01 63 D3
2019-07-26 21:55:09.400 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=5, callback=8, payload=08 05 07 60 0D 01 01 20 01 63
2019-07-26 21:55:09.401 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=5, callback=8, payload=08 05 07 60 0D 01 01 20 01 63
2019-07-26 21:55:09.401 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-07-26 21:55:09.401 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Application Command Request (ALIVE:DONE)
2019-07-26 21:55:09.401 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: resetResendCount initComplete=true isDead=false
2019-07-26 21:55:09.401 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2019-07-26 21:55:09.401 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: Incoming command class COMMAND_CLASS_BASIC, endpoint 1
2019-07-26 21:55:09.401 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: SECURITY NOT required on COMMAND_CLASS_BASIC
2019-07-26 21:55:09.401 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 5: Received COMMAND_CLASS_BASIC V0 BASIC_SET
2019-07-26 21:55:09.401 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 5: Basic report, value = 99
2019-07-26 21:55:09.401 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-07-26 21:55:09.402 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_BASIC, value = 99
2019-07-26 21:55:09.402 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:e562eb0b:node5:switch_dimmer1 to 100 [PercentType]
2019-07-26 21:55:09.402 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Commands processed 1.
2019-07-26 21:55:09.402 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@75a091c5.
2019-07-26 21:55:09.403 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-07-26 21:55:09.403 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-07-26 21:55:09.403 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-07-26 21:55:09.403 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-07-26 21:55:09.431 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 05 07 60 0D 01 01 20 01 63 DB
2019-07-26 21:55:09.438 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=5, callback=0, payload=00 05 07 60 0D 01 01 20 01 63
2019-07-26 21:55:09.438 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=5, callback=0, payload=00 05 07 60 0D 01 01 20 01 63
2019-07-26 21:55:09.438 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-07-26 21:55:09.438 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Application Command Request (ALIVE:DONE)
2019-07-26 21:55:09.439 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: resetResendCount initComplete=true isDead=false
2019-07-26 21:55:09.439 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2019-07-26 21:55:09.439 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: Incoming command class COMMAND_CLASS_BASIC, endpoint 1
2019-07-26 21:55:09.439 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: SECURITY NOT required on COMMAND_CLASS_BASIC
2019-07-26 21:55:09.439 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 5: Received COMMAND_CLASS_BASIC V0 BASIC_SET
2019-07-26 21:55:09.439 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 5: Basic report, value = 99
2019-07-26 21:55:09.439 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-07-26 21:55:09.439 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_BASIC, value = 99
2019-07-26 21:55:09.439 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:e562eb0b:node5:switch_dimmer1 to 100 [PercentType]
2019-07-26 21:55:09.440 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Commands processed 1.
2019-07-26 21:55:09.440 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@235788fc.
2019-07-26 21:55:09.440 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-07-26 21:55:09.440 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-07-26 21:55:09.440 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-07-26 21:55:09.440 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-07-26 21:55:10.986 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 08 05 07 60 0D 01 01 20 01 00 B0
2019-07-26 21:55:10.992 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=5, callback=8, payload=08 05 07 60 0D 01 01 20 01 00
2019-07-26 21:55:10.993 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=5, callback=8, payload=08 05 07 60 0D 01 01 20 01 00
2019-07-26 21:55:10.993 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-07-26 21:55:10.993 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Application Command Request (ALIVE:DONE)
2019-07-26 21:55:10.993 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: resetResendCount initComplete=true isDead=false
2019-07-26 21:55:10.993 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2019-07-26 21:55:10.993 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: Incoming command class COMMAND_CLASS_BASIC, endpoint 1
2019-07-26 21:55:10.993 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: SECURITY NOT required on COMMAND_CLASS_BASIC
2019-07-26 21:55:10.993 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 5: Received COMMAND_CLASS_BASIC V0 BASIC_SET
2019-07-26 21:55:10.993 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 5: Basic report, value = 0
2019-07-26 21:55:10.993 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-07-26 21:55:10.994 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_BASIC, value = 0
2019-07-26 21:55:10.994 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:e562eb0b:node5:switch_dimmer1 to 0 [PercentType]
2019-07-26 21:55:10.994 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Commands processed 1.
2019-07-26 21:55:10.994 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@7ff0b764.
2019-07-26 21:55:10.994 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-07-26 21:55:10.994 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-07-26 21:55:10.995 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-07-26 21:55:10.995 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-07-26 21:55:11.024 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 05 07 60 0D 01 01 20 01 00 B8
2019-07-26 21:55:11.030 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=5, callback=0, payload=00 05 07 60 0D 01 01 20 01 00
2019-07-26 21:55:11.030 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=5, callback=0, payload=00 05 07 60 0D 01 01 20 01 00
2019-07-26 21:55:11.030 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-07-26 21:55:11.031 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Application Command Request (ALIVE:DONE)
2019-07-26 21:55:11.031 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: resetResendCount initComplete=true isDead=false
2019-07-26 21:55:11.031 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2019-07-26 21:55:11.031 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: Incoming command class COMMAND_CLASS_BASIC, endpoint 1
2019-07-26 21:55:11.031 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: SECURITY NOT required on COMMAND_CLASS_BASIC
2019-07-26 21:55:11.031 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 5: Received COMMAND_CLASS_BASIC V0 BASIC_SET
2019-07-26 21:55:11.031 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 5: Basic report, value = 0
2019-07-26 21:55:11.031 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-07-26 21:55:11.031 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_BASIC, value = 0
2019-07-26 21:55:11.031 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:e562eb0b:node5:switch_dimmer1 to 0 [PercentType]
2019-07-26 21:55:11.032 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Commands processed 1.
2019-07-26 21:55:11.032 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1babc2eb.
2019-07-26 21:55:11.032 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-07-26 21:55:11.032 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-07-26 21:55:11.032 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-07-26 21:55:11.032 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

You can see the dimmer changing to 99, then back to 0, but no mention of Scene ID.

The switch is set to “Roller Blind”, so a rocker switch is connected to S1 and S2 allowing hold for dim. In this instance, I should be seeing Scene ID 10 when turned on and 11 when turned off.

mstormi · July 26, 2019, 9:04pm

I don’t understand. What is a “rocker switch” ? and what does that have to do with blinds ??
You really need to explain your setup a lot better.

drc · July 26, 2019, 9:10pm

Apologies, there is varying terminology and it can be difficult to find a common understanding. Refering to the manual (https://manuals.fibaro.com/content/manuals/en/FGD-212/FGD-212-EN-T-v1.3.pdf) on Page 25 I have Parameter 20 set to “Roller Blind”. Physically, this is a momentary switch that sits in an off position, but can be pressed up (S1 On), or down (S2 On). When letting go of the switch, it always retracts back to the centre, off position. See below image.

It is called a roller blind switch because people typically use them for electronic blinds, but they are also good for lights (hold to dim). This all works fine by the way.

mstormi · July 26, 2019, 9:22pm

I don’t know how FGD behaves with this sort of switch.
Did you triple click ?
Did you correctly map the scene_number channel to an item ? Does habmin show it’s linked ?
Why did you add controller to association group 2 ? Only #1 is required (lifeline).

drc · July 26, 2019, 9:34pm

According to the manual, I should be receiving Scene ID’s for any of the following:

I did try the switch in a standard “Switch” configuration a while ago but it made no difference. Just now I pressed three times, but no Scene ID showed in the logs.

Habmin shows the following items:

“Test” is the manual item you asked me to create, and “Scene Number” is the one created by PaperUI.

Association group 2 was set to Controller as I was having some strange behaviour when it was not defined, with regards to changing the dimming level on Openhab.

BUT

I just went into PaperUI Control and the item created by Paper UI and the manual item are now working! I think the triple click must have put it into a pairing state. Now whenever i single click or hold, I see the scene number as it should be in the above table. Crazy!

2019-07-26 22:37:00.077 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=5, callback=0, payload=00 05 04 2B 01 0B 00
2019-07-26 22:37:00.077 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-07-26 22:37:00.077 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Application Command Request (ALIVE:DONE)
2019-07-26 22:37:00.077 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: resetResendCount initComplete=true isDead=false
2019-07-26 22:37:00.077 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: Incoming command class COMMAND_CLASS_SCENE_ACTIVATION, endpoint 0
2019-07-26 22:37:00.077 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 5: SECURITY NOT required on COMMAND_CLASS_SCENE_ACTIVATION
2019-07-26 22:37:00.077 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 5: Received COMMAND_CLASS_SCENE_ACTIVATION V1 SCENEACTIVATION_SET
2019-07-26 22:37:00.077 [DEBUG] [ass.ZWaveSceneActivationCommandClass] - NODE 5: Scene activation: Scene 11, Time 0
2019-07-26 22:37:00.077 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-07-26 22:37:00.077 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SCENE_ACTIVATION, value = 11
2019-07-26 22:37:00.078 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:e562eb0b:node5:scene_number to 11 [DecimalType]
2019-07-26 22:37:00.078 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 5: Commands processed 1.

Many thanks for your help

drc · July 26, 2019, 9:42pm

Just one more question - it seems to be one-way only - i.e. I receive Scene ID’s, but cannot set them from Openhab. Is that expected behaviour?

mstormi · July 26, 2019, 9:55pm

yes