If that is by design, then I suggest warning the user that when they do so much as click the name of their bridge in the integration app (something that someone might intuitively try if they think there are any settings behind that option), the authentication for the existing bridge will be irrevocably deleted. I volunteer to be labeled as the "idiot" you should assume your users are.
I'm not sure if some wording changed in the integration app in the last few updates, but it no longer seems as clear to me as I once thought it was that the integration app would let you add multiple Hue bridges. Glad to hear that it's actually coming in a future update though! Won't help me (unless just clicking the above will no longer erase my username...) but should help people who run into the Hue limit, and it would roughly parallel what someone might expect based on how the Lutron integration works.
@mike.maxwell is there a way to manually enter an IP for the Hue Bridge for discovery like you can in the Hue App?
I have 4 Hue Bridges and for some reason the discovery process only finds two of them, the other two never show up despite trying for several days now.
I rebooted Hubitat and the problematic Hue Bridges but still no joy. The Hue App on either iOS or Android has no trouble discovering them, same with ST, Alexa, etc. Just seems Hubitat can't find them for some reason!
I've got the same issue. Two hubs here... one auto-discovers... the second one just won't. I'm assuming that device auto-discovery is just mDNS/ZeroConf/Bonjour... in which case... I can confirm that both devices are answering mDNS lookups:
Ah. OK. That explains it. SSDP isn't one I've had exposure to before - I've always used mDNS (Zeroconf, effectively) for device discovery in the past, and (mistaken) assumed this was the way everybody else did it
