Thank you for your fast help. It was defenetly working before
Creating new message for command SWITCH_MULTILEVEL_START_LEVEL_CHANGE
may you can explain which are the right commands for blinds_control
I still donāt understand why the device doesnāt report this class. I agree that it seems it should be implemented, but itās not reporting it from what I can see from the aboveā¦
Does your device show the same?
If needed here is a debug log while switching the rollershutter item to UP/STOP/DOWN:
https://gist.github.com/sihui62/8b8c4977018721b3e107ae5ffa5773dc
Does it show this class in the NIF in the XML file?
If you are asking me:
<node>
<deviceClass>
<basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
<genericDeviceClass>MULTILEVEL_SWITCH</genericDeviceClass>
<specificDeviceClass>MOTOR_CONTROL_CLASS_B</specificDeviceClass>
</deviceClass>
<homeId>0xc239030a</homeId>
<nodeId>33</nodeId>
<version>4</version>
<manufacturer>0x10f</manufacturer>
<deviceId>0x1000</deviceId>
<deviceType>0x302</deviceType>
<listening>true</listening>
<frequentlyListening>false</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<supportedCommandClasses>
<entry>
<commandClass>NO_OPERATION</commandClass>
<noOperationCommandClass>
<version>1</version>
<instances>0</instances>
<versionSupported>1</versionSupported>
</noOperationCommandClass>
</entry>
<entry>
<commandClass>ASSOCIATION</commandClass>
<associationCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<maxGroups>3</maxGroups>
</associationCommandClass>
</entry>
<entry>
<commandClass>SENSOR_MULTILEVEL</commandClass>
<multiLevelSensorCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<sensors>
<entry>
<multilevelSensorType>POWER</multilevelSensorType>
<multilevelSensor>
<sensorType>POWER</sensorType>
<initialised>true</initialised>
</multilevelSensor>
</entry>
</sensors>
<isGetSupported>true</isGetSupported>
</multiLevelSensorCommandClass>
</entry>
<entry>
<commandClass>CONTROLLER_REPLICATION</commandClass>
<controllerReplicationCommandClass>
<version>0</version>
<instances>0</instances>
<versionSupported>0</versionSupported>
</controllerReplicationCommandClass>
</entry>
<entry>
<commandClass>SWITCH_MULTILEVEL</commandClass>
<multiLevelSwitchCommandClass>
<version>3</version>
<instances>1</instances>
<versionSupported>3</versionSupported>
<switchTypePrimary>CLOSE_OPEN</switchTypePrimary>
<switchTypeSecondary>CLOSE_OPEN</switchTypeSecondary>
<isGetSupported>true</isGetSupported>
</multiLevelSwitchCommandClass>
</entry>
<entry>
<commandClass>PROTECTION</commandClass>
<protectionCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<localModes>
<localProtection>UNPROTECTED</localProtection>
<localProtection>PROTECTED</localProtection>
</localModes>
<rfModes>
<rfProtection>UNPROTECTED</rfProtection>
<rfProtection>NORFCONTROL</rfProtection>
</rfModes>
</protectionCommandClass>
</entry>
<entry>
<commandClass>METER</commandClass>
<meterCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<meterType>ELECTRIC</meterType>
<meterScales>
<meterScale>E_KWh</meterScale>
<meterScale>E_W</meterScale>
</meterScales>
<canReset>true</canReset>
<isGetSupported>true</isGetSupported>
<isSupportRequestSupported>true</isSupportRequestSupported>
</meterCommandClass>
</entry>
<entry>
<commandClass>BASIC</commandClass>
<basicCommandClass>
<version>0</version>
<instances>0</instances>
<versionSupported>0</versionSupported>
<isGetSupported>true</isGetSupported>
</basicCommandClass>
</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>SWITCH_BINARY</commandClass>
<binarySwitchCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</binarySwitchCommandClass>
</entry>
<entry>
<commandClass>MULTI_INSTANCE_ASSOCIATION</commandClass>
<multiAssociationCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<maxGroups>2</maxGroups>
</multiAssociationCommandClass>
</entry>
<entry>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<manufacturerSpecificCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>271</deviceManufacturer>
<deviceType>770</deviceType>
<deviceId>4096</deviceId>
</manufacturerSpecificCommandClass>
</entry>
<entry>
<commandClass>VERSION</commandClass>
<versionCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<libraryType>LIB_SLAVE_ENHANCED</libraryType>
<protocolVersion>3.52</protocolVersion>
<applicationVersion>25.25</applicationVersion>
</versionCommandClass>
</entry>
<entry>
<commandClass>SCENE_ACTIVATION</commandClass>
<sceneActivationCommandClass>
<version>0</version>
<instances>0</instances>
<versionSupported>0</versionSupported>
</sceneActivationCommandClass>
</entry>
<entry>
<commandClass>CONFIGURATION</commandClass>
<configurationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<configParameters>
<entry>
<int>32</int>
<configurationParameter>
<index>32</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>33</int>
<configurationParameter>
<index>33</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>3</int>
<configurationParameter>
<index>3</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>35</int>
<configurationParameter>
<index>35</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>40</int>
<configurationParameter>
<index>40</index>
<size>1</size>
<value>10</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>10</int>
<configurationParameter>
<index>10</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>42</int>
<configurationParameter>
<index>42</index>
<size>2</size>
<value>3600</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>43</int>
<configurationParameter>
<index>43</index>
<size>1</size>
<value>10</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>12</int>
<configurationParameter>
<index>12</index>
<size>2</size>
<value>150</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>44</int>
<configurationParameter>
<index>44</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>13</int>
<configurationParameter>
<index>13</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>14</int>
<configurationParameter>
<index>14</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>17</int>
<configurationParameter>
<index>17</index>
<size>1</size>
<value>10</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>18</int>
<configurationParameter>
<index>18</index>
<size>1</size>
<value>10</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>50</int>
<configurationParameter>
<index>50</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>22</int>
<configurationParameter>
<index>22</index>
<size>2</size>
<value>240</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>29</int>
<configurationParameter>
<index>29</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>30</int>
<configurationParameter>
<index>30</index>
<size>1</size>
<value>2</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
<entry>
<int>31</int>
<configurationParameter>
<index>31</index>
<size>1</size>
<value>0</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
</configParameters>
</configurationCommandClass>
</entry>
</supportedCommandClasses>
<securedCommandClasses/>
<associationGroups>
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<associations/>
</associationGroup>
</entry>
<entry>
<int>2</int>
<associationGroup>
<index>2</index>
<associations/>
</associationGroup>
</entry>
<entry>
<int>3</int>
<associationGroup>
<index>3</index>
<associations/>
</associationGroup>
</entry>
</associationGroups>
<nodeNeighbors>
<int>1</int>
<int>4</int>
<int>10</int>
<int>11</int>
<int>12</int>
<int>13</int>
<int>23</int>
</nodeNeighbors>
<lastSent>2017-06-11 06:36:38.147 UTC</lastSent>
<lastReceived>2017-06-11 06:36:38.191 UTC</lastReceived>
</node>
Looks like we are on different firmware versions, may be difficult to compare then:
mine:
<applicationVersion>25.25</applicationVersion>
But it was working until the last change. Hope soon both commands will work like before on 1.8 / 1.9
Well, Iām not sure how to fix that as the binding hasnāt changed with respect to this command class 
. Currently it looks like the device didnāt report the command class, so the binding wonāt support it if the binding doesnāt reportā¦
Maybe it would help to ex-/include the device to get a new node.xml? In the node.xml of sihui there is a SWITCH_MULTILEVEL command
You could try just deleting the XML and restarting, or click on the āreinitialise deviceā option. Iām just a bit surprised as the class doesnāt seem to be in the NIF even, and thatās unlikely to change by reinitialising.
Hello @chris
I have now checked some details. First of all in my old node.xml (before updating anything) the SWITCH_MULTILEVEL entry was there. Like on the node.xml of sihui.
If I have a look in the ESH-INF declartion it says:
<channel id="blinds_control" typeId="blinds_control">
<label>Blinds control</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:Command:StopMoveType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:Command:UpDownType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
But after updating to the latest version the entry for SWITCH_MULTILEVEL is no longer in the node.xml and therefore it is not working. Is it not possible to āfakeā this entry or it seems, that there is a problem initialisiing it cause it worked before and the entry was there. And even more it works before, so the device definitely supports this command.
Iām not sure what your point is? The database information is not directly related to what the device supports.[quote=āRobZe89, post:111, topic:9396ā]
But after updating to the latest version the entry for SWITCH_MULTILEVEL is no longer in the node.xml
[/quote]
The node.xml is not related to the database. The node.xml comes from what the device states it supports - not the other way around.
Yes - we can force it by adding an option to the database, but Iām not sure why it was previously there, and now itās not.
Whatās strange is that itās not listed in the NIF. This is where the device tells us what command classes it supports - the device should be totally self descriptive so the fact that itās not showing this is strange. Maybe Iāve screwed up somewhere and dropped the multilevel switch out of the list of command classes in the binding (although then no-ones dimmers would work, so I doubt that).
Can you provide a logfile during initialisation of the device (delete the XML first).
Thank you for your explanation. I see the problem now.
Here you find a log of the initialisation. Hope this helps you.
2017-06-13 09:16:33.472 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:78d06d54:node10.
2017-06-13 09:16:33.510 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Controller status changed to ONLINE.
2017-06-13 09:16:33.511 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Controller is ONLINE. Starting device initialisation.
2017-06-13 09:16:33.515 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating node properties.
2017-06-13 09:16:33.516 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating node properties. MAN=271
2017-06-13 09:16:33.517 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating node properties. MAN=271. SET. Was 271
2017-06-13 09:16:33.519 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Properties synchronised
2017-06-13 09:16:33.527 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Update ASSOCIATION group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@1eb1c9d: Adding node_1_0
2017-06-13 09:16:33.529 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Configuration synchronised
2017-06-13 09:16:33.611 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
2017-06-13 09:16:33.612 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising Thing Node...
2017-06-13 09:16:33.614 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:switch_binary for OnOffType
2017-06-13 09:16:33.615 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:switch_binary for OnOffType
2017-06-13 09:16:33.618 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:blinds_control for UpDownType
2017-06-13 09:16:33.623 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:blinds_control for StopMoveType
2017-06-13 09:16:33.629 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:blinds_control for PercentType
2017-06-13 09:16:33.637 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:blinds_control for PercentType
2017-06-13 09:16:33.642 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:scene_number for DecimalType
2017-06-13 09:16:33.645 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:scene_number for DecimalType
2017-06-13 09:16:33.650 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:sensor_power for DecimalType
2017-06-13 09:16:33.653 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:sensor_power for DecimalType
2017-06-13 09:16:33.657 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:meter_watts for DecimalType
2017-06-13 09:16:33.661 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:meter_watts for DecimalType
2017-06-13 09:16:33.665 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:meter_kwh for DecimalType
2017-06-13 09:16:33.669 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:meter_kwh for DecimalType
2017-06-13 09:16:33.673 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:blinds_lamella for PercentType
2017-06-13 09:16:33.677 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:blinds_lamella for PercentType
2017-06-13 09:16:33.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:blinds_shutter for PercentType
2017-06-13 09:16:33.685 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:blinds_shutter for PercentType
2017-06-13 09:16:33.689 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Polling intialised at 1800 seconds - start in 1800000 milliseconds.
2017-06-13 09:16:33.692 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Device initialisation complete.
So you can add this to the database? Would be great to come to an end and have a working solution. If you can make it work soon I will do of course a donation for your work. Iām sure there are other people in this thread who will do too.
If possible I would like to understand what is happening first.
Can I ask you to try 2 things.
Iād like to get a log of the device initialisation, and Iād like to see what happens if you manually adjust the blindsā¦
So, can you try the followingā¦
Stop the binding, delete the XML, and restart. Wait till the device is initialised, then manually change the blinds. I assume when the blinds change it will send an update to the binding (is that true?) and itās possible that this will then add the multilevel switch class.
Iād like to specifically look at what the device sends in the NIF, and also see what happens when this manual move is doneā¦
@sihui can you also try this on the master version that I think you are using?
What a pitty, I migrated to the development binding this morning 
(btw, without any major problems).
But because I am on a manual install I can easily revert back to yesterdays version, will do that tomorrow and report ā¦
Ok, no worries. If you get the chance it would be interesting, if not then the dev branch will be fine.
Thanks.
Hello Chris
Sure we can have a look at it. Here youāll find the data. I hope I got the right data, Iāve cutted out some other nodes.
2017-06-14 20:53:09.626 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:78d06d54:node10.
2017-06-14 20:53:09.632 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Controller status changed to ONLINE.
2017-06-14 20:53:09.634 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Controller is ONLINE. Starting device initialisation.
2017-06-14 20:53:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating node properties.
2017-06-14 20:53:09.640 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating node properties. MAN=271
2017-06-14 20:53:09.643 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating node properties. MAN=271. SET. Was 271
2017-06-14 20:53:09.648 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Properties synchronised
2017-06-14 20:53:09.653 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Update ASSOCIATION group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@70d1b1: Adding node_1_0
2017-06-14 20:53:09.657 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Configuration synchronised
2017-06-14 20:53:09.734 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
2017-06-14 20:53:09.735 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising Thing Node...
2017-06-14 20:53:09.737 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:switch_binary for OnOffType
2017-06-14 20:53:09.739 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:switch_binary for OnOffType
2017-06-14 20:53:09.741 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:blinds_control for UpDownType
2017-06-14 20:53:09.745 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:blinds_control for StopMoveType
2017-06-14 20:53:09.748 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:blinds_control for PercentType
2017-06-14 20:53:09.751 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:blinds_control for PercentType
2017-06-14 20:53:09.755 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:scene_number for DecimalType
2017-06-14 20:53:09.758 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:scene_number for DecimalType
2017-06-14 20:53:09.761 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:sensor_power for DecimalType
2017-06-14 20:53:09.764 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:sensor_power for DecimalType
2017-06-14 20:53:09.768 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:meter_watts for DecimalType
2017-06-14 20:53:09.771 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:meter_watts for DecimalType
2017-06-14 20:53:09.774 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:meter_kwh for DecimalType
2017-06-14 20:53:09.777 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:meter_kwh for DecimalType
2017-06-14 20:53:09.780 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:blinds_lamella for PercentType
2017-06-14 20:53:09.783 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:blinds_lamella for PercentType
2017-06-14 20:53:09.786 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising cmd channel zwave:device:78d06d54:node10:blinds_shutter for PercentType
2017-06-14 20:53:09.787 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising state channel zwave:device:78d06d54:node10:blinds_shutter for PercentType
2017-06-14 20:53:09.790 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Polling intialised at 1800 seconds - start in 1800000 milliseconds.
2017-06-14 20:53:09.793 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Device initialisation complete.
2017-06-14 20:54:03.544 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Wed Jun 14 20:54:07 CEST 2017 - 3644ms
2017-06-14 20:54:05.136 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 00 0A 08 91 01 0F 26 03 03 4D 2F 2C
2017-06-14 20:54:05.169 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2017-06-14 20:54:05.174 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage inputMessage: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=10, callback=0, payload=00 0A 08 91 01 0F 26 03 03 4D 2F
2017-06-14 20:54:05.179 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lockMessage: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=10, callback=0, payload=00 0A 08 91 01 0F 26 03 03 4D 2F
2017-06-14 20:54:05.184 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=10, callback=0, payload=00 0A 08 91 01 0F 26 03 03 4D 2F
2017-06-14 20:54:05.185 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-06-14 20:54:05.186 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Application Command Request (ALIVE:GET_CONFIGURATION)
2017-06-14 20:54:05.187 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Incoming command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY, endpoint 0
2017-06-14 20:54:05.188 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY not found, trying to add it.
2017-06-14 20:54:05.190 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Unknown command class 0x91
2017-06-14 20:54:05.191 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Unsupported zwave command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY (0x91)
2017-06-14 20:54:05.192 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Commands processed 1.
2017-06-14 20:54:05.192 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1738266.
2017-06-14 20:54:05.193 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction 253 ApplicationCommandHandler.
2017-06-14 20:54:05.194 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : state >> WAIT_DATA
2017-06-14 20:54:05.195 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : node >> 10
2017-06-14 20:54:05.195 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : class >> 145 == 112.
2017-06-14 20:54:05.196 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : commd >> 1 == 6.
2017-06-14 20:54:05.197 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Command NOT verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1738266.
2017-06-14 20:54:05.197 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2017-06-14 20:54:05.198 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2017-06-14 20:54:05.199 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2017-06-14 20:54:05.199 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start
2017-06-14 20:54:05.200 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing
2017-06-14 20:54:05.201 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2017-06-14 20:54:05.276 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Wed Jun 14 20:54:07 CEST 2017 - 1912ms
2017-06-14 20:54:06.288 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 0A 06 31 05 04 22 03 3C D6
2017-06-14 20:54:06.319 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2017-06-14 20:54:06.323 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage inputMessage: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=10, callback=0, payload=00 0A 06 31 05 04 22 03 3C
2017-06-14 20:54:06.326 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lockMessage: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=10, callback=0, payload=00 0A 06 31 05 04 22 03 3C
2017-06-14 20:54:06.329 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=10, callback=0, payload=00 0A 06 31 05 04 22 03 3C
2017-06-14 20:54:06.330 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-06-14 20:54:06.331 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Application Command Request (ALIVE:GET_CONFIGURATION)
2017-06-14 20:54:06.332 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2017-06-14 20:54:06.333 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: SECURITY not supported
2017-06-14 20:54:06.334 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Received COMMAND_CLASS_SENSOR_MULTILEVEL V2 SENSOR_MULTILEVEL_REPORT
2017-06-14 20:54:06.335 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 10: Sensor Type = Power(4), Scale = 0
2017-06-14 20:54:06.336 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 10: Sensor Value = 82.8
2017-06-14 20:54:06.336 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2017-06-14 20:54:06.337 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2017-06-14 20:54:06.338 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 82.8
2017-06-14 20:54:06.339 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating channel state zwave:device:78d06d54:node10:sensor_power to 82.8 [DecimalType]
2017-06-14 20:54:06.341 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Commands processed 1.
2017-06-14 20:54:06.342 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@a0660a.
2017-06-14 20:54:06.343 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction 253 ApplicationCommandHandler.
2017-06-14 20:54:06.343 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : state >> WAIT_DATA
2017-06-14 20:54:06.344 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : node >> 10
2017-06-14 20:54:06.344 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : class >> 49 == 112.
2017-06-14 20:54:06.345 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : commd >> 5 == 6.
2017-06-14 20:54:06.346 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Command NOT verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@a0660a.
2017-06-14 20:54:06.346 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2017-06-14 20:54:06.347 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2017-06-14 20:54:06.348 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2017-06-14 20:54:06.348 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start
2017-06-14 20:54:06.349 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing
2017-06-14 20:54:06.350 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
2017-06-14 20:54:11.985 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Wed Jun 14 20:54:14 CEST 2017 - 2544ms
2017-06-14 20:54:12.020 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 0A 06 31 05 04 22 00 00 E9
2017-06-14 20:54:12.049 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2017-06-14 20:54:12.053 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage inputMessage: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=10, callback=0, payload=00 0A 06 31 05 04 22 00 00
2017-06-14 20:54:12.055 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lockMessage: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=10, callback=0, payload=00 0A 06 31 05 04 22 00 00
2017-06-14 20:54:12.057 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=10, callback=0, payload=00 0A 06 31 05 04 22 00 00
2017-06-14 20:54:12.058 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-06-14 20:54:12.059 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Application Command Request (ALIVE:GET_CONFIGURATION)
2017-06-14 20:54:12.060 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2017-06-14 20:54:12.061 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: SECURITY not supported
2017-06-14 20:54:12.062 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Received COMMAND_CLASS_SENSOR_MULTILEVEL V2 SENSOR_MULTILEVEL_REPORT
2017-06-14 20:54:12.070 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 10: Sensor Type = Power(4), Scale = 0
2017-06-14 20:54:12.071 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 10: Sensor Value = 0E+1
2017-06-14 20:54:12.072 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2017-06-14 20:54:12.073 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2017-06-14 20:54:12.075 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 0E+1
2017-06-14 20:54:12.077 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating channel state zwave:device:78d06d54:node10:sensor_power to 0 [DecimalType]
2017-06-14 20:54:12.079 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Commands processed 1.
2017-06-14 20:54:12.080 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@b21b56.
2017-06-14 20:54:12.090 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction 254 ApplicationCommandHandler.
2017-06-14 20:54:12.103 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : state >> WAIT_DATA
2017-06-14 20:54:12.109 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : node >> 10
2017-06-14 20:54:12.114 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : class >> 49 == 112.
2017-06-14 20:54:12.118 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking transaction : commd >> 5 == 6.
2017-06-14 20:54:12.121 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Command NOT verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@b21b56.
2017-06-14 20:54:12.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2017-06-14 20:54:12.126 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2017-06-14 20:54:12.127 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2017-06-14 20:54:12.127 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start
2017-06-14 20:54:12.128 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing
2017-06-14 20:54:12.128 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer
Little delay, no time today, sonās car broke down, will provide the results tomorrow.
Thatās fine, thanks - Iām tied up with a work thin today anyway - customers in the building so gotta take 'em out for dinner!