Whats up with this switch?

I’m trying to get my first z-wave stuff going.

I did the pairing correctly I think, and habmin is showing the device but it’s just showing unknown for everything. The device is a Aeon Labs Aeotec Smart Switch Gen5 ZW075-C07 which I don’t think is in the database so I suspect I need to do something, but shouldn’t the node show a device id?

The values have changed a lit bit if that matters. I’ve also moved it closer to the control stick.

I’ve changed the com to tcp software on my server and it’s working a bit better but I still can’t control the switch! I’m getting this in the logs:

2016-01-26 20:47:20.876 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 2 attempts left!
2016-01-26 20:47:25.877 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 1 attempts left!
2016-01-26 20:47:30.878 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 0 attempts left!
2016-01-26 20:47:35.879 [WARN ] [WaveController$ZWaveSendThread] - NODE 2: Too many retries. Discarding message: Message: class = SendData (0x13), type = Request (0x00), payload = 02 03 85 02 03
2016-01-26 20:47:40.880 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 2 attempts left!
2016-01-26 20:47:45.881 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 1 attempts left!
2016-01-26 20:47:50.882 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 0 attempts left!
2016-01-26 20:47:55.884 [WARN ] [WaveController$ZWaveSendThread] - NODE 2: Too many retries. Discarding message: Message: class = SendData (0x13), type = Request (0x00), payload = 02 03 70 05 02
2016-01-26 20:48:00.885 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 2 attempts left!
2016-01-26 20:48:05.906 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 1 attempts left!
2016-01-26 20:48:10.907 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 0 attempts left!
2016-01-26 20:48:45.894 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 2 attempts left!
2016-01-26 20:48:50.895 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 1 attempts left!
2016-01-26 20:48:55.896 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 0 attempts left!
2016-01-26 20:49:00.898 [WARN ] [WaveController$ZWaveSendThread] - NODE 2: Too many retries. Discarding message: Message: class = SendData (0x13), type = Request (0x00), payload = 02 03 70 05 02
2016-01-26 20:50:05.895 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 2 attempts left!
2016-01-26 20:50:10.897 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 1 attempts left!
2016-01-26 20:50:15.898 [ERROR] [WaveController$ZWaveSendThread] - NODE 2: Timeout while sending message. Requeueing - 0 attempts left!
2016-01-26 20:50:20.901 [WARN ] [WaveController$ZWaveSendThread] - NODE 2: Too many retries. Discarding message: Message: class = SendData (0x13), type = Request (0x00), payload = 02 03 70 05 02
2016-01-26 20:52:40.877 [ERROR] [z.i.p.i.ZWaveNodeStageAdvancer] - NODE 2: Node advancer: Retries exceeded at GET_CONFIGURATION

I have the same problem with my first tries with openhab in ubuntu 15.10, and Aeon zstick gen5. My switch is a greenwave powernode ns310 and does not show up in habmin from its own, but the openhab log file looks the same. Did you get any further?

If you have lots of timeouts like this, then it means that openhab is not able to communicate with the device - you need to resolve this issue or nothing will work (at least not reliably).

Restarting the server resolved it for me.

Then I guess I have a different problem. I will start my own thread. It’s probably a newbe problem.