home-assistant / home-assistant.io

:blue_book: Home Assistant User documentation
https://www.home-assistant.io
Other
4.76k stars 7.19k forks source link

Missing hint for discovery: Only working when in same subnet #28810

Closed viseradius closed 10 months ago

viseradius commented 1 year ago

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

home-assistant[bot] commented 1 year 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!

Code owner commands Code owners of `hue` can trigger bot actions by commenting: - `@home-assistant close` Closes the feedback. - `@home-assistant rename Awesome new title` Renames the feedback. - `@home-assistant reopen` Reopen the feedback. - `@home-assistant unassign hue` Removes the current integration label and assignees on the feedback, add the integration domain after the command.
marcelveldt commented 1 year ago

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.

viseradius commented 1 year ago

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.

marcelveldt commented 1 year ago

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 ?

viseradius commented 1 year ago

I thought so too. In my previous setup using Home Assistant OS I could enter the IP. Now, using Docker, it didn't work.

github-actions[bot] commented 10 months ago

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.