Fibaro FGD212 Dimmer 2, binary 'switch' missing?

OH2.1, and migrated from 1.x.
I’m linking things to items, and have linked the dimmer to my ‘Dimmer’ item which works ok. Eg. this works:

Dimmer kitchenlightsdimmer “Dimmer [%d %%]” (gLightsLiving) { zwave=“3:1:command=SWITCH_MULTILEVEL” }

However in OH1.8, I also had a related ‘switch’ item defined as:

Switch kitchenlights “Kitchen” (gLightsLiving) { zwave=“3:command=SWITCH_MULTILEVEL” }

But under the Channels of the Dimmer thing I cannot find a ‘switch’ type that I can associate with in order to turn the light on and off? I can obviously turn it on or off by dragging the dimmer slider left/right, but I want a switch item to fully turn it on/off as well. The only ‘switch’ items shown for the FGD212 ‘thing’ are “Reset the total power consumption”, “Alarm”, and “Alarm 1”. Linking to any of these doesn’t trigger the light on/off - if I link to alarm, the openhab event.log does show it saying the light turn on/off but the actual light does not.

What have I done wrong here?!

Hi @chimeranzl

In OH2 there is another command class availible

Use {channel=“zwave:device:xxx:node3:switch_dimmer”}

Regards
Michael

Hi Michael,

Thanks, but I already tested this also and it does not work.I did:

// Switch kitchenlights “Kitchen” (gLightsLiving) { zwave=“3:command=SWITCH_MULTILEVEL” }
Switch kitchenlights “Kitchen” (gLightsLiving) { zwave=“zwave:device:fbcf2efa:node3:switch_dimmer” }

Does not trigger the light switch on/off. However the event logs show DO show that it is receiving an event:

2017-07-03 10:05:08.893 [ItemCommandEvent ] - Item ‘kitchenlights’ received command OFF
2017-07-03 10:05:08.927 [ItemStateChangedEvent ] - kitchenlights changed from ON to OFF
2017-07-03 10:05:13.728 [ItemCommandEvent ] - Item ‘kitchenlights’ received command ON
2017-07-03 10:05:13.766 [ItemStateChangedEvent ] - kitchenlights changed from OFF to ON

???

Is your node up’n’running?
Can you control it from Habmin or PaperUI?

Toole to Debug Logging and post it, and then please

Regards, Michael

Yes its up and running - as per original post, I can control the light via the dimmer item, just not on/off from the switch.

(Habmin is down at the moment, that’s another issue I’m dealing with, it just sits there saying “loading…”)

In PaperUI, yes it shows up no problem at all. I’ve linked the dimmer thing to an item, and as above can slide the dimmer left/right and the light actually dims down/up - so communication to the zwave device works ok. I also copy/pasted from the channel to the sitemap file to ensure no typo’s. After enabling zwave debugging, if I flick the switch on/off in OH, I get NO log entries. As another test to ensure debugging was enabled, sliding the dimmer DOES return debug data:

2017-07-03 10:30:52.765 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Command received zwave:device:fbcf2efa:node3:switch_dimmer --> 61
2017-07-03 10:30:52.771 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 3: Creating new message for command SWITCH_MULTILEVEL_SET
2017-07-03 10:30:52.875 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-07-03 10:30:52.878 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 0. Queue={}
2017-07-03 10:30:52.891 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 03 03 26 01 3D 25 9C 45
2017-07-03 10:30:52.894 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 3: Sending REQUEST Message = 01 0A 00 13 03 03 26 01 3D 25 9C 45
2017-07-03 10:30:52.923 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2017-07-03 10:30:52.928 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-07-03 10:30:52.931 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
2017-07-03 10:30:52.936 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 9C 00 00 02 75
2017-07-03 10:30:52.948 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
2017-07-03 10:30:52.951 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
2017-07-03 10:30:52.954 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: Sent Data successfully placed on stack.
2017-07-03 10:30:52.956 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-07-03 10:30:52.982 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 9C 00 00 02 00 00 7B
2017-07-03 10:30:53.012 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 9C 00 00 02 00 00 7B
2017-07-03 10:30:53.022 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=9C 00 00 02
2017-07-03 10:30:53.037 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: SendData Request. CallBack ID = 156, Status = Transmission complete and ACK received(0)
2017-07-03 10:30:53.041 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Starting initialisation from DONE
2017-07-03 10:30:53.056 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1c3a863 already registered
2017-07-03 10:30:53.071 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=3, callback=156, payload=03 03 26 01 3D
2017-07-03 10:30:53.103 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=9C 00 00 02
2017-07-03 10:30:53.107 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=156, expected=SendData, cancelled=false        transaction complete!
2017-07-03 10:30:53.109 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2017-07-03 10:30:53.118 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-07-03 10:30:53.123 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 3: Response processed after 214ms/2726ms.

Its as though when clicking the switch item, the sitemap isn’t passing back its state back to OH?

I’ve just noticed, I have 2 x sitemaps. I have one actual sitemap file called home.sitemap, in that it starts with:

sitemap home label=“My House” {

etc

and shows up in OpenHAB as a site called “My House”. However also in OpenHAB, it shows a 2nd sitemap called “home”. If I select to load “My House”, it shows everything in my actual sitemap file (legacy 1.x stuff), if I choose “home”, it presumably shows everything that is added via 2.x bindings which I also assume is stuff added to the database rather than items file.

Why does it show 2 x sitemaps? What have I f@#$%ked up on here?!!

Argh, I’m a total muppet. Realised I did this:
Switch kitchenlights “Kitchen” (gLightsLiving) { zwave=“zwave:device:fbcf2efa:node3:switch_dimmer” }

Instead of this:
Switch kitchenlights “Kitchen” (gLightsLiving) { channel=“zwave:device:fbcf2efa:node3:switch_dimmer” }

Problem fixed, my bad…!!!