All the fibaro dimmer in my network fail except one

Configuration Z-Wave
1

Hi,

I use Home Assistant for a while but I decided today to migrate my Zwave network from Jeedom to Home Assistant. Now that it’s done I’ve some really strange behaviour.

My network is composed 11 devices some have batteries and some are inwall. In the network I have 4 fibaro dimmers FGD212. Only one is working as expected, the 3 others are visible, have their entities but they can’t turn the light on. When I click on the light entity it enables for one second or two then go back to turned off state.

From my understanding of the logs, when I turn on the light the messages are sent but the device don’t respond and something time out (I don’t know what time out) :

2021-08-15T06:56:32.230Z DRIVER » [Node 006] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      8
                                  └─[MultilevelSwitchCCSet]
                                      target value: 255
                                      duration:     default
2021-08-15T06:56:32.241Z DRIVER « [RES] [SendData]
                                    was sent: true
2021-08-15T06:56:32.256Z DRIVER « [REQ] [SendData]
                                    callback id:     8
                                    transmit status: OK
2021-08-15T06:56:32.608Z CNTRLR   [Node 018] [Multilevel Sensor] Power: metadata updated            [Endpoint 0]
2021-08-15T06:56:32.609Z CNTRLR   [Node 018] [~] [Multilevel Sensor] Power: 0 => 0                  [Endpoint 0]
2021-08-15T06:56:32.612Z DRIVER « [Node 018] [REQ] [ApplicationCommand]
                                  └─[MultilevelSensorCCReport]
                                      type:  Power
                                      scale: Watt
                                      value: 0
2021-08-15T06:56:37.268Z DRIVER » [Node 006] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      9
                                  └─[MultilevelSwitchCCGet]
2021-08-15T06:56:37.278Z DRIVER « [RES] [SendData]
                                    was sent: true
2021-08-15T06:56:37.293Z DRIVER « [REQ] [SendData]
                                    callback id:     9
                                    transmit status: OK
2021-08-15T06:56:47.300Z CNTRLR   [Node 006] Timed out while waiting for a response from the node

One thing that is weird is that I can’t get access to device configuration on the 3 that are not working but I can on the one working.

I was hoping to exclude the devices and reinclude them but I can’t exclude them because they respond correctly to ping, then I get an Error 46. Here from the logs :

2021-08-15T07:07:51.656Z CNTRLR « [Node 006] ping successful
Z-Wave error ZWaveError: The node removal process could not be started because the node responded to a ping.
    at ZWaveController.removeFailedNode (/usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:2661:10)
    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:27:17)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:93:62) {
  code: 46,
  context: undefined,
  transactionSource: undefined
}

I as well tried to heal/reinterview the device, heal the network multiple times but didn’t solve the issue.

I hope someone can help understand this
Thanks for reading.

2

I finally did what I didn’t want to do but it solved my issue !

I did a factory reset on my dimmers, reinclude them in unsecure mode and it’s now working in Hass.
I just have to find the right configuration so that my physical switch work again…

If it helps somebody one day, never know.

1 Like
3

hi @jbleuzen, thanks for sharing the solution. I had the same issue and found your topic. I did a quick exclude and include and all Fibaro dimmers are working again.

Thanks