carealtor Posted January 28 Posted January 28 The dream would be to be able to use HueEmulator with my Brilliant Home Control panels. I've had discussion with Jimbo in the past, but now it has been awhile and wanted to see if anything has changed that might make this a possibility. As I understand the issue (and I could be way off because I don't claim to understand these things) is that a real Hue bridge runs on port 80 and thus that is the only port that Brilliant looks at. It is also my understanding that ISY also runs on port 80 and that cannot be changed. Thus, HueEmulator cannot run on port 80. If Brilliant would change the way it works to look at the port that HueEmulator is using, it would probably work. But Brilliant is not going to do this. I have tried and they see no reason to make the change since real Hue runs on port 80. My workaround had been to use the Emulated Hue integration in Home Assistant, but now that is not working either. Talking with Brilliant support at length, I was able to learn this information: "One thing that did change with the Hue integration recently was we switched the discovery of Hue to use MDNS instead of UPnP (Hue will be deprecating UPnP). It may be possible the virtual hub mentioned (Home Assistant Emulated Hue) doesn't implement MDNS properly so we cannot find it on our end after switching the discovery method." I have no idea what this means, but it seems to be why the Home Assistant Emulated Hue integration used to work, but now it doesn't. Another thing I have run across that I have not seen before is this tidbit from the Home Assistant Emulated Hue integration readme: "This virtual bridge runs at HTTP port 80 and HTTPS port 443 on your local network. These ports can not be changed as the HUE infrastructure requires them to be at these defaults." Does this mean that HueEmulator could be made to work on port 443? Probably wishful thinking.
Recommended Posts