Aeotec Labs USB Z-Stick Gen5 and Aeotec Multi-Sensor 4 [Solved]

Highly recommend you set up a separate zwave.log in your logback.xml (or logback_debug.xml) to run at DEBUG level. That will tell you what your controller sees at which z-node and ports within it (if needed).

see here logback config

Thanks bob, that helps!

My zwave log is showing the below. What does the last line mean? Does it mean it cannot find my controller or there is no device paired to my controller? As a quick background, I am using windows 7 and already installed in AEOTEC stick driver and it is associated to COM4 and pretty sure I paired it correctly already.

2015-10-15 09:10:35.237 DEBUG o.o.b.z.i.ZWaveActivator[:36]- Z-Wave binding started. Version 1.7.1
2015-10-15 09:10:35.267 DEBUG o.o.b.z.i.ZWaveActiveBinding[:175]- ConverterHandler not initialised. Polling disabled.
2015-10-15 09:10:35.363 DEBUG o.o.b.z.i.ZWaveActivator[:36]- Z-Wave binding started. Version 1.8.0.201508211938
2015-10-15 09:10:35.386 DEBUG o.o.b.z.i.ZWaveActiveBinding[:175]- ConverterHandler not initialised. Polling disabled.

Which version of zwave and openHAB are you using?
Looks like your zwave binding jar is not good. I say this because in the past when i eported the plugin from source, I forgot to check “use classe files from project” and the ant task failed with compiling ConverterHandler class. As such some class files were not exported in the jar and i go the same error as yours.

You have two different z-wave binding jars in that log…a 1.7.1 and a 1.8.0.z pointbuild. Check your openhab/addons directory and get rid of one of those jars.

Thanks! I got rid of the 1.8.0.z that I copied over when I installed in hadmin.

Now there is alot more lines in the log. The last line reading “No nodes to ping”. Does this mean that maybe I don’t have my Aeon multi-sensor 4 paired correctly to my Aeon Labs USB Z-Stick?

2015-10-16 08:24:08.455 DEBUG o.o.b.z.i.p.ZWaveController[:190]- Message: class = IsFailedNodeID (0x62), type = Response (0x01), payload = 00 
2015-10-16 08:24:08.455 DEBUG o.o.b.z.i.p.s.IsFailedNodeMessageClass[:54]- NODE 2: Is currently marked as healthy by the controller
2015-10-16 08:24:08.455 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:63]- Sent message Message: class = IsFailedNodeID (0x62), type = Request (0x00), payload = 02 
2015-10-16 08:24:08.456 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:64]- Recv message Message: class = IsFailedNodeID (0x62), type = Response (0x01), payload = 00 
2015-10-16 08:24:08.456 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:65]- Checking transaction complete: class=IsFailedNodeID, expected=IsFailedNodeID, cancelled=false
2015-10-16 08:24:08.456 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:68]-          transaction complete!
2015-10-16 08:24:08.456 DEBUG o.o.b.z.i.p.ZWaveController[:682]- Notifying event listeners: ZWaveTransactionCompletedEvent
2015-10-16 08:24:08.456 DEBUG o.o.b.z.i.ZWaveActiveBinding[:433]- ZwaveIncomingEvent
2015-10-16 08:24:08.456 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:1005]- NODE 2: Node advancer - FAILED_CHECK: Transaction complete (IsFailedNodeID:Request) success(true)
2015-10-16 08:24:08.456 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:201]- NODE 2: Node advancer - checking initialisation queue. Queue size 1.
2015-10-16 08:24:08.457 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:207]- NODE 2: Node advancer - message removed from queue. Queue size 0.
2015-10-16 08:24:08.457 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:267]- NODE 2: Node advancer - FAILED_CHECK: queue length(0), free to send(true)
2015-10-16 08:24:08.457 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 2: Node advancer: loop - FAILED_CHECK try 1: stageAdvanced(false)
2015-10-16 08:24:08.457 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:860]- NODE 2: Node advancer - advancing to WAIT
2015-10-16 08:24:08.457 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 2: Node advancer: loop - WAIT try 0: stageAdvanced(true)
2015-10-16 08:24:08.457 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:380]- NODE 2: Node advancer: WAIT - Listening=false, FrequentlyListening=false
2015-10-16 08:24:08.458 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:398]- NODE 2: Node advancer: WAIT - Still waiting!
2015-10-16 08:24:08.458 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1374]- NODE 255: Response processed after 5ms/110ms.
2015-10-16 08:25:39.012 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:353]- Network Monitor: No nodes to ping!

