Zwave Timeout - Fibaro FGWP102

Hi,

from the very beginning I get regular timeouts for my node 4 which is a Fibaro wall plug FGWP102.
It works perfectly with openhab 2, sending on every channel etc… BUT it seems that something
is hanging somewhere with this device. I tried to exclude, remove from Habmin, include back in again with the same result that I get these timeout messages. Trying to capture these with debug mode shows this:

15:17:30.406 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 4: Transaction not completed: node address inconsistent.  lastSent=4, incoming=255
15:17:33.362 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 18 00 04 00 03 12 32 02 21 74 00 00 00 00 00 00 00 00 00 00 00 00 00 00 97
15:17:33.383 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
15:17:33.384 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 18 00 04 00 03 12 32 02 21 74 00 00 00 00 00 00 00 00 00 00 00 00 00 00 97
15:17:33.385 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 18 00 04 00 03 12 32 02 21 74 00 00 00 00 00 00 00 00 00 00 00 00 00 00 97
15:17:33.386 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 03 12 32 02 21 74 00 00 00 00 00 00 00 00 00 00 00 00 00 00

My AEON Labs Smart Switch 6 (ZW096) does not get these timeout messages…
@chris Are there any known issues with this Fibaro Wall Plug so I can just ignore these messages from the log or is there anything I can do to improve? (actually running #710).

regards,
Bernd

I’ve gone through the same steps with a 101 model.
I started to ignore the timeouts :sunglasses:

@sihui thanks for sharing your experience with the wall plug. I think I’ll do the same as you did for the moment.

Bernd

@chris, I just installed a new FGWP102 and having the same problems as above people.
At first I could not turn the device off at all (it went OFF then immediately ON again) even though parameter was set to not always be on.
Deleted it and rediscovered the item and now it works.
I recently managed to have NO red warnings in my karaf console so this node is a bit of an eyesore now :slight_smile:
Edit: openhab2RC1 and I uninstalled bindning/reinstalled it, same problem.