ZWAVE-Problems when writing value

Add-ons Bindings
1

I just pass my Openhab configuration from Ubuntu to my Mac.
With ZWave, all items has been properly recognize when I put my USB controller. They are all online and I receive properly the data.
The problem is when I want to write a value, it looks like there is no writing. Here is what I have in the log.

00:14:20.151 [DEBUG] [ding.zwave.handler.ZWaveSerialHandler] - NODE 8: Sending REQUEST Message = 01 0A 00 13 08 03 25 01 00 25 1C F0 
00:14:20.151 [DEBUG] [ding.zwave.handler.ZWaveSerialHandler] - Message SENT
00:14:20.151 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 114: [WAIT_RESPONSE] priority=Set, requiresResponse=true, callback: 28
00:14:20.152 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
00:14:20.152 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
00:14:20.152 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
00:14:20.152 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 00 E9 
00:14:20.153 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction TID 114: [WAIT_RESPONSE] priority=Set, requiresResponse=true, callback: 28
00:14:20.153 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=00 
00:14:20.153 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg: ACK
00:14:20.153 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=00 
00:14:20.153 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction TID 114: [WAIT_RESPONSE] priority=Set, requiresResponse=true, callback: 28
00:14:20.153 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
00:14:20.153 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Last transaction: TID 114: [WAIT_RESPONSE] priority=Set, requiresResponse=true, callback: 28
00:14:20.153 [DEBUG] [ave.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=00 
00:14:20.154 [DEBUG] [ol.serialmessage.SendDataMessageClass] - NODE 8: sentData was not placed on stack.
00:14:20.154 [DEBUG] [ve.internal.protocol.ZWaveTransaction] - TID 114: Transaction CANCELLED
00:14:20.154 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Holdoff Timer started...
00:14:20.154 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
00:14:20.154 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 8: Retry count exceeded. Discarding message: TID 114: [CANCELLED] priority=Set, requiresResponse=true, callback: 28
00:14:20.154 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 8: TID 114: Transaction completed
00:14:20.154 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 8: notifyTransactionResponse TID:114 CANCELLED
00:14:20.155 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
00:14:20.155 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

For what I see Data are not sent, but I don’t know what I should do ?
Thanks for your help.

2

Can you tell us more about your setup? Esp. what device you want to write a value to?

If it is a battery driven device, information exchange will only happen when the device wakes up. Normally there is a procedure of pressing a button several times or something similar on the device itself, have a look into the documentation. If you try that, your device will wake up, talk to the controller and will receive the value update. That way you can at least check whether communication happens and we can start from there.

1 Like
3

Hi,

Thanks for your help.
That’s happen with all the devices. Here the trial was with a switch not on battery.

Regards

4

Could tell us a bit more about what you do to “write a value”?
Are you sending a command to an Item? Or editing a device parameter in PaperUI, or in Habmin?

5

It’s a bit hard to see what is happening with this short log, but the command is being rejected by the controller. This happens when the controller is very busy - possibly due to a lot of network traffic, but it’s extremely difficult to know from just a binding log, and this probably needs a sniffer log.

What would be interesting is to see if this happens all the time, or if some commands do work - this is why a larger log is always useful (this is only logging 4 milliseconds!).

1 Like
6

Sorry for late answering.
Yes, i was sending a command to the actuator.
In this case, a ON or OFF command.

7

Hi, thanks for your help.
None of the commands were passing. Bit all the readings were working correctly. By exemple, by switching manually, i had directly an update of the status.