[SOLVED] Fibaro Door/Window sensor 2 (FGDW-002) not sending door open

Just install the zwave binding through PaperUI or HABmin (after having it removed from addons folder).
This will only work if you are on a Milestone (at least M4) or a snapshot version of openHAB.

If you are on an old openHAB build (2.3 or something) you need to dl the jar and drop it into your addons folder:

https://ci.openhab.org/job/openHAB2-Bundles/org.openhab.binding$org.openhab.binding.zwave/

Yes - I believe you can do this through the openhabian config software (I’m not a user of openhabian myself so can’t say in detail).

Thanks @sihui

What I did so far

  • stopped openhab
  • deleted the jar from the addon folder
  • started openhabian-config
  • Ran
    ** 01 Update (the tool)
    ** 02 Upgrade system (and started sweating when I noticed how much was happening to my system :wink: but all went well)
    ** 03 Openhab stable

So now I am on

  • openhab 2.4.0~20180616001001-1
  • zwave binding 2.3.0.201806262322

As you can see the zwave binding is installed but on 2.3

How do I get to OH M4?

cheers
Stefan

I have no idea how to do that with openHABian, never used that, sorry.
But I’m pretty sure a search in this forum will help …

Yeah, that’s what I guessed:

openhabian-config shows the following options (release is installed at the moment on my system):

41

  • openHAB release Install or switch to the latest openHAB release
  • openHAB testing Install or switch to the latest openHAB testing build
  • openHAB snapshot Install or switch to the latest openHAB SNAPSHOT build

If you refer to M4 do we talk about testing or Snapshot build?

I think it is testing. Snapshot will give you the very latest, and the testing/milestone builds are updated every month.

1 Like

@chris @sihui

  • I used openhabian-config
  • Option 41: openhab testing

the following shows that it retrieves M4

