I’ve been trying to connect my Everspring AN157 (which is in the database) to my Raspberry Pi 3 with a z-wave.me stick through OH2. I installed Habmin, including and excluding devices worked and I connected my AN157, which is now called node2. In Paper UI the node is listed as: Node 2, Unknown Device, zwave:device:1564819d336:node2 .
I can provide the XML file if necessary
My .items file looks like this:
Switch Testlamp "Testlamp" { channel="zwave:device:1564819d336:node2:switch_binary" }
And my sitemap looks like this:
sitemap home label="test"
{
Frame label = "test"
{
Switch item=Testlamp
}
}
When flicking this switch I get the following error:
14:28:52.159 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Command received zwave:device:1564819d336:node2:switch_binary --> ON
14:28:52.164 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Command for unknown channel zwave:device:1564819d336:node2:switch_binary with OnOffType
When pressing the on/off button on the device itself (I think it sends a message so the status can be updated?) I get the following:
14:31:52.284 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 49 84 02 09 03 10 01 25 27 72 86 75 73 D4
14:31:52.289 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
14:31:52.291 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0F 00 49 84 02 09 03 10 01 25 27 72 86 75 73 D4
14:31:52.293 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0F 00 49 84 02 09 03 10 01 25 27 72 86 75 73 D4
14:31:52.294 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 02 09 03 10 01 25 27 72 86 75 73
14:31:52.302 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 2: Application update request. Node information received.
14:31:52.303 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
14:31:52.304 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@17fe7ad already registered
14:31:52.304 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 2: Application update request. Requesting node state.
14:31:52.305 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveDelayedPollEvent
14:31:52.306 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveDelayedPollEvent
14:31:52.307 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling intialised at 7200 seconds - start in 75 milliseconds.
14:31:52.309 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Poll, dest=2, callback=8, payload=02 01 00
14:31:52.311 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 02 09 03 10 01 25 27 72 86 75 73
14:31:52.312 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=8, expected=SendData, cancelled=false MISMATCH
14:31:52.383 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling...
Can anyone tell me why the device doesn’t receive the command (or doesn’t switch when it receives the command)?