Closed tbach closed 1 year ago
Thanks for the debug logs. What version of the plugin are you using?
I first noted it on 0.5.3, which was the behavior described in the ticket - I then tried 0.5.4-beta10 and the detection bug didn't change, but the switches seemed to confuse the actual BAF app/fan itself even more. I've stayed on beta10 in order to use the noLights
pref for now.
I think I have a handle on what's going on but I don't know how to resolve it yet. I could add a noDownlight
pref as a temporary hack or you can run with noLights
until we figure out a proper fix.
I'm totally fine to run with noLights for now. Appreciate your looking into it on a Sunday!
As it stands I don't know of non-hacky way to address this without breaking downlight detection for the user who opened issue #14. I've asked for more information that could help to find a reasonable solution.
In the meantime, I think a config option would be the most practical work-around.
In the interim, having config options to override auto-detection for cases like this might be the most flexible path forward. Basically, for now, keep auto-detection the way it is but give config keys that let a slightly more advanced user say "ignore auto detection, set uplight/downlight/etc to _____"
That sounds reasonable. How about for now I'll do uplight and downlight and see how that works out?
Makes sense to me
homebridge-i6-bigassfans@0.5.4-beta11 groks uplightEquipped
and downlightEquipped
with values or true
or false
. With any luck "downlightEquipped": false
should address this extraneous light issue.
Works great with "downlightEquipped": false
- thank you @oogje
I know this issue is closed but I'm new to Homebridge and this plugin and I wanted to share my experience incase someone runs into a similar problem I had.
I was running 0.5.4 of the plugin and I have a Haiku H/I fan with an uplight BUT only an LED "downlight" that indicates connectivity to the remote or app. It's not able to be turned on to light the room.
When I first installed the plugin, it would detect the fan with a "Light" switch and an "Uplight" switch. Homebridge would change both switches and reflect the current status as long as I changed it in the app or the remote. As soon as I made the change in Homebridge, the light would stop listening to commands from ALL sources. The only way to fix this was to power cycle it at the wall switch. I initially had given up last night, but I love a challenge.
I found this issue thread and my problem was similar enough that I followed a previous suggestion of trying one of the beta versions. Up until this point, no version of JSON configs would change any of the behaviors. Once I installed 0.6.0 beta 9 and rebooted with my last JSON config file I had previously used, I noticed the JSON had removed some of the variables I had forced before to suppress light detection. It took a few more seconds to connect to the fan (about 5 or 6 reconnect errors), but it finally connected and IT WORKS. I can control the light from Homebridge. All I really wanted to do was to be able to schedule the uplight based on sun up/down throughout the year, heck even a scheduler that let you pick the months that it would be active would've been great...but BAF didn't include that functionality which is CRAZY for how expensive these fans are.
Regardless, I wanted to thank you @tbach for your hard work on this and hopefully my post helps someone else reading this.
To be clear, @oogje did all the work here and deserves all the credit, I just raised the original issue.
You're correct, that was my mistake as looking who closed the issue.
Thanks @oogje !!
You all deserve credit for reporting and engaging.
Describe The Bug: I have configured a Haiku Gen 4 fan with an installed Uplight. During device detection, both an uplight and downlight are detected (see logs below). This creates a second light switch in Homekit which does not do anything, but which when activated (via homekit) confuses the BAF app - even using the BAF app the uplight cannot be used until the erroneous downlight switch is deactivated in homekit and the uplight switch is toggled. E.g. if the erroneous downlight switch is the last-used light switch in homekit, no lights will work.
Logs:
Plugin Config:
Environment: