Keep getting "Endpoint 0 not found. Cannot set command classes." for Z-Wave

TordYevl · May 22, 2016, 8:18pm

I keep getting “Endpoint 0 not found. Cannot set command classes.” in my log.
I use the new Z-Wave binding.
Anyone know how to fix this?

Debug printout from when it happens, tricky to know start and end for a specific event though.

2016-05-22 22:03:13.877 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0C 12 60 0D 01 00 32 02 21 64 01 42 D8 64 00 3C 01 42 D8 5E
2016-05-22 22:03:13.877 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Application Command Request (ALIVE:DONE)
2016-05-22 22:03:13.877 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 12: Starting initialisation from DONE
2016-05-22 22:03:13.877 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@18a04ac3 already registered
2016-05-22 22:03:13.877 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Incoming command class MULTI_INSTANCE
2016-05-22 22:03:13.877 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Received Multi-instance/Multi-channel Request
2016-05-22 22:03:13.877 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Controller has no endpoints. Probably originating (1) and destination (0) endpoints should be swapped.
2016-05-22 22:03:13.877 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Requested Command Class = METER (0x32)
2016-05-22 22:03:13.877 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Endpoint 0 not found. Cannot set command classes.
2016-05-22 22:03:13.877 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 22: Transaction not completed: node address inconsistent.  lastSent=22, incoming=255
2016-05-22 22:03:13.976 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 18 00 04 00 0C 12 60 0D 02 00 32 02 21 64 00 AA 19 5E 00 3C 00 AA 19 4F CA
2016-05-22 22:03:13.976 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-05-22 22:03:13.976 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 18 00 04 00 0C 12 60 0D 02 00 32 02 21 64 00 AA 19 5E 00 3C 00 AA 19 4F CA
2016-05-22 22:03:13.976 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 18 00 04 00 0C 12 60 0D 02 00 32 02 21 64 00 AA 19 5E 00 3C 00 AA 19 4F CA
2016-05-22 22:03:13.977 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0C 12 60 0D 02 00 32 02 21 64 00 AA 19 5E 00 3C 00 AA 19 4F
2016-05-22 22:03:13.977 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Application Command Request (ALIVE:DONE)
2016-05-22 22:03:13.977 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 12: Starting initialisation from DONE
2016-05-22 22:03:13.977 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@18a04ac3 already registered
2016-05-22 22:03:13.977 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Incoming command class MULTI_INSTANCE

TordYevl · July 14, 2016, 11:22am

Trying to bump to this issue which I still have.
Any clues?
Node 12 is a DSB28 Home Energy Meter G2.

2016-07-14 13:15:31.848 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 18 00 04 00 0C 12 60 0D 01 00 32 02 21 64 00 02 92 4A 00 3C 00 02 92 45 D7
2016-07-14 13:15:31.849 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-07-14 13:15:31.849 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 18 00 04 00 0C 12 60 0D 01 00 32 02 21 64 00 02 92 4A 00 3C 00 02 92 45 D7
2016-07-14 13:15:31.849 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 18 00 04 00 0C 12 60 0D 01 00 32 02 21 64 00 02 92 4A 00 3C 00 02 92 45 D7
2016-07-14 13:15:31.849 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0C 12 60 0D 01 00 32 02 21 64 00 02 92 4A 00 3C 00 02 92 45
2016-07-14 13:15:31.849 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Application Command Request (ALIVE:DONE)
2016-07-14 13:15:31.849 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 12: Starting initialisation from DONE
2016-07-14 13:15:31.849 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@28da8483 already registered
2016-07-14 13:15:31.849 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 12: Incoming command class MULTI_INSTANCE
2016-07-14 13:15:31.849 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Received Multi-instance/Multi-channel Request
2016-07-14 13:15:31.849 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Controller has no endpoints. Probably originating (1) and destination (0) endpoints should be swapped.
2016-07-14 13:15:31.849 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Requested Command Class = METER (0x32)
2016-07-14 13:15:31.849 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 12: Endpoint 0 not found. Cannot set command classes.

chris · July 14, 2016, 11:33am

This indicates that a device probably didn’t describe it’s endpoints fully in the NIF. Can you provide some information on what the device is?