Now it appears that binding worked. Node 2 is showing my multi-sensor in habmin, but when I open my app to view the sensor details, it is not showing me the temp still but seems like battery is working fine. I had followed this thread to setup the item parameters. Please note I already tried deleting zwave.xml to solve the get request error per another post I read but that didn’t help in my case.

See below for logs.

2015-10-16 10:27:20.487 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:780]- NODE 2: Found 1 instances of SENSOR_MULTILEVEL
2015-10-16 10:27:20.487 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:309]- ============ Requesting TEMPERATURE!
2015-10-16 10:27:20.487 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:247]- NODE 2: Node doesn't support get requests for MULTI_LEVEL_SENSOR
2015-10-16 10:27:20.487 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:309]- ============ Requesting LUMINANCE!
2015-10-16 10:27:20.487 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:247]- NODE 2: Node doesn't support get requests for MULTI_LEVEL_SENSOR
2015-10-16 10:27:20.487 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:309]- ============ Requesting RELATIVE_HUMIDITY!
2015-10-16 10:27:20.487 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:247]- NODE 2: Node doesn't support get requests for MULTI_LEVEL_SENSOR
2015-10-16 10:27:20.487 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking BATTERY
2015-10-16 10:27:20.487 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:776]- NODE 2: Node advancer: DYNAMIC_VALUES - found    BATTERY
2015-10-16 10:27:20.488 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:780]- NODE 2: Found 1 instances of BATTERY
2015-10-16 10:27:20.488 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:808]- NODE 2: Node advancer: DYNAMIC_VALUES - queued 0 frames
2015-10-16 10:27:20.488 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:860]- NODE 2: Node advancer - advancing to DONE
2015-10-16 10:27:20.488 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 2: Node advancer: loop - DONE try 0: stageAdvanced(true)
2015-10-16 10:27:20.488 DEBUG o.o.b.z.i.p.i.ZWaveNodeSerializer[:107]- NODE 2: Serializing to file etc\zwave\node2.xml
2015-10-16 10:27:20.498 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:819]- NODE 2: Node advancer: Initialisation complete!
2015-10-16 10:27:20.499 DEBUG o.o.b.z.i.p.ZWaveController[:682]- Notifying event listeners: ZWaveInitializationCompletedEvent
2015-10-16 10:27:20.499 DEBUG o.o.b.z.i.ZWaveActiveBinding[:425]- NODE 2: ZWaveIncomingEvent Called, Network Event, Init Done. Setting device ready.
2015-10-16 10:27:20.499 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:730]- Network initialised - starting network monitor.
2015-10-16 10:27:20.505 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1374]- NODE 2: Response processed after 1823ms/2723ms.
2015-10-16 10:27:21.499 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:506]- NODE 2: No more messages, go back to sleep
2015-10-16 10:27:21.499 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:202]- NODE 2: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2015-10-16 10:27:21.499 DEBUG o.o.b.z.i.p.SerialMessage[:109]- NODE 2: Creating empty message of class = SendData (0x13), type = Request (0x00)
2015-10-16 10:27:21.499 DEBUG o.o.b.z.i.p.ZWaveController[:985]- Callback ID = 33
2015-10-16 10:27:21.499 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 0
2015-10-16 10:27:21.500 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 0
2015-10-16 10:27:21.500 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 09 00 13 02 02 84 08 25 21 6D 
2015-10-16 10:27:21.500 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 2: Sending REQUEST Message = 01 09 00 13 02 02 84 08 25 21 6D 
2015-10-16 10:27:21.507 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1528]- Receive Message = 01 04 01 13 01 E8 
2015-10-16 10:27:21.508 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1452]- Receive queue ADD: Length=1
2015-10-16 10:27:21.508 DEBUG o.o.b.z.i.p.ZWaveController[:1210]- Receive queue TAKE: Length=0
2015-10-16 10:27:21.508 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 04 01 13 01 E8 
2015-10-16 10:27:21.508 DEBUG o.o.b.z.i.p.ZWaveController[:1211]- Process Message = 01 04 01 13 01 E8 
2015-10-16 10:27:21.509 DEBUG o.o.b.z.i.p.ZWaveController[:190]- Message: class = SendData (0x13), type = Response (0x01), payload = 01 
2015-10-16 10:27:21.509 DEBUG o.o.b.z.i.p.s.SendDataMessageClass[:38]- NODE 2: Sent Data successfully placed on stack.
2015-10-16 10:27:21.524 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1528]- Receive Message = 01 07 00 13 21 00 00 03 C9 
2015-10-16 10:27:21.525 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1452]- Receive queue ADD: Length=1
2015-10-16 10:27:21.525 DEBUG o.o.b.z.i.p.ZWaveController[:1210]- Receive queue TAKE: Length=0
2015-10-16 10:27:21.525 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 09 00 13 21 00 00 03 00 00 C7 
2015-10-16 10:27:21.525 DEBUG o.o.b.z.i.p.ZWaveController[:1211]- Process Message = 01 09 00 13 21 00 00 03 00 00 C7 
2015-10-16 10:27:21.525 DEBUG o.o.b.z.i.p.ZWaveController[:190]- Message: class = SendData (0x13), type = Request (0x00), payload = 21 00 00 03 
2015-10-16 10:27:21.525 DEBUG o.o.b.z.i.p.s.SendDataMessageClass[:74]- NODE 2: SendData Request. CallBack ID = 33, Status = Transmission complete and ACK received(0)
2015-10-16 10:27:21.526 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:63]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 02 02 84 08 
2015-10-16 10:27:21.526 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:64]- Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 21 00 00 03 
2015-10-16 10:27:21.526 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:65]- Checking transaction complete: class=SendData, expected=SendData, cancelled=false
2015-10-16 10:27:21.526 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:68]-          transaction complete!
2015-10-16 10:27:21.526 DEBUG o.o.b.z.i.p.ZWaveController[:682]- Notifying event listeners: ZWaveTransactionCompletedEvent
2015-10-16 10:27:21.526 DEBUG o.o.b.z.i.ZWaveActiveBinding[:433]- ZwaveIncomingEvent
2015-10-16 10:27:21.526 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:372]- NODE 2: Went to sleep
2015-10-16 10:27:21.526 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:435]- NODE 2: Is sleeping
2015-10-16 10:27:21.526 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:372]- NODE 2: Went to sleep
2015-10-16 10:27:21.526 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:435]- NODE 2: Is sleeping
2015-10-16 10:27:21.527 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1374]- NODE 2: Response processed after 27ms/2723ms.
2015-10-16 10:28:51.319 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:353]- Network Monitor: No nodes to ping!
2015-10-16 10:30:21.324 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:353]- Network Monitor: No nodes to ping!

