Closed viseradius closed 10 months ago
Hey there @balloob, @marcelveldt, mind taking a look at this feedback as it has been labeled with an integration (hue
) you are listed as a code owner for? Thanks!
If you are technical enough to split up your network into different subnets, you should also know about all the downsides of that and the implication that things such as discovery will not work unless you implement some sort of mdns responder in your network (which comes with a load of issues on its own).
You would have this issue with any integration that relies on mdns for discovery so I don't really see the point of adjusting the documentation. TIP: Just make sure that HA is on the same (v)LAN as your IoT devices, you can even make it multi homed if you really insist to have this additional layer of complexity.
Nevertheless I was wondering, because I wasn't even able to add the hue bridge manually. The integration immediately stated that there is no bridge.
Yes, because it is meant to be used on the same subnet. This is consumer grade gear, that does not play well with enterprise network setups ;-)
Nevertheless I believe there should be a possibility to manual enter an IP in the setup flow ?
I thought so too. In my previous setup using Home Assistant OS I could enter the IP. Now, using Docker, it didn't work.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Feedback
Hi, I noticed that the discovery of the hue bridge only worked, when HA (Docker) and the hue bridge are on the same subnet.
A small change to the readme would be good but a change in the discovery even better.
Thanks
URL
https://www.home-assistant.io/integrations/hue/
Version
2023.8.4
Additional information
No response