…indeed it is.
No, the time stamps are completely random. Sometimes there’s hours in between readings, sometimes minutes. Annoyingly, it seems that that setting autoreport features (i e parameter 8 set to 5 or 0) has no effect whatsoever on reporting. The sensor still reports humidity deltas of 1 though I’ve set parameter 8 to 5. Setting parameter 6,7 and 8 to 0 doesn’t change the behaviour in any way.
Well, that could be it. Is that a bug? Is there some other way to monitor this?
You could poll the device variable but it would tell you the same as the variable watch. This is apparently a problem with the device, or the way that the MCV driver handles it. Either way there’s not an obvious way to code around it. I can’t really see what problem this gives you.
The problem would be to tell if the sensor i completely dead or just sensing the same temp and humidity. As far as I have understood it, Vera reports non responding sensors after days.
As of now, in my cabin, I have a camera watching a physical thermometer and the camera ftp:s the pictures to a web page that I check on a regular basis. Once, I had a power brownout on a really cold day. I did check the web page, but did not realise that the power was down as there was no time stamp on the images. After this incident, I wan’t temperature reportings on a regular basis, say every hour.
Also, it seems that others have discovered that there are issues with the ST814 sensor:
If it’s that critical, use different hardware. I switched to Netatmo for exactly these reasons, and get readings every ten minutes (and one decimal place on temperature.)
Also, it seems that others have discovered that there are issues with the ST814 sensor:
Yes, I love that website. Always an interesting read. Their ‘Wasp in a Box’ algorithm for calculating occupancy is terrific.
I see. Do the parameters show 0 as their current value? It seems as if your updated settings didn’t make it to the device, after a wake-up. (I manually forced the update by pushing the link button, but that’s not an option for you as this is a remote device.)
Well, this is actually a scenario where the updates are pushed (or pulled) regularly, say every hour, but you don’t see the update of an unchanged value because of how you observe the variable.
You could have a custom scene with some Luup that monitors the timestamp of the updates and ‘do something’ if you observe an anomaly. Or, if you used the wake-up mechanism, you could monitor the [tt]LastWakeup[/tt] variable. That one should change (as its contents are the timestamp itself). I don’t know if you can do this in EventWatcher.
I’m going to guess, based on the linked thread, that that is old info. Or put differently, originally, there were some issues observed with the ST814 when used with Vera. Even though the root cause could be considered a bug in the ST814, a workaround was posted here (on that same thread). And MCV has since included that workaround in Vera’s firmware, so things should work out-of-the-box. I’m not aware of other issues with the ST814.
No, but you can do it in dataMine or DataYours.
I see. Do the parameters show 0 as their current value? It seems as if your updated settings didn’t make it to the device, after a wake-up. (I manually forced the update by pushing the link button, but that’s not an option for you as this is a remote device.)[/quote]
Yes, they do.
I'm going to guess, based on the linked thread, that that is old info.
Apparently not. To me it seems obvious that a sensor should either report automatically on deltas or whenever you wan’t it to. If I don’t want to save battery, I’m capable to decide that on my own. Also, what kind of crappy software system would not automatically give you the timestamps of entities in a readable form if you want. In fact, Vera is the first system I’ve ever seen that doesn’t. Hey, all I wan’t is the LastWakeup or BatteryDate presented to me in readable form together with the temp/humidity, just to know that the sensor is alive.
I’m giving up.
The only reliably pollable temperature reporting devices are actual HVAC thermostats that were included while on line power, AFAIK.
No one has ever been satisfied trying to turn the ST814 into something it isn’t. I use the st814 to control a humidity range in my basement. I consider it to be the best designed and built battery powered zwave device I own.
I recently replaced my piece of crap fortezz water sensor with the Everspring model. Night and day on build quality.
If Everspring actually had customer service I would buy all their products just to acknowledge product designers who put skilled effort into their work.
Andreas,
Take a look at the MySensors website and I can tell you you can get exactly what you are looking for for less money to get your bridge and sensor working.
PLUS, those devices report their last read time right on the Device in the vera UI.
You can transmit temperature and humidity at any interval you wish.
They are easy to build, require no soldering or programming skills, Hek’s MySensors team has it down pretty well…
Good Luck in your quest, sorry you haven’t been able to get there yet.
Am I the only one that believes that some sort of time stamp should be presented together with the entity? As I said, Vera is the first system that I’ve came across that doesn’t. Even my kitchen oven has a digital clock.
OK. Have you tried setting the parameters to some other, non-zero, value; just to see if those take effect appropriately, and you’re thus seeing an issue specifically with disabling?
(As said, in my brief test the other day, setting the parameters to stop auto-reporting based on delta worked fine, and setting auto-report based on time interval, appeared to work also; I tried 1 minute and 2 minute intervals.)
Apparently not.What is this in reference to?
To me it seems obvious that a sensor should either report automatically on deltas or whenever you wan't it to. If I don't want to save battery, I'm capable to decide that on my own.To me too.
Also, what kind of crappy software system would not automatically give you the timestamps of entities in a readable form if you want. In fact, Vera is the first system I've ever seen that doesn't. Hey, all I wan't is the LastWakeup or BatteryDate presented to me in readable form together with the temp/humidity, just to know that the sensor is alive.[quote="AndreasE, post:31, topic:180750"]Am I the only one that believes that some sort of time stamp should be presented together with the entity? As I said, Vera is the first system that I've came across that doesn't. Even my kitchen oven has a digital clock.[/quote] Nope, you're not the only one. It would be very handy if these time stamps were easily accessible and in human readable form. I didn't think that was news. Given the frequency of firmware updates and MCV taking in our feedback, you're best off going with a forum suggestion.
(At this point, I actually wish my kitchen oven didn’t have a digital clock, or that it supports NTP. ;D)
The Everspring isn’t designed to report temperature accurately at a high reporting frequency. If it could be programmed to report or be polled frequently the next complaint would be that the device sucks as a thermostat.
The Aeon multisensor can be plugged in and set to report temperature frequently. It just doesn’t report an accurate temperature as it heats up from being frequently awake. The multisensor is a great example of how a device trying to do many things ends up doing nothing particularly well.
A battery powered thermostat capable of being polled reliability is about three times the cost of the Everspring. An example is the Remotec ZTS-100. It’s sluggish in answering the poll if set up on battery, but it will answer. Its a more robust device with a thermal design that is intended as a thermostat that is awake and busy on the network.
I would like my car to fly, but I didn’t pay for a flying car.
Just wanted to clarify that the OP’s use case appears to be a reasonable temperature report, say every hour, with an observable time stamp to assure the reading is current, but no other reporting, so as to maximize battery life; as this is a sensor in a remote, cold location. (Presumably some form of immediate action is required if the temperature starts to approach freezing levels.)
He may need to capture the group 1 report to get a timestamp, which Vera may not see correctly. From what I remember always been a question as to whether Vera handles this aspect of this device correctly.
On vera the people dissatisfied with device are really wanting something pollable. On dream green house they could have let the device trigger and set a virtual switch like “high humidity”. Then they could use that switch in their logic.
Yes, I tried to set paramater 8 to 1 and the sensor started to report like crazy even though I set parameter 6 to 60 (minutes, that is). Setting parameter 6 to 1, 7 to 0 and 8 to 0 doesn’t doesn’t change the behaviour, i e the sensor only reports on delta (according to EventWatcher).
I don’t quite understand the settings. Setting parameter 8 to 1 (autoreport on humidity changing by 1) and parameter 6 to 0 (autoreport off), what does that imply? Setting parameter 7 and 8 to 0 and parameter 6 to 60?