The logs look fine - I don’t see any errors or problems? Have you configured the device to send the temperature?

Yes, I believe so. Here’s what I have in item and sitemap-

From .ITEM

Number Multi1_temp “office - Multi Temperature [%.1f °F]” (multi,multiGraph) {zwave=“2:command=SENSOR_MULTILEVEL,sensor_type=1”}
Number Multi1_humidity “office - Multi Humidity [%.0f %%]” (multi,multiGraph) {zwave=“2:command=SENSOR_MULTILEVEL,sensor_type=5”}
Number Multi1_luminance “office - Multi Luminance [%.0f Lux]” (multi) {zwave=“2:command=SENSOR_MULTILEVEL,sensor_type=3”}
Contact Multi1_motion “office - Multi motion [MAP(motion.map):%s]” (multi,motion) {zwave=“2:command=SENSOR_BINARY,respond_to_basic=true”}
Number Multi1_battery “office - Multi battery [%d %%]” (multi,battery) {zwave=“2:command=BATTERY”}

From Sitemap

Frame label=“My First Sensor” {
Text item=Multi1_humidity
Text item=Multi1_temp
Text item=ulti1_luminance
Text item=Multi1_motion
Text item=Multi1_battery
}

Yes, but have you configured the device itself? You need to set the device configuration correctly or it won’t send the temperature etc. Has this been done?

From memory it’s parameters around 100 to 102, but you should check the manual.

Continuing the discussion from Aeon Labs USB Z-Stick Gen5 and Aeon Multi-Sensor 4:

yes, I’ve set it to the following based on other people’s setup for this sensor. See below. Double-checking the manual, it also said to associate to group one… which I assume is 101.

101: Which reports to send automatically in timing to group 1: 225
102: group 2: 0
103: group 3: 0
111: Interval to send out reports to group 1: 240 (also personal preference for testing battery life)
112: Interval to send out reports to group 2: 720
113: Interval to send out reports to group 3: 720

It must be working then :smile:

