-
Notifications
You must be signed in to change notification settings - Fork 40
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
Fan not being added. #125
Comments
Exhaust fan + speaker? If so, thats pretty sweet. Is this the fan? I see the model is TBD too |
I havent added the functionality of the speaker but the fan should initialize now on the pre-release dev-exhaust-fan-setup. Let me know if that fixes your issue! https://github.com/jdeath/Hubspace-Homeassistant/releases/tag/dev-exhaust-fan-setup |
That is the one. The manual/box say it's a bf1112 |
Awesome, thanks for the confirmation. I just force pushed an update that should fix this issue and correctly identify the fan! |
Fan is now recognized as having a on/off/hi/low. Setting it to hi/low/off turns it on/off correctly. Just hitting "on" throws the following error
|
I guess the issue runs the whole way 😂 Let me take a look at that |
FWIW - i updated the comment with more debug testing: `Fan is now recognized as having a on/off/hi/low. Setting it to hi/low/off turns it on/off correctly. Just hitting "on" throws the following error` |
Should be fixed now if you want to re-pull the tag. Actions sure are a pain sometimes haha |
Looks better. There was a weird behavior when turning it on. Turned it on -> ha marked it on -> device turned on -> ha marked it off -> (I assume the polling cycle occurs) ha marked it on. It was like some issue with the polling cycle after the on? not sure if it's possible to schedule quicker polling temporarily after an event? Either way, it's now working! Thanks for the speedy updates. |
Does that happen every time or sporadically? I think it may have been as it was polling but not sure. |
Sporadically |
_dump_hs_devices.json
The text was updated successfully, but these errors were encountered: