this post was submitted on 02 Sep 2025
260 points (97.4% liked)
Technology
74873 readers
2647 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You should be able to pick up an old style timer plug for under 10 euro / USD in your hardware store.
They're a tiny bit fiddly to set up but given how power hungry those things are you'll be saving money in no time.
We have one around here somewhere. I'll see if I can dig you out a picture.
Internet was faster....
These timers have no concept of understanding if the air is too humid.
They want a cooldown period so the unit isn't cycling constantly.
eg. turning on and off 30 times in an hour because the sensor triggers the moment it see's 46% when it's set to 45.
They want it so that it triggers on pull humidity down to 45%, wait an hour no matter what then trigger the next time it sees 46% or greater, which could be immediately... or in 5 more hours.
A pure timer wouldn't get the same effect at all.
Best answer I can think of off hand would be Home Assistant related. Get a humidity sensor and a z-wave switch/outlet. Use a dumb dehumifier that turns on as long as it has power...
On humidity sensor change check if above 45%. If it is, turn on power. wait until below 45% again... turn power off then wait 60 minutes. Make sure automation is set to not run concurrently, that way the currently running automation script must complete it's 60 minutes cooldown before it can run again