Hey team, I’m new to Docker so this might be something obvious that I’m missing.
I have a yeelight that I’m looking to test out diyHue with. I have a rpi2b here but I’m just looking to get diyHue running in a familiar environment before I push on there.
I can get the docker container running in both host and bridge mode:
docker run -d --name diyHue --restart=always --network=host -e MAC=MYMACADDRESS -v /mnt/hue-emulator/config:/opt/hue-emulator/config diyhue/core:latest docker run -d --name diyHue --restart=always --network=bridge -v /mnt/hue-emulator/config:/opt/hue-emulator/config -e MAC=MYMACADDRESS -e IP=MYIPADDRESS -p 80:80/tcp -p 443:443/tcp -p 1900:1900/udp -p 2100:2100/udp -p 1982:1982/udp diyhue/core:latest
Looking at the docker logs, everything is coming up well enough, with the final log saying the server is running and providing the IP address. All good so far.
But, I can only access the web interface when I’m using the bridge version. That also means that the diyHue node (? I assume it’s called a node) shows up in my hue app when I’m running in bridge mode.
I’d be happy to push on with bridge mode, except my yeelight doesn’t show up! This github issue suggests that it’s because of the way yeelights are discovered, and I should be using host mode to proceed (or, apply some complicated fixes I don’t understand right now)
So, to get to my point - I’m trying to access the web interface of diyHue running in docker ‘host’ mode. There’s a good chance I’m just missing something obvious with my Docker config. Please help!