search

leikoilja / ha-google-home

Home Assistant Google Home custom component
MIT License
431 stars 73 forks source link

Allow a list of local IP addresses to be used to add devices #340

Open mkjustuk opened 3 years ago

mkjustuk commented 3 years ago

If the Google devices connect via a VLAN or similar and don't have mDNS paths back to the HA network, they are not added. The Google cast addon for instance gets around this by having an option to list the IP (reserved) addresses of the Google devices.

DurgNomis-drol commented 3 years ago

Not a terrible idea i think, we didn't include this at first because of simplicity for the end user, but you raise a good point about when not having the ability to use mDNS

leikoilja commented 3 years ago

Sounds like a reasonable feature request. Not impossible to implement but we would need to think of an elegant way to match the provided IP addresses with it's local authentication tokens that are coming from glocaltokens underlying package.

Jay2645 commented 2 years ago

One little snag here:

I have 2 Nest Wi-Fi speakers, which are essentially Google Homes inside of a mesh Wi-Fi repeater. I'm going through all my Google devices and giving them static IPs only to discover that Google, in their infinite wisdom, has decided that their Wi-Fi pucks cannot be assigned static IPs. Anyone with a Nest Wi-Fi point will have to deal with the fact that it may change its IP from time to time.

It's not the end of the world, but it is fairly annoying since the combination Wi-Fi puck and speakers are by far the devices which I personally use the most often.

When this gets implemented, can a note be added to the README mentioning that Google Wifi pucks cannot have a DHCP address and will need to be reconfigured from time to time? Unless you guys think of a clever workaround.