I have gotten the device propperly registered with my zwave network, so far so good. I can see the following in my zwave debug log when opening an closing the magnet sensor.
I have configured a item like this Contact Door_GF_Hall_zw "Inngangdør [%s]" <frontdoor> (Doors) {zwave="29:command=sensor_binary,sensor_type=10"}
and i sitemap entry like Text item=Door_GF_Hall_zw label="Inngangdør [%s]"
The problem is that the door is reported to be OPEN, regardless of what state sent by the sensor.
I can see som entries in the zwave log that might point out a problem, but I’m not have the proper zwave skils to understand what the problem might be.
Hi, and thanks a ton for helping out. Highly appreciated!
Actually I got it working by using the following binding config.
29:command=sensor_binary,respond_to_basic=TRUE
Now status is updated with OPEN or CLOSED according to the sensor position, except in one situation. I I closed the door “with a slam” like my kids have a tendency to do, the led on the door sensor starts to blink blue for like 4-5 seconds (like the tamper button has been release), and then the door i still listed as OPEN in OpenHAB. The tamper button underneath the sensor cannot be release by a slam, because I have mounted the sensor with screws that are pretty good tightened. Is there a vibration sensor in the device that can be disabled, it doesn’t look like that to me?
Greetings,
I’m also testing this device but I’m having some issues.
I have two FGK-10x sensors: one with the 2.5 firmware and the other with v3.2.
While the one with the older firmware works flawlessly, the other one fails to be properly recognized by the zwave binding.
During discovery it is being reported as Z-Wave Node 7 (010F:0701:1001:3.2) and then no channels nor properties pop up in the thing configuration.
The version of the zwave binding I’m using is 2.0.0.201607010102.
Should I open an issue for this?
On closer inspection, the newer version you have is totally different to the older version. It looks like all the parameters and some command classes are different.
just for clarifying, if you explain to me what to do a little bit in detail, I will try do this, I found an entry of the old one of the sensor (til version 2.5?) one in your database. Do I have create an account and modify these version with the parameters of the new version? There is only a short description in the sensor box, I had to download the detailed version from fibaro, don’t know it this version the current valid one?
I’ve created the new version here. Looking at the manual, the parameters are totally different to the previous version, so someone will need to add them by hand (ie we can’t really copy the old ones and then modify a couple of them to make them the same as the new device).
I also attached the manual to the database at the link above (the manual is at the bottom of the page).
So, you will need to create an account on the database site, then let me know and I’ll give you access to edit. From here there are two things to do - firstly, if OH has created an XML file (in the /etc/zwave folder for OH1) then upload this to the site using the tools button at the top right of the page (select “Update Device”). Then you will need to manually add the parameters and the options, and also the association groups - these should all be listed in the manual, so it’s “simply” a case of adding them to the database (it should be easy, but it will take a bit of time).
Let me know if that makes sense. There is a database overview on the site with some information, or if you have questions, just fire away and I’ll hopefully be able to answer them…
where do I find the xml there is no etc/zwave … my folders are:
openHAB-System: cd /usr/share/openhab
Addons: cd /usr/share/openhab/addons
Konfigurationsdateien cd /etc/openhab/configurations
Log-Files: cd /var/log/openhab
I uploaded the xml and fillied in the parameters from the manual. Regarding the associations, there are only headlines in the manual. Please check my work and let me know how we go one.
).