I’m a little confused. You’re using a sensor_binary channel in this item definition, but the device database entry for the FGK101 v2.5 shows there is no sensor_binary channel, only a sensor_door channel.
The device database entry shows that there is no alarm_tamper channel. If you can post a debug log showing that the device produces a tamper alarm, we can update the database to add that channel.
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:
That one which I do not touch and was configered in Z-Wave binding 2.0 shown me more channels
Shows me all my used channels in habmin. Something must be wrong with habmin settings? Or database.
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 other devices still stay at old config. The old once still working. For me it looks like there is a change in the database. On chris homepage I cannot see this change. looks still good.
I now deleted the device again, deleted the xlm-file and added again. No new xlm-file is created. Is this correct?
The only thing I can think of is that between the time when you originally added the device to your system (2 years ago?) and when you installed 2.3, the database changed for that device. Then by deleting and readding the device, you picked up the database definition that came with 2.3.
You need to manually wake up the device until it is fully initialized. Once fully initialized, it will write out the node.xml.
OK, what should I do to fix it? In chris database it looks good. Should I ask him directly?
My suggestion would be to update to a recent 2.4 Milestone or Snapshot release. It will be much easier to debug any issues.
What you see in the database today is the state of that device as of today, not what it might’ve been some time in the past.
Yes, you certainly could ask @chris. I’ll go out on a limb and say that he’ll probably suggest you upgrade to a 2.4 Milestone or Snapshot release.
Good guess 
It’s hard to comment too much about code that is so old. It would be good if you can update to 2.4 - shortly (a few weeks) there will be 2.4 final - if there is a bug, then it would be good to fix it before it is released otherwise people will have to wait another 6 months for the next release.
Thanks for the reply. Can I use the z-wave 2.4 binding with my OH 2.3 installation?
Steps to do (as i remember from other posts)
Is there a way back if it will not work? I have 40 door/window sensors and a lot of other z-wave devices which should work after the update. If not, my wife will kill me 
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.
So I first create a test system and plug in my z-wave stick there. Will report what happens. But it takes some time.
Solved with newest z-wave snapshot, but other problems occur.
see:
