ZWave Fibaro FGK-10x reports mostly CLOSED in OH1

[Joel_S (Joel)]

Hello
Having found a lot to read and fix, this one is really difficult to do.
openHAB is 1.8.3
zwave addon is org.openhab.binding.zwave-1.9.0-SNAPSHOT.jar as it was suggested in anoterh post here.
All installed FGK-10x report CLOSED in OH1 when the door is closing or opening.
However, when leaving the doors open and the FGK sends an automatic update, the correct status is reported into OH. Also presing the TMP button repots correctly the status, but only once for 30 minutes or so. It’s very strange.

When looking at the zwave logs, the OPEN or CLOSE messages are different in the payload of the message.

Message for OPEN is
[eController$ZWaveReceiveThread:1530]- Receive Message = 01 0F 00 04 00 0E 09 71 05 00 00 00 FF 06 16 00 68
[eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
[b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
[o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0F 00 04 00 0E 09 71 05 00 00 00 FF 06 16 00 68
[b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0F 00 04 00 0E 09 71 05 00 00 00 FF 06 16 00 68
[b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 0E 09 71 05 00 00 00 FF 06 16 00
[ApplicationCommandMessageClass:40 ]- NODE 14: Application Command Request (ALIVE:DONE)
[ApplicationCommandMessageClass:58 ]- NODE 14: Incoming command class ALARM
[z.i.p.c.ZWaveAlarmCommandClass:82 ]- NODE 14: Received Alarm Request
[z.i.p.c.ZWaveAlarmCommandClass:94 ]- NODE 14: Alarm report - Value = 0
[z.i.p.c.ZWaveAlarmCommandClass:113 ]- NODE 14: Alarm Type = General (0)
[b.z.i.protocol.ZWaveController:648 ]- Notifying event listeners: ZWaveAlarmValueEvent
[.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
[.z.internal.ZWaveActiveBinding:466 ]- NODE 14: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
[ApplicationCommandMessageClass:89 ]- Transaction not completed: node address inconsistent.

Message for CLOSED is
[eController$ZWaveReceiveThread:1530]- Receive Message = 01 0F 00 04 00 0E 09 71 05 00 00 00 FF 06 17 00 69
[eController$ZWaveReceiveThread:1446]- Receive queue ADD: Length=1
[b.z.i.protocol.ZWaveController:1194]- Receive queue TAKE: Length=0
[o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0F 00 04 00 0E 09 71 05 00 00 00 FF 06 17 00 69
[b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0F 00 04 00 0E 09 71 05 00 00 00 FF 06 17 00 69
[b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 0E 09 71 05 00 00 00 FF 06 17 00
[ApplicationCommandMessageClass:40 ]- NODE 14: Application Command Request (ALIVE:DONE)
[ApplicationCommandMessageClass:58 ]- NODE 14: Incoming command class ALARM
[z.i.p.c.ZWaveAlarmCommandClass:82 ]- NODE 14: Received Alarm Request
[z.i.p.c.ZWaveAlarmCommandClass:94 ]- NODE 14: Alarm report - Value = 0
[z.i.p.c.ZWaveAlarmCommandClass:113 ]- NODE 14: Alarm Type = General (0)
[b.z.i.protocol.ZWaveController:648 ]- Notifying event listeners: ZWaveAlarmValueEvent
[.z.internal.ZWaveActiveBinding:449 ]- ZwaveIncomingEvent
[.z.internal.ZWaveActiveBinding:466 ]- NODE 14: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
[ApplicationCommandMessageClass:89 ]- Transaction not completed: node address inconsistent.

For the items I tried several combinations, like

Contact	FibDS_GF_Terrace		"Terrasse"	<door>		(Door_GF)	{zwave="14:command=sensor_binary"} 

Contact	FibDS_GF_Terrace		"Terrasse"	<door>		(Door_GF)	{zwave="14:command=sensor_binary,respond_to_basic=TRUE"}

Contact	FibDS_GF_Terrace		"Terrasse"	<door>		(Door_GF)	{zwave="14:1command=sensor_binary"} 

Contact	FibDS_GF_Terrace		"Terrasse"	<door>		(Door_GF)	{zwave="14:1command=sensor_binary,respond_to_basic=TRUE"}

Alternatively I al tried senson_alarm, alarm, sensor.

The zwave logs shows that it seems to be an “ALARM” meesage and not a sensor_binary or sensor_alarm. None of them shows the door actually opening; they all report CLOSED.

What did I miss? Does anybody see a problem right on?

[chris (Chris Jackson)]

This is likely associated with the implementation of the ALARM vs NOTIFICATION class. I’d suggest a quick search as this has been discussed recently.

Maybe try here -:

Fibaro Door Window contact FGK-10x

Hi, I have found a configuration that seems to make it possible to use the device as the old one. My primary mistake was that I where so focused on the Configuration Parameter section, that I didn’t look carefull enough in the Association Groups. Every now and then during configuration it just forgets the Lifeline Association. Besides from that there is some problems with the configurationparameters. Not all parameters is allowed, found that the default suggested values for the parameters bel…

[sihui]

@Joel_S

For the items I tried several combinations

My FGK101 is working fine with

Contact FibDWS1_C_IN1 "FibDWS1_C_IN1" { zwave="6:command=sensor_binary,respond_to_basic=true" }

Note that in your item definition the syntax is wrong! You are missing a colon behind the endpoint number. But because an endpoint is not needed it actually doesn’t matter

Edit: also check parameter 3 in your hardware config: it should be set to “normally open”

[chris (Chris Jackson)]

@sihui

But because an endpoint is not needed it actually doesn’t matter

Hmmm - firstly, well spotted ;).

However, this is not correct - it does matter. The binding will read this as a parameter - the 1command, and not command, and it will therefore not accept this configuration… A colon needs to be present right before the command.

[sihui]

@chris

However, this is not correct

I know
But what I meant: he shouldn’t use an endpoint because it is not needed (at least not with my FGK101).
So the two options he tried with an endpoint number in there can be omitted.
(Sometimes it is hard to explain something in a not native language )

[Joel_S (Joel)]

Thank you for the replies. I read the link about the notification stuff, but it didn’t help.
I tried to look up the FGK-101 in the zwave.jar addon. For the version I have of the FGK (version 4), and couldn’t find anything. The Normal_Open parameter is not present on version 4.
For some reasons, I still have my Zipabox where I connected the FGK-101. It was recognized nearly without problems and it shows correctly the OPEN or CLOSED state. However it doesn’t show any Tamper alarm, but at that point I don’t care. In Zipato the O/C states are shown as NOTIFICATION and under that ACCESS_CONTROL and somewhere I read “VALUE=6”.
So, since I’m not really a programmer and I don’t know what to look for exactly, I will probably use the FGK-101 to monitor windows that should never be opened anyway, or simply connect the FGKs to the ZipaBox and read the values with openHAB. Apparently in OH2 the FGKs are supposed to work correctly.