Hi,
2017-09-15 21:20:17.446 [WARN ] [ssage.ApplicationCommandMessageClass] - NODE 10: Not initialized yet, ignoring message.
The thing (Popp Wireless Thermostatic Valve TRV - alias Danfoss) is properly initialized, reporting back temperature after 5min intervals. However, after reboot the message above appears. The device is not working till wake up by pressing button on it…
Any thoughts how to solve this issue? Using version 2.2.0 of the binding
chris
September 15, 2017, 8:01pm
2
It should sort itself out after it wakes up for the first time after the restart.
Not really … an example after restart… seems that Node is sending message (temperature) in set intervals but it’s being refused by controller …
2017-09-15 22:24:11.744 [WARN ] [ssage.ApplicationCommandMessageClass] - NODE 10: Not initialized yet, ignoring message.
After pressing button, node fixed after couple of minutes… log below. Thanks a lot for help with that.
2017-09-15 22:35:47.360 [hingStatusInfoChangedEvent] - ‘zwave:device:15e86de7967:node10’ changed from OFFLINE: Node not found in Z-Wave network to ONLINE: Node initialising: EMPTYNODE
chris
September 15, 2017, 9:15pm
5
Yep. As I said, the device needed to wake up to complete the initialisation after the binding was restarted. This is perfectly normal…
chris
September 15, 2017, 9:16pm
6
Just to clarify, the device had not woken up at this time. A notification is not the same as a wakeup message. A wakeup will occur every hour or so - or if you push the button on the device (as you found
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!
chris
September 15, 2017, 9:24pm
8
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>
chris
September 15, 2017, 10:32pm
11
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…
chris
September 16, 2017, 8:01am
13
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…
chris
September 16, 2017, 10:18am
15
Please enable debug logging - normal logging is of limited use when you want to work out what is happening.
nibi79
September 16, 2017, 5:23pm
16
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?
nibi79
September 16, 2017, 5:29pm
17
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 | ERROR
nibi79
September 16, 2017, 5:48pm
18
I 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:
chris
September 16, 2017, 5:53pm
19
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.
nibi79
September 16, 2017, 6:08pm
20
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?
).
