Effect of changing openHAB versions on ZWave controller/stability

mbelleville · September 17, 2015, 1:31am

I play around with different nightly builds of openHAB fairly regularly. In particular if I need to get the latest version of the openHAB ZWave database.

Typically, all I do is shut down the running version openhab, copy all of the configuration files into the new openhab directory, then start up the new version of openhab (or roll back to an older one).

I am wondering if these actions may lead to long term problems in my ZWave network. Is there any reason why swapping versions of openHAB like this could cause issues with the ZWave controller?

I just did this today and now I am having a very difficult time getting my ZWave network back to normal again. I am getting lots of these messages in the logs:
[ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending

If I attempt to turn a ZWave light switch on/off, the light does not react immediately. There is a delay of several seconds/minutes, then I get a burst of those error messages in the logs and the light switch reacts at the same time.

Example: turn dimmer to off using openhab android app, the following log messages occur before the light actually turns off

2015-09-16 21:25:32.618 [INFO ] [runtime.busevents ] - Light_FF_Media_Ceiling_Dimmer received command 0
2015-09-16 21:25:32.618 [INFO ] [runtime.busevents ] - Light_FF_Media_Ceiling_Dimmer state updated to 0
2015-09-16 21:28:19.621 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:19.721 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:19.821 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:19.921 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:20.022 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:20.122 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:20.223 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:20.326 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:20.427 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:20.528 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:20.628 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:20.729 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:20.834 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:20.935 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:21.036 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:21.136 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:21.237 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending
2015-09-16 21:28:21.337 [ERROR] [eController$ZWaveReceiveThread] - Protocol error (CAN), resending

If anyone would like to see a debug log instead of a normal log let me know…

wawa79 · October 19, 2015, 9:35am

Hello,
I am experiencing the same issue wih my Sigma UZB controller and openHab 1.7.1. I have 35 ZWave devices which run fast and smooth with HomeSeer2 and lag a lot with OpenHAB.

ZWave commands are sometimes not processed at all (I can seen the command message but not the state message) or sometimes processed a few minutes after the command. I am also surprised how slow the initialization of the network is (20-30min) compared to HS2 (a few secs) and wonder if the ZWave binding is not flooding the ZWave controller queue…

Below is an extract of my debug log as I could not attach a ZIP or LOG file.

2015-10-14 00:11:44.998 [DEBUG] [eController$ZWaveReceiveThread:1528]- Receive Message = 01 17 00 04 00 25 11 60 06 01 32 02 21 34 00 00 00 00 00 00 00 00 00 00 9A 
2015-10-14 00:11:44.998 [DEBUG] [eController$ZWaveReceiveThread:1452]- Receive queue ADD: Length=1
2015-10-14 00:11:44.998 [DEBUG] [b.z.i.protocol.ZWaveController:1210]- Receive queue TAKE: Length=0
2015-10-14 00:11:44.998 [ERROR] [eController$ZWaveReceiveThread:1543]- Protocol error (0), resending
2015-10-14 00:11:44.998 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 17 00 04 00 25 11 60 06 01 32 02 21 34 00 00 00 00 00 00 00 00 00 00 9A 
2015-10-14 00:11:44.998 [DEBUG] [b.z.i.protocol.ZWaveController:1211]- Process Message = 01 17 00 04 00 25 11 60 06 01 32 02 21 34 00 00 00 00 00 00 00 00 00 00 9A 
2015-10-14 00:11:44.998 [DEBUG] [b.z.i.protocol.ZWaveController:190 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 25 11 60 06 01 32 02 21 34 00 00 00 00 00 00 00 00 00 00 
2015-10-14 00:11:44.998 [DEBUG] [ApplicationCommandMessageClass:38  ]- NODE 37: Application Command Request (ALIVE:PING)
2015-10-14 00:11:44.998 [DEBUG] [ApplicationCommandMessageClass:56  ]- NODE 37: Incoming command class MULTI_INSTANCE
2015-10-14 00:11:44.998 [DEBUG] [ZWaveMultiInstanceCommandClass:145 ]- NODE 37: Received Multi-instance/Multi-channel Request
2015-10-14 00:11:44.998 [DEBUG] [ZWaveMultiInstanceCommandClass:233 ]- NODE 37: Requested Command Class = METER (0x32)
2015-10-14 00:11:44.998 [DEBUG] [ZWaveMultiInstanceCommandClass:257 ]- NODE 37: Instance = 1, calling handleApplicationCommandRequest.
2015-10-14 00:11:44.998 [DEBUG] [z.i.p.c.ZWaveMeterCommandClass:109 ]- NODE 37: Received Meter Request
2015-10-14 00:11:44.998 [DEBUG] [z.i.p.c.ZWaveMeterCommandClass:157 ]- NODE 37: Meter: Type=Electric(1), Scale=W(2), Value=0E+1
2015-10-14 00:11:44.998 [DEBUG] [b.z.i.protocol.ZWaveController:682 ]- Notifying event listeners: ZWaveMeterValueEvent
2015-10-14 00:11:44.998 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ]- ZwaveIncomingEvent
2015-10-14 00:11:44.998 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ]- NODE 37: Got a value event from Z-Wave network, endpoint = 1, command class = METER, value = 0E+1
2015-10-14 00:11:44.998 [DEBUG] [ApplicationCommandMessageClass:85  ]- Transaction not completed: node address inconsistent.
2015-10-14 00:11:45.092 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 108
2015-10-14 00:11:45.092 [DEBUG] [WaveController$ZWaveSendThread:1374]- NODE 9: Response processed after 109ms/156ms.
2015-10-14 00:11:45.108 [ERROR] [eController$ZWaveReceiveThread:1543]- Protocol error (CAN), resending
2015-10-14 00:11:45.108 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 107
2015-10-14 00:11:45.108 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.108 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 9: Sending REQUEST Message = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.202 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 108
2015-10-14 00:11:45.202 [DEBUG] [WaveController$ZWaveSendThread:1374]- NODE 9: Response processed after 94ms/156ms.
2015-10-14 00:11:45.202 [ERROR] [eController$ZWaveReceiveThread:1543]- Protocol error (CAN), resending
2015-10-14 00:11:45.202 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 107
2015-10-14 00:11:45.202 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.202 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 9: Sending REQUEST Message = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.295 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 108
2015-10-14 00:11:45.295 [DEBUG] [WaveController$ZWaveSendThread:1374]- NODE 9: Response processed after 93ms/156ms.
2015-10-14 00:11:45.295 [ERROR] [eController$ZWaveReceiveThread:1543]- Protocol error (CAN), resending
2015-10-14 00:11:45.311 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 107
2015-10-14 00:11:45.311 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.311 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 9: Sending REQUEST Message = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.405 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 108
2015-10-14 00:11:45.405 [DEBUG] [WaveController$ZWaveSendThread:1374]- NODE 9: Response processed after 94ms/156ms.
2015-10-14 00:11:45.405 [ERROR] [eController$ZWaveReceiveThread:1543]- Protocol error (CAN), resending
2015-10-14 00:11:45.405 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 107
2015-10-14 00:11:45.405 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.405 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 9: Sending REQUEST Message = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.498 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 108
2015-10-14 00:11:45.498 [DEBUG] [WaveController$ZWaveSendThread:1374]- NODE 9: Response processed after 93ms/156ms.
2015-10-14 00:11:45.498 [ERROR] [eController$ZWaveReceiveThread:1543]- Protocol error (CAN), resending
2015-10-14 00:11:45.514 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 107
2015-10-14 00:11:45.514 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.514 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 9: Sending REQUEST Message = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.608 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 108
2015-10-14 00:11:45.608 [DEBUG] [WaveController$ZWaveSendThread:1374]- NODE 9: Response processed after 94ms/156ms.
2015-10-14 00:11:45.608 [ERROR] [eController$ZWaveReceiveThread:1543]- Protocol error (CAN), resending
2015-10-14 00:11:45.608 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 107
2015-10-14 00:11:45.608 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.608 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 9: Sending REQUEST Message = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.702 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 108
2015-10-14 00:11:45.702 [DEBUG] [WaveController$ZWaveSendThread:1374]- NODE 9: Response processed after 94ms/156ms.
2015-10-14 00:11:45.702 [ERROR] [eController$ZWaveReceiveThread:1543]- Protocol error (CAN), resending
2015-10-14 00:11:45.717 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 107
2015-10-14 00:11:45.717 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.717 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 9: Sending REQUEST Message = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.811 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 108
2015-10-14 00:11:45.811 [DEBUG] [WaveController$ZWaveSendThread:1374]- NODE 9: Response processed after 94ms/156ms.
2015-10-14 00:11:45.811 [ERROR] [eController$ZWaveReceiveThread:1543]- Protocol error (CAN), resending
2015-10-14 00:11:45.811 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 107
2015-10-14 00:11:45.811 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.811 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 9: Sending REQUEST Message = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:45.905 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 108
2015-10-14 00:11:45.920 [DEBUG] [eController$ZWaveReceiveThread:1528]- Receive Message = 01 04 01 13 01 E8 
2015-10-14 00:11:46.827 [DEBUG] [WaveController$ZWaveSendThread:1374]- NODE 9: Response processed after 1016ms/1016ms.
2015-10-14 00:11:46.827 [DEBUG] [eController$ZWaveReceiveThread:1452]- Receive queue ADD: Length=1
2015-10-14 00:11:46.827 [DEBUG] [b.z.i.protocol.ZWaveController:1210]- Receive queue TAKE: Length=0
2015-10-14 00:11:46.827 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 04 01 13 01 E8 
2015-10-14 00:11:46.827 [DEBUG] [b.z.i.protocol.ZWaveController:1211]- Process Message = 01 04 01 13 01 E8 
2015-10-14 00:11:46.827 [DEBUG] [b.z.i.protocol.ZWaveController:190 ]- Message: class = SendData (0x13), type = Response (0x01), payload = 01 
2015-10-14 00:11:46.827 [DEBUG] [b.z.i.p.s.SendDataMessageClass:38  ]- NODE 9: Sent Data successfully placed on stack.
2015-10-14 00:11:46.827 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 107
2015-10-14 00:11:46.827 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:46.827 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 9: Sending REQUEST Message = 01 08 00 13 09 01 00 25 08 C1 
2015-10-14 00:11:49.514 [DEBUG] [z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 107 - deferring network monitor functions.
2015-10-14 00:11:52.827 [DEBUG] [o.b.z.i.protocol.SerialMessage:109 ]- NODE 255: Creating empty message of class = SendDataAbort (0x16), type = Request (0x00)
2015-10-14 00:11:52.827 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 03 00 16 EA 
2015-10-14 00:11:52.842 [DEBUG] [WaveController$ZWaveSendThread:1341]- NODE 9: Sending ABORT Message = 01 03 00 16 EA 
2015-10-14 00:11:53.842 [ERROR] [WaveController$ZWaveSendThread:1356]- NODE 9: Timeout while sending message. Requeueing - 0 attempts left!
2015-10-14 00:11:53.842 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 9: Got an error while sending data. Resending message.
2015-10-14 00:11:53.842 [DEBUG] [b.z.i.protocol.ZWaveController:985 ]- Callback ID = 127
2015-10-14 00:11:53.842 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 108
2015-10-14 00:11:53.842 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 107
2015-10-14 00:11:53.842 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 08 00 13 09 01 00 25 7F B6 
2015-10-14 00:11:53.842 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 9: Sending REQUEST Message = 01 08 00 13 09 01 00 25 7F B6 
2015-10-14 00:11:54.514 [DEBUG] [z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 107 - deferring network monitor functions.
2015-10-14 00:11:59.514 [DEBUG] [z.internal.ZWaveNetworkMonitor:315 ]- Network Monitor: Queue length is 107 - deferring network monitor functions.

I am new to openHab and impressed by its simplicity, consistency, platform-independency, extensibility compared to tools such as Jeedom or Domoticz to name few I tested as succesors to the messy HS2 at home.
It took me only 2 days to switch all my HA system from HS2 to OpenHAB 1.7.1 and benefit from the great Web UI with no pain and no coding. The “intelligence” (rules) of my HA is hosted in python scripts running in Eventghost which gives me the best organization/flexibility/extensibility. Unfortunately, due to the ZWave binding unresponsiveness, I keep the ugly outdated HS2 running to forward/receive ZWave messages to Eventghost which forwards state/command to OpenHAB through Mqtt.

I believe OpenHAB has the right simple and robust model and that OpenHAB2 goes on step further (things/items separation). But to become the HA software killer I am dreaming of, I need the ZWave binding to be more stable (and also a tool to design rules as powerful as Eventghost + python scripting)

Any help is appreciated (I am even ready to change ZWave hardware if one “more compatible” with OH could solve my issue)

dan12345 · October 19, 2015, 4:00pm

I’ve found the Aeotec gen5 zwave USB stick to work very well with OH1 on an odroid, old Thinkpad and PC. Almost immediate response (in both directions). Noticeably faster than my old Vera. So I suspect your problem is the hardware not the binding.

That said, when I’ve moved the stick to a new PC, or new installation, it does take a while for the zwave network to heal and settle down. But after a few hours it’s just as solid as it was before.

chris · October 19, 2015, 5:10pm

Do you have any DEAD devices in your network? I’ve seen this cause such problems, but normally if devices are responding, the system works very well for me - I’ve used the UZB1 and the Gen2 and Gen5 Aeon sticks with around 50 devices in the network…

wawa79 · October 19, 2015, 8:29pm

That might be the problem: I have 4 Fibaro devices which I setup for testing purpose but which are currently disconnected from the mains.
They appear as dead in HABmin but are not deleted when choosing the “Delete node” command. Should I exclude them from the controller?

wawa79 · October 19, 2015, 8:30pm

Thank you for the advise. I will first investigate the dead devices as suggestd by @chris

chris · October 19, 2015, 8:38pm

Are they battery devices? I’ve not worked out how to remove battery devices . The issue is that it’s only possible to delete devices that the controller thinks are dead - this doesn’t happen for battery devices.

If mains devices (which you do say they are) then they should be able to be deleted. If they don’t delete, then please send a log and I’ll take a look (debug log).

wawa79 · October 19, 2015, 10:22pm

No, they are not deleted. See the log below:

2015-10-19 22:19:39.624 [DEBUG] [.z.i.config.ZWaveConfiguration:975 ]- NODE 5: Delete node
2015-10-19 22:19:39.639 [DEBUG] [s.RemoveFailedNodeMessageClass:42  ]- NODE 5: Marking node as having failed.
2015-10-19 22:19:39.639 [DEBUG] [o.b.z.i.protocol.SerialMessage:109 ]- NODE 255: Creating empty message of class = RemoveFailedNodeID (0x61), type = Request (0x00)
2015-10-19 22:19:39.639 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 1
2015-10-19 22:19:39.639 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 0
2015-10-19 22:19:39.639 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 05 00 61 05 FE 60 
2015-10-19 22:19:39.639 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 255: Sending REQUEST Message = 01 05 00 61 05 FE 60 
2015-10-19 22:19:39.655 [DEBUG] [eController$ZWaveReceiveThread:1528]- Receive Message = 01 04 01 61 00 9B 
2015-10-19 22:19:39.655 [DEBUG] [eController$ZWaveReceiveThread:1452]- Receive queue ADD: Length=1
2015-10-19 22:19:39.655 [DEBUG] [b.z.i.protocol.ZWaveController:1210]- Receive queue TAKE: Length=0
2015-10-19 22:19:39.655 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 04 01 61 00 9B 
2015-10-19 22:19:39.655 [DEBUG] [b.z.i.protocol.ZWaveController:1211]- Process Message = 01 04 01 61 00 9B 
2015-10-19 22:19:39.655 [DEBUG] [b.z.i.protocol.ZWaveController:190 ]- Message: class = RemoveFailedNodeID (0x61), type = Response (0x01), payload = 00 
2015-10-19 22:19:39.655 [DEBUG] [s.RemoveFailedNodeMessageClass:53  ]- Got RemoveFailedNode response.
2015-10-19 22:19:39.655 [DEBUG] [s.RemoveFailedNodeMessageClass:58  ]- NODE 5: Remove failed node successfully placed on stack.
2015-10-19 22:19:44.655 [ERROR] [WaveController$ZWaveSendThread:1356]- NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2015-10-19 22:19:44.655 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 1
2015-10-19 22:19:44.655 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 0
2015-10-19 22:19:44.655 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 05 00 61 05 FE 60 
2015-10-19 22:19:44.655 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 255: Sending REQUEST Message = 01 05 00 61 05 FE 60 
2015-10-19 22:19:49.671 [ERROR] [WaveController$ZWaveSendThread:1356]- NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2015-10-19 22:19:49.671 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 1
2015-10-19 22:19:49.671 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 0
2015-10-19 22:19:49.671 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 05 00 61 05 FE 60 
2015-10-19 22:19:49.671 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 255: Sending REQUEST Message = 01 05 00 61 05 FE 60 
2015-10-19 22:19:54.686 [ERROR] [WaveController$ZWaveSendThread:1356]- NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2015-10-19 22:19:54.686 [DEBUG] [b.z.i.protocol.ZWaveController:667 ]- Enqueueing message. Queue length = 1
2015-10-19 22:19:54.686 [DEBUG] [WaveController$ZWaveSendThread:1258]- Took message from queue for sending. Queue length = 0
2015-10-19 22:19:54.686 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 05 00 61 05 FE 60 
2015-10-19 22:19:54.686 [DEBUG] [WaveController$ZWaveSendThread:1315]- NODE 255: Sending REQUEST Message = 01 05 00 61 05 FE 60 
2015-10-19 22:19:59.702 [WARN ] [WaveController$ZWaveSendThread:1365]- NODE 255: Too many retries. Discarding message: Message: class = RemoveFailedNodeID (0x61), type = Request (0x00), payload = 05 FE 
2015-10-19 22:20:14.608 [DEBUG] [z.internal.ZWaveNetworkMonitor:341 ]- NODE 25: Sending periodic PING.

wawa79 · October 28, 2015, 9:00pm

Finally devices seem to have been deleted by HABAdmin. And after one week of testing, all zwave devices are proudly showing a green icon in HABAdmin and I no longer get lags or delays in response.

Thanks a lot!

FunMiles · December 8, 2015, 7:11am

I am having a very similar problem. I’ve been remodeling my house while living in a friend’s condo. There, I setup a few plug in devices. Today my electrician installed a dozen ZWave dimmers in my house and I took my laptop and an Aeon gen 5 USB stick. I experienced the same problems as mbelleville.
I understand openHAB thinks the plugins in the condo are dead, but I don’t see why it should suddenly make other devices pretty much unusable. What is the mechanism that makes this happens?
And do the devices need to be removed from the usb stick pairing or from the OpenHAB configuration files?

wolf_from_the_north · December 10, 2015, 10:14am

chris,

i can say that removal of battery devices is possible.
in my case i had to switch the battery of my fibaro door contact sensor, the manual states to reinclude the device or else the battery will be marked empty.
after a while the controller thinks the node is dead because of this, and i got the delete button.
i have not deleted the node yet cause i like my correct numbering
but i do think its possible.