I have tried removing the batteries, and removing and adding the multisensor. I don’t know what to try next.
I have a few phantom nodes in my network. I suspect these are coming from failed pairing with the multisensor.
Once you pair the device with the controller you need to wake it up multiple times until the zwave binding has a chance to interrogate it and figure out what kind of device it is. Look at the manual for the multisensor for how to wake it up.
I set the sensitivity to the max and I can see the little LED turning on over and over again. It’s been a few days like this and it is sitting right next to the stick, but the binding still hasn’t found it.
Any ideas?
OK so I tried clicking the button on the back a bunch of times to keep it awake. Openhab was able to interrogate it enough to properly ID it. Now it says: Uninitialized, HANDLER_MISSING_ERROR. Any idea why?
13], type=Request[0x00], priority=Immediate, dest=20, callback=217, payload=14 02 30 02
05:24:45.356 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 14 02 80 02 25 DA 8E
05:24:45.356 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 14 02 84 07
05:24:45.357 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=217, expected=ApplicationCommandHandler, cancelled=true MISMATCH
05:24:45.358 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 20: Sending REQUEST Message = 01 09 00 13 14 02 80 02 25 DA 8E
05:24:45.368 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
05:24:45.375 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
05:24:45.376 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
05:24:45.378 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
05:24:45.379 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
05:24:45.380 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 20: Sent Data successfully placed on stack.
05:24:45.381 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 05 00 13 DA 00 33
05:24:45.387 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
05:24:45.389 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 13 DA 00 00 00 31
05:24:45.390 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 13 DA 00 00 00 31
05:24:45.391 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=DA 00
05:24:45.392 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 20: SendData Request. CallBack ID = 218, Status = Transmission complete and ACK received(0)
05:24:45.393 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Starting initialisation from DONE
05:24:45.394 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@11977c6 already registered
05:24:45.395 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=20, callback=218, payload=14 02 80 02
05:24:45.396 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=DA 00
05:24:45.396 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=218, expected=ApplicationCommandHandler, cancelled=false MISMATCH
05:24:47.184 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 14 03 80 03 64 02
05:24:47.190 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
05:24:47.191 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 14 03 80 03 64 02
05:24:47.193 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 14 03 80 03 64 02
05:24:47.194 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 14 03 80 03 64
05:24:47.195 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 20: Application Command Request (ALIVE:DONE)
05:24:47.196 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Starting initialisation from DONE
05:24:47.197 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@11977c6 already registered
05:24:47.197 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 20: Incoming command class BATTERY
05:24:47.198 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 20: Received Battery Request
05:24:47.199 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 20: Battery report value = 100
05:24:47.200 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
05:24:47.201 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
05:24:47.202 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
05:24:47.204 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Updating channel state zwave:device:29ff9890:node20:battery-level to 100 [DecimalType]
05:24:47.205 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.IllegalStateException: Could not update state, because callback is missing
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.updateState(BaseThingHandler.java:267)[105:org.eclipse.smarthome.core.thing:0.9.0.b5]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:1104)[208:org.openhab.binding.zwave:2.1.0]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:567)[208:org.openhab.binding.zwave:2.1.0]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveBatteryCommandClass.handleApplicationCommandRequest(ZWaveBatteryCommandClass.java:109)[208:org.openhab.binding.zwave:2.1.0]
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[208:org.openhab.binding.zwave:2.1.0]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:248)[208:org.openhab.binding.zwave:2.1.0]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:214)[208:org.openhab.binding.zwave:2.1.0]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:208)[208:org.openhab.binding.zwave:2.1.0]
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1324)[208:org.openhab.binding.zwave:2.1.0]
05:24:50.373 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 20: Timeout while sending message. Requeueing - 2 attempts left!
05:24:50.374 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 20: Is sleeping
05:24:50.375 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 20: Putting message SendData in wakeup queue.
Check the database if your id is listed.
Check your userdata/zwave folder if an xml file has been created.
ID is listed in the DB, but where is this userdata/zwave folder?
That depends on your installation method (which you did not tell):
http://docs.openhab.org/installation/linux.html#file-locations
Also make sure you are on a recent zwave snapshot binding (or the 2.2 stable) because newer devices are not supported with older binding versions.
OK, I’ll bump the install. Currently on 2.1. Hmm, what’s the best way to do that…
But this sensor is old old. I had it running with OH1.
My install is via repo on Raspbian.
I attached items to each channel and now the node says it’s online. I can’t recall exactly what I did, but it seemed like when I set the temperature unit (to Celsius) it snapped into action.
I get a value for the battery but it’s 100% and hasn’t changed. That has to be wrong. All other values are 0.
I set group 1 to 225, is there anything else I can try?
Watching the logs I see the sensor wake up and send the battery info when motion is detected, but it doesn’t send any of the other data.
OK that’s goofy. I skimmed the logs again and found it has started to send all the data.
The last couple of things I tried were updating to 2.2, making sure group 1 was set to 225 and taking the batteries out of the sensor for 30 seconds.
Now on to the last remaining light switches!
1 Like