Fibaro Door Window contact FGK-10x

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?

anon83483981 · February 3, 2017, 8:57pm

Hi again Chris,

Sorry but even on snapshot 2.1.0~20170203040910-1 the zwave node is named “Z-Wave Node 55 (010F:0701:3001:3.2)”.

Please help!

chris · February 3, 2017, 9:07pm

It looks like it should be included -:

github.com

openhab/org.openhab.binding.zwave/blob/master/ESH-INF/thing/fibaro_fgk101_3_2.xml#L62


      <property name="binding:*:OnOffType">SENSOR_ALARM;type=GENERAL</property>
    </properties>
  </channel>
</channels>


<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
  <property name="vendor">Fibargroup</property>
  <property name="modelId">FGK101</property>
  <property name="manufacturerId">010F</property>
  <property name="manufacturerRef">0701:1001,0701:3001,0701:2001</property>
  <property name="versionMin">3.2</property>
  <property name="dbReference">381</property>
  <property name="defaultAssociations">1</property>
</properties>


<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>


  <!-- PARAMETER DEFINITIONS -->
  <parameter-group name="configuration">

I suspect there might be an issue where versions are equal - I’ll take a look…

chris · February 3, 2017, 9:18pm

FTR.

anon83483981 · February 3, 2017, 11:17pm

Thank you! When will it build so I can update my snapshot and test?

chris · February 3, 2017, 11:20pm

Shortly - the build is in progress… Give it a go in an hour or two (or tomorrow morning if you’re in Europe).

anon83483981 · February 3, 2017, 11:49pm

I’ve just looked in my debug logs and it has:

2017-02-04 12:48:13.740 [DEBUG] [inding.zwave.internal.ZWaveActivator] - Z-Wave binding started. Version 2.1.0.201701231811

I’ve been updating from the Ubuntu repo on bintray, though, so I’m not sure why it’s saying that. Is there a cache of addons I need to remove when I install the new package?

EDIT: I’ve managed to install the correct version of the addon by installing additionally the openhab2-addons package.

Subsequently, I’m now using v2.1.0.201702020955 of the addon, and it’s now recognized the Fibaro sensor.

2017-02-04 13:07:39.781 [DEBUG] [inding.zwave.internal.ZWaveActivator] - Z-Wave binding started. Version 2.1.0.201702020955

2017-02-04 13:08:34.583 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 56: Device discovery resolved to thingType zwave:fibaro_fgk101_03_002

I’m not sure if this means the commit you just made isn’t needed, but a sincere thanks for your help with this.

meyju · March 8, 2017, 2:32pm

Hi,

just received my Fibaro FGK-10x and can not bring it to work properly. The initialisation seems ok for me. I created an item for sensor_door and one for sensor_binary and linked it again the Thing.

‘sensor_door’ stays everytime on ‘CLOSED’ state.

