Core: Philips Hue host parameter not accepting FQDN anymore

[tedstriker]

Home Assistant release with the issue:
0.66.0

Last working Home Assistant release (if known):
0.65.5

Operating environment (Hass.io/Docker/Windows/etc.):
pip installation on a Pi

Component/platform:
https://home-assistant.io/components/hue/

Description of problem:
Until release 0.66.0 it was possible to use a FQDN (e.g. hue.example.com) as a valid host entry.
Now it is necessary to use a IP instead of a host name.
As I run a DNS server in my environment it was very convenient to organise things that way.
Would be very good to have the component resolve hostnames again.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

hue:
  bridges:
    - host: hue.example.com
      allow_hue_groups: false

Traceback (if applicable):

Invalid config for [hue]: not a valid value for dictionary value @ data['hue']['bridges'][0]['host']. Got 'hue.example.com'. (See /home/homeassistant/.homeassistant/configuration.yaml, line 96). Please check the docs at https://home-assistant.io/components/hue/

Additional information:

[Danielhiversen]

https://community.home-assistant.io/t/use-dns-names-instead-of-ip-address/48804

[audunmg]

I think this line should just be cv.string, is ipaddress validation is really necessary?

https://github.com/home-assistant/home-assistant/blob/5a9013cda58a3a99e1f1e9fa73e18c5895a4f56c/homeassistant/components/hue/__init__.py#L44

[tedstriker]

@feitingen did you try if it still works with a hostname?

[audunmg]

No, sorry I haven't had the time. I'll try as soon as I can, probably tomorrow.

[audunmg]

Replace that line with
vol.Required(CONF_HOST): cv.string,
and it works.

Tested just fine both with IP address and FQDN parameter.

I can make a tiny pull request for this.

[audunmg]

To clarify, it didn't work with a hostname without that change.

In all fairness, the documentation clearly states using an IP address, but it's really inconvenient to set up the hue every time the IP address changes. (it usually happens when the wife is home and I'm not)

[balloobbot]

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 with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[audunmg]

This issue is why I'm not using home-assistant anymore.
Of course there were other issues, but this really made me give up on it.

I'm not angry about it, it just became too much effort trying to keep home-assistant working and I don't have enough time.

[balloobbot]

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 with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[sweharris]

I'm new to home assistant and pip tells me I'm using homeassistant (0.89.2)

The Hue component still does not allow hostnames. "huebridge1.my.domain" is self-documenting. "10.0.0.99" is not.

Autodiscovery is not an option when devices are on different networks. Other components (eg lutron_caseta, tplink_switch) appear to work with hostnames; hue doesn't :-(

[stale[bot]]

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 with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jceloria]

So default behavior has changed recently where the use of groups is disabled? and I'm unable to use a FQDN? so I have to use a IP and specify the host just to get the groups back?

Yet another brilliant decision.