Command class class COMMAND_CLASS_SWITCH_BINARY for endpoint 1 not found

Setup, Configuration and Use Beginners
,
1

Hi guys,

I know there are several similar topics but I still cannot solve my problem. I am using OH3.4 on a Pi4 with ZStick Gen5+. I have a couple of Fibaro FGS223 modules added to my zwave network. Some of them are working fine and for some the log shows some troubles.

2023-09-22 19:41:31.619 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 50: Command received zwave:device:e216f68b3e:node50:switch_binary1 --> ON [OnOffType]
2023-09-22 19:41:31.620 [DEBUG] [converter.ZWaveBinarySwitchConverter] - NODE 50: Command class class COMMAND_CLASS_SWITCH_BINARY for endpoint 1 not found
2023-09-22 19:41:31.620 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 50: No messages returned from converter
2023-09-22 19:41:58.501 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 50: Command received zwave:device:e216f68b3e:node50:switch_binary1 --> OFF [OnOffType]
2023-09-22 19:41:58.502 [DEBUG] [converter.ZWaveBinarySwitchConverter] - NODE 50: Command class class COMMAND_CLASS_SWITCH_BINARY for endpoint 1 not found
2023-09-22 19:41:58.503 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 50: No messages returned from converter

I’ve searched for a suitable solution and found the following:

https://community.openhab.org/t/fibaro-doubleswitch-fgs223-command-class-switch-binary-for-endpoint-1-not-found/145386/3

I’ve then compared the node.xml files from a working node (node_61) and one which is not doing so (Node_50). There are major differences.
network_fc386414__node_50.xml (8.6 KB)
network_fc386414__node_61.xml (34.6 KB)

Would it help to “copy/paste” the working xml file to the one which is not working? Or is it possible to help OH to identify the node in the right way?

Would be glad to get some advice.

Thanks a lot in advance!

Regards,
Matthias

2

I can see that the device was changed in early January 2023, so if you bought the working and not working at different times that could be why they are different. If you are on OH3.4.x, not OH3.4.0, you should be able to use the “reinitialize device” to pick up the right properties on the non-working device. Also deleting from the device UI (not excluding with the controller) and rescanning should work as well.
Copy/Paste/ then edit XML might work (have never tried) and is fraught with issues. I wouldn’t try that.

3

Thanks for the quick response. Neither reinitializing nor remove/add thing solved it. I had to exclude the device from the network and reinclude them. This solved the issue.

Regards,
Matthias

1 Like