Good idea 
You wonât, Iâm confident âŠ
The upgrade did not work well. I went successfully to beta5 but there was no change in the system whatsoever. Everything worked as before. mapdb was alive and kicking.
I did not bother and I did a clean reinstall which did the trick.
As you have predicted now I have all the missing channels namely the âDoor Openâ
Many thanks for the pointers!
Then I think this is likely the problem. You should upgrade to the latest snapshot to get the updated device definitions.
Hi guys,
I thought Iâd post in this thread as Iâve got a similar issue as Christos. Iâm using the same hardware, the Fibaro door sensor FGK101.
I installed it the other day and everything seemed to go well. It was included and configured smoothly.
I created the items on the channels that I wanted. Right now I have items for both the door switch and the door contact.
However niether of these trigger when opening / closing. I canât seem to figure out why. My configuration settings in habmin for the door sensor are currently the exact same as rud posted in his working example.
Iâve got lifeline set to my controller as well.
Iâm unsure in which direction to go next since everything seems to be set up correctly but it still aint workin.
Would love some advice on where I should go next in trying to find out what the problem could be. 
Which version of openHAB, which version of the zwave binding?
Anything in your events.log, anything in your openhab.log?
If nothing in your openhab.log, switch to debug and take a look again.
My openhab.log shows this when opening the door:
And my event log does not show any events connected to the door sensor (node20)
As a test, I opened one of my other doors with a sensor from a different manufacturer and that made an event show up that sated the sensor when from OFF to ON.
Edit my Openhab version is Build 732.
I attempted an upgrade but my system hang during the process. Trying to resolve that issue now. Will come back after testing again.
After some reading I found that I just had to press [SPACE] to continue reading the later part of a text concerning on of the packages in the linux upgrade processes. Waited over two hours first to see if the process would finish. haha you learn something new every day. 
Now I have the most recent SNAPSHOT Build #743
I tried once again with the Fibaro door sensor. I got the same type of error.
Managed to get into debug now as well in karaf and tail the log. Opened the log later in windows notepad but the format is very off and not suited for reading. Attaching the karaf tail here.
Does the Z-wave binding update automatichally when I download the newest openhab? Or should I update this sepereately somehow? Iâve never done that before after running the online distro of openhab.
Just copy the log from your karaf via CTRL-C and paste it here, then format it with âpreformatted textâ = </> button or three backticks at the beginning or at the end of your text, it willl look similar to this:
```
backticks
```
preformatted text
Itâs even easier: uninstall a binding through PaperUI (or HABmin), wait a minute, install it again and it is updated.
Next thing you should do is: take a look at your zwave xml file for node 20 and find out the type and id of your sensor. There are multiple sensors with the same name and they behave differently:
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/125
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/381
thanks for your help sihui!
I did what you suggested with the binding, removed & added it again in paper ui. Still the same type of error in the logs though.
Iâm thinking it perhaps has to do with the match between the binding and the actual sensor as well. Maybe it is identified incorrectly somehow.
Iâm looking in the xml for the door sensor. Iâm not sure though if the data populated in the xml comes from the device or if it comes from the zwave binding in openhab. So itâs hard to determine if the values in there are correct or not.
<node>
<deviceClass>
<basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
<genericDeviceClass>SENSOR_NOTIFICATION</genericDeviceClass>
<specificDeviceClass>NOTIFICATION_SENSOR</specificDeviceClass>
</deviceClass>
<homeId>0xf2e219e5</homeId>
<nodeId>20</nodeId>
<version>4</version>
<manufacturer>0x10f</manufacturer>
<deviceId>0x1001</deviceId>
<deviceType>0x701</deviceType>
<listening>false</listening>
<frequentlyListening>false</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<supportedCommandClasses>
<entry>
<commandClass>DEVICE_RESET_LOCALLY</commandClass>
<deviceResetLocallyCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</deviceResetLocallyCommandClass>
</entry>
<entry>
<commandClass>CONFIGURATION</commandClass>
<configurationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<configParameters>
<entry>
<int>1</int>
<configurationParameter>
<index>1</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>2</int>
<configurationParameter>
<index>2</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>3</int>
<configurationParameter>
<index>3</index>
<size>1</size>
<value>6</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>4</int>
<configurationParameter>
<index>4</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>70</int>
<configurationParameter>
<index>70</index>
<size>2</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>71</int>
<configurationParameter>
<index>71</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>72</int>
<configurationParameter>
<index>72</index>
<size>1</size>
<value>15</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>10</int>
<configurationParameter>
<index>10</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>11</int>
<configurationParameter>
<index>11</index>
<size>1</size>
<value>2</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>12</int>
<configurationParameter>
<index>12</index>
<size>2</size>
<value>255</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>13</int>
<configurationParameter>
<index>13</index>
<size>2</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>14</int>
<configurationParameter>
<index>14</index>
<size>2</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>15</int>
<configurationParameter>
<index>15</index>
<size>2</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>50</int>
<configurationParameter>
<index>50</index>
<size>2</size>
<value>300</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>51</int>
<configurationParameter>
<index>51</index>
<size>2</size>
<value>10</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>20</int>
<configurationParameter>
<index>20</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>52</int>
<configurationParameter>
<index>52</index>
<size>2</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>53</int>
<configurationParameter>
<index>53</index>
<size>2</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>54</int>
<configurationParameter>
<index>54</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>55</int>
<configurationParameter>
<index>55</index>
<size>2</size>
<value>540</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>56</int>
<configurationParameter>
<index>56</index>
<size>2</size>
<value>40</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>30</int>
<configurationParameter>
<index>30</index>
<size>2</size>
<value>5</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>31</int>
<configurationParameter>
<index>31</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
</configParameters>
</configurationCommandClass>
</entry>
<entry>
<commandClass>BASIC</commandClass>
<basicCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</basicCommandClass>
</entry>
<entry>
<commandClass>FIRMWARE_UPDATE_MD</commandClass>
<firmwareUpdateCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>3</versionSupported>
</firmwareUpdateCommandClass>
</entry>
<entry>
<commandClass>NO_OPERATION</commandClass>
<noOperationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</noOperationCommandClass>
</entry>
<entry>
<commandClass>MULTI_INSTANCE_ASSOCIATION</commandClass>
<multiAssociationCommandClass>
<version>3</version>
<instances>1</instances>
<versionSupported>3</versionSupported>
<maxGroups>5</maxGroups>
</multiAssociationCommandClass>
</entry>
<entry>
<commandClass>ALARM</commandClass>
<alarmCommandClass>
<version>5</version>
<instances>1</instances>
<versionSupported>5</versionSupported>
<alarms>
<entry>
<alarmType>ACCESS_CONTROL</alarmType>
<alarmState>
<alarmType>ACCESS_CONTROL</alarmType>
<reportedEvents>
<int>22</int>
<int>23</int>
</reportedEvents>
<outer-class reference="../../../.."/>
</alarmState>
</entry>
<entry>
<alarmType>BURGLAR</alarmType>
<alarmState>
<alarmType>BURGLAR</alarmType>
<reportedEvents>
<int>3</int>
</reportedEvents>
<outer-class reference="../../../.."/>
</alarmState>
</entry>
</alarms>
<v1Supported>true</v1Supported>
<isGetSupported>true</isGetSupported>
</alarmCommandClass>
</entry>
<entry>
<commandClass>SENSOR_BINARY</commandClass>
<binarySensorCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
<types/>
</binarySensorCommandClass>
</entry>
<entry>
<commandClass>CRC_16_ENCAP</commandClass>
<crc16EncapsulationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</crc16EncapsulationCommandClass>
</entry>
<entry>
<commandClass>SENSOR_ALARM</commandClass>
<alarmSensorCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<alarms>
<entry>
<alarmSensorType>GENERAL</alarmSensorType>
<alarmSensor>
<alarmType>GENERAL</alarmType>
</alarmSensor>
</entry>
</alarms>
<isGetSupported>true</isGetSupported>
<isSupportedGetSupported>true</isSupportedGetSupported>
</alarmSensorCommandClass>
</entry>
<entry>
<commandClass>SCENE_ACTIVATION</commandClass>
<sceneActivationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</sceneActivationCommandClass>
</entry>
<entry>
<commandClass>VERSION</commandClass>
<versionCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<libraryType>LIB_SLAVE_ENHANCED</libraryType>
<protocolVersion>4.5</protocolVersion>
<applicationVersion>3.2</applicationVersion>
<hardwareVersion>1</hardwareVersion>
</versionCommandClass>
</entry>
<entry>
<commandClass>ASSOCIATION_GROUP_INFO</commandClass>
<associationGroupInfoCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<autoSubscribeGroups>
<int>1</int>
<int>3</int>
<int>4</int>
<int>5</int>
</autoSubscribeGroups>
</associationGroupInfoCommandClass>
</entry>
<entry>
<commandClass>APPLICATION_STATUS</commandClass>
<ZWaveApplicationStatusClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</ZWaveApplicationStatusClass>
</entry>
<entry>
<commandClass>ZWAVE_PLUS_INFO</commandClass>
<zwavePlusCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<zwPlusVersion>1</zwPlusVersion>
<zwPlusRole>6</zwPlusRole>
<zwPlusNodeType>0</zwPlusNodeType>
<zwPlusDeviceType>0xc06</zwPlusDeviceType>
<zwPlusInstallerIcon>0xc06</zwPlusInstallerIcon>
<isGetSupported>true</isGetSupported>
</zwavePlusCommandClass>
</entry>
<entry>
<commandClass>BATTERY</commandClass>
<batteryCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<batteryLevel>100</batteryLevel>
<batteryLow>false</batteryLow>
<isGetSupported>true</isGetSupported>
</batteryCommandClass>
</entry>
<entry>
<commandClass>POWERLEVEL</commandClass>
<powerLevelCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<powerLevel>0</powerLevel>
<powerTimeout>0</powerTimeout>
</powerLevelCommandClass>
</entry>
<entry>
<commandClass>WAKE_UP</commandClass>
<WakeUpCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<targetNodeId>1</targetNodeId>
<interval>21600</interval>
<minInterval>3600</minInterval>
<maxInterval>64800</maxInterval>
<defaultInterval>21600</defaultInterval>
<intervalStep>1</intervalStep>
<lastWakeup>2017-01-21 12:49:19.322 UTC</lastWakeup>
<isGetSupported>true</isGetSupported>
</WakeUpCommandClass>
</entry>
<entry>
<commandClass>MULTI_INSTANCE</commandClass>
<multiInstanceCommandClass>
<version>0</version>
<instances>0</instances>
<versionSupported>0</versionSupported>
<endpoints/>
<useDestEndpointAsSource>false</useDestEndpointAsSource>
<endpointsAreTheSameDeviceClass>false</endpointsAreTheSameDeviceClass>
</multiInstanceCommandClass>
</entry>
<entry>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<manufacturerSpecificCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>271</deviceManufacturer>
<deviceType>1793</deviceType>
<deviceId>4097</deviceId>
</manufacturerSpecificCommandClass>
</entry>
<entry>
<commandClass>ASSOCIATION</commandClass>
<associationCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<maxGroups>5</maxGroups>
</associationCommandClass>
</entry>
</supportedCommandClasses>
<securedCommandClasses/>
<associationGroups>
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<name>Lifeline</name>
<profile1>0x0</profile1>
<profile2>0x1</profile2>
<commands>
<commandClass>ALARM</commandClass>
<commandClass>DEVICE_RESET_LOCALLY</commandClass>
<commandClass>BATTERY</commandClass>
</commands>
<associations>
<associationMember>
<node>1</node>
<endpoint>0</endpoint>
</associationMember>
</associations>
</associationGroup>
</entry>
<entry>
<int>2</int>
<associationGroup>
<index>2</index>
<name>Control</name>
<profile1>0x20</profile1>
<profile2>0x1</profile2>
<commands>
<commandClass>BASIC</commandClass>
</commands>
<associations/>
</associationGroup>
</entry>
<entry>
<int>3</int>
<associationGroup>
<index>3</index>
<name>Alarm</name>
<profile1>0x71</profile1>
<profile2>0x6</profile2>
<commands>
<commandClass>SENSOR_ALARM</commandClass>
</commands>
<associations/>
</associationGroup>
</entry>
<entry>
<int>4</int>
<associationGroup>
<index>4</index>
<name>Sensor ZW3</name>
<profile1>0x71</profile1>
<profile2>0x6</profile2>
<commands>
<commandClass>SENSOR_BINARY</commandClass>
</commands>
<associations/>
</associationGroup>
</entry>
<entry>
<int>5</int>
<associationGroup>
<index>5</index>
<name>Tamper ZW3</name>
<profile1>0x71</profile1>
<profile2>0x7</profile2>
<commands>
<commandClass>SENSOR_ALARM</commandClass>
</commands>
<associations/>
</associationGroup>
</entry>
</associationGroups>
<nodeNeighbors>
<int>1</int>
<int>4</int>
<int>8</int>
<int>15</int>
<int>16</int>
<int>18</int>
<int>19</int>
</nodeNeighbors>
<lastSent>2017-01-21 13:11:06.409 UTC</lastSent>
<lastReceived>2017-01-21 13:20:48.775 UTC</lastReceived>
</node>
I do notice that in the binding in the zwave device database for openhab there is some kind of message at the beginning of the data entry with the exact same wording as I get in my error from the logs.
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/381
At the very top there are a few messages about parameters and the last of thoese state âEndpoint 0 has no command class linked to the basic classâ.
I wonder if this is connected to my issue?
So it is the newer version.
Probably. I had a similar problem with another device, the database had to be updated and I had to reinitialize the device.
I would start with reinitializing: delete the thing (PaperUI or HABmin), delete the xml (save it somewhere), hit the + button for the zwave binding and start discovery again, then add the thing again and wake the sensor up several times.
If that does not help you definitely need a zwave debug log (type log:set DEBUG org.openhab.binding.zwave at karaf) and post it here so that chris can take a look at it.
Cheers sihui, Iâll follow your suggested steps then and see how things go.
One remark, I did a search to find out how to exclude in habmin and according to this post there is a button in habmin but I canât seem to find it. Do you know where in habmin itâs located?
https://groups.google.com/d/msg/openhab/9L_B5WzOyuI/lk2ZmuGJvhQJ
In my devices instruction it says that I should put the zwave controller in exclusion mode and then tripple klick the button on the device itself.
I found the button! It was located under anvanced settings after first marking the controller in the things list.
1 Like
You should not do that!
That removes the device from your controller. My suggestion above is delete the âThingâ, not exclude the device.
It is almost never required to exclude any devices from your controller.
To reinitialize it is enough to delete the thing and add it back. Then a new xml file is created and the newest settings from the database are applied.
But to answer your question: go to HABmin, select your controller in âThingsâ, go to Tools, switch to âShow advanced settingsâ and voila, the button âExlude devicesâ is present.
hehe okay I see. I actually did exclude it now. Not to worry though I guess. Iâll include it again see what happens. Check things and later come back to the delete option if the issue still persists.
Not really, it will create a new node number now âŠ
Iâve gone through the steps now in habmin and recorded the Debug logs in karaf during all of the steps.
- Deleted items connected to the thing
- Deleted the thing
- Deleted the XML file (and making a back-up)
- Re-included the thing in habmin
- Did multiple awakenings
- Tested function of the door sensor âsimulating open and close or the actual doorâ
- Added two items, the binary door switch and the door contact
- Did multiple awakenings
- Tested function of the door sensor âsimulating open and close or the actual doorâ
What I notice now after getting the device back into openhab is that now there is no XML file created for Node21. No XML file what so ever. Iâve refreshed the folder a couple of times (samba share) and I even went in with root access and looked.
The tests of opening and closing the door still give the same error as in the past. âEndpoint 0 not foundâ
I have the Logs so Iâll post them as well one by one. I devided them up for each type of activity I was doing for example deleting the old thing, and including the new thing etc.
Maybe they can give some more information. I do see some red parts here and there but it doesnât really tell me much.
Then the initialization process isnât finished yet: wake it up a couple of more times until it gets created.
Ah okay, then I will do that. 
I got the XML file created at last. It was actually created once I decided to delete everything again. I began deleting the items then it just popped into existence!
But alas still the same failed door sensing function.
The main errors I see is during inclusion and during open/close of door.
Error during inclusion:
17:22:24.220 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_12_2 len=3
17:22:24.220 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_12_2 - id = '12'
17:22:24.220 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_56_2
17:22:24.220 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_56_2 len=3
17:22:24.221 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_56_2 - id = '56'
17:22:24.221 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_53_4
17:22:24.221 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_53_4 len=3
17:22:24.221 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_53_4 - id = '53'
17:22:24.221 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_53_4 - size = '4'
17:22:24.222 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Size error 4<>2 from config_53_4
17:22:24.222 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_55_2
17:22:24.222 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_55_2 len=3
17:22:24.222 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_55_2 - id = '55'
17:22:24.222 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_13_2
17:22:24.223 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_13_2 len=3
17:22:24.223 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_13_2 - id = '13'
17:22:24.223 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_14_2
17:22:24.223 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Processing config_14_2 len=3
Error during open/close tests of door
17:27:55.655 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 04 00 15 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00 07
17:27:55.681 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
17:27:55.683 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 13 00 04 00 15 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00 07
17:27:55.685 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 13 00 04 00 15 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00 07
17:27:55.687 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 15 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00
17:27:55.687 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 21: Application Command Request (ALIVE:DONE)
17:27:55.688 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 21: Starting initialisation from DONE
17:27:55.688 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@10e2dd6 already registered
17:27:55.689 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 21: Incoming command class MULTI_INSTANCE
17:27:55.689 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 21: Received MULTI_INSTANCE command V0
17:27:55.690 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 21: Requested Command Class = ALARM (0x71)
17:27:55.690 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 21: Endpoint 0 not found. Cannot set command classes.
17:27:55.691 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=21, callback=183, payload=15 02 84 08
17:27:55.693 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 15 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00
17:27:55.694 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=183, expected=SendData, cancelled=false MISMATCH
17:28:07.819 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 04 00 15 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00 06
17:28:07.851 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
17:28:07.853 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 13 00 04 00 15 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00 06
17:28:07.855 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 13 00 04 00 15 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00 06
17:28:07.857 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 15 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00
17:28:07.858 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 21: Application Command Request (ALIVE:DONE)
17:28:07.858 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 21: Starting initialisation from DONE
17:28:07.858 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@10e2dd6 already registered
17:28:07.859 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 21: Incoming command class MULTI_INSTANCE
17:28:07.859 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 21: Received MULTI_INSTANCE command V0
17:28:07.860 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 21: Requested Command Class = ALARM (0x71)
17:28:07.860 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 21: Endpoint 0 not found. Cannot set command classes.
17:28:07.861 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=21, callback=183, payload=15 02 84 08
17:28:07.864 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 15 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00
17:28:07.864 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=183, expected=SendData, cancelled=false MISMATCH
But I also have the full logs of everything. Not sure if itâs all needed thourgh. What do you think?