Aeotec Multisensor 6 - Reporting every minute after updating to 2.2.4.158

I finally updated firmware from 2.2.2.129 yesterday. Since updating I am getting battery reporting events every minute (I capture events in a database, description logging was turned off). I am using the built in driver, sensor is on mains power. This was definitely not happening before the update. Anyone know what I can do to fix this? There are no options to configure reporting in the driver.

UPDATE: I turned on logging and all attributes are being reported every minute. In my logging DB, I had turned off the other attributes, so I was just seeing batteries.

However, battery % reporting started happening yesterday as there are no prior events in the database

@csteele - originally, I was using your driver but switched to the built-in one. However, now I cannot find that driver (the one in Github was older than the version I had installed - GitHub was 1.7.1?). It was also not available in Hubitat Package Manager. Is it still available? If so, where can I get it from? Thanks!

Don't know.. it's all still working for me... first github:

Both versions are out there, but you're probably well past platform 2.2.3 and thus the v2.0 driver would be best.

For HPM:

Screen Shot 2021-01-21 at 6.52.36 AM

I just installed the Driver and got v2.0, as I was expecting.

Screen Shot 2021-01-21 at 6.57.02 AM

If I go to the csteele-PD repository, I see 2 repositories and neither of them has the driver :man_shrugging:t4:

I was searching on Multisensor and then on Aeotec and neither of those brought up the driver (it shows the one by Sebastian Yepes). Searching by your username showed it!

I finally went to 2.2.4 yesterday (was on 2.2.2.129 till then)

csteele-PD is my development repo and is unlikely to be useful a week later. My public repo, along with many others is in the Community space:

1 Like

I switched back to your driver as it seemed that illuminance reporting with the other driver was not refreshing. Today was the first "sunny" day since I had changed the drivers and the lux reading was stuck at 16. Switched to your driver and the lux reading was >100 ( :+1:t4:).

I set the "Luminance Change Amount (LUX)" parameter to "1" and I was getting reports as the value changed - very frequently as I have the sensor pointed towards a window. Since I use the Lux value to turn on/off an indoor light (<=20, turn on; >=30 turn off), reporting change by 10 Lux (default) in this range seems too wide but a change of 1 Lux (my setting) outside of this range creates a lot of noise. Any thoughts on how I can balance the two (lux change/report frequency)?

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.