That's why I prefer change reporting vs timed reporting .. The times are set by default to not report frequent unless there is a change by the amount set..
3 Likes
Awesome! Motion clear time is definitely a popular setting to customize sensors with 
No, as long as it is properly refreshed on systemStart, to handle reboot after power fail, so that these values are correct after a period of being down. At present, for example, power status (mains/battery) isn’t correct after power fail / power restore reboot for the Ring Alarm Extender Gen 2 because the power restore event is missed.
It’s much more often than that for some of the built-in drivers. The Ring Alarm Extender Gen 2 gives battery reports once an hour. The Aeotec Recessed Door Sensor 7 gives battery reports once an hour, even if the door stays closed. SmartThings MultiPurpose Sensor v5 gives battery reports every 5 to 10 minutes, even if the door stays closed.
So it’s much more than twice a day for the battery reports by built-in drivers. Battery life could be improved if it could be set to only a few times a day.
Well that's just obsessive .. On devices that have this configurable I usually set this to the maximum value and request battery on wakeup.. I am going to re-examine 2 z-wave ones you specified as I have those installed..
1 Like
So glad I came on here and looked. Just transitioned from Smartthings and couldn't figure out why my motion based rules weren't working. Looking forward to the updated driver.
Just set up my new hubitat with two of these sensors. The temperature and humidity values are not accurate and don't actually change very much over the day. For e.g. I have another sensor that reports temp of 67F and 50% humidity whereas both ZSE11's reports 62F and 67% humidity. Any one else running into this issue? New to zwave so I'm not sure if I need to do anything to configure these in any way.
Thanks!
I never thought to compare, but mine is a few feet away from a Honeywell T6 Pro thermostat, and the latest reports for the two are:
- Temperature: Thermostat = 68.0 °F, Q Sensor = 63.4 °F
- Humidity: Thermostat = 44%, Q Sensor = 64%
The values were a few hours old when I checked, but I did a refresh right before this (and a wakeup) to get new values. The temperature difference surprises me a bit, but I suppose the thermostat is still a few feet away and in a wall, where this sensor is not; I never expect consistency with cheap humidity sensors, but that difference isn't too small, either, so I don't know.
But it sounds like your concern is more with reporting frequency. The Q Sensor has a few parameters (172, 183, and 184, specifically) that affect either time- or change-based reporting for these attributes, so checking those would be a good first step if you don't think readings are coming in frequently enough. I'm not sure what Hubitat's built-in driver exposes for these (mine has them all), but you could use the Basic Z-Wave Tool coupled with the Q Sensor manual (to find your desired values for each parameter) to set them for sure.
Thanks for corroborating my results. My values are different in a very similar way for both my sensors.
Less concerned about the frequency of reporting the readings for now. But it looks like I cannot use it for now to control the thermostat
Also seeing inconsistency with temperature (not looking at Humidity). Sometimes it is accurate within a degree, other times I need to refresh it. Other times it is just off by multiple degrees F.
Mine is about 8-10% low on temp and about 10-15% high on humidity, compared to other sensors I have compared so far.
A couple things I've noticed on these sensors with one on battery and one on DC:
- When on DC, the sensor starts to frequently report ghost motion (every few minutes). I have the sensors set to 8 (max) sensitivity since they're otherwise often slow to detect. I have had both units do this, but only on DC. The second unit that experienced this, I unplugged and left sit for a few days and turned it back on and it was fine for a day or two, but has just started doing it again. I placed the sensor in a closet at one point to validate it wasn't environmental, and it still reported motion.
- The motion clear parameter (13) doesn't seem to do anything. Both sensors will report motion, and then about a second later report inactive. This leads to more-frequent-than-needed motion reports, although not as bad as the 4-in-1 which reports active constantly on the C7.
Curious if anyone else has seen this behavior? I might think it was an unit issue if it didn't happen on both sensors.
Would be great for an option to always report temp (or all sensors) when motion is triggered. Ideally when turned on, it would report values and then motion so rules using motion triggers have updated values.
1 Like
If the device is mains-powered, you can do that with the refresh() command, though, of course, with that being done on the hub side after the fact rather than on the sensor side at the same time, there may be a few hundred milliseconds or more of delay after motion before the events are generated on Hubitat. I guess I'd rather have faster motion than needing to wait for all of this on the sensor side, though (especially with Z-Wave sensors that already don't have a fast reputation). 
On battery power, this, of course, will not work, since it won't execute the "get"s until the device is woken up (either at the wake-up interval, often something like twice a day by default, or by holding the button).
In all cases, the change-based reporting thresholds will probably be the most useful: if the value hasn't changed enough to send a report, then it's probably reasonable to assume it's close enough to whatever it was last time that your automations shouldn't be affected. (There is also time-based configuration, but I usually set that pretty high or disable it myself.)
My ZSE11 stopped reporting motion after I updated my hub to 2.2.7. Anyone else having this issue?
One of mine reports motion for minutes before going inactive, then sometimes shows motion when there isn't. The other two are either not reporting, or miss reporting randomly.
Mine reports the first time pretty reliably (on usb power), but the subsequent motions are very hit or miss.
I'm returning mine, they are far too unpredictable. The old 4-in-1 just works. Really wish we could get an inexpensive device like the old IRIS motion sensors, talk about a solid device...
1 Like
I've giving them one more go. I'm defaulting them and trying from scratch.
Two of my three respond mostly within a second, the other sometimes takes 3-4 seconds to notice motion.
I can't get the Basic Zwave Tool or the community driver to set the motion timeout to anything but the 30 second default. All other variables are adjustable fine.
And I just realized these are only 100 degrees and 20 ft, vs 125 degrees and 40 ft for the 4-in-1. Why come out with a lower performing sensor? Plus they don't have the temp color reporting like the 4-in-1.
You must have missed the notes from Agnes earlier in this thread...
How is it completely different when it does the same things, only worse? Doesn't matter if it's a Tahoe or Escalade, it does the same thing, but at least one has better "something". 
1 Like
