Ok, so if I understand correctly, even if I see this message, it should be fixed after an hour, correct? Will wait then and see… thanks a lot!
Yes… One point - it depends on the device wakeup setting. Normally, this is an hour, but you could have a different setting. The wakeup time is displayed in the device configuration…
Well then that’s 299 seconds… i.e. time when also temp value is send…(wake up configuration - wake up interval)…
This is xml of that node…
<node>
<deviceClass>
<basicDeviceClass>SLAVE</basicDeviceClass>
<genericDeviceClass>NOT_KNOWN</genericDeviceClass>
<specificDeviceClass>NOT_USED</specificDeviceClass>
</deviceClass>
<homeId>0xce62511b</homeId>
<nodeId>11</nodeId>
<version>1</version>
<manufacturer>0x2</manufacturer>
<deviceId>0xa010</deviceId>
<deviceType>0x115</deviceType>
<listening>false</listening>
<frequentlyListening>false</frequentlyListening>
<routing>false</routing>
<security>false</security>
<beaming>false</beaming>
<maxBaudRate>9600</maxBaudRate>
<nodeInformationFrame>
<commandClass>BATTERY</commandClass>
<commandClass>CLIMATE_CONTROL_SCHEDULE</commandClass>
<commandClass>CLOCK</commandClass>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<commandClass>MULTI_CMD</commandClass>
<commandClass>PROTECTION</commandClass>
<commandClass>SENSOR_MULTILEVEL</commandClass>
<commandClass>THERMOSTAT_SETPOINT</commandClass>
<commandClass>VERSION</commandClass>
<commandClass>WAKE_UP</commandClass>
</nodeInformationFrame>
<supportedCommandClasses>
<entry>
<commandClass>WAKE_UP</commandClass>
<WakeUpCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<targetNodeId>1</targetNodeId>
<interval>299</interval>
<minInterval>60</minInterval>
<maxInterval>1800</maxInterval>
<defaultInterval>300</defaultInterval>
<intervalStep>60</intervalStep>
<lastWakeup>2017-09-15 20:06:56.952 UTC</lastWakeup>
<isGetSupported>true</isGetSupported>
</WakeUpCommandClass>
</entry>
<entry>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<manufacturerSpecificCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>2</deviceManufacturer>
<deviceType>277</deviceType>
<deviceId>40976</deviceId>
</manufacturerSpecificCommandClass>
</entry>
<entry>
<commandClass>CLOCK</commandClass>
<clockCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</clockCommandClass>
</entry>
<entry>
<commandClass>THERMOSTAT_SETPOINT</commandClass>
<thermostatSetpointCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<setpoints>
<entry>
<setpointType>HEATING</setpointType>
<setpoint>
<setpointType>HEATING</setpointType>
<initialised>true</initialised>
<initCount>0</initCount>
<outer-class reference="../../../.."/>
</setpoint>
</entry>
</setpoints>
<isGetSupported>true</isGetSupported>
</thermostatSetpointCommandClass>
</entry>
<entry>
<commandClass>CLIMATE_CONTROL_SCHEDULE</commandClass>
<climateControlScheduleCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</climateControlScheduleCommandClass>
</entry>
<entry>
<commandClass>SENSOR_MULTILEVEL</commandClass>
<multiLevelSensorCommandClass>
<version>6</version>
<instances>1</instances>
<versionSupported>6</versionSupported>
<sensors>
<entry>
<multilevelSensorType>TEMPERATURE</multilevelSensorType>
<multilevelSensor>
<sensorType>TEMPERATURE</sensorType>
<initialised>true</initialised>
</multilevelSensor>
</entry>
</sensors>
<isGetSupported>true</isGetSupported>
</multiLevelSensorCommandClass>
</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>
</rfModes>
</protectionCommandClass>
</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>VERSION</commandClass>
<versionCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<libraryType>LIB_SLAVE_ROUTING</libraryType>
<protocolVersion>3.67</protocolVersion>
<applicationVersion>1.0</applicationVersion>
</versionCommandClass>
</entry>
<entry>
<commandClass>MULTI_CMD</commandClass>
<multiCommandCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</multiCommandCommandClass>
</entry>
</supportedCommandClasses>
<securedCommandClasses/>
<associationGroups/>
<nodeNeighbors/>
<lastSent>2017-09-15 20:06:57.955 UTC</lastSent>
<lastReceived>2017-09-15 20:06:58.42 UTC</lastReceived>
</node>
So it should initialise after 5 minutes.
Normally it’s unrelated to wakeup, but I don’t know the device so it might use the wakeup setting.
Unfortunately it’s not fixing automatically after some time… I’ve let it till morning and no change except for error on node saying that it’s not able to communicate with controller… If the button is pushed then it’s fixed immediately…
I guess the binding is working ok given it works when you press the button. I don’t really know the device so don’t know it’s wakeup strategy. What do the logs show?
Just this one… Device is rebranded Danfoss living…
Please enable debug logging - normal logging is of limited use when you want to work out what is happening.
so… I’ll try to enable debug logging by type the following command when I’m connected to karaf:
log:set debug org.openhab.binding.zwave
but log:get still shows only the following level:
Logger | Level
ROOT | WARN
What I’m doing wrong?
sorry forget it… log:list ist my friend
.
openhab> log:list
Logger | Level
-------------------------------------------------------------------
ROOT | WARN
javax.jmdns | ERROR
org.apache.aries.spifly | ERROR
org.apache.karaf.kar.internal.KarServiceImpl | ERROR
org.eclipse.smarthome | INFO
org.jupnp | ERROR
org.openhab | INFO
org.openhab.binding.zwave | DEBUG
org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper | ERROR
smarthome.event | INFO
smarthome.event.InboxUpdatedEvent | ERROR
smarthome.event.ItemAddedEvent | ERROR
smarthome.event.ItemRemovedEvent | ERROR
smarthome.event.ItemStateEvent | ERROR
smarthome.event.ThingStatusInfoEvent | ERRORI restart openhab at 7:40 pm, that’ what I found in the log for node 12, 14, 15:
2017-09-16 19:45:24.607 [WARN ] [ssage.ApplicationCommandMessageClass] - NODE 15: Not initialized yet, ignoring message.
2017-09-16 19:46:34.391 [WARN ] [ssage.ApplicationCommandMessageClass] - NODE 14: Not initialized yet, ignoring message.
and nothing for node 12.
Your Log Viewer shows the following when I filter node 14 and 15:
Please can you provide the log - or at least provide the image and click on the received messages that are in green so I can see what they are.
sorry stupid question…how can I provide the log? only jpg, jpeg, png, gif, ico, xml, json, pdf, svg, css are supported! rename the file to one of these extension or is their another way?
Yes - rename to XML or something. That will still only allow short files - the other alternative is to use dropbox or something.
Anyway, this image is probably ok - I can see what is be going on. It will need a binding update to resolve this as it seems to be a new feature of these devices.
ok sounds good to me! I understand that you don’t need my log anymore?
Please let me know if I can do something!
And apart from that let me say thank you for the great job you do!!!
In hind site, I’d quite like to see the log 
. Can you email it to me (chris -at- cd-jackson.com).
Thanks.
logs are on the way to you
Thanks.
Is there an XML file being created for this device? It would be in the {userdata}/zwave folder.
If not, can you click on the button a few times (say 4 or 5 times, each 5 or 10 seconds apart) so that I can see the device initialisation. I suspect that something else is going wrong somewhere…