Fibaro Dimmer 2 doesn't react on input

Add-ons Bindings
, ,
1

Hey, because a problem comes rarely alone, I do have another question :wink:

I’ve a Fibaro Dimmer 2 installed and it’s behaving a little bit awkward. It got recognised by OH2 and works with an external switch connected to it. But because it’s mounted in the lamp and I don’t want to use a hard wired switch, it should also work wireless. So I configured it in OH2 and tried to set a dimm level on my smartphone. I can see that those commands are sent by the interface in the log files, but nothing happens…

09:21:37.599 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'ZWaveNode9FGD212Dimmer2_Dimmer' received command 31
09:21:37.608 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Command received zwave:device:cb930e03:node9:switch_dimmer --> 31
09:21:37.616 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 9: Creating new message for command SWITCH_MULTILEVEL_SET
09:21:37.618 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
09:21:37.618 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
09:21:37.621 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 09 03 26 01 1F 25 35 C4 
09:21:37.627 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 9: Sending REQUEST Message = 01 0A 00 13 09 03 26 01 1F 25 35 C4 
09:21:37.637 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
09:21:37.640 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09:21:37.642 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
09:21:37.645 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
09:21:37.647 [INFO ] [marthome.event.ItemStateChangedEvent] - ZWaveNode9FGD212Dimmer2_Dimmer changed from NULL to 31
09:21:37.647 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
09:21:37.648 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 9: Sent Data successfully placed on stack.
09:21:37.678 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 35 00 00 04 DA 
09:21:37.682 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09:21:37.683 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 35 00 00 04 00 00 D4 
09:21:37.685 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 35 00 00 04 00 00 D4 
09:21:37.688 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=35 00 00 04 
09:21:37.689 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 9: SendData Request. CallBack ID = 53, Status = Transmission complete and ACK received(0)
09:21:37.690 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 9: Starting initialisation from DONE
09:21:37.691 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=9, callback=53, payload=09 03 26 01 1F 
09:21:37.693 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=35 00 00 04 
09:21:37.694 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=53, expected=SendData, cancelled=false        transaction complete!
09:21:37.695 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
09:21:37.696 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
09:21:37.697 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 9: Response processed after 68ms/2978ms.

Has anyone an idea about that? That particular device is also chatting a lot with the interface while the environment idles.

Cheers

2

I still have that issue, but I recently noticed that the automatic calibration didn’t work correctly as the parameter 14 says : “calibration procedure not performed or Dimmer operates on manual settings”

So I tried to force it through parameter 13 but then I get these lines in the log:

16:22:48.044 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Configuration update received
16:22:48.287 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Configuration update config_52_2 to 3600
16:22:48.288 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Error getting configurationCommandClass
16:22:48.289 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Configuration update config_31_1 to 0
16:22:48.291 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Error getting configurationCommandClass
16:22:48.292 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Configuration update config_33_1 to 0
16:22:48.293 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Error getting configurationCommandClass
16:22:48.294 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Configuration update config_54_1 to 0
16:22:48.295 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Error getting configurationCommandClass
16:22:48.296 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Configuration update config_10_2 to 0
16:22:48.297 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Error getting configurationCommandClass
16:22:48.298 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Configuration update config_50_1 to 10
16:22:48.300 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Error getting configurationCommandClass
16:22:48.301 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Configuration update group_5 to null

Does anyone have an idea?