Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Max button should set value of fan to 7 #2

Open
tgsoverly opened this issue Jan 30, 2017 · 6 comments · May be fixed by #10
Open

Max button should set value of fan to 7 #2

tgsoverly opened this issue Jan 30, 2017 · 6 comments · May be fixed by #10

Comments

@tgsoverly
Copy link
Owner

No description provided.

@jterrace
Copy link
Contributor

Why is 7 used as the max? Mine goes up to 10

@tgsoverly
Copy link
Owner Author

The version I built this off of went to 7. 🤷‍♂️

@jterrace
Copy link
Contributor

Interesting. What model number and software version do you have? Mine is 3200 WHF and software version 2.15.1.

@tgsoverly
Copy link
Owner Author

tgsoverly commented Jul 21, 2018 via email

@jterrace
Copy link
Contributor

No, I bought the older generation 2 controller instead of using the new capacitive fancy one (from here https://blog.airscapefans.com/archives/new-controls). You can actually see on that page in the last paragraph, they say it's not compatible at all with the remote control or API. I'm not sure why they went with a capacitive switch anyway, since capacitive switches are awful for usability.

I can make the max value a parameter so people can pick. Unfortunately, I don't see "10" anywhere in the API responses to be able to set it programmatically. Though it's possible it might depend on the software version, which is available.

Anyway, I have a lot of improvements I could send you, but I'm not allowed to contribute to an open source project without a license by policy of where I work. So if you add a license, I'll send you my changes.

@tgsoverly
Copy link
Owner Author

tgsoverly commented Jul 21, 2018 via email

@jterrace jterrace linked a pull request Jun 24, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants