I will look to cache the state in the binding (ie in the XML) so that it’s retained between restarts, and for initial acquisition I think we have to assume that a notification is not triggered in every case. I think there’s no real option since we can read back the state.
Sigma told me that reading the state was not meaningful - I don’t agree with that, but at the end of the day we won’t be changing the zwave standard so we have to live with what’s available 
Is this really necessary? I think that’s what the persistence is for?! For the initial acquisition a binding-related solution would be fine, but I think for the restart scenario one can use persistence services.
There is a database that is just made for something like this. MAPDB will only store the last state of the items that are configured to be persisted.
No, but it’s how the system works, so might as well make use of it. This is done for alarms, configuration, associations etc already…
Yes - I’m very aware of this and other solutions, but as above we already store the device state in the XML already so I might as well use it and avoid questions that I get right now…
Hi Chris,
don’t get me wrong, I certainly don’t want to rush you, but do you leave a note here when you made the necessary changes? I don’t want to try every new snapshot version… 
Hi Chris,
I’m suffering on the same issue with the Fibaro Smoke Sensors.
I also get false alarms when the smoke sensor is waking up, and sending his current status.
As I read above, you’ve fixed the issue in a nightly version of the zwave binding 2.x.
I’m currently running openhab 2.0 stable version and I’m roughly new in openhab2.
So I don’t know how to upgrade a single binding.
Could you please advise me what do?
I need to know:
One further question:
In which files are the values of the zwave devices stored on openhab2 system?
It would be nice, if you could assist me…
Thanks a lot
Regards.
Helmut
Will do - I’ll try and take a look at this over the weekend - we had a long power outage here last night / today so haven’t done much except recover crashed hard disk tonight! :(.
No - further changes are needed.
If you’re using the snapshot version of OH2, then just uninstall zwave and reinstall again.
Through PaperUI or HABmin.
I’m not sure what you mean by ‘values’? Data is typically stored in persistence databases if that’s what you mean?
Hi,
thanks for quick response.
I’m not sure, which version i’am using.
My openhabian says, I’m running on openhab 2.0.0-1
I think that is no snapshot? (I think it’s the stable version)
Can I update the zwave binding manually?
With values I mean:
Is there any possibility to see, which values are sent by a zwave device?
Hmm - still not really sure what you mean. If you want to see the data being sent by the device, then you should look at the logfile. That’s about the only place this raw data is provided.
yes, that’s what I’m looking for 
Where is log file located? Sorry but I’m really new…
Further questions:
I’m not sure, which version i’am using.
My openhabian says, I’m running on openhab 2.0.0-1
I think that is no snapshot? (I think it’s the stable version)
Can I update the zwave binding manually?
This is, what PaperUI is currently showing me:
Does a reinstallation really helps?
http://docs.openhab.org/administration/logging.html
You can, but it’s not so easy. You need to uninstall the binding, and add the new binding into the addons folder. You probably also need to manage dependancies - ie the serial driver - which will also need to be added before the binding will start.
OK,
so what is the best solution to get the smoke detectors working?
Should I change from stable version of openhab2 to snapshot?
How does this work?
… or should I wait for next stable version? If so, when will it come?
Personally, I would, but that’s my preference ;).
Probably another couple of months - the plan is nominally around every 3 months.
OK, than I will move to a snapshot release.
I’m currently running openhabian.
How can I move from stable to snapshot release?
I which version of the zwave binding the false alarm issue is fixed?
I’d suggest taking a look in the docs -:
http://docs.openhab.org/installation/index.html
As I said above, it’s not fixed yet ;).
OK, thanks a lot.
So I’ll wait until the error will be fixed. If you have a fixed version, which must be tested, I’ll do so
How do I get the information that the error is fixed?
Will the fixed version be available on the stable 2.0. release?
It should be a few days - either keep an eye on Github commits or ask here in a bunch of days.
No. It will be in 2.1 stable.
OK thanks a lot for you patience…
I’ll look in a few days…
In the meantime, I will have a look on how to change to snapshot release…
@helmar74, you can switch from stable to snapshot (=unstable) using these commands (doing this within the openhabian tool is not yet supported):
wget -qO - 'https://bintray.com/user/downloadSubjectPublicKey?username=openhab' | sudo apt-key add -
echo 'deb http://dl.bintray.com/openhab/apt-repo2 unstable main' | sudo tee /etc/apt/sources.list.d/openhab2.list
sudo apt-get update
sudo apt-get install openhab2
All the settings will be kept, but it’s never wrong to make a backup before.
I’ve done this a couple of days ago, exactly because of the same reason. I’m waiting for the fix for these smoke sensors.