I am struggling with the recent version of the Z-Wave-Dev-Branch (Dev-Snapshot 201710241752). I am using several FGK001 Fibaro Door/Window-Sensors which used to work well with the Dev-Snapshots. I just reincluded one device with the current binding and since then it does not report the door status …

If by “deleted the node” you mean deleted the XML file, then this won’t work - you need to do one of the following -: Stop OH, delete the node, start OH In the thing configuration, select the reinitialize node opton.

Ok, I tested now intensively the last different versions of the DEV binding in my test environment (same controller type, same FGK101 door sensor version, same OH2 snapshot version but only one node to speed up test cases) . The finding: FGK101 works only if included in the network with network wid…

@chris : And two more (hopefully useful) files: The xml generated by the DEV Snaphot version 20171024 which is NOT working (Node 181): network_d763b7a3__node_181.xml (22.8 KB) and here the xml generated by the DEV Snaphot version 20170918 which works perfectly (with all binding versions if inclusi…

@chris : Did you have a chance to look into this?

@chris I think I run into the same problem. I’m on OH 2.3 stable. I prepare for the migration to 2.4. For this I delete one sensor thing and added it again (no exclude/include). Now the sensor is not working as before. There must be a change in the database. Some of the channels are no longer there …

This is the XML-file from another one which is still working. But this one was not deleted and readded, config was from z-wave binding version 2.0. maybe this help. node58.xml (9.9 KB)

[image] HomeAutomation: Switch DoorSensor42_Binary "Fenster Wohnzimmer Links [%s]" <contact>(gMAPDB){ channel="zwave:device:15a7a49f3a6:node42:sensor_binary"} I’m a little confused. You’re using a sensor_binary channel in this item definition, but the device database entry for the FG…

Thanks for the reply. If I use habmin and try to add a new channel it gives me only: sensor_binary alarm_tamper battery-level and all old channels which work for over 2 years now, will not get any data anymore. Problematic device: [grafik] That one which I do not touch and was configered in…

Sorry, maybe I misunderstood your original post. I thought you were running a recent 2.4 version (milestone or snapshot)?

Sorry for misleading you. I’m on OH 2.3 stable. But I want to find out if I go to 2.4 (which causes the need for all my z-wave devices to delete and re-add) I had problems. So I deleted one of my perfect working sensors and re-add him again. Now the possible channels are totally different to the ot…

FGK001 stops working after (re)inclusion with Z-Wave-DEV-Binding

Add-ons Bindings

mhilbush (Mark) November 23, 2018, 4:50pm 32

I’m not sure. Someone else will have to weigh in on this.

It’s all described here.

Make a backup of your installation. Test your backup to make sure it works. Then install 2.4.

Welcome to my world. LOL. It’s always best to beg for forgiveness after the fact.

There are plenty of people here to help you through any issues.