I have an Everspring ST814 temp/humidity sensor. As of now the temperature and humidity are read whenever these are changing. However, I would like the temperature and humidity to be read (say) every hour. I’ve tried disabling auto report in the sensor and changing the wake up interval and poll settings in the device settings, but with no luck.
Wakeup is a parameter that opens up a communications window to allow configuration changes and changing its frequency will not affect the frequency of its readings.
I’m guessing that the firmware is programmed to transmit on changes, as to preserve battery life.
Are you asking for a report that takes a reading from your sensor at hourly intervals, or are you looking to make sure that the sensor is maintaining and reporting its states with sufficient frequency?
The latter.
don’t trust it, eh?
Whole degrees C or F make it a problem, too. If it reported back decimal changes in temperature, it would report back an order of magnitude more often…
Well, as of now, no updates can mean nothing has changed, or complete breakdown. It would be nice to know witch.
Does anybody have a clue how to poll the device say every hour?
You could create a scene to run every hour and select the Poll action for your device on the ADVANCED tab. It may not achieve what you want, though. If it is a battery-operated device, the poll will be queued until the next device wake-up.
As previously stated, battery operated devices only transmit on changes, in order to preserve battery.
Checking a temperature sensor is easy, simply put a hot or cold source near it. I blow dryer set on low can elevate it, something like a small fan or compressed air can can lower temp. You should then see temp changes in Vera.
If you switch to MySensors you can have it report at specified intervals, and it will display the time last updated. Battery or no battery, as you like.
[quote=“TC1, post:8, topic:180750”]As previously stated, battery operated devices only transmit on changes, in order to preserve battery.
Checking a temperature sensor is easy, simply put a hot or cold source near it. I blow dryer set on low can elevate it, something like a small fan or compressed air can can lower temp. You should then see temp changes in Vera.[/quote]
My sensor is not in the vicinity, so doing manual tricks will not work. As I said, no updates would mean everything is like it used to be - or a dead sensor. If it’s -35 degrees outside, I would like to know if the sensor is sending data correctly or is dead.
this is sort of a ‘nature of the beast’ thing with the battery devices. Be assured that if the device does not get successfully polled, meaning that it is no longer in communication with Vera, it should show as an error on the device on your dashboard.
Even indoors, temperature and light are changing incrementally with enough frequency that you can have some assurance that it is working.
Another thing to worry about is the battery, which (you may know) you can monitor and send an alert when it drops to an uncomfortable level.
You may want to try to generate an alert if the device is reporting the exact same readings for more than X hours. Look at PLEG for that.
I’ve read that Vera reacts on no communication after days, rather than after hours.
This is hard for me to understand. I do understand that the sensor only reports changing entities, but I did turn off autoreport. Still, the sensor only reports changing entities. How come?
It’s been stated over and over, to preserve battery life.
If the Z-wave device is permanently powered during the inclusion process, then it can be polled on a regular basis. This is part of the Z-wave process/specification.
I understand that. But I have disabled autoreport? According to the manual autoreport means setting the temp/humidity changes on which the sensor will autoreport. If I disable autoreport, why does it autoreport anyway?
The ST814 can auto-report based on time, and based on delta. Or Vera could poll it.
Presumably, you have set parameters 7 and 8 to 0, which is supposed to disable auto-reporting based on delta.
Did you also set parameter 6 to 0? If so, you could set the wakeup to 1 hour, and the poll interval to 60.
Alternatively, you could set parameter 6 to 1 hour, the wakeup to say 1 day, and the poll interval to 60.
Having the sensor push the values may be more reliable than having Vera pull the values.
Just looking to confirm what you have tried / are looking to do; I have not actually tried your use case on a sensor yet. (Mine are set to auto-report on delta and time.)
Yes, I did set parameters 6, 7 and 8 to 0. Still, the sensor only reports on delta. ???
Thanks for confirming that. I’ll see if I can find a moment to attempt to reproduce this.
What did you set the wake-up and poll interval to? And how are you confirming that the device only sends deltas / are you saying you see the values change outside of the wake-up interval?
I’ve set the poll and wake up to 3 600 (seconds). I’m using the log function in EventWatcher to see that only deltas are reported.
OK; but are these deltas reported right when you would expect them? That is, they are spaced a multiple of 3600 seconds (i.e. the wake-up interval) apart?
I tested the parameters. It appears to behave as expected: settings parameters 7 and 8 to 0 will stop auto-reporting based on the configured delta. Setting parameter 6 to 1, will cause readings to be pushed to Vera every minute.
At the Z-Wave level the values are always reported, whether they changed or not. Vera does appear to update the timestamp for unchanged values also.
Presumably it is your way of monitoring (i.e. EventWatcher and its underlying mechanism (which may be the [tt]variable_watch[/tt] mechanism provided by Luup) to lead you to believe the device only reports deltas, where in fact it’s Vera?