Can't find Yeelight lamp within Hue app

Support
1

Problem:
I am unable to find my Yeelight through the official Hue app. Hue bridge is connecting just fine.

Environment used:
I use the docker Container running in bridge mode on Windows. I was unable to setup Host mode. For some reason i can’t connect to my localhost within bridge mode so the linkbutton won’t work. My yeeligt is pingable through the Docker CLI.

I’m not that experienced with Docker and i wanted to try diyHue out before buying a Raspberry Pi 4.

If more information is needed, please let me know.

2

Are you able to access the WebUI for DIYHue? Are you able to add the bridge to the Hue or Hue Essentials app? I would suspect that bridge mode is going to make it difficult to work correctly. Are you running anything else on your PC that uses any of the ports DIYHue does? 80, 443, etc?

I think bridge mode might be possible but I was only ever able to get DIYHue working in Host mode or in MAC/VLAN mode (where you create a dummy network connection that has it’s own IP and MAC address). But I did it on my Pi, so I wouldn’t know how to set that up on Windows. I’m sure there are tutorials out there though.

3

Hi Ryan!
Yes i am able to access the WebUI for DIYHue and i am able to add the bridge to the Hue app. I am able to add the bridge to the Hue essentials app as well. Port 443/80 are open and are only used by DIYHue.

I did some digging and i could see that the Gateway in the config.json is set to 192.168.2.1 instead of my network gateway (192.168.2.254). I am unable to change it though as it overwrites itself when i try to search the lights. Can it possibly have something to do with that?

Thanks for the support!

4

Small update:
Managed to edit the config by editing the Py script. Didn’t fix the issue though…

This is the output i get when trying to search for lights:

2020-10-24 19:15:40,491 - root - DEBUG - shelly: <discover> invoked!

2020-10-24 19:15:40,493 - root - DEBUG - ESPHome: <discover> invoked!

2020-10-24 19:15:40,507 - root - INFO - MQTT discovery called

2020-10-24 19:15:40,507 - root - DEBUG - Hyperion: <discover> invoked!

172.17.0.1 - - [24/Oct/2020 19:15:40] "GET /api/8b963184158511eba4f60242ac110002/lights HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:40] "GET /api/8b963184158511eba4f60242ac110002/groups HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:40] "GET /api/8b963184158511eba4f60242ac110002/lights/new HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:40] "GET /api/8b963184158511eba4f60242ac110002/sensors/new HTTP/1.1" 200 -

2020-10-24 19:15:41,309 - root - DEBUG - Sending M-Search response to 172.17.0.2

172.17.0.1 - - [24/Oct/2020 19:15:41] "GET /api/8b963184158511eba4f60242ac110002/lights/new HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:41] "GET /api/8b963184158511eba4f60242ac110002/sensors/new HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:42] "GET /api/8b963184158511eba4f60242ac110002/config HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:42] "GET /api/8b963184158511eba4f60242ac110002/lights HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:42] "GET /api/8b963184158511eba4f60242ac110002/groups HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:43] "GET /api/8b963184158511eba4f60242ac110002/lights/new HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:43] "GET /api/8b963184158511eba4f60242ac110002/sensors/new HTTP/1.1" 200 -

2020-10-24 19:15:43,493 - root - DEBUG - Yeelight search end

172.17.0.1 - - [24/Oct/2020 19:15:44] "GET /api/8b963184158511eba4f60242ac110002/lights/new HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:44] "GET /api/8b963184158511eba4f60242ac110002/sensors/new HTTP/1.1" 200 -

2020-10-24 19:15:44,462 - root - INFO - sync with lights

2020-10-24 19:15:44,728 - root - DEBUG - tasmota: probing ip 172.17.0.1

2020-10-24 19:15:44,729 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 172.17.0.1:80

2020-10-24 19:15:44,730 - root - DEBUG - shelly: found ip: 172.17.0.1

2020-10-24 19:15:44,730 - root - DEBUG - shelly: probing ip 172.17.0.1

2020-10-24 19:15:44,731 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 172.17.0.1:80

172.17.0.1 - - [24/Oct/2020 19:15:44] code 404, message not found

172.17.0.1 - - [24/Oct/2020 19:15:44] "GET /shelly HTTP/1.1" 404 -

172.17.0.1 - - [24/Oct/2020 19:15:44] code 404, message not found

172.17.0.1 - - [24/Oct/2020 19:15:44] "GET /cm?cmnd=Status%200 HTTP/1.1" 404 -

2020-10-24 19:15:44,733 - urllib3.connectionpool - DEBUG - http://172.17.0.1:80 "GET /shelly HTTP/1.1" 404 447

2020-10-24 19:15:44,734 - urllib3.connectionpool - DEBUG - http://172.17.0.1:80 "GET /cm?cmnd=Status%200 HTTP/1.1" 404 447

172.17.0.1 - - [24/Oct/2020 19:15:44] "GET /api/8b963184158511eba4f60242ac110002/lights HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:44] "GET /api/8b963184158511eba4f60242ac110002/groups HTTP/1.1" 200 -

2020-10-24 19:15:45,543 - root - INFO - [

"192.168.2.2:80",

"192.168.2.3:80",

"192.168.2.21:80",

"192.168.2.28:80",

"192.168.2.38:80",

"192.168.2.254:80"

]

2020-10-24 19:15:45,544 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.2.2:80

172.17.0.1 - - [24/Oct/2020 19:15:45] code 404, message not found

172.17.0.1 - - [24/Oct/2020 19:15:45] "GET /api/8b963184158511eba4f60242ac110002/lights/new HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:45] "GET /detect HTTP/1.1" 404 -

2020-10-24 19:15:45,548 - urllib3.connectionpool - DEBUG - http://192.168.2.2:80 "GET /detect HTTP/1.1" 404 447

2020-10-24 19:15:45,549 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.2.3:80

172.17.0.1 - - [24/Oct/2020 19:15:45] code 404, message not found

172.17.0.1 - - [24/Oct/2020 19:15:45] "GET /detect HTTP/1.1" 404 -

2020-10-24 19:15:45,550 - urllib3.connectionpool - DEBUG - http://192.168.2.3:80 "GET /detect HTTP/1.1" 404 447

2020-10-24 19:15:45,551 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.2.21:80

2020-10-24 19:15:45,555 - urllib3.connectionpool - DEBUG - http://192.168.2.21:80 "GET /detect HTTP/1.1" 404 30

2020-10-24 19:15:45,556 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.2.28:80

2020-10-24 19:15:45,563 - urllib3.connectionpool - DEBUG - http://192.168.2.28:80 "GET /detect HTTP/1.1" 404 30

2020-10-24 19:15:45,565 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.2.38:80

172.17.0.1 - - [24/Oct/2020 19:15:45] "GET /api/8b963184158511eba4f60242ac110002/sensors/new HTTP/1.1" 200 -

2020-10-24 19:15:45,570 - urllib3.connectionpool - DEBUG - http://192.168.2.38:80 "GET /detect HTTP/1.1" 404 None

2020-10-24 19:15:45,571 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 192.168.2.254:80

2020-10-24 19:15:45,577 - urllib3.connectionpool - DEBUG - http://192.168.2.254:80 "GET /detect HTTP/1.1" 302 0

2020-10-24 19:15:45,578 - urllib3.connectionpool - DEBUG - Resetting dropped connection: 192.168.2.254

2020-10-24 19:15:45,581 - urllib3.connectionpool - DEBUG - http://192.168.2.254:80 "GET /login.htm HTTP/1.1" 301 45

2020-10-24 19:15:45,582 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): mijnmodem.kpn:443

2020-10-24 19:15:45,593 - root - INFO - ip 192.168.2.254:80 is unknown device: HTTPSConnectionPool(host='mijnmodem.kpn', port=443): Max retries exceeded with url: /login.htm (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1056)')))

2020-10-24 19:15:45,595 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 127.0.0.1:8080

2020-10-24 19:15:45,596 - root - INFO - registration fail, is the link button pressed?

2020-10-24 19:15:46,016 - root - DEBUG - ESPHome: probing ip 172.17.0.1

2020-10-24 19:15:46,017 - urllib3.connectionpool - DEBUG - Starting new HTTP connection (1): 172.17.0.1:80

172.17.0.1 - - [24/Oct/2020 19:15:46] "GET /text_sensor/light_id HTTP/1.1" 200 -

2020-10-24 19:15:46,018 - urllib3.connectionpool - DEBUG - http://172.17.0.1:80 "GET /text_sensor/light_id HTTP/1.1" 200 90

2020-10-24 19:15:46,019 - root - DEBUG - ESPHome: ip 172.17.0.1 is unknown device, list indices must be integers or slices, not str

172.17.0.1 - - [24/Oct/2020 19:15:46] "GET /api/8b963184158511eba4f60242ac110002/lights/new HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:46] "GET /api/8b963184158511eba4f60242ac110002/sensors/new HTTP/1.1" 200 -

172.17.0.1 - - [24/Oct/2020 19:15:47] "GET /api/8b963184158511eba4f60242ac110002/lights HTTP/1.1" 200 -

I think it has to do with the certificate. When accessing the page i receive a certificate invalid error, but i can’t seem to fix it.

5

I have been able to fix the issue!
I have built my container from scratch within a Raspberry Pi VM. I can connect to my bridge and i can find my lights!

Thanks for the support :slight_smile: