-
Notifications
You must be signed in to change notification settings - Fork 14
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
Haiku fans show up in Lutron app all in the same room duplicated #26
Comments
Interesting - I would believe that SN's/unique identifiers are being used differently in the Lutron app vs the Home app, however I'm not sure what the proper way to report the SN through homebridge is (if there even is a way to report it such that it'll be picked up by Homekit - I think it might be by specifying I also couldn't find "Default-XXX" in the homebridge repo - but there is an issue where others mention that string. Maybe it's a default that's populated on apple's side in the case the accessory doesn't report it. Sorry I can't be more help on this |
@sean9keenan appreciate the response, I'm going to go ahead and get one level deeper on this. Perhaps assigning serial numbers based on the MAC/IP address, etc. |
I think this serial number issue is the cause of issues in the eve app as well.
|
Not sure if this problem is on the Homebridge BigAssFans side, or Lutron side, but this is really weird:
When I have my 6 Haiku fans set up in Homebridge, synced to HomeKit in different rooms, they all end up showing up in my Lutron app in one room, duplicated (all six entries are the same fan), and randomly change from one fan to the next. It also causes the Lutron app to hang up and slow down.
Here's an example of one moment in time. It'll randomly change the fan represented to Guest Room, then Master Bedoom, etc for all the entries (yet stay in the same room next to each other) once in a while.
Controls do sort of work, I was able to get my fan to spin up to 100%, back to 0%, etc with the Luton quick set buttons.
So a few things that are odd:
Thoughts? I'm going to email Lutron as well but I don't expect to get a lot of traction from them on debugging and/or fixing this.
The text was updated successfully, but these errors were encountered: