Strange problem with Z-wave binding 1.8.3 on Windows Machine

Hello community,

I get some strange problem with Z-wave. I have normally Openhab 1 running on RPi 2 with AEON Z-wave Stick Gen.5. I have there 22 nodes and everything works fine. Now I want to test backup solution if RPi for some reason fails. For this I have installed OpenHAB 1 on my windows laptop, installed all needed bindings and copied all configuration files from RPi. In Openhab.cfg I changed COM port from Linux to Windows one. Finally I took Z-wave USB Stick from RPi and plugged it into Laptop.
After starting OH on laptop it starts and I can access sitemap as usual, but I start to get strange z-wave errors, like one below:

2016-11-27 11:35:32.518 [ERROR] [WaveController$ZWaveSendThread] - NODE 28: Timeout while sending message. Requeueing - 2 attempts left!
2016-11-27 11:35:32.518 [ERROR] [b.z.i.p.s.SendDataMessageClass] - NODE 28: Got an error while sending data. Resending message.
2016-11-27 11:35:37.520 [ERROR] [WaveController$ZWaveSendThread] - NODE 28: Timeout while sending message. Requeueing - 1 attempts left!
2016-11-27 11:35:37.520 [ERROR] [b.z.i.p.s.SendDataMessageClass] - NODE 28: Got an error while sending data. Resending message.
2016-11-27 11:35:42.522 [ERROR] [WaveController$ZWaveSendThread] - NODE 28: Timeout while sending message. Requeueing - 0 attempts left!
2016-11-27 11:35:42.522 [ERROR] [b.z.i.p.s.SendDataMessageClass] - NODE 28: Got an error while sending data. Resending message.
2016-11-27 11:35:47.526 [WARN ] [WaveController$ZWaveSendThread] - NODE 28: Too many retries. Discarding message: Message: class = SendData (0x13), type = Request (0x00), payload = 1C 03 70 05 01

This happens with several nodes and during this time Z-wave is very slow. But after some time the errors dissapear and all Z-wave nodes start to work correctly.
What could be the problem?

Not exactly ‘strange’ - this quite simply means that the controller didn’t receive the response from the device - hence a timeout.

Or, forgot to say, why this is strange: if I stop OH on laptop, start Aeon Z-wave utility and ping all those nodes it reports 100% success frames and green status. So the nodes are surely accessable.

Ok - a bit strange then, I agree, but I’m not sure there’s much more I can say from what you’ve presented - it’s a timeout, and it should mean that it didn’t get a response. I’d suggest getting a logfile for starters to see if that shows anything usefil…