Thanks Kevin. I updated my post above during the time you replied. I wasn’t expecting such a quick response!
The current reading is 1880 lux, and my light meter reads about 80. I do quite a bit with lighting, so I have a pretty good feel for what’s a reasonable reading and what’s not (1880 is not reasonable under the circumstances). The light meter is fairly accurate. I entered a value in the range of 16000, and it seemed to make no difference.
Have you had any luck with coefficient changes making a noticeable difference? If so, perhaps I have an issue with my sensor.
Are you waking the device up after changing the setting and verifying that it says “0 Pending Changes” before testing it? While writing the handler I set it high and low and the change made a difference, but I wasn’t testing to see if it was accurate.
I’ll go back and do another clean run with it to make sure it’s updated everything. I thought I did it properly, but I’ve been fiddling around with it quite a bit and could easily have overlooked this step.
Hello. I have successfully set up this device controller, but the LED disable setting doesn’t completely disable the LED. I tried first setting parameter 10 to zero, and also tried setting parameters 10 - 15 to zero, but the small white LED still flashes. In each attempt, I reset the sensor until the pending updates was zero. Is the LED supposed to be completely disabled with these settings?
I apologize if I’m not using the correct terminology. The only way I could get the pending updates to go to zero was to remove the battery from the trisensor for a time and then they would count down to zero. If I left the battery in, they didn’t decrease. That is what I meant by reset.
I ran into another problem with the DH where the sensor would show as disconnected after about 12 - 24 hours. I ended up reverting it to the original (non-custom) device handler and it has not disconnected since. The LED settings also stayed as they were with the custom DH (the only light that flashes with motion is a small white LED).
SmartThings compatible means it will be identified as the correct device and all basic functionality will work, but the built-in handlers rarely provide settings for most of the configuration parameters.
If you want local execution you can use this handler to configure the device and then change the type back to the built-in handler.
What I did notice is that triggering motion quite frequently caused the device to freeze. I’ve placed it in a location where motion triggers are infrequent and the device has not needed a battery pull. Still not good enough but I’ve not had time to take up with support and I’ve not done a firmware update. Not sure whether Aeon have pushed a firmware update (if that is how these things are updated)!.
Thank you so much for this!
I’ve been using the DH that Aeotec recommended and it simply wouldn’t update with any of the preference changes (over days, with waking up the sensor repeatedly, also tried re-inclusion…)
With this, it’s all working great!
Just a note, If you want the changes to be applied faster, simply wake up the sensor by pressing the button for 5s (light goes sort of yellow, and you might need to do this twice to get all the pending changes in).
Love the DTH, works great. I was wondering if there was a way to use the temperature as the ‘primary’ indicator. I am using these mainly for temperature monitoring along with several Multisensor 6s. I would like all the sensors to show the current temps from the main device listing in the app.
Hello, extremely new to custom device handlers and how to read the code. I would like for the sensor to check the illuminance level every 3 minutes. I may want to make it shorter or longer in the future. Where is that parameter in the code?
PS Thanks for sharing this device handler. It really makes the Aeotec TriSensor much better.
There’s an option for “Light Reporting Interval” in the device settings. I believe the device’s settings are accessible in both new mobile apps, but I know that screen is really buggy in the new Android app so I recommend always using the classic mobile app when changing settings.
Most battery devices, like the TriSensor, sleep so after saving the settings you need to manually wake it up or wait for it to wake up on its own which should happen every 4 hours. If you open live logging before saving the settings it should show the instructions for manually waking the device up when you tap save.