Get:1 [https://dl.bintray.com/openhab/apt-repo2 testing/main](https://dl.bintray.com/openhab/apt-repo2%20testing/main) armhf openhab2 all 2.4.0~M4-1 [74.8 MB]
  • Note that in this case the zwave binding was “lost” and had to reinstalled via paper ui!

Unfortunately now the trouble begins:

  • I am getting jetty exceptions regularly (I checked all postings around this but couldn’t really find a good solution which might point into the right direction)
An I/O error has occurred while writing a response message entity to the container output stream.
  • I deleted the Fibaro motion sensor and searched for it again and… it did NOT come up anymore.

Then I manually restarted the OH service

  • and it was found
  • and (knock on wood) I haven’t seen the exception again within the last 10 minutes.

BUT the real bad news is that the Motion Sensor (even though ONLINE) does not send anything (at least nothing is shown in the ZWave Debug output) when I a motion is happening and the LED shows that it has recognized it.

:cry:

I can suggest three things -:

  1. Delete the thing, and add it back (not excluding/including). This will ensure you have the latest thing definition.
  2. Reinitialise the device - there’s an option in HABmin/PaperUI if you enable advanced mode, called “reinitialise device” (or similar) select this. This will make the binding reconfigure the device.
  3. Exclude and reinclude. Sometimes during the reinitialising, the binding doesn’t detect a subtle change in associations and doing this completely clears things.

I would suggest to keep debug logs of these actions, and if they don’t resolve the problem, I will take a look at them.

re 1: I had done that before

re 2: Do you refer to “Heal the device?”

image

No - it’s called “Reinitialise device” or something like that. As I said, you need to enable advanced mode.

Ah - I see advanced mode is enabled. This means the device has not finished initialisation then.

We are slowly getting there! :smiley:

  • I pressed the button on the device three times which triggers wake up and sending initialisation data
  • and guess what, all of a sudden the menu entry “reinitialise the device” appears (so you were right that the device was not initialised… it is now)
  • and I received a few values: temperature, luminance and battery
  • but unfortunately not the motion and tamper

(bad luck, btw, through installing M4 the debug mode was switched off - I have now turned it back on again)

PS:
btw, I am so “talkative”, so in the case someone else runs into the same problem they can follow exactly what I was doing

So there is really nothing at all received? It’s not sending something, that the binding is not interpreting?

Can you post the attributes for your device so I can see exactly what it is (ie firmware version, type and ID are needed at least)

Good idea :slight_smile:

yes, that seams to be the case

2018-10-28 15:00:41.417 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 51: Application update request. Node information received. Transaction null
2018-10-28 15:00:41.419 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 51: resetResendCount initComplete=true isDead=false
2018-10-28 15:00:41.421 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 51: Application update - no transaction.
2018-10-28 15:00:41.685 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 51: Is awake with 0 messages in the queue
2018-10-28 15:00:41.688 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 51: Start sleep timer at 1000ms
2018-10-28 15:00:41.690 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 51: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2018-10-28 15:00:41.712 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 51: Node Status event - Node is AWAKE
2018-10-28 15:00:42.190 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 51: WakeupTimerTask 0 Messages waiting, state DONE
2018-10-28 15:00:42.690 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 51: WakeupTimerTask 0 Messages waiting, state DONE
2018-10-28 15:00:42.693 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 51: No more messages, go back to sleep
2018-10-28 15:00:42.696 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 51: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2018-10-28 15:00:42.698 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 51: SECURITY not supported
2018-10-28 15:00:42.703 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 51: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2018-10-28 15:00:42.705 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 51: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@e0718f
2018-10-28 15:00:42.710 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 51: Bump transaction 670 priority from Immediate to Immediate
2018-10-28 15:00:42.713 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 51: Adding to device queue
2018-10-28 15:00:42.716 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 51: Added to queue - size 8
2018-10-28 15:00:42.732 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 51: Sending REQUEST Message = 01 09 00 13 33 02 84 08 25 99 E4 
2018-10-28 15:00:42.773 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 51: sentData successfully placed on stack.
2018-10-28 15:00:42.779 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 51: TID 670: Transaction not completed
2018-10-28 15:00:42.809 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 51: SendData Request. CallBack ID = 153, Status = Transmission complete and ACK received(0)
2018-10-28 15:00:42.812 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 51: resetResendCount initComplete=true isDead=false
2018-10-28 15:00:42.818 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 51: Response processed after 80ms
2018-10-28 15:00:42.820 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 51: TID 670: Transaction completed
2018-10-28 15:00:42.822 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 51: notifyTransactionResponse TID:670 DONE
2018-10-28 15:00:42.824 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 51: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-10-28 15:00:42.827 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 51: Went to sleep COMPLETE

and that was while I was moving before it.

What exactly do mean with attributes? These properties?

|dbReference|115|
|---|---|
|defaultAssociations|3|
|manufacturerId|010F|
|manufacturerRef|0800:1001,0800:2001,0800:3001,0801:1001,0801:2001|
|modelId|FGMS001|
|vendor|Fibargroup|
|versionMax|2.8|
|zwave_beaming|true|
|zwave_class_basic|BASIC_TYPE_ROUTING_SLAVE|
|zwave_class_generic|GENERIC_TYPE_SENSOR_BINARY|
|zwave_class_specific|SPECIFIC_TYPE_ROUTING_SENSOR_BINARY|
|zwave_deviceid|4097|
|zwave_devicetype|2048|
|zwave_frequent|false|
|zwave_lastwakeup|2018-10-28T14:00:41Z|
|zwave_listening|false|
|zwave_manufacturer|271|
|zwave_neighbours|1,3,4,10,18,19,20,21,22,23,30,40,41|
|zwave_nodeid|51|
|zwave_routing|true|
|zwave_secure|false|
|zwave_version|2.7|

Can you also provide the XML file for this node (in the userdata/zwave folder).

Thanks

Sure
network_fed4ea89__node_51.xml (19.7 KB)

I don’t see anything wrong here. With this device, which is one of the older, non ZWave-Plus devices, it supports the association group 3 for sending reports to the controller. This must be configured ok as you are getting temperature and luminance, and this is the only group that will send these messages.

I guess we should double check that these sensor readings are being sent by the device without polling, otherwise these could be received without the association being set.

What would be useful is to see the debug log I mentioned above when you were doing the reinitialisation. This would confirm (or not) that the group is set.

So it would make sense to delete the device and add it again?