IS 140-2 Z, connection problems, malfunction

I’ve got an IS 140-2 Zwave, controller is vendor 0x0658 product 0x0200, Aeon Labs Z-wave stick, openhab 3.1

It needed manual inclusion, but worked for a few days. But now no motion events nor luminance changes any more, no automatic switch on of the lamp on motion.

Has anybody experienced this, too? Log entries below

Is the device defective?

Is the controller not suitable?

Is the distance to controller too far? (10 meters, but with house wall (obviously))

Or does it need a firmware update (how)?

Thanks for any hints
Juergen

2021-08-15 19:56:10.795 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zwave:device:controller:node3’ changed from ONL
INE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2021-08-15 19:56:10.799 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘IS140_Status’ changed from ON to OFF
2021-08-15 19:56:30.321 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zwave:device:controller:node3’ changed from OFF
LINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE
2021-08-15 19:56:30.324 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘IS140_Status’ changed from OFF to ON

2021-08-15 07:07:23.124 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 2 has invalid device class. generic = 0xf0, specific = 0x90.
2021-08-15 07:07:23.406 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 2 has invalid device class. generic = 0xf0, specific = 0x90.
2021-08-15 07:07:23.641 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 3 has invalid device class. generic = 0xff, specific = 0x2.
2021-08-15 08:48:06.918 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 2 has invalid device class. generic = 0xf0, specific = 0x90.
2021-08-15 08:48:07.063 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 2 has invalid device class. generic = 0xf0, specific = 0x90.
2021-08-15 08:48:07.129 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 3 has invalid device class. generic = 0xff, specific = 0x2.
2021-08-15 08:48:07.402 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 3 has invalid device class. generic = 0xff, specific = 0x2.
2021-08-15 10:33:38.628 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 2 has invalid device class. generic = 0xf0, specific = 0x90.
2021-08-15 10:33:38.781 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 2 has invalid device class. generic = 0xf0, specific = 0x90.
2021-08-15 10:33:38.863 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 2 has invalid device class. generic = 0xf0, specific = 0x90.
2021-08-15 10:33:39.100 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 2 has invalid device class. generic = 0xf0, specific = 0x90.
2021-08-15 10:33:39.354 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 3 has invalid device class. generic = 0xff, specific = 0x2.
2021-08-15 10:33:39.586 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 3 has invalid device class. generic = 0xff, specific = 0x2.

Finally got the idea to move the controller stick nearer to the IS 140-2 Zwave, looks like it is working for now.
Distance was first about 4m y + 6m x, now 0 y + 5m x. Strange that this should make a difference.