[Solved] Fibaro FPWG102 (FW: 3.2) uses wrong configuration

Setup, Configuration and Use Beginners
, ,
1

My setup: openhabian on Raspberry Pi 3 / ZME UZB1 / fresh install / only UZB1 and FPGW102 connected

There are already some topics around the FPGW102, but not exactly with the issue I found.

I have some trouble with a Fibaro Wall Plug FPGW102 (type 0602:1001, firmware 3.2).
Inclusion was fine, I also could get it to switch but it doesn’t deliver any information back and it is not possible to make any configuration changes. The typical log entries look like this:

2017-04-28 11:50:13.083 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Timeout while sending message. Requeueing - 0 attempts left!
2017-04-28 11:50:13.085 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 5: Got an error while sending data. Resending message.
2017-04-28 11:50:18.242 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Timeout while sending message. Requeueing - 2 attempts left!
2017-04-28 11:50:18.244 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 5: Got an error while sending data. Resending message.
2017-04-28 11:50:23.248 [ERROR] [ocol.ZWaveController$ZWaveS<img src="//community-openhab-org.s3-eu-central-1.amazonaws.com/original/2X/7/7e11fdbc51d3c13b5aa3dd1f43e6d5c7ee961298.PNG" width="535" height="269">endThread] - NODE 5: Timeout while sending message. Requeueing - 1 attempts left!
2017-04-28 11:50:23.249 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 5: Got an error while sending data. Resending message.
2017-04-28 11:50:28.253 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Timeout while sending message. Requeueing - 0 attempts left!
2017-04-28 11:50:28.299 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 5: Got an error while sending data. Resending message.
2017-04-28 11:50:33.305 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Too many retries. Discarding message: Message: class=SendData[0x13], type=Request[0x00], priority=Config, dest=5, callback=12, payload=05 03 70 05 10

After some searching and investigation in the Z-Wave database it seems to be clear, that Fibaro changed some parameters between the firmware versions.

When including the device, the binding recognizes the device absolutely correct as:
Type / ID: 0602:1001
Firmware Version: 3.02

So it recognizes the device correct.
Now the parameters:
1: Always on function
16: Remember device status after power failure
34: Reaction to alarms
35: Response to alarms
…

But looking at the Z-Wave database, the parameters are different! For instance it is 16 for older FPGW102 and 2 in the newer version:

FPGW102_3.PNG764×129 7.16 KB

In the database I see two FPGW102, one for firmware versions before 3.2 and one after.
That’s basically fine. Looking at the definition for the older FPGW102 I found: Ah, this is, what openHAB uses!
I’m new to openHAB but I guess that’s why the configuration goes wrong and that’s why the channels do not work.

Now, how can I setup openHAB to use the right device description?

Many thanks for any response and help.

2

You don’t say what version of the binding you are using? If it’s not the latest snapshot then I would suggest to update so you have the latest definitions as some changes were made on this recently.

3

Er, of course…

‘bundle:list’ in the console says:

209 | Active   |  80 | 2.0.0                 | ZWave Binding

Is this, what you are looking for? It was installed today very normal from the Paper UI.

4

Yes. This is the master release from January and I’m pretty sure there have been updates to this device since then. You should look to use the snapshot version to get the updated database.

5

Well, that does the trick. Thank you.
I used the same “trick” on my main system on a Synology and it worked too.