# Fibaro FGSD 002 not getting data **URL:** \ **Category:** Runtime\ **Tags:** error, zwave1, fibarosmoke\ **Created:** [January 6, 2017, 8:11pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665 "2017-01-06T20:11:41Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![MrBoggi](https://community.openhab.org/letter_avatar_proxy/v4/letter/m/d6d6ee/32.png) [@MrBoggi](https://community.openhab.org/u/MrBoggi)\ **Post date:** [January 6, 2017, 8:11pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/1 "2017-01-06T20:11:41Z")
Hi I have 9 Fibaro Smoke detectors, FGSD-002. All get included OK but I do not get any values from any of them. When I included them, they all got discovered as smokedetectors: ![](https://community-openhab-org.s3-eu-central-1.amazonaws.com/original/2X/3/3904d015fdbd20b7d3e22ed64a54bb91bba7d8ee.png) I have added items, or added them when linking but I do not get any values. I have tried waking up the devices standing right next to the z-wave stick but without any luck. My log shows the following: ![](https://community-openhab-org.s3-eu-central-1.amazonaws.com/original/2X/e/e5e1a995e2bb37dbbe865d442422c01ac9a9d4bd.png) It is the same for all items added to all smokesensors. I do not have problems with any other devices. Any good advice out there? I’m running OpenHab2 on a virtual computer running Ubuntu 16.04. //Morten ---
**Author:** ![jaydee73](https://community.openhab.org/letter_avatar_proxy/v4/letter/j/8edcca/32.png) [@jaydee73](https://community.openhab.org/u/jaydee73)\ **Post date:** [January 6, 2017, 8:41pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/2 "2017-01-06T20:41:09Z")
Which version of OH2 (and the zwave binding) do you use? The smoke sensor seems to be a little “special” to get it going and Chris made some changes to the binding recently. Maybe you haven’t the latest version? And have you added them just in the last minutes/hours? If so, let them wake up some more times (preferrable the automatic wakeup, not the triggered one). There is some data to be transferred and maybe the device “needs some time”. ---
**Author:** ![MrBoggi](https://community.openhab.org/letter_avatar_proxy/v4/letter/m/d6d6ee/32.png) [@MrBoggi](https://community.openhab.org/u/MrBoggi)\ **Post date:** [January 6, 2017, 9:06pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/3 "2017-01-06T21:06:42Z")
I run version: 2.0.0~20170103034422 of OH2. Not shure where to find the version of the binding. I first added all a couple of days ago. Yesterday I removed them all with “exclude devices” and added them again. So they all have been connected for aprox 24 hours now. What I see on all of them is: ![](https://community-openhab-org.s3-eu-central-1.amazonaws.com/original/2X/0/0580cb36bf0fa53d92d1a5cd538a7b9cf76d5a8a.png) And for wakeup interval: ![](https://community-openhab-org.s3-eu-central-1.amazonaws.com/original/2X/5/5bd87d1a414f30ba3e300141cca8faabd37693c7.png) Not shure how it handles the 0 sec. update interval. For now I try to get one up and running before I try the other ones but this one has had the “pending” for 24 hours now.. I have used the smoke sensors in Homeseer and there it was no problems getting the data. ---
**Author:** ![jaydee73](https://community.openhab.org/letter_avatar_proxy/v4/letter/j/8edcca/32.png) [@jaydee73](https://community.openhab.org/u/jaydee73)\ **Post date:** [January 7, 2017, 8:12am UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/4 "2017-01-07T08:12:23Z")
> [@MrBoggi](#): > > I run version: 2.0.0~20170103034422 of OH2. This should be ok. > [@MrBoggi](#): > > Yesterday I removed them all with “exclude devices” and added them again. This also could be a problem. Have you also resetted the device itself? I did the same with my smoke sensor and have realized that they were nevertheless some “artifacts” left on the controller. Every new inclusion was successful, but I couldn’t communicate with the device. I had to use a tool called Zensys to remove the old nodes. See here: > [@Remove a ghost Z-Wave Node from HABmin](https://community.openhab.org/t/remove-a-ghost-z-wave-node-from-habmin/6640): > > Hi, I have a ghost/zombie node in my Aeon Labs Z-Wave controller. The node is the result of a battery-device that ran out of battery. I had to reinclude the node, but the original node could not be removed using the exclusion proccess. I was able to include the node again, but I was unable to exclude the node before the new inclusion. The thing is that I have two nodes for the same device. One works fine. The other is a ghost node. I would like to know if it is possible to delete this ghost … You can check if this is also your problem by enabling DEBUG logging and then do a manual wakeup of the sensor (tripple button press). Does this produce any logging informations? If so, then it’s alright. If not, you might have the same problem as me. > [@MrBoggi](#): > > For now I try to get one up and running before I try the other ones This is a good approach. ---
**Author:** ![MrBoggi](https://community.openhab.org/letter_avatar_proxy/v4/letter/m/d6d6ee/32.png) [@MrBoggi](https://community.openhab.org/u/MrBoggi)\ **Post date:** [January 8, 2017, 12:56pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/5 "2017-01-08T12:56:46Z")
Ok.. So now I have deleted ALL my smokesensors and shadows of them with zentool. Then I tried adding one. It came up OK in “inbox” so I added it as a thing and added a couple of items. So far so good… ![](https://community-openhab-org.s3-eu-central-1.amazonaws.com/original/2X/2/2594114f9137a2901257596e4ef81d0d5d9d2edb.png) Then I check some parameters because I do not get any values. First is wakeup interval that is 0. Try to set it to i.e 60: ![](https://community-openhab-org.s3-eu-central-1.amazonaws.com/original/2X/8/8b77b9402c0e43bb3f384e78823133af1e8692e8.png) It has been stuck at pending for over 1 hour. Then I check Association Groups. All empty so I try to set OpenHab to the 1 group: ![](https://community-openhab-org.s3-eu-central-1.amazonaws.com/original/2X/7/7789a3c34057d90001599390296e6740bd5ab855.png) Also stuck at “pending”. I have tried waking up the device about 50 times standing right next to the Z-wave stick… The FGSD002 seems to be impossible to get to work ☹ Anyone got any good advice? //Morten ---
**Author:** ![jaydee73](https://community.openhab.org/letter_avatar_proxy/v4/letter/j/8edcca/32.png) [@jaydee73](https://community.openhab.org/u/jaydee73)\ **Post date:** [January 8, 2017, 3:29pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/6 "2017-01-08T15:29:36Z")
Maybe I have one. 😉 In fact, I do expect a similar behavior with the recent build. I hope it’s related to a minor code-change in the binding. I’m talking to Chris about this issue here: > [@Fibaro smoke sensor (FGSD-002) / Not getting all values from the device](https://community.openhab.org/t/fibaro-smoke-sensor-fgsd-002-not-getting-all-values-from-the-device/15032): > > Hi @chris, I am using the Fibaro smoke sensor (FGSD-002) for my OpenHAB2 installation (previously running successfully on OH1). The device is fully recognized as a thing (node 8) and all channels are found. I want to get the following values from the device to use them in my items/sitemap file: alarm\_smoke alarm\_heat battery-level sensor\_temperature Except alarm\_heat everything works fine. But I can’t get any value from the device for alarm\_heat. Can you please have a look at the debug f… Let’s see if he can figure it out. Don’t give up. The device has worked properly before. So we will get this going again. ---
**Author:** ![MrBoggi](https://community.openhab.org/letter_avatar_proxy/v4/letter/m/d6d6ee/32.png) [@MrBoggi](https://community.openhab.org/u/MrBoggi)\ **Post date:** [January 8, 2017, 4:56pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/7 "2017-01-08T16:56:15Z")
Great. Looking forward to feedback and maybe a solution. I have 10 of them 😛 ---
**Author:** ![jaydee73](https://community.openhab.org/letter_avatar_proxy/v4/letter/j/8edcca/32.png) [@jaydee73](https://community.openhab.org/u/jaydee73)\ **Post date:** [January 9, 2017, 5:20pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/8 "2017-01-09T17:20:51Z")
I’ve made some (quite positive) progress with my re-adding of the sensors. See the link above and my latest answer to chris. After the re-add and two manual wakeups, I got the device initialized and the xml was created. Maybe you’ll give it a try and try it yourself? ---
**Author:** ![MrBoggi](https://community.openhab.org/letter_avatar_proxy/v4/letter/m/d6d6ee/32.png) [@MrBoggi](https://community.openhab.org/u/MrBoggi)\ **Post date:** [January 9, 2017, 8:22pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/9 "2017-01-09T20:22:47Z")
> [@jaydee73](#): > > See the link above and my latest answer to chris. Hmmm… What answer are you refering to here? Kind of lost now 😄 ---
**Author:** ![jaydee73](https://community.openhab.org/letter_avatar_proxy/v4/letter/j/8edcca/32.png) [@jaydee73](https://community.openhab.org/u/jaydee73)\ **Post date:** [January 10, 2017, 1:11pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/10 "2017-01-10T13:11:04Z")
This one: > [@Fibaro smoke sensor (FGSD-002) / Not getting all values from the device](https://community.openhab.org/t/fibaro-smoke-sensor-fgsd-002-not-getting-all-values-from-the-device/15032/39): > > Well, here is what I found out: I upated through apt-get and had to switch the mechanism to the new repository at bintray first. Before I had: 195 | Active | 80 | 2.0.0.201701071314 | ZWave Binding And after the update/upgrade: 195 | Active | 80 | 2.0.0.201701071702 | ZWave Binding So only a slighty newer build. But gladly your changes were implemented in the newer build (at least I think so). Initialisation went well and I also got the xml files soon afterwards. I got a wakeup… You should: - delete the thing and the node xml (only if the device was fully initialized. Otherwise I would suggest to exclude it again and also delete all shadows in the controller, followed by a reset of the device) - update/upgrade your installation to get the latest zwave binding (yours is from 2017/01/03 and the probably necessary changes in the binding were on 2017/01/09 (be aware of the latest changes in the repository structure yesterday!)) - check if you have the latest binding (log into the karaf console and type bundle:list to get a full list of all installed packages). - re-add the device (or include it again, based on what you did above). Check the configuration parameters. Do update/change them if necessary. Wake it up 2-3 times (for me 2 times were enough) and see if the xml was created. ---
**Author:** ![MrBoggi](https://community.openhab.org/letter_avatar_proxy/v4/letter/m/d6d6ee/32.png) [@MrBoggi](https://community.openhab.org/u/MrBoggi)\ **Post date:** [January 10, 2017, 1:36pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/11 "2017-01-10T13:36:35Z")
Ok. I will give it a try in a few hours. I belive it is fully initialized so deleting the thing and xml is my first try. Thanks for the good instructions > [@jaydee73](#): > > be aware of the latest changes in the repository structure yesterday! What changes do I need to be aware of? Will a normal > ``` > sudo apt-get update > sudo apt-get upgrade > > ``` be enough? ---
**Author:** ![jaydee73](https://community.openhab.org/letter_avatar_proxy/v4/letter/j/8edcca/32.png) [@jaydee73](https://community.openhab.org/u/jaydee73)\ **Post date:** [January 10, 2017, 1:52pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/12 "2017-01-10T13:52:08Z")
> [@MrBoggi](#): > > deleting the thing and xml is my first try. If an xml is there, it should be fully initialized. > [@MrBoggi](#): > > Will a normal > > sudo apt-get update > sudo apt-get upgrade > be enough? No. The apt-get repository switched over from cloudbees to bintray yesterday. And another change has happened. See this both threads: > [@Replacement of the Apt Snapshot Repository](https://community.openhab.org/t/replacement-of-the-apt-snapshot-repository/19674/): > > This thread is since outdated. The openHAB snapshots/unstable builds have once again moved to a less restricted repository. The announcement below is superseded. To always find the latest installation instructions, please consult the official documentation. The following article will always be up to date: [http://docs.openhab.org/installation/linux.html#package-repository-installation](http://docs.openhab.org/installation/linux.html#package-repository-installation) All, good news but also a breaking change for the “snapshot apt repository” users: From now on the openHAB … > [@A single distro from now on!](https://community.openhab.org/t/a-single-distro-from-now-on/19903): > > All, Today we again have a major update of the openHAB distro. I worked heavily on [a bigger refactoring](https://github.com/openhab/openhab-distro/pull/369) during the last days, which resulted in a single distro, so that users no longer have to choose between online and offline distro. You can find the snapshot builds [on our Jenkins at Cloudbees](https://openhab.ci.cloudbees.com/job/openHAB-Distribution/) - it is now simply called openhab-2.0.0-SNAPSHOT.zip/tar.gz. If you download this, it will behave the same way as the online distro before, i.e. it does not include any add-ons, but will load them on d… So you should get your standard OH installation up-to-date first. If you made all the necessary changes, you can use apt-get update/upgrade again. And after that, continue with the Fibaro problem. ---
**Author:** ![DrLaban](https://community.openhab.org/letter_avatar_proxy/v4/letter/d/9de053/32.png) [@DrLaban](https://community.openhab.org/u/DrLaban)\ **Post date:** [January 10, 2017, 3:36pm UTC](https://community.openhab.org/t/fibaro-fgsd-002-not-getting-data/19665/13 "2017-01-10T15:36:12Z")
I did the switchover now. I’m not sure if its just a placebo effect, but the whole zwave part seems much faster now. The traffic between the devices after a server reboot is over after a few minutes. Earlier this could take 30 mins or more before everything settled.