Forgive me I’m a novice in this topic. 
You won’t have to receive “new” data every 3 minutes to store it. If the value hasn’t changed, the persistence stores the same value again. And if the value has changed, the sensor reports it and with the next persistence cycle it will be persisted. Trust me, it works. You are making things far too complicate! 
Please refer to this post -:
You can have a look at my temperature chart. The green line is from the smoke sensor. I moved the sensor this morning from my bedroom to my living room. The temperature increase from 17°C to 21°C was immediately reported (and persisted).
You can also see, that also small changes of the bedroom temperature are recognized.
Good morning.
During last night my sensor reported for two times a change of the temperature and stored the change in the mysql database.
My config for this is:
- 20: Temperature report interval = 30 (this means 300 seconds)
- 21: Temperature report hysteresis = 3 (this means 0.3 degree)
This could be possible but I will check the behavior over the next days.
At this time I’m happy to see that values were send and stored. Thanks to all for your hints.
When I put my sensor next to the fire, it went from around 21C to 60C over a period of a minute or so, and reported updates every bunch of seconds. I’ve not changed any of the default settings (I think!) other than ones related to alarms which I was testing last night, so it can report quite often under this condition at least…
This are my last 3 entries in my sql database
2016-12-11 05:00:07 18.3
2016-12-11 10:09:14 18.2
2016-12-11 10:53:08 19.6
At 10:09 and 10:53 I pushed the button on the device. With my config to send a temperature report every 5 minutes when the temperature change is 0.1 degrees. So it doesn’t work. My persit file said to save ervery change.
I told you that the sensor wakes up in the last night for two times and send the values to openhab. Here ist the screenshot from it. It was always a “wakeup”. There was no report send. So my problem is still threre. The normal temperature report is not send regulary. 
Ok in the night the temperature would not change so much, but between 10:09 and 10:53 nothing happend too. The picture is the same. And within this time period the temperature changed!
Check that the lifeline association (group 1) is set to the controller.
Yes - looks ok…
Sorry when I maybe missed some information, but have we already figured out safely wether this is a persistence related problem or a device related one?
When you increase the temperature in the room were the sensor is, is your item of the sensor_temperature updated on your sitemap? I think until now you always wrote that the temperature isn’t “reported”, but I don’t know if you meant “persisted”?
No it isn’t reported to openhab. The item on the sitemap has the same value. Only when I manually push the button on the sensor, this sitemap temperature will also updated. When it is reported to openhab then it was persited. My problem is that there is no regualar reporting.
Sorry, but I’m running out of ideas.
Last hint: Update your installation (OH2 to latest snapshot, zwave binding), exclude the device completely (not just delete and re-add), do a hardware reset of the device and then include it again.
Maybe this helps…
I can only say that it’s running for me. Maybe it’s a malfunction of your device?
Thanks for the last idea. I did it. New installation with latest snapshot and zwave binding. Device was excluded, hardware reset of controller and device and now trying to include it again.
What happend now: Device unknown.
So I can’t include it again to my things. What’s the problem now?
Until now it’s a normal behavior. Zwave devices are unknown until they are fully initialized. For mains powered device this happens usually during seconds. For battery devices (like the smoke sensor), it can take some time (hours, sometimes days, depending on the wakeup cycle). You can speed this up by waking up the device manually. For me, no later than the second wake up and the device was recognized.
Thanks. I am so impatient. No the device is still back in my system. The next steps will be done in the next days or at the weekend.
Problem solved. The nightly build instead of the last beta solved all my problemes. Systems is still working now.
Thanks to all
Sorry for reactivation of this old topic, but actually, i can still observe this issue with “binding-zwave - 2.4.0.M4”. It’s only battery level and temperature that is updated regulary. Other alarms remains undefined. Even i trigger polling manually:
2018-11-07 23:51:02.667 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Command received zwave:device:512:node27:alarm_smoke --> REFRESH
2018-11-07 23:51:02.671 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling intialised at 1800 seconds - start in 50 milliseconds.
2018-11-07 23:51:02.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Command received zwave:device:512:node27:alarm_heat --> REFRESH
2018-11-07 23:51:02.682 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling intialised at 1800 seconds - start in 50 milliseconds.
2018-11-07 23:51:02.687 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Command received zwave:device:512:node27:alarm_smoke --> REFRESH
2018-11-07 23:51:02.694 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling intialised at 1800 seconds - start in 50 milliseconds.
2018-11-07 23:51:02.704 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Command received zwave:device:512:node27:alarm_system --> REFRESH
2018-11-07 23:51:02.707 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling intialised at 1800 seconds - start in 50 milliseconds.
2018-11-07 23:51:02.710 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Command received zwave:device:512:node27:sensor_temperature --> REFRESH
2018-11-07 23:51:02.713 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling intialised at 1800 seconds - start in 50 milliseconds.
2018-11-07 23:51:02.719 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Command received zwave:device:512:node27:alarm_tamper --> REFRESH
2018-11-07 23:51:02.721 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling intialised at 1800 seconds - start in 50 milliseconds.
2018-11-07 23:51:02.725 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Command received zwave:device:512:node27:battery-level --> REFRESH
2018-11-07 23:51:02.728 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling intialised at 1800 seconds - start in 50 milliseconds.
2018-11-07 23:51:02.778 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling...
2018-11-07 23:51:02.781 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:512:node27:sensor_temperature
2018-11-07 23:51:02.784 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 27: Generating poll message for COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2018-11-07 23:51:02.787 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 27: Creating new message for command SENSOR_MULTILEVEL_GET
2018-11-07 23:51:02.789 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: SECURITY NOT required on COMMAND_CLASS_SENSOR_MULTILEVEL
2018-11-07 23:51:02.792 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Command Class COMMAND_CLASS_SENSOR_MULTILEVEL is NOT required to be secured
2018-11-07 23:51:02.796 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:512:node27:alarm_heat
2018-11-07 23:51:02.800 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:512:node27:alarm_smoke
2018-11-07 23:51:02.802 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:512:node27:alarm_system
2018-11-07 23:51:02.805 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:512:node27:alarm_tamper
2018-11-07 23:51:02.807 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Polling zwave:device:512:node27:battery-level
2018-11-07 23:51:02.809 [DEBUG] [rnal.converter.ZWaveBatteryConverter] - NODE 27: Generating poll message for COMMAND_CLASS_BATTERY endpoint 0
2018-11-07 23:51:02.812 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: SECURITY NOT required on COMMAND_CLASS_BATTERY
2018-11-07 23:51:02.814 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Command Class COMMAND_CLASS_BATTERY is NOT required to be secured
2018-11-07 23:51:02.817 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Bump transaction 10168 priority from Get to Immediate
2018-11-07 23:51:02.819 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Adding to device queue
2018-11-07 23:51:02.821 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Transaction already in queue - removed original
2018-11-07 23:51:02.824 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Added to queue - size 6
2018-11-07 23:51:02.829 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Bump transaction 10169 priority from Get to Immediate
2018-11-07 23:51:02.831 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Adding to device queue
2018-11-07 23:51:02.834 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Transaction already in queue - removed original
2018-11-07 23:51:02.836 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Added to queue - size 6
2018-11-07 23:52:05.573 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Application Command Request (ALIVE:DONE)
2018-11-07 23:52:05.575 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: resetResendCount initComplete=true isDead=false
2018-11-07 23:52:05.577 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Is awake with 2 messages in the queue
2018-11-07 23:52:05.579 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Start sleep timer at 1000ms
2018-11-07 23:52:05.580 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2018-11-07 23:52:05.616 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 27: Node Status event - Node is AWAKE
2018-11-07 23:52:05.618 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Commands processed 1.
2018-11-07 23:52:05.619 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@fe2264.
2018-11-07 23:52:05.630 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 27: Sending REQUEST Message = 01 0B 00 13 1B 04 31 04 01 00 25 E4 0D
2018-11-07 23:52:05.657 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: sentData successfully placed on stack.
2018-11-07 23:52:05.662 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: TID 10168: Transaction not completed
2018-11-07 23:52:05.934 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: SendData Request. CallBack ID = 228, Status = Transmission complete and ACK received(0)
2018-11-07 23:52:05.935 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: resetResendCount initComplete=true isDead=false
2018-11-07 23:52:05.938 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: TID 10168: Transaction not completed
2018-11-07 23:52:06.075 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Application Command Request (ALIVE:DONE)
2018-11-07 23:52:06.077 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: resetResendCount initComplete=true isDead=false
2018-11-07 23:52:06.081 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: WakeupTimerTask 2 Messages waiting, state DONE
2018-11-07 23:52:06.080 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2018-11-07 23:52:06.085 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: SECURITY NOT required on COMMAND_CLASS_SENSOR_MULTILEVEL
2018-11-07 23:52:06.087 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 27: Received COMMAND_CLASS_SENSOR_MULTILEVEL V8 SENSOR_MULTILEVEL_REPORT
2018-11-07 23:52:06.089 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 27: Sensor Type = Temperature(1), Scale = 0
2018-11-07 23:52:06.092 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 27: Sensor Value = 21.5
2018-11-07 23:52:06.094 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2018-11-07 23:52:06.096 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 21.5
2018-11-07 23:52:06.099 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Updating channel state zwave:device:512:node27:sensor_temperature to 21.5 °C [QuantityType]
2018-11-07 23:52:06.104 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Commands processed 1.
2018-11-07 23:52:06.106 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1749c14.
2018-11-07 23:52:06.109 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1749c14.
2018-11-07 23:52:06.111 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: notifyTransactionResponse TID:10168 DONE
2018-11-07 23:52:06.117 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-11-07 23:52:06.139 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 27: Sending REQUEST Message = 01 09 00 13 1B 02 80 02 25 E5 BE
2018-11-07 23:52:06.169 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: sentData successfully placed on stack.
2018-11-07 23:52:06.172 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: TID 10169: Transaction not completed
2018-11-07 23:52:06.424 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: SendData Request. CallBack ID = 229, Status = Transmission complete and ACK received(0)
2018-11-07 23:52:06.425 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: resetResendCount initComplete=true isDead=false
2018-11-07 23:52:06.429 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: TID 10169: Transaction not completed
2018-11-07 23:52:06.552 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Application Command Request (ALIVE:DONE)
2018-11-07 23:52:06.554 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: resetResendCount initComplete=true isDead=false
2018-11-07 23:52:06.556 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Incoming command class COMMAND_CLASS_BATTERY, endpoint 0
2018-11-07 23:52:06.557 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: SECURITY NOT required on COMMAND_CLASS_BATTERY
2018-11-07 23:52:06.559 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 27: Received COMMAND_CLASS_BATTERY V1 BATTERY_REPORT
2018-11-07 23:52:06.561 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 27: Battery report value = 100
2018-11-07 23:52:06.563 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-11-07 23:52:06.565 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BATTERY, value = 100
2018-11-07 23:52:06.567 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Updating channel state zwave:device:512:node27:battery-level to 100 [DecimalType]
2018-11-07 23:52:06.572 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Commands processed 1.
2018-11-07 23:52:06.573 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@ad3a27.
2018-11-07 23:52:06.575 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@ad3a27.
2018-11-07 23:52:06.576 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: notifyTransactionResponse TID:10169 DONE
2018-11-07 23:52:06.578 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-11-07 23:52:06.582 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: WakeupTimerTask 0 Messages waiting, state DONE
2018-11-07 23:52:07.081 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: WakeupTimerTask 0 Messages waiting, state DONE
2018-11-07 23:52:07.083 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: No more messages, go back to sleep
2018-11-07 23:52:07.086 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 27: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2018-11-07 23:52:07.087 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: SECURITY NOT required on COMMAND_CLASS_WAKE_UP
2018-11-07 23:52:07.090 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2018-11-07 23:52:07.094 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@10047b0
2018-11-07 23:52:07.097 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Bump transaction 10170 priority from Immediate to Immediate
2018-11-07 23:52:07.100 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Adding to device queue
2018-11-07 23:52:07.104 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Added to queue - size 5
2018-11-07 23:52:07.117 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 27: Sending REQUEST Message = 01 09 00 13 1B 02 84 08 25 E6 B3
2018-11-07 23:52:07.153 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: sentData successfully placed on stack.
2018-11-07 23:52:07.157 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: TID 10170: Transaction not completed
2018-11-07 23:52:07.361 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 27: SendData Request. CallBack ID = 230, Status = Transmission complete and ACK received(0)
2018-11-07 23:52:07.363 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: resetResendCount initComplete=true isDead=false
2018-11-07 23:52:07.366 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: Response processed after 242ms
2018-11-07 23:52:07.368 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: TID 10170: Transaction completed
2018-11-07 23:52:07.370 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 27: notifyTransactionResponse TID:10170 DONE
2018-11-07 23:52:07.371 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 27: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-11-07 23:52:07.374 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 27: Went to sleep COMPLETE
Parmater 2 is enabled:
and association is set to Z-Wave controller:
Items definition:
Number B_SmokeSensor_BatteryLevel "Smoke" {channel="zwave:device:512:node27:battery-level", expire="7h"}
Number B_SmokeSensor_Temperature "Temperature" {channel="zwave:device:512:node27:sensor_temperature"}
Switch B_SmokeSensor_AlarmSystem "System [MAP(failure.map):%s]" {channel="zwave:device:512:node27:alarm_system"}
Switch B_SmokeSensor_AlarmTamper "Tamper [MAP(failure.map):%s]"{channel="zwave:device:512:node27:alarm_tamper"}
Switch B_SmokeSensor_AlarmSmoke "Smoke [MAP(fire.map):%s]"{channel="zwave:device:512:node27:alarm_smoke"}
Switch B_SmokeSensor_AlarmHeat "Heat [MAP(fire.map):%s]" {channel="zwave:device:512:node27:alarm_heat"}
and fire.map:
NULL=?
-=?
ON=Fire!
OFF=OK
When doing somke test i could see that B_SmokeSensor_AlarmSmoke item was correctly set. However, i would like get updates regarding status when there is no fire as well. Is it possible with this device or this is some bug?