Another case of Fibaro Dimmer 2 (FGD212) can't be controlled from ZWAVE-JS or ZWAVE-JS-UI

[oztourer]

Checklist

• I am not using Home Assistant. Or: a developer has told me to come here.
• I have checked the troubleshooting section and my problem is not described there.
• I have read the changelog and my problem is not mentioned there.

Deploy method

Home Assistant Add-on

Z-Wave JS UI version

9.27.8

ZwaveJS version

14.3.7

Describe the bug

I have a Mios Vera Edge and have been running the Vera integration in Home Assistant for some years. I want to retire the Vera functionality but use it as a network attached zwave controller. I have successfully stopped the Vera applications and set up ser2net so that I can access the zwave network from zwave-js-ui. That is mostly working well, using the Vera's S0 key in zwave-js-ui so that I do not have to rebuild my network. Most devices work as expected but I have two Fibaro FGD212 in-wall dimmers and these devices are not successfully interviewed. They are correctly recognised as Fibaro Dimmer 2 and their in-built sensors are added to the device that is created in the zwave-js embedded in zwave-js-ui. No dimmer switch entity is created though so I cannot control the dimmer from Home Assistant. The expected configuration entries for the device are also not present in zwave-js-ui.

I have tried re-interviewing the device (debug log attached) and much of the process works as expected but the log does show an error related to "querying Basic CC state":

  CNTRLR   [Node 009] Interviewing Basic...
  CNTRLR » [Node 009] querying Basic CC state...
  CNTRLR   [Node 009] Timed out while waiting for a response from the node (ZW0201)
  CNTRLR   [Node 009] No response to Basic Get command, assuming Basic CC is unsupported.

zwave-js-ui lists only the following command classes for the interviewed device:

• Multilevel Sensor v4
• Meter v3
• Notification v5
• Manufacturer Specific v2
• Version v2
• Configuration

So no Multilevel Switch and therefore no switch entity available for Home Assistant.

To Reproduce

Try to include a Fibaro Dimmer 2 (FDG212) in the zwave network and later try to re-interview it. The same error will result in both cases.

Expected behavior

A new device and list of entities should be added to the Zwave integration and one of the entities should be a switch.

Additional context

I can nuke or unNuke the Vera at will. All devices work correctly in the Vera UI as well as in Home Assistant using the Vera integration. Switching to ser2net for a network attached zwave controller and using Zwave-JS-UI always gives the same result - most devices work fine with the exception of the Fibaro Dimmer 2.

debug_interview2.log
node_9.json
node_9_dump.json

[oztourer]

Further information: I have a spare Fibaro Dimmer 2 so I tried including that through zwave-js-ui. It claimed to fail but did in fact add the device. The result was the same as when interviewing existing nodes - sensors recognised but no switch added and no configuration entries under Config. During inclusion I get a number of log messages "Dropping message with invalid payload" so it may be that the Vera embedded zwave controller uses a non-standard protocol, or a protocol not currently recognised by node-zwave-js. Or that some of the messages coming from the FGD212 are not recognised by node-zwave-js.

I was able to include an Aeon Labs DSD37 Range Extender without any error messages being generated.

[oztourer]

I decided to exclude and then include the Fibaro Dimmer 2, which causes it to reset itself to default values. The device now configures itself correctly in zwave-js and I get the expected switches. I do not have any load on one of the switch inputs and had configured that one to activate scenes -maybe this caused the device to be handled incorrectly during inclusion? Note that I should still have switches configured in this case as I use a push-button switch to trigger a scene.

Although I still see the report above as describing a bug the issue is in my case resolved.