Released v1.2.0, which adds an "excessive change threshold" to turn on the fan on the first report in a long while, if it exceeds a certain increase.
For those who saw my other post, I've gone all-in on the Aqara Temp/Humidity sensors, which I'm loving. I've only found two downsides:
- They tend to be less chatty about their status than the Zooz sensors, in certain cases.
- The more current driver, from Markus, doesn't allow for the option to send humidity events even if the humidity hasn't changed from a previous report, and "helpfully" even avoids sending events when it does change, if the change is small enough.
These two things conspire to sometimes yield a very long period between updates, which plays havoc with calculations of change rate based on a more reasonable reporting frequency. I considered a number of workarounds for this, but the one I felt would be the simplest for the user to understand is to simply trigger on a sufficiently-large increase regardless of how the math would indicate the change rate since last report to work out.
Hope this is useful!
