fix: BlueAirFan.async_turn_on() number of positional arguments #70
Conversation
This file contains 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
|
looks good, thanks |
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.
I was setting up this integration tonight and was running into an issue turning my Classic 605 and Classic 205 devices on with the Home Assistant Service Fan: Turn On function available on a custom card.
Looking at closed issues, my issue was basically identical to #52. Reading through the discussion, I saw @dahlb's fix in 63db8fc. I replicated this for the
BlueairFanclass with some limitations. Looking through the theblueair_apisource for non-AWS devices, it doesn't look like BlueAir returns arunningboolean (granted I haven't poked their API manually), so I just chose the lowest available speed initially for a "toggle" action.