One of the options available enables threshold update, check to see if it is on. When it is set to ‘on’ it should take effect… emphasis on ‘should’ because it doesn’t work for me at all.
Also I raised a ticket with this issue, I would suggest you do the same.
Thanks @zsunsun! I think my impatience got the better of me. The default refresh setting of 7200 seconds I think needed to run it’s course for me yesterday, before the new thresholds came into effect. I have the temp, humidity, and illuminance set at 5 minutes now each with lowered thresholds to report and that did the trick. Looking back at my logs overnight is showing that I’m getting the desired functionality now
Hello Rich, I’m glad to hear threshold setting is working for you. For me it still does nothing…
Triple click on the switch on back should wake the sensor up to do a refresh on the settings which will override daily update cycle (AFAIK from manual).
Can you check of you set threshold higher for LUX value and see if it works as expected?
Hey @zsunsun. I upped the threshold on the LUX to test and it still seems to be reporting every 5 minutes as I have it set regardless of the threshold setting. Let know if there is anything else I can check if it helps you troubleshoot.
Thanks @Rich. This confirms that I’m not the only one seeing threshold getting ignored.
It’s been 4 days since I opened my ticket, so I’ll wait few more days and start return process. I don’t think spending money on a product that’s not backed by the company behind is a wise move.
Hey @zsunsun - let me find your ticket - not sure why no one has answered it, but I’ll take a look.
We are working with the manufacturer on a few bugs we found on the sensor.
Tagging @EricM_Inovelli as well.
I can promise you we stand by our products.
Do you have a public list of known bugs and their status (ie: being investigated, pending firmware fix, etc)?
Not for the sensor, I’ll get the page started shortly - good call!
Hey @zsunsun. I haven’t really checked the threshold usage. I’ve been having it report updates every 5 minutes and it’s been working great. the battery still looks to be at 100 at least according to hubitat! I’ll see if I can play around with some of the thresholding to see if my experience is the same.
Thanks @Eric_Inovelli for getting the bugs posted. The visibility you all provide into what you’re doing is awesome. Keep up the good work!
Hello Eric,
Do you have a link to this page? I cannot find it.
Haha this is funny, the ticket is cancelled citing ‘handled through community’
@zsunsun Did you ever get anywhere with this? I just installed a second one of these sensors and it doesn’t care what settings I use it reports everything its not supposed to. I can turn all sensors off except for temp and it reports everything.
Hello!
Nope, nothing on this one. I’m not sure how this company tracks issues. Try raising a ticket, you may have a better luck.
Hello Eric, it’s been a while. Do you have link to the page?
Hey! Yeah right here: 4-1 Sensor | Project Grand Slam (v2.0 - Bug & Enhancements)
Here’s to getting this fixed before we start production!
Are there any updates to this “bug”?
I just received 4 of these sensors as well and have enabled the Report Only When Thresholds Are Met (110) setting on all sensors. However, the sensors seem to be reporting on the reporting interval regardless of the report thresholds.
I’ve had them up for about 2 days so far. I’ve had no problems configuring the reporting interval and the PIR settings by waking up the device. The report threshold setting are being saved and “enabled”, but the reporting behavior does not reflect this.
All my sensors have Firmware Version: 2.4
Did you press config button three times to wake device?
@stu1811
Yes, I did wake the device with 3 clicks in order to get the config to update every time I make a config change.
Right now, I have two sensors with the Threshold Setting ON, and two sensors with the Threshold Setting OFF.
Here are my other setting for all 4 sensors:
Regardless of the “Report Only When Thresholds Are Met” (110) setting, all 4 sensors are reporting at the corresponding reporting interval with no deviation.
With the above settings, I would expect:
I already tried to invert the 110 setting on each sensor to verify that I was not able to get this behavior to work on any of the 4 sensors I have. (110 = 1 and 110 = 0, no effect on reporting behavior)
I think I figured it out… when you disable (turn off) the intervals, the thresholds start working. Disable Luminance by making Luminance Reporting Interval [103] = 0. Then set your threshold and watch it work in the logs.
