I'm not at home to properly observe this. Will keep an eye on it and let you know. Thanks for all your efforts and quick replies. This app is exactly what I was looking for.
Exhaust fan switch log still shows two ON responses to the apps command however the app appears to properly respond and leave the fan running (not seeing the ON/OFF cycle I saw before latest version.
I'm still a little confused as to why the logs for exhaust fan switch are showing multiple responses to the commands, but I guess as long as it doesn't confuse the app it's OK.
Even more curious is why the log is showing 4 responses to commands sent via the dashboard app (perhaps an error in that app). I'll ask in the appropriate forum.
Again, thanks for all your work on this. I'll see if I notice any response time slow downs but I'm guessing I won't since you discovered the cause.
Edit: I noticed that the response from the switch changing states (in logs) isn't registered in the device events only in the logs. It also seems to show double responses only when controlled by apps or by local dashboard access. It shows the quad response when controlled by "cloud" dashboard.
If I was going to make a feature request... It would be an option to configure the percentage drop/increase in humidity before the auto-cycle begins/ends.
Updated the code to turn off after it reduces to X% of the max increase.
Example, you set it to 25%, the fan turns on at 41% humidity. The humidity increases to 49%. The Fan will not turn off until it gets back to 43% or lower. You can also set a delay for how long until it turns off after it reaches that humidity.
Adding the code does only that.. adds the code to the Hub. You then have to tell the Hub to Use the Code via the Load New Apps button. Built-in (Hubitat created) apps are at the top of the list, added code (custom apps) are at the bottom.
Since this app appears to be very stable and not much extra development seems to be necessary, perhaps an option to disable some of the logging might be prudent?
Only reason I mention it, is that the "past logs" will fill up pretty quick with logs from your app which would be unnecessary assuming everything is working properly?
Yes, Andy's version checking code is really nice too.