In the log I can see the following error:
[ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 11: Endpoint 0 not found. Cannot set command classes.

I attached the xml file node11.xml (19.6 KB) and the debug log looks like this (where I open and close the sensor):

2017-03-08 14:58:52.377 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 04 00 0B 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00 19
2017-03-08 14:58:52.393 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-08 14:58:52.404 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 13 00 04 00 0B 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00 19
2017-03-08 14:58:52.410 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 13 00 04 00 0B 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00 19
2017-03-08 14:58:52.416 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0B 0D 60 0D 00 00 71 05 00 00 00 FF 06 17 00
2017-03-08 14:58:52.422 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 11: Starting initialisation from DONE
2017-03-08 14:58:52.425 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1d6894d already registered
2017-03-08 14:58:52.431 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 11: Received MULTI_INSTANCE command V0
2017-03-08 14:58:52.434 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 11: Requested Command Class = ALARM (0x71)
2017-03-08 14:58:52.437 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 11: Endpoint 0 not found. Cannot set command classes.
2017-03-08 14:58:52.459 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 08 0B 03 30 03 00 C1
2017-03-08 14:58:52.464 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-08 14:58:52.469 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 08 0B 03 30 03 00 C1
2017-03-08 14:58:52.473 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 08 0B 03 30 03 00 C1
2017-03-08 14:58:52.478 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=08 0B 03 30 03 00
2017-03-08 14:58:52.482 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 11: Starting initialisation from DONE
2017-03-08 14:58:52.484 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1d6894d already registered
2017-03-08 14:58:52.484 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 0B 03 30 03 00 C9
2017-03-08 14:58:52.485 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 11: Received SENSOR_BINARY command V1
2017-03-08 14:58:52.486 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 11: Sensor Binary report, type=Unknown, value=0
2017-03-08 14:58:52.488 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveBinarySensorValueEvent
2017-03-08 14:58:52.489 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2017-03-08 14:58:52.491 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 0
2017-03-08 14:58:52.493 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:ea3e020e:node11:sensor_binary to OFF [OnOffType]
2017-03-08 14:58:52.498 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-08 14:58:52.500 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 0B 03 30 03 00 C9
2017-03-08 14:58:52.504 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 0B 03 30 03 00 C9
2017-03-08 14:58:52.509 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0B 03 30 03 00
2017-03-08 14:58:52.515 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 11: Starting initialisation from DONE
2017-03-08 14:58:52.518 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1d6894d already registered
2017-03-08 14:58:52.524 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 11: Received SENSOR_BINARY command V1
2017-03-08 14:58:52.527 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 11: Sensor Binary report, type=Unknown, value=0
2017-03-08 14:58:52.530 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveBinarySensorValueEvent
2017-03-08 14:58:52.534 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2017-03-08 14:58:52.537 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 0
2017-03-08 14:58:52.540 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:ea3e020e:node11:sensor_binary to OFF [OnOffType]


2017-03-08 14:58:57.311 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 04 00 0B 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00 18
2017-03-08 14:58:57.318 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-08 14:58:57.323 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 13 00 04 00 0B 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00 18
2017-03-08 14:58:57.327 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 13 00 04 00 0B 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00 18
2017-03-08 14:58:57.331 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0B 0D 60 0D 00 00 71 05 00 00 00 FF 06 16 00
2017-03-08 14:58:57.335 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 11: Starting initialisation from DONE
2017-03-08 14:58:57.337 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1d6894d already registered
2017-03-08 14:58:57.341 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 11: Received MULTI_INSTANCE command V0
2017-03-08 14:58:57.343 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 11: Requested Command Class = ALARM (0x71)
2017-03-08 14:58:57.345 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 11: Endpoint 0 not found. Cannot set command classes.
2017-03-08 14:58:57.393 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 08 0B 03 30 03 FF 3E
2017-03-08 14:58:57.398 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-03-08 14:58:57.404 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 08 0B 03 30 03 FF 3E
2017-03-08 14:58:57.407 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 08 0B 03 30 03 FF 3E
2017-03-08 14:58:57.411 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=08 0B 03 30 03 FF
2017-03-08 14:58:57.415 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 11: Starting initialisation from DONE
2017-03-08 14:58:57.416 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1d6894d already registered
2017-03-08 14:58:57.420 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 11: Received SENSOR_BINARY command V1
2017-03-08 14:58:57.422 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 11: Sensor Binary report, type=Unknown, value=255
2017-03-08 14:58:57.424 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveBinarySensorValueEvent
2017-03-08 14:58:57.425 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2017-03-08 14:58:57.427 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 255
2017-03-08 14:58:57.430 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:ea3e020e:node11:sensor_binary to ON [OnOffType]

I just changed the Association Group 1 Lifeline to “openHAB Controller” and wake up the sensor to sync properly.

I’m using openHAB2 Stable (from openHABian) with Binding Version 2.0.0. The Sensor has the Firmware Version 3.2 (as I can see in HABmin)

Hope someone can help me, find the problem…

Kind regards
Julian

chris · March 8, 2017, 2:45pm

Please make sure you are using the latest ZWave binding - it should solve the issue with the endpoint error.

anfaenger · March 8, 2017, 2:49pm

I’ve had the same problems a few weeks ago.

I did like @sihui and @chris suggested and that solved my problem:

meyju · March 8, 2017, 4:24pm

Thanks @anfaenger & @chris, I updated to the Snapshot version and now the sensor works as expected.

Now I have some other problems, like some Syntax errors in the Sitemaps and Item files but this is some diligence work…

Thanks again and this community is awesome

NilsAcht · March 14, 2017, 2:31pm

Hi, i also have this issue.

After some tips from this post i managed to see the “Closed” status on HABmin.

I removed the ZWAVE Biding and reinstalled it. Now i see “Closed”. But it never changed to open.

I am completly new to openHAB2 an would be thankfull if someone can halp me.

Thanks
Nils

anfaenger · March 14, 2017, 7:15pm

Did you check, what chris suggested?
To get, the newest version, I had to switch from stable to snapshot.

NilsAcht · March 15, 2017, 6:59am

Sorry but how did i Update to the snapshot? I’m using openHABian in the latest version.