TordYevl · July 14, 2016, 12:34pm

It’s a DSB28 Home Energy Meter G2, is there any other info needed?

nbar · January 27, 2017, 10:10pm

Hi @chris!

I have got the same problem with my Fibaro FGK-101 door sensor (I attached the node.xml file) when the device sends the temperature message:

2017-01-27 23:06:36.595 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 0E 0A 60 0D 00 00 31 05 01 42 09 15 E9 
2017-01-27 23:06:36.601 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-01-27 23:06:36.604 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 0E 0A 60 0D 00 00 31 05 01 42 09 15 E9 
2017-01-27 23:06:36.606 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 0E 0A 60 0D 00 00 31 05 01 42 09 15 E9 
2017-01-27 23:06:36.609 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0E 0A 60 0D 00 00 31 05 01 42 09 15 
2017-01-27 23:06:36.610 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:DONE)
2017-01-27 23:06:36.611 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 14: Starting initialisation from DONE
2017-01-27 23:06:36.612 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1e52eae already registered
2017-01-27 23:06:36.613 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class MULTI_INSTANCE
2017-01-27 23:06:36.614 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 14: Received MULTI_INSTANCE command V0
2017-01-27 23:06:36.615 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 14: Requested Command Class = SENSOR_MULTILEVEL (0x31)
2017-01-27 23:06:36.616 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 14: Endpoint 0 not found. Cannot set command classes.

Furthermore the configuration for this device seems to have a problem when trying to set the temperature report interval (parameter 52) since HABmin only accepts zero and 5 as values (even HABmin describes in the tooltip for this parameter, that the value has to be between 5 and 32400). If I enter a value higher than five, the value is resetted after pushing the save button.

Can you help me with both issues?

Thank you very much in advance!

Kind regards, Nico.

node14.xml (20.4 KB)

Update:
Sorry, I forgot to mention, that I am using this sensor without magnet but in “external button”-mode (my standard door bell). And of course, I installed a DS18B20 temperature sensor.

chris · January 28, 2017, 8:42am

I’ll need to look at this further as the device is sending illegal frames -:

The spec doesn’t allow the sending and receiving endpoint to be 0. This might be something to do with the way associations have been configured so I’ll have a look at that.

chris · January 28, 2017, 9:26am

One other point - please make sure you are using the latest SNAPSHOT binding.

nbar · January 28, 2017, 11:30pm

I checked the version of the binding:

openhab> list | grep -i wave
193 | Active   |  80 | 2.0.0                 | ZWave Binding
openhab> feature:list | grep -i wave
openhab-binding-zwave                     | 2.0.0            | x        | Started     | addons-2.0.0            | Z-Wave Binding
openhab> feature:info openhab-binding-zwave
Feature openhab-binding-zwave 2.0.0
Description:
  Z-Wave Binding
Feature has no configuration
Feature has no configuration files
Feature depends on:
  openhab-runtime-base 0.0.0
  openhab-transport-serial 0.0.0
Feature contains followed bundles:
  mvn:org.openhab.binding/org.openhab.binding.zwave/2.0.0 start-level=80
Feature has no conditionals.

Based on this I am not sure if I am using the latest snapshot. But since I am using openHABian and it shows me zero available updates after login, I hope to do so.

Is there another way to find out the build number of the used/depoyed binding-jar?

jaydee73 · January 29, 2017, 5:35am

You are using the stable 2.0 OH runtime, therefore also the stable 2.0 zwave binding. This is NOT the snapshot version.

I am facing the same problem. It’s no easy task to use a stable runtime with a snapshot version of a single binding…

David_Watzinger · March 10, 2017, 1:41pm

Hy!

I have the same problem with my Fibaro FGK-101 door sensor…
When I put the magnet close to the Sensor, or away from it, thhere is the log message:

[ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 3: Endpoint 0 not found. Cannot set command classes.

Has somebody a solution for this problem? I don´t know what to do now…

chris · March 10, 2017, 1:52pm

As has been stated a few times above, please use the latest snapshot version of the binding.

David_Watzinger · March 10, 2017, 2:27pm

Thank you, now it works fine