Repository navigation
Add hood wind speed sensor and faster state feedback after commands - #371
Merged
gvigroux merged 2 commits intoOct 30, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two small changes, tested on a Haier HATS9CBS4BWIFI hood (integration 0.8.4, Home Assistant 2026.x):
New sensor for hoods:
Wind speed(windSpeed, 0 = off … 5 = max).The hood exposes its current suction speed, but no entity reported it, so there was no way to get state feedback for the fan in Home Assistant. The sensor is only created for appliance type
HOwhenwindSpeedis present.Faster refresh after a command.
HonBaseCoordinatornow passes aDebouncerwith a 1.5 s cooldown (constantREQUEST_REFRESH_COOLDOWNinbase.py) instead of Home Assistant's 10 s default. With the default, aasync_request_refresh()issued right after a command was often swallowed by the cooldown, so the UI showed the new state only ~20–30 s later. With 1.5 s, bursts of refresh requests are still coalesced (andimmediate=Truekeeps the first one instant), but feedback arrives within a few seconds. The regular 60 s polling interval is unchanged, so the load on the hOn API only increases when the user actually sends commands.Testing