That might be the problem, everybody I know has only one device and the app works fine, including me. I’ll try to get another bulb or strip. Sorry for the inconvenience
Hay man, thanx for trying! I’d really like a solution to control the bulb(s) from my PC
I have 3 color bulbs and 1 mono bulb. Doesn’t work for me either
I have 1 RGB bulb, and Windows 10 on LAN, bulb is on 2,4Ghz, works fine with Android (phone is on 5Ghz and no issues).
I see no bulbs, and I can’t add it manually the IP adress of it.
I supposed your Windows 10 must be connected to same W-Fi with the bulb not LAN.
Please correct me if I am wrong.
I have one bulb but it is not detected. Neither by your app or the chrome app.
Version “yeelight_toolbox_1.1.5” working fine for me on my Win10 64.
Is there a way to start the movie mode via command line?
I updated the app to 1.1.6.
I might have found the cause for the bulb scanning issues.
Please test it and leave your feedback.
Thanks!
There isn’t
is there any plans to include, or a way you can start it with Google Home or Home Assistant
It still doesn’t work for me. Nothing happens when I run it and click discover…
Please, all people that Yeelight Toolbox doesn’t recognize their bulbs, try this little program to see if it recognizes them. It’s a command terminal program that only sends the discovery message through the network and receives the possible bulbs responses. It will show you the received messages and the number of bulbs detected.
You can download it here: https://drive.google.com/open?id=1RLK_77zSKWHjvcDe6V7vyPfw-UEU6sw9
It looks like this:
Thanks.
Pablo has been helping me resolve the issue. We think it is windows messing with network adapters. Please, try his app and post your results.
Edit: I also published 1.1.7 with Pablo’s fix. Now it should work flawlessly even if your computer has multiple virtual network adapters. Please, provide feedback and try Pablo’s app to verify if mine still fails. Thanks!
The command line first found 7 bulbs, then 9… I’m afraid to run it the 3rd time I have 5 devices
The 1.1.7 still does nothing…
Discovery message succesfully sended through IP 169.254.255.178
Received message:
HTTP/1.1 200 OK
Cache-Control: max-age=3600
Date:
Ext:
Location: yeelight://192.168.1.220:55443
Server: POSIX UPnP/1.0 YGLC/1
id: 0x00000000035e4652
model: color
fw_ver: 56
support: get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene cron_add cron_get cron_del set_ct_abx set_rgb set_hsv set_adjust set_music set_name
power: on
bright: 100
color_mode: 2
ct: 4080
rgb: 2945792
hue: 359
sat: 100
name: Lamp Right
Received message:
HTTP/1.1 200 OK
Cache-Control: max-age=3600
Date:
Ext:
Location: yeelight://192.168.1.231:55443
Server: POSIX UPnP/1.0 YGLC/1
id: 0x000000000361ddcd
model: mono
fw_ver: 53
support: get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene cron_add cron_get cron_del set_adjust set_name
power: off
bright: 100
color_mode: 2
ct: 4000
rgb: 0
hue: 0
sat: 0
name: Kitchen
Received message:
HTTP/1.1 200 OK
Cache-Control: max-age=3600
Date:
Ext:
Location: yeelight://192.168.1.221:55443
Server: POSIX UPnP/1.0 YGLC/1
id: 0x00000000035b446d
model: color
fw_ver: 56
support: get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene cron_add cron_get cron_del set_ct_abx set_rgb set_hsv set_adjust set_music set_name
power: on
bright: 100
color_mode: 2
ct: 4080
rgb: 10483
hue: 359
sat: 100
name: Lamp Left
Received message:
HTTP/1.1 200 OK
Cache-Control: max-age=3600
Date:
Ext:
Location: yeelight://192.168.1.220:55443
Server: POSIX UPnP/1.0 YGLC/1
id: 0x00000000035e4652
model: color
fw_ver: 56
support: get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene cron_add cron_get cron_del set_ct_abx set_rgb set_hsv set_adjust set_music set_name
power: on
bright: 100
color_mode: 2
ct: 4080
rgb: 2945792
hue: 359
sat: 100
name: Lamp Right
Received message:
HTTP/1.1 200 OK
Cache-Control: max-age=3600
Date:
Ext:
Location: yeelight://192.168.1.210:55443
Server: POSIX UPnP/1.0 YGLC/1
id: 0x0000000003343c0c
model: stripe
fw_ver: 40
support: get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene cron_add cron_get cron_del set_ct_abx set_rgb set_hsv set_adjust set_music set_name
power: off
bright: 100
color_mode: 2
ct: 4000
rgb: 16711680
hue: 0
sat: 100
name: Strip
Received message:
HTTP/1.1 200 OK
Cache-Control: max-age=3600
Date:
Ext:
Location: yeelight://192.168.1.230:55443
Server: POSIX UPnP/1.0 YGLC/1
id: 0x0000000003472b4c
model: mono
fw_ver: 53
support: get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene cron_add cron_get cron_del set_adjust set_name
power: on
bright: 100
color_mode: 2
ct: 4000
rgb: 0
hue: 0
sat: 0
name: Diner
Received message:
HTTP/1.1 200 OK
Cache-Control: max-age=3600
Date:
Ext:
Location: yeelight://192.168.1.210:55443
Server: POSIX UPnP/1.0 YGLC/1
id: 0x0000000003343c0c
model: stripe
fw_ver: 40
support: get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene cron_add cron_get cron_del set_ct_abx set_rgb set_hsv set_adjust set_music set_name
power: off
bright: 100
color_mode: 2
ct: 4000
rgb: 16711680
hue: 0
sat: 100
name: Strip
Received message:
HTTP/1.1 200 OK
Cache-Control: max-age=3600
Date:
Ext:
Location: yeelight://192.168.1.221:55443
Server: POSIX UPnP/1.0 YGLC/1
id: 0x00000000035b446d
model: color
fw_ver: 56
support: get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene cron_add cron_get cron_del set_ct_abx set_rgb set_hsv set_adjust set_music set_name
power: on
bright: 100
color_mode: 2
ct: 4080
rgb: 10483
hue: 359
sat: 100
name: Lamp Left
Received message:
HTTP/1.1 200 OK
Cache-Control: max-age=3600
Date:
Ext:
Location: yeelight://192.168.1.230:55443
Server: POSIX UPnP/1.0 YGLC/1
id: 0x0000000003472b4c
model: mono
fw_ver: 53
support: get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene cron_add cron_get cron_del set_adjust set_name
power: on
bright: 100
color_mode: 2
ct: 4000
rgb: 0
hue: 0
sat: 0
name: Diner
9 devices found!
Press any key to continue . . .
If it detects more devices than you actually have, it is not a problem. It happens because of the way the program has to handle repeated bulb responses (each bulb sends two identical messages when they receive the discovery message). If you look at the IPs of the bulbs that respond, the program caught these messages:
192.168.1.220 - twice
192.168.1.231 - once
192.168.1.221 - twice
192.168.1.210 - twice
192.168.1.230 - twice
(Please, next time take a screenshot rather than copying the entire text, thanks )
The important thing is that my program discovered the devices and, consequently, the discovery algorithm works (for you, at least).
We’ll look into it to definitely solve the problem.
The new version 1.1.7 still doesn’t detect my light.
And Pablo tool detect 0 device. Any idea ? Thanks.
That’s strange… Could you try again switching off and on again the bulb around ten seconds before running my program? If you try multiple times and it doesnt work any time, tell us… Although that would mean that we havent found the problem…
Thanks in advance.
Still doesn’t work. Also tried to reset the bulb (and reactivating LAN mode), but still doesn’t work.
One strange think is that official demo of developer mode doesn’t work too.
If the official demo doesnt work too, I cant help you much more. I recommend you to try on another PC if you can. Try also to turn off the firewall. If nothing works, maybe its your local network. You can use Wireshark to see what happens to the packets, if your PC sends and receives correctly.
Good luck!