I have had mine for almost two years and they are rock solid. The new drivers from markus seem to be helping with the dropping off for others. I havent run into that
2 Likes
Please forgive me for asking, but could someone add a bit of code to provide a selectable time delay before engaging the process? I'd probably select 30 minutes or so.
I need the fan to stay off until I finish the shower. It's a wall fan, not exhaust, and while I'm still showering/wet, would prefer it not be blowing on me.
Do you mind being a Beta tester for this function?
I'd be honored!
Generic Zigbee drivers.
e.g. Generic Zigbee Moisture driver
or the Konke Zigbee Temperature Humidity Sensor
or you might want to try this:
https://raw.githubusercontent.com/markus-li/Hubitat/development/drivers/expanded/zigbee-sonoff-temperature-humidity-sensor-expanded.groovy
have repeatedly made reference to the best/range of values you worked out, thanks for posting this overview!
1 Like
Another good way to get started is to turn on detail logging of your humidity sensor. Start your shower. You should see how fast and to what numbers your humidity gets and how fast your sensor is reacting. Then you can manually turn on your fan and see how quickly it drops. That made setting mine up the first time much faster.
One of the reasons I wrote the 2 sensor code was realizing that I wanted the bathroom back down near the humidity in the whole house. My house humidity fluctuates a lot between summer and winter.
4 Likes
Released 1.2 in HPM (2.0.7 for my numbering)
Added an optional delay fan turn on.
2 Likes
I have a lot of fans so I added parent-child structure to the app. You can use it if you want. Everything works the same within the app. It's still all @napalmcsr code for the app.
Parent App
https://pastebin.com/raw/uNAGevBb
Child App
https://pastebin.com/raw/G5a55DiB
I've been too lazy to do this myself. I am in the process of moving, and will update to this structure after that and setup the new house.
Saved you some time then. It's all done now. 
I did the same for the Auto Lock app so it was easy to transfer.
I wonder if this breaks HPM?
Probably have to update the manifest and change the version number in both.
1 Like
I'm going to think this through, I tried to update to the code and it made all of my current fans break since it was no longer a single app, but a child without a parent.
I'm guessing people would have to manually update in the future.
Yea, you have to redo your fans because they are all under the parent app now, but all good after that. Could also rename the app and roll it as a separate package that people could migrate to.
Yeah, that might be better, and I deprecate the original.
I'm thinking of renaming and using @lewis.heidrick parent-child code moving forward. I would deprecate the old Smart Humidity Fan and stop developing/ support on it. Anyone have any heartache over that? Not that I have developed against it lately...
Latest Parent/Child update that shows the fan status and able to pause child apps. Status updates on the app page on load or refresh. Would love for someone to help test it for me. I think it's all good but someone almost always finds something.
Parent App:
https://pastebin.com/raw/BT9feENP
Child App:
https://pastebin.com/raw/pDYEjatA
1 Like
@lewis.heidrick
I get an error when trying to install the child app
errorjava.lang.NullPointerException: Cannot invoke method contains() on null object on line 128 (page1)
