Fibaro Door Window contact FGK-10x

berni · November 27, 2016, 5:03pm

After some attempts to include the FGK-10x (new zwave plus G5 version) I succeeded, its fully initialized and included, however the device doesn’t seem to work. When changing the name of the device in the device properties, I get a 500 internal Server error:

{
  "error": {
    "message": "Duplicate channels zwave:device:158964d7947:node28:alarm_general",
    "http-code": 500,
    "exception": {
      "class": "java.lang.IllegalArgumentException",
      "message": "Duplicate channels zwave:device:158964d7947:node28:alarm_general",
      "localized-message": "Duplicate channels zwave:device:158964d7947:node28:alarm_general"
    }
  }
}

I already deleted the device and re-added it.
Also I see in the log that the device is sending the sensor state:

2016-11-27 18:00:17.443 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 28: Application Command Request (ALIVE:DONE)
2016-11-27 18:00:17.444 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 28: Starting initialisation from DONE
2016-11-27 18:00:17.444 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@66c86e already registered
2016-11-27 18:00:17.444 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 28: Incoming command class CRC_16_ENCAP
2016-11-27 18:00:17.445 [DEBUG] [.ZWaveCRC16EncapsulationCommandClass] - NODE 28: Received CRC 16 Encapsulation Request
2016-11-27 18:00:17.445 [DEBUG] [.ZWaveCRC16EncapsulationCommandClass] - NODE 28: Calling handleApplicationCommandRequest.
2016-11-27 18:00:17.446 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 28: Received ALARM command V5
2016-11-27 18:00:17.446 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 28: Process NOTIFICATION_REPORT V5
2016-11-27 18:00:17.446 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 28: NOTIFICATION report - 0 = 0, event=22, status=255
2016-11-27 18:00:17.447 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 28: Alarm Type = ACCESS_CONTROL (0)
2016-11-27 18:00:17.447 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2016-11-27 18:00:17.447 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 28: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-11-27 18:00:17.448 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 28: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2016-11-27 18:00:17.449 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2016-11-27 18:00:17.449 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 22, type OnOffType
2016-11-27 18:00:17.450 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 28: Updating channel state zwave:device:158964d7947:node28:alarm_general to ON [OnOffType]

However it doesn’t seem to update this ON/OFF value anywhere.

How can I fix this?

njogu · December 4, 2016, 9:09am

Hi Can you send working configuration? I’m not able to make the sensor work
Tks

njogu · December 4, 2016, 9:20am

The sensor respond always CLOSED …
But in the debug I have 2 different payload:
payload = 00 05 09 71 05 00 00 00 FF 06 16 00
and
payload = 00 05 09 71 05 00 00 00 FF 06 17 00

How can I intercept the Open & Closed situation?

Tks

mr_eskildsen · December 4, 2016, 9:18pm

The situation about this sensor has changed since my posting.
First of all you should check what version of the sensor you have (there is two version, which is very different). The new one is a Z-Wave Plus, where the old onbe isn’t. I belive that OpenHAB after some struggles finally supports both. Actually OpenHAB should initialise the device correctly, you can eventually do an reinitialise (please notice that it is a battery device so make sure to wake it up regulary until the process has finished).
It should not be needed to do any tweaks any more.

njogu · December 5, 2016, 11:20am

It doesn’t work …

16-12-04 16:08:21.976 [INFO ] [rialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------
2016-12-04 16:11:38.161 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.
2016-12-04 16:11:40.288 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.
2016-12-04 16:11:43.347 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.
2016-12-04 16:11:46.745 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.
2016-12-04 16:17:33.924 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.
2016-12-04 16:17:36.528 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.
2016-12-04 16:17:38.764 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.
2016-12-04 16:17:40.032 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.
2016-12-04 16:36:29.872 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.
2016-12-04 16:36:31.156 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.
2016-12-04 16:36:31.298 [WARN ] [.z.internal.ZWaveActiveBinding] - NODE 5: No item bound for event, endpoint = 0, command class = ALARM, value = 0, ignoring.

If I open or close the door the signal is always the same … I am not able to distiguish if the door is open or closed …

mr_eskildsen · December 5, 2016, 3:01pm

The log indicates that the alarm channel isn’t bound. That doesn’t matter because that does not contain the state. To be honest, i am not using the alarm channel. For the NEW FGK-10X I have the following mapping:

Switch sensorWindow1 "Windows1 [%s]" { channel="zwave:device:382d29d2:node29:sensor_binary"}

And for the old sensor I do this:

Contact sensorWindow2 "Windows2 [%s]" { channel="zwave:device:382d29d2:node12:sensor_door"}

That works for both in my case.

njogu · January 5, 2017, 3:49pm

another doubt … it is possible with this senso to read the door/window state? it is possible to know if the door is open? I am able to catch only tha state change of the sensor …

mr_eskildsen · January 5, 2017, 7:05pm

If you map the channel to an Item in openHAB, you can read the state at any time. The change of state can be used to trigger a rule.

Hope that gives sense

njogu · January 6, 2017, 12:15pm

It works! Tks!

Mike_Weiss · January 8, 2017, 5:37pm

I was not able to make the sensor work with z-wave addon till now. What solved my problems was using the z-way binding, which is in my opinion a great works. Thanks a lot for it!

anon83483981 · January 25, 2017, 3:55am

Hey guys, I’ve just received a new FGK101 with firmware v3.2, and it isn’t initializing properly (showing as ‘unknown’ in OH2).

Which version of the zwave plugin do I need to get it working properly, and where do I put this in OH2 (I’m using 2.0RC1).

It’s showing up as “Z-Wave Node 48 (010F:0701:3001:3.2)”.

chris · January 25, 2017, 5:52am

I’ve updated the database with these codes and will update the snapshot binding tonight. You will need to ensure you’re using the snapshot version to get this update…

anon83483981 · January 25, 2017, 8:07am

Sorry for the noob response, but how do I do that - where do I download the snapshot from? Do I need to install the entire OH2 snapshot package, or just the zwave addon snapshot?

chris · January 25, 2017, 9:10am

If you are using a fixed version runtime (as you are) then you will need to update to the snapshot runtime. If you are using the snapshot runtime, then to update the binding you just need to uninstall the binding and install it again.

anon83483981 · January 25, 2017, 9:21am

Is there any issue with running the 2.0RC runtime with the 2.1-SNAPSHOT addons (I’m using the Ubuntu repo on bintray)

chris · January 25, 2017, 9:36am

No - this should be fine, but I’m not sure how you will do it. When you install a binding using the UI, it will install the binding with the same version as your runtime. Maybe something else sorts this out for you…

anon83483981 · January 25, 2017, 9:38am

OK I’ll have a play, I did try upgrading to the snapshot runtime but my sitemap was all wacked (instead of actually showing my sitemap, it just listed every single Thing in order, with nothing else) so I reinstalled 2.0RC1.

Edit: It appears to just be the default sitemap (_default) that’s affected, if I copy and rename it to something else it’s fine.

anon83483981 · January 25, 2017, 7:44pm

I’ve uninstalled the binding and reinstalled, using the snapshot runtime - should this be enough to grab the version you updated last night?

chris · January 26, 2017, 7:13am

I suspect that the binding didn’t build, so it probably didn’t include the updates. I forced a build last night - hopefully that completed ok (I didn’t go back and double check).

anon83483981 · January 27, 2017, 10:22pm

Hey Chris, it still doesn’t seem to work, it’s now showing as ‘unknown device’ but without the node id in the title. What can I do next?