Failing to include Z-wave device FGD211 Fibaro dimmer

RolfV · October 30, 2018, 8:40am

Hi all,

At first I made a ticket for this at the CD Jackson website, but @chris asked me to make a topic about this instead.
I recently got a Fibaro Dimmer FGD211. It’s a second hand item, so I first had to exclude/reset it, and that seemed to work fine.
So far I have however been unable to include the device via HABmin. Below you can find a piece of the log when I start the inclusion via HABmin, and from what I understand there are some messages incoming to add the device to the network, but then I do not see any change in HABmin.

Anyone who can tell me what is going on here?
Thanks!

2018-10-30 09:18:21.577 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Stop zwave:serial_zstick:4b85e013
2018-10-30 09:18:21.578 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave inclusion process not running - nothing to do
2018-10-30 09:18:21.579 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Start zwave:serial_zstick:4b85e013
2018-10-30 09:18:21.579 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2
2018-10-30 09:18:21.580 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
2018-10-30 09:18:21.580 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller start inclusion
2018-10-30 09:18:21.581 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:true.
2018-10-30 09:18:21.581 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-30 09:18:21.582 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A C1 CC BD 
2018-10-30 09:18:21.583 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 CC BD 
2018-10-30 09:18:21.583 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2018-10-30 09:18:21.584 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2018-10-30 09:18:21.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 195: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 204
2018-10-30 09:18:21.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-10-30 09:18:21.585 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-10-30 09:18:21.585 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 195: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 204
2018-10-30 09:18:21.586 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2018-10-30 09:18:21.586 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A CC 01 00 00 7F 
2018-10-30 09:18:21.586 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-30 09:18:21.586 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2018-10-30 09:18:21.586 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=AddNodeToNetwork[74], type=Request[0], dest=1, callback=204, payload=CC 01 00 00 
2018-10-30 09:18:21.587 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=AddNodeToNetwork[74], type=Request[0], dest=1, callback=204, payload=CC 01 00 00 
2018-10-30 09:18:21.587 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 195: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 204
2018-10-30 09:18:21.587 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-10-30 09:18:21.588 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 195: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 204
2018-10-30 09:18:21.588 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 195: (Callback 204)
2018-10-30 09:18:21.588 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2018-10-30 09:18:21.588 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 195: callback 204
2018-10-30 09:18:21.589 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=AddNodeToNetwork[74], type=Request[0], dest=1, callback=204, payload=CC 01 00 00 
2018-10-30 09:18:21.589 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Learn ready.
2018-10-30 09:18:21.589 [DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion event: Current state IncludeSent, new event IncludeStart
2018-10-30 09:18:21.590 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 195: Transaction COMPLETED
2018-10-30 09:18:21.590 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Response processed after 6ms
2018-10-30 09:18:21.590 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: TID 195: Transaction completed
2018-10-30 09:18:21.590 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:195 DONE
2018-10-30 09:18:21.591 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-30 09:18:21.591 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-30 09:18:51.580 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Stop zwave:serial_zstick:4b85e013
2018-10-30 09:18:51.580 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller stopping inclusion at IncludeStart
2018-10-30 09:18:51.581 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
2018-10-30 09:18:51.581 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-30 09:18:51.582 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 CD 78 
2018-10-30 09:18:51.583 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 CD 78 
2018-10-30 09:18:51.583 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2018-10-30 09:18:51.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 196: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 205
2018-10-30 09:18:51.590 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2018-10-30 09:18:51.591 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-10-30 09:18:51.591 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-10-30 09:18:51.591 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 196: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 205
2018-10-30 09:18:51.592 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2018-10-30 09:18:51.592 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-30 09:18:51.592 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2018-10-30 09:18:51.681 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A CD 06 00 00 79 
2018-10-30 09:18:51.682 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=AddNodeToNetwork[74], type=Request[0], dest=6, callback=205, payload=CD 06 00 00 
2018-10-30 09:18:51.683 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=AddNodeToNetwork[74], type=Request[0], dest=6, callback=205, payload=CD 06 00 00 
2018-10-30 09:18:51.683 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 196: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 205
2018-10-30 09:18:51.684 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-10-30 09:18:51.684 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 196: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 205
2018-10-30 09:18:51.684 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 196: (Callback 205)
2018-10-30 09:18:51.684 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2018-10-30 09:18:51.685 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 196: callback 205
2018-10-30 09:18:51.685 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=AddNodeToNetwork[74], type=Request[0], dest=6, callback=205, payload=CD 06 00 00 
2018-10-30 09:18:51.685 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Done.
2018-10-30 09:18:51.686 [DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion event: Current state IncludeDone, new event IncludeDone
2018-10-30 09:18:51.686 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
2018-10-30 09:18:51.686 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2018-10-30 09:18:51.687 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller end exclusion
2018-10-30 09:18:51.687 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWaveController include done
2018-10-30 09:18:51.687 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 196: Advanced to DONE
2018-10-30 09:18:51.688 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Response processed after 104ms
2018-10-30 09:18:51.688 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: TID 196: Transaction completed
2018-10-30 09:18:51.688 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:196 DONE
2018-10-30 09:18:51.689 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-30 09:18:51.689 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-30 09:18:51.690 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 00 B5 
2018-10-30 09:18:51.690 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 00 B5 
2018-10-30 09:18:51.691 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2018-10-30 09:18:51.691 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 197: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0
2018-10-30 09:18:51.691 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2018-10-30 09:18:51.692 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-10-30 09:18:51.692 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-10-30 09:18:51.693 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 197: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0
2018-10-30 09:18:51.693 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2018-10-30 09:18:51.693 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-30 09:18:51.693 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2018-10-30 09:18:56.691 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 255: TID 197: Timeout at state WAIT_REQUEST. 3 retries remaining.
2018-10-30 09:18:56.691 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 197: Transaction is current transaction, so clearing!!!!!
2018-10-30 09:18:56.691 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 197: Transaction CANCELLED
2018-10-30 09:18:56.692 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:197 CANCELLED
2018-10-30 09:18:56.692 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

chris · October 30, 2018, 8:45am

Thanks for posting here @RolfV.

Just to post what I said privately, this log doesn’t really show any device activity. It shows the binding putting the controller into inclusion mode, and then 30 seconds, it takes it out of inclusion mode. This is all normal, and there is no sign of any device joining.

Have you put the device into inclusion mode? I know these days many devices are meant to automatically enter inclusion when they are powered on if they are not included already. I would say it doesn’t hurt to do this manually if you’re not already doing so.

RolfV · October 30, 2018, 8:52am

Thanks Chris.
I was, based on the Received msg (0): Message: class=AddNodeToNetwork[74], type=Request[0], dest=1, callback=204, payload=CC 01 00 00 under the impression that the device actually sent something to the controller/binding, but from you I understand that this is not the case.
What I do every time when I start inclusion, that I manually triple click the “B-button” as described in the manual for this device.

In the meantime I tried to put the controller into Exclusion mode and then manually exclude the device, resulting in the following log:

2018-10-30 09:43:28.480 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4B 05 02 B6 
2018-10-30 09:43:28.480 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4B 05 02 B6 
2018-10-30 09:43:28.481 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2018-10-30 09:43:28.482 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 222: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 2
2018-10-30 09:43:28.488 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2018-10-30 09:43:28.488 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-10-30 09:43:28.488 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-10-30 09:43:28.489 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 222: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 2
2018-10-30 09:43:28.489 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2018-10-30 09:43:28.489 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-30 09:43:28.490 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2018-10-30 09:43:28.579 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4B 02 06 00 00 B7 
2018-10-30 09:43:28.580 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=RemoveNodeFromNetwork[75], type=Request[0], dest=6, callback=2, payload=02 06 00 00 
2018-10-30 09:43:28.580 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=RemoveNodeFromNetwork[75], type=Request[0], dest=6, callback=2, payload=02 06 00 00 
2018-10-30 09:43:28.581 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 222: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 2
2018-10-30 09:43:28.581 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2018-10-30 09:43:28.581 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 222: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 2
2018-10-30 09:43:28.582 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 222: (Callback 2)
2018-10-30 09:43:28.582 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2018-10-30 09:43:28.582 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 222: callback 2
2018-10-30 09:43:28.583 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=RemoveNodeFromNetwork[75], type=Request[0], dest=6, callback=2, payload=02 06 00 00 
2018-10-30 09:43:28.583 [DEBUG] [serialmessage.RemoveNodeMessageClass] - Remove Node: Done.
2018-10-30 09:43:28.583 [DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion event: Current state ExcludeFail, new event ExcludeDone
2018-10-30 09:43:28.584 [DEBUG] [serialmessage.RemoveNodeMessageClass] - Ending EXCLUSION mode.
2018-10-30 09:43:28.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2018-10-30 09:43:28.584 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller end exclusion
2018-10-30 09:43:28.585 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWaveController include done
2018-10-30 09:43:28.585 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 0: Deleting a node that doesn't exist.
2018-10-30 09:43:28.591 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 222: Advanced to DONE
2018-10-30 09:43:28.591 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Response processed after 109ms
2018-10-30 09:43:28.592 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: TID 222: Transaction completed
2018-10-30 09:43:28.592 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:222 DONE
2018-10-30 09:43:28.593 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-30 09:43:28.593 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-30 09:43:28.593 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4B 05 00 B4 
2018-10-30 09:43:28.594 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4B 05 00 B4 
2018-10-30 09:43:28.594 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2018-10-30 09:43:28.595 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 223: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0
2018-10-30 09:43:28.595 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2018-10-30 09:43:28.595 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-10-30 09:43:28.596 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2018-10-30 09:43:28.596 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 223: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0
2018-10-30 09:43:28.596 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2018-10-30 09:43:28.596 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-30 09:43:28.597 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

Here I see at some point NODE 0: Deleting a node that doesn't exist.. What does that mean, if anything?

Thanks!

chris · October 30, 2018, 9:44am

No - this is a response from the controller to say that it is now in inclusion mode. If a device was added, we would see some additional messages showing that a slave device was found.

It just means that there was no node to delete. The binding probably shouldn’t log this at this point, but it’s simply a log issue.

RolfV · October 30, 2018, 10:04am

Ah good to know. So really nothing happens then, as I see this same behaviour everytime.

So no exclusion either. I recall seeing a message earlier in HABmin when I was first trying to exclude the device (it was second hand after all) that “Node … was successfully removed from …” or something like that, and based on that I concluded that I was able to exclude the device, and therefore that it was alive. But that might have been Node 0 as well then.

So I start to think more and more that the device is actually dead, which also is a valid conclusion in the end.

sihui · October 30, 2018, 11:13am

Did you try resetting the device to factory defaults instead of excluding?

Reset by holding B button for 3 sec. after connecting mains voltage to the Dimmer

RolfV · October 30, 2018, 11:16am

Yes, but I am not sure how to find out if that has been done successfully, that’s not clear from the manual to me.
After that, I tried including it, but without any success so far.

sihui · October 30, 2018, 11:16am

Actually there is a better (working?) solution in another forum:

Turn off powe supply,

Hold B button

While holding B button, turn on supply

Hold B button for 5 sec (In relay you should hear click sound)

Release button and turn off and onn power supply.

RolfV · October 30, 2018, 11:17am

I will try that this evening, thanks for that. I am not sure if you should expect a click in a dimmer, but I will see what happens and report back.

FloatingBoater · October 30, 2018, 12:57pm

Hi,

I have several FGD211, and have found them all to be troublesome to include/ exclude.

The plastic moulding has a little tab which pushes PCB-mounted ‘B’ button underneath. This can sometimes become deformed, making it harder to tell when the button has gone click.
The device does have a useful multi-coloured LED which gives lots of feedback on what the unit is actually doing, that is if you know the colours, and can see them!

FIBARO Dimmer 2 has a MENU with each position indicated by the specified LED indicator colour. In order to enter the menu press the B-button and hold for at least 2 seconds. While the B-button is still pressed, LED indicator colour will change in the following sequence:

BLUE - initiate the load calibration procedure
RED - load calibration procedure with FIBARO Bypass 2
WHITE - activate turning the load on/off using the B-button
GREEN - reset the energy consumption data memory
VIOLET - initiate the Z-Wave network range test
YELLOW - reset the FIBARO Dimmer 2 to factory defaults

Release the B-button to choose the desired function and confirm your choice with the B-button click.

Once installed in a wall, I have had to Exclude and Include devices via the S1 switch - triple clicking is VERY unreliable, and has taken me 20 attempts to get the right speed.

Slower clicking of the external S1 switch seems to work better. I use a momentary wall switch for S1.

For reference, the v1.2 manual is here (might be slight differences depending on your firmware version):

BTW - if you find issues turning on your lights, you are not alone. Earlier FGD-211 load calibration doesn’t work that well and even with Fibaro setting changes, mine turn off immediately after an ON command about 30% of the time.

No, a Fibaro FGB-002 bypass load and 3-wire connection don’t help.

Yes - they can be that bad, and my main workaround is to add several ON commands in a rules file.

RolfV · October 30, 2018, 2:01pm

That applies to the Dimmer 2, the FGD212, while I have a FGD 211, a Dimmer 1 that I am struggling with. So far I haven’t seen anything blink, so no led in the FGD 211 unfortunately.

I’m not sure if there should be a tab in a FGD 211, but if so, it has broken off before I even got the device, because I have a device with a (rather deep) hole in it, and somewhere below I can find the B-button. And that also doesn’t really help when trying to click 3 times at some predefined speed.

In any case it sounds like this device is a lot of fun… Let’s see how far I’m going to take it

RolfV · October 30, 2018, 7:03pm

This doesn’t seem to work either, and I definitely didn’t hear a click while holding the B button for over 8 seconds.

Guess it’s a dead device then.
But at least I learned a bit more about z-wave logs in the progress

FloatingBoater · October 31, 2018, 7:55pm

Hi,

Apologies - I didn’t check and thought the FGD211 was the single channel version, not the previous v1.

A lot seems common though - the process for association looks the same, and on the v2 is very unreliable.

It should be noted that the push-button connected to S1 terminal is a master push-button, it activates the basic functionality of the Dimmer (turning the light on/off, dimming) and starts the learning mode (Include / Exclude).

Questions and suggestions:

Does the module switch the light on and off via S1?
This should work without any configuration and no Z-Wave association.
Is the switch you have between Sx and S1 momentary?
e.g. normally open circuit, push to connect, and not a ‘normal’ ON / OFF light switch. Triggering association is hard, so flipping a ON/OFF switch three times may be even harder to get just right.
Have you tried a test rig, especially one simplified using 3-wire connection for power, and a simple incandescent bulb (not a LED or CF)?
Be careful with mains electricity, but a controlled test circuit removes other factors which could be causing problems.

I don’t think the module is able to make a ‘click’ - this is a dimmer module, so there is no relay only a triac.

I have managed to disassociate and associate v2 dimmers installed in walls using only the S1 switch - timing of the three presses is hard, but after trying different speeds, has worked without touching the B button.