Are you sure the configuration is being sent to the device? Can you post the XML file (etc/zwave/node2.xml).

I guess the next step is getting the logfiles to see if something is being received.

Yes, you are right that it was working… but only in my dreams…:frowning: maybe today I may be lucky enough to make it a reality. :smile:

Attached is node2.xml Looking at node2.xml, it seems that the configuration is matching?

here’s the last part of my zwave log file-

2015-10-16 14:12:21.182 DEBUG o.o.b.z.i.ZWaveActiveBinding[:433]- ZwaveIncomingEvent
2015-10-16 14:12:21.182 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:1005]- NODE 2: Node advancer - DYNAMIC_VALUES: Transaction complete (SendData:Request) success(true)
2015-10-16 14:12:21.182 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:201]- NODE 2: Node advancer - checking initialisation queue. Queue size 1.
2015-10-16 14:12:21.183 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:207]- NODE 2: Node advancer - message removed from queue. Queue size 0.
2015-10-16 14:12:21.183 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:267]- NODE 2: Node advancer - DYNAMIC_VALUES: queue length(0), free to send(true)
2015-10-16 14:12:21.183 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 2: Node advancer: loop - DYNAMIC_VALUES try 1: stageAdvanced(false)
2015-10-16 14:12:21.183 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking BASIC
2015-10-16 14:12:21.183 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking MANUFACTURER_SPECIFIC
2015-10-16 14:12:21.183 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking ASSOCIATION
2015-10-16 14:12:21.184 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking CONFIGURATION
2015-10-16 14:12:21.184 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking BATTERY
2015-10-16 14:12:21.184 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:776]- NODE 2: Node advancer: DYNAMIC_VALUES - found    BATTERY
2015-10-16 14:12:21.184 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:780]- NODE 2: Found 1 instances of BATTERY
2015-10-16 14:12:21.184 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking WAKE_UP
2015-10-16 14:12:21.184 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking SENSOR_BINARY
2015-10-16 14:12:21.184 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:776]- NODE 2: Node advancer: DYNAMIC_VALUES - found    SENSOR_BINARY
2015-10-16 14:12:21.184 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:780]- NODE 2: Found 1 instances of SENSOR_BINARY
2015-10-16 14:12:21.185 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking SENSOR_MULTILEVEL
2015-10-16 14:12:21.185 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:776]- NODE 2: Node advancer: DYNAMIC_VALUES - found    SENSOR_MULTILEVEL
2015-10-16 14:12:21.185 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:780]- NODE 2: Found 1 instances of SENSOR_MULTILEVEL
2015-10-16 14:12:21.185 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:309]- ============ Requesting RELATIVE_HUMIDITY!
2015-10-16 14:12:21.185 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:247]- NODE 2: Node doesn't support get requests for MULTI_LEVEL_SENSOR
2015-10-16 14:12:21.185 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:309]- ============ Requesting LUMINANCE!
2015-10-16 14:12:21.185 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:247]- NODE 2: Node doesn't support get requests for MULTI_LEVEL_SENSOR
2015-10-16 14:12:21.186 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:309]- ============ Requesting TEMPERATURE!
2015-10-16 14:12:21.186 DEBUG o.o.b.z.i.p.c.ZWaveMultiLevelSensorCommandClass[:247]- NODE 2: Node doesn't support get requests for MULTI_LEVEL_SENSOR
2015-10-16 14:12:21.186 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking NO_OPERATION
2015-10-16 14:12:21.186 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:773]- NODE 2: Node advancer: DYNAMIC_VALUES - checking VERSION
2015-10-16 14:12:21.186 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:808]- NODE 2: Node advancer: DYNAMIC_VALUES - queued 0 frames
2015-10-16 14:12:21.186 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:860]- NODE 2: Node advancer - advancing to DONE
2015-10-16 14:12:21.186 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:333]- NODE 2: Node advancer: loop - DONE try 0: stageAdvanced(true)
2015-10-16 14:12:21.187 DEBUG o.o.b.z.i.p.i.ZWaveNodeSerializer[:107]- NODE 2: Serializing to file etc\zwave\node2.xml
2015-10-16 14:12:21.201 DEBUG o.o.b.z.i.p.i.ZWaveNodeStageAdvancer[:819]- NODE 2: Node advancer: Initialisation complete!
2015-10-16 14:12:21.202 DEBUG o.o.b.z.i.p.ZWaveController[:682]- Notifying event listeners: ZWaveInitializationCompletedEvent
2015-10-16 14:12:21.202 DEBUG o.o.b.z.i.ZWaveActiveBinding[:425]- NODE 2: ZWaveIncomingEvent Called, Network Event, Init Done. Setting device ready.
2015-10-16 14:12:21.203 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:730]- Network initialised - starting network monitor.
2015-10-16 14:12:21.203 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1374]- NODE 2: Response processed after 59ms/2728ms.
2015-10-16 14:12:22.182 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:506]- NODE 2: No more messages, go back to sleep
2015-10-16 14:12:22.182 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:202]- NODE 2: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2015-10-16 14:12:22.182 DEBUG o.o.b.z.i.p.SerialMessage[:109]- NODE 2: Creating empty message of class = SendData (0x13), type = Request (0x00)
2015-10-16 14:12:22.182 DEBUG o.o.b.z.i.p.ZWaveController[:985]- Callback ID = 5
2015-10-16 14:12:22.183 DEBUG o.o.b.z.i.p.ZWaveController[:667]- Enqueueing message. Queue length = 1
2015-10-16 14:12:22.183 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1258]- Took message from queue for sending. Queue length = 0
2015-10-16 14:12:22.183 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 09 00 13 02 02 84 08 25 05 49 
2015-10-16 14:12:22.183 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1315]- NODE 2: Sending REQUEST Message = 01 09 00 13 02 02 84 08 25 05 49 
2015-10-16 14:12:22.190 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1528]- Receive Message = 01 04 01 13 01 E8 
2015-10-16 14:12:22.191 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1452]- Receive queue ADD: Length=1
2015-10-16 14:12:22.191 DEBUG o.o.b.z.i.p.ZWaveController[:1210]- Receive queue TAKE: Length=0
2015-10-16 14:12:22.191 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 04 01 13 01 E8 
2015-10-16 14:12:22.191 DEBUG o.o.b.z.i.p.ZWaveController[:1211]- Process Message = 01 04 01 13 01 E8 
2015-10-16 14:12:22.191 DEBUG o.o.b.z.i.p.ZWaveController[:190]- Message: class = SendData (0x13), type = Response (0x01), payload = 01 
2015-10-16 14:12:22.191 DEBUG o.o.b.z.i.p.s.SendDataMessageClass[:38]- NODE 2: Sent Data successfully placed on stack.
2015-10-16 14:12:22.407 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1528]- Receive Message = 01 07 00 13 05 01 00 16 F9 
2015-10-16 14:12:22.408 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveReceiveThread[:1452]- Receive queue ADD: Length=1
2015-10-16 14:12:22.410 DEBUG o.o.b.z.i.p.ZWaveController[:1210]- Receive queue TAKE: Length=0
2015-10-16 14:12:22.411 DEBUG o.o.b.z.i.p.SerialMessage[:233]- Assembled message buffer = 01 09 00 13 05 01 00 16 00 00 F7 
2015-10-16 14:12:22.411 DEBUG o.o.b.z.i.p.ZWaveController[:1211]- Process Message = 01 09 00 13 05 01 00 16 00 00 F7 
2015-10-16 14:12:22.411 DEBUG o.o.b.z.i.p.ZWaveController[:190]- Message: class = SendData (0x13), type = Request (0x00), payload = 05 01 00 16 
2015-10-16 14:12:22.412 DEBUG o.o.b.z.i.p.s.SendDataMessageClass[:74]- NODE 2: SendData Request. CallBack ID = 5, Status = Transmission complete, no ACK received(1)
2015-10-16 14:12:22.412 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:63]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 02 02 84 08 
2015-10-16 14:12:22.413 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:64]- Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 05 01 00 16 
2015-10-16 14:12:22.413 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:65]- Checking transaction complete: class=SendData, expected=SendData, cancelled=false
2015-10-16 14:12:22.413 DEBUG o.o.b.z.i.p.s.ZWaveCommandProcessor[:68]-          transaction complete!
2015-10-16 14:12:22.414 DEBUG o.o.b.z.i.p.s.SendDataMessageClass[:108]- NODE 2: WAKE_UP_NO_MORE_INFORMATION. Treated as ACK.
2015-10-16 14:12:22.414 DEBUG o.o.b.z.i.p.ZWaveController[:682]- Notifying event listeners: ZWaveTransactionCompletedEvent
2015-10-16 14:12:22.414 DEBUG o.o.b.z.i.ZWaveActiveBinding[:433]- ZwaveIncomingEvent
2015-10-16 14:12:22.415 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:372]- NODE 2: Went to sleep
2015-10-16 14:12:22.415 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:435]- NODE 2: Is sleeping
2015-10-16 14:12:22.415 DEBUG o.o.b.z.i.p.ZWaveController$ZWaveSendThread[:1374]- NODE 2: Response processed after 232ms/2728ms.
2015-10-16 14:12:24.549 DEBUG o.o.b.z.i.c.ZWaveBatteryConverter[:60]- NODE 2: Generating poll message for BATTERY endpoint 0
2015-10-16 14:12:24.549 DEBUG o.o.b.z.i.p.c.ZWaveBatteryCommandClass[:137]- NODE 2: Creating new message for application command BATTERY_GET
2015-10-16 14:12:24.549 DEBUG o.o.b.z.i.p.SerialMessage[:109]- NODE 2: Creating empty message of class = SendData (0x13), type = Request (0x00)
2015-10-16 14:12:24.549 DEBUG o.o.b.z.i.p.ZWaveController[:985]- Callback ID = 6
2015-10-16 14:12:24.550 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:241]- NODE 2: Putting message SendData in wakeup queue.
2015-10-16 14:13:54.555 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:353]- Network Monitor: No nodes to ping!
2015-10-16 14:15:24.560 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:353]- Network Monitor: No nodes to ping!
2015-10-16 14:16:54.565 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:353]- Network Monitor: No nodes to ping!
2015-10-16 14:18:24.570 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:353]- Network Monitor: No nodes to ping!
2015-10-16 14:19:54.575 DEBUG o.o.b.z.i.ZWaveNetworkMonitor[:353]- Network Monitor: No nodes to ping!

node2.xml (7.7 KB)

Everything looks fine with the config and there’s nothing strange in the log I think.

The configuration should mean that the device sends the data every 12 minutes - the log is only for 7 minutes. I guess you’ve waited longer to see what is received, but at the moment, there are no messages being received from the device yet…

Thanks for your help on all this Chris.

Hmm, configuration for group 1 was 240 and I thought that was for every 4 mins. How did you determine 12 mins? I didn’t think the values in group 2 and 3 matters for me right now… or does it?

As for log, Looking at the zlog file, it seems that it has been loggin data over 1 hr… How did you determine it was 3 minutes? I also attached the entire log here. I had to cut off part of the log when I pasted earlier due to post size limitation.log.pdf (162.0 KB)

Sorry - you’re right, it is 6 minutes :blush:

I’m not sure then - everything appears ok. One thing you can try is to delete the XML file, and restart the binding. Wake the device up and hopefully it will recreate the XML. What this does is to download all the configuration from the device - it just makes sure that what we are looking at in the XML file is really consistent with what’s in the device - just in case we’re fooling ourselves and the device is actually configured differently (??).

1 Like

I deleted node2.XML but do not know how to restart binding. How do you manually restart binding?

For now, restarted hab server but experiencing the same issue after the xml file got created. One thing to note is that every time I start hab, I have to click on the button on my device for it to show up on Node 2 in habmin. Could this somehow be contributing to the issue I am experiencing? I figure I would try to resolve issue later after I get the sensor working correctly.

Unenroll the device and enroll it again. The log states that Sensor multilevel is not supported by the device. Maybe it’s gone bad. Try updating the firmware on it.

What do you mean by enroll? When I start the runtime server, the device is showing grey on startup. I have to put the button on my device to change it to ‘green’. Is that what you meant by ‘enroll’? I assume green means good since my aeotec z-stick is always green. Not sure what yellow, red, and grey means.

I looked all over for Aeotec Z-Wave Gen5 Muti-Sensor firmware but can’t find a firmware one Aeotec’s website. They only seem to have firmware for their other multi-sensor that are not GEN5 version I have.

Not sure if this helps, but this is what I see in my configuration in HABMIN:

Will, after doing a rebooting my computer, it started working. :slight_smile: Not sure why that worked since I tried that yesterday and still had problems. Thanks everyone for chipping in!

This is normal. Battery devices aren’t normally awake. They wake up periodically and send data, or you can wake them up manually by pushing the button. Either way, they need to wake up before they are known to be online after a binding restart.

I don’t think it does does it? I can see something that states that GET isn’t supported, but that’s not the same as the whole command class not being supported (or did I miss this?). GET not being supported is quite normal.

Anyway, glad this is working :smile: