FGK-101 not showing open/close status

Add-ons Bindings
1

Hello all,

I am trying to include a Fibaro Door/Window Sensor. But it won’t work.
I have installed OpenHab2 on an RPi3 like shown on docs.openhab.org

Debug from the Z-Wave:



> 17:40:39.296 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 04 09 71 05 00 00 00 FF 06 17 00 63 
> 17:40:39.299 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
> 17:40:39.301 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0F 00 04 00 04 09 71 05 00 00 00 FF 06 17 00 63 
> 17:40:39.303 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0F 00 04 00 04 09 71 05 00 00 00 FF 06 17 00 63 
> 17:40:39.305 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 04 09 71 05 00 00 00 FF 06 17 00 
> 17:40:39.307 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 4: Application Command Request (ALIVE:DONE)
> 17:40:39.308 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Starting initialisation from DONE
> 17:40:39.309 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1d26185 already registered
> 17:40:39.311 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 4: Incoming command class ALARM
> 17:40:39.312 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: Received ALARM command V5
> 17:40:39.313 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: Process NOTIFICATION_REPORT V5
> 17:40:39.314 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: NOTIFICATION report - 0 = 0, event=23, status=255
> 17:40:39.315 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: Alarm Type = ACCESS_CONTROL (0)
> 17:40:39.316 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
> 17:40:39.318 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveAlarmValueEvent
> 17:40:39.319 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
> 17:40:39.321 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
> 17:40:39.322 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 23, type OnOffType
> 17:40:39.323 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Updating channel state zwave:device:158edb796df:node4:alarm_general to ON [OnOffType]
> 17:40:39.326 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=4, callback=250, payload=04 02 84 08 
> 17:40:39.328 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 04 09 71 05 00 00 00 FF 06 17 00 
> 17:40:39.329 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=250, expected=SendData, cancelled=false      MISMATCH
> 17:40:39.442 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 04 09 71 05 00 00 00 FF 06 16 00 62 
> 17:40:39.446 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
> 17:40:39.448 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0F 00 04 00 04 09 71 05 00 00 00 FF 06 16 00 62 
> 17:40:39.450 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0F 00 04 00 04 09 71 05 00 00 00 FF 06 16 00 62 
> 17:40:39.452 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 04 09 71 05 00 00 00 FF 06 16 00 
> 17:40:39.454 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 4: Application Command Request (ALIVE:DONE)
> 17:40:39.455 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Starting initialisation from DONE
> 17:40:39.457 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1d26185 already registered
> 17:40:39.458 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 4: Incoming command class ALARM
> 17:40:39.459 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: Received ALARM command V5
> 17:40:39.460 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: Process NOTIFICATION_REPORT V5
> 17:40:39.461 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: NOTIFICATION report - 0 = 0, event=22, status=255
> 17:40:39.462 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: Alarm Type = ACCESS_CONTROL (0)
> 17:40:39.463 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
> 17:40:39.464 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveAlarmValueEvent
> 17:40:39.465 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
> 17:40:39.467 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
> 17:40:39.468 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 22, type OnOffType
> 17:40:39.469 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Updating channel state zwave:device:158edb796df:node4:alarm_general to ON [OnOffType]
> 17:40:39.471 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=4, callback=250, payload=04 02 84 08 
> 17:40:39.473 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 04 09 71 05 00 00 00 FF 06 16 00 
> 17:40:39.475 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=250, expected=SendData, cancelled=false      MISMATCH

I already read something in other topics about changing the config file. But I can’t find it on the RPi.
Many Thanks

2

It looks like it’s probably included ok (I’m assuming it’s node 4?).

I can also see that the binding is updating the channels -:

NODE 4: Updating channel state zwave:device:158edb796df:node4:alarm_general to ON [OnOffType]

So it appears to be working to me? What doesn’t work?

Please when pasting logs, don’t format as quotes as it’s hard to read and doesn’t process well. Please use the </> button.

3

Hello Chris,

the problem with alarm_general is that if the magnet is at the sensor or away from it, it always shows ON

In the debug you see two actions, one time getting magnet and sensor together. And one separate them.

4

Ok - can you update the log formatting please and I’ll take a better look.

Cheers
Chris

5

Hi Chris,

should be looking better now.
Yes, Node 4 is my Fibaro FGK101

Something I might should mention: On the pakaging it’s written FGK-107 (but this should be only the difference in color)

Firmware is 3.5

Thank you,
Mike

6

It looks like the database just needs an update to change the channel to sensor_door. In the meantime, can you provide the node4.xml file that OH generates please?

7

I have to reproduce it as I have crashed my RPi.

Is there a possibility to change the configuration to get it working before the database had been updated?

The assumption with sensor_door I also already made before (sent before the post here to: chris@cd-jackson.com)

EDIT: node4.xml (18.3 KB)

8

Not easily - you’d need to modify the source and compile the binding yourself.

9

as a newcomer I probably won’t be able doing that.

How to get the updated database in than?

10

I’ve already done it. So long as you’re not using the apt-get version, it should already be available (apt-get I guess won’t be available till tomorrow).

11

It’s working now!

12

Thanks.