See issue outlined here. Basically, fan.increase_speed can turn the fan on, but decrease cannot. This is weird, asymmetric behavior. It makes automations messier by requiring if/else so that a button can both decrease and turn off a fan, where the turn on/increase does not need this.
Don’t forget to vote. This seems a sensible idea.
Sounds more like a bug to be honest. There appears nothing in the code which would block this on purpose.
I would say you should write up an issue in the github repo for this Sign in to GitHub · GitHub
2 Likes
Maybe this is a bug, and also maybe it’s just on my end. I’m able to call increase speed and have it go from 0% → 33% → 67% → 100%. Right after that I can call fan decrease and it goes from 100% → 67%… but that’s it? I’ve spammed the button a hundred times and it doesn’t go below 67% (I thought it was going down to 33% yesterday…).
You’re right, I had originally assumed it was some intentional design but now I see it works differently than I initially thought. Bug created! Action for fan decrease speed only works once · Issue #124097 · home-assistant/core · GitHub