Yeelights

The Yeelight app said it found a bulb (bulb1) but when I look at the device list i can't find it. I waited and it happened again. I'm trying to add two bulbs. They show up quickly for mDNS.

Update - I now see image

OK, I figured out I need to choose the bulb in the second screen. The drop-down UI is not obvious -- it should use a standard drop down. But I've figured it out. BUt the null device turned out to be a duplicate


but it's still not finding the two new bulbs.

Did you turn on the LAN control at each bulb in Yeelight app?

Thank-You for posting this. Hubitat just arrived 1 hour ago. Setup Hue integration easy but Yeelights were being stubborn and invisible....

Had missed the need for or existence of LAN integration in Yeelight app, solved :grin:

1 Like

Yes, made sure the LAN settings is on. I see the devices in mDNS. Well, I see four -- not sure if the lamp is showing up. I'm looking at the mDNS info but not sure how to tell which is the lamp.

(Message to the IoT world -- please respond on port 80 with a self-description)

Tracked it down. The lamp does not seem to provide an mDNS response.

BTW, it would be nice if the Yeelight device status provided the IP address last used. (I know it can change).

After a day or so it finds three devices. One is called "Bulb1" which never shows but may really be the Yee Lamp which does show and work. But the third bulb and/or the strip are never found. They do show up with mDNS but not the SSDP search.

I have a group of RGB Yeelights in my living room lamp fixture. I grouped them together for ease of singular control. Whenever the bulbs in group do heartbeat I'm getting an error, not sure if I have a problem with group creation, seems to work with simple schedule and basic controls.

[codebox]dev:92019-02-17 02:36:32.185 pm errorgroovy.lang.MissingMethodException: No signature of method: groupBulbDimmer.heartbeat() is applicable for argument types: () values: [] (heartbeat)

dev:82019-02-17 02:36:32.153 pm debugheartbeat- message sent...

dev:82019-02-17 02:36:32.152 pm debugts- ct:1550442992125, lhb: 1550442872242, age: 119883

dev:82019-02-17 02:36:32.150 pm debuggetReTry- reTryCount:0

dev:72019-02-17 02:36:32.110 pm debugheartbeat- message sent...

dev:72019-02-17 02:36:32.102 pm debugts- ct:1550442992099, lhb: 1550442872188, age: 119911

dev:72019-02-17 02:36:32.100 pm debuggetReTry- reTryCount:0

dev:62019-02-17 02:36:32.079 pm debugheartbeat- message sent...

dev:62019-02-17 02:36:32.075 pm debugts- ct:1550442992065, lhb: 1550442872141, age: 119924

dev:62019-02-17 02:36:32.073 pm debuggetReTry- reTryCount:0

dev:52019-02-17 02:36:32.055 pm debugheartbeat- message sent...

dev:52019-02-17 02:36:32.044 pm debugts- ct:1550442992038, lhb: 1550442872134, age: 119904

dev:52019-02-17 02:36:32.042 pm debuggetReTry- reTryCount:0

dev:42019-02-17 02:36:32.040 pm debugheartbeat- message sent...

dev:42019-02-17 02:36:32.024 pm debugts- ct:1550442992022, lhb: 1550442872088, age: 119934

dev:42019-02-17 02:36:32.020 pm debuggetReTry- reTryCount:0[/codebox]

I think recreating the group should fix that, I have a group of 5 yeeelight bulbs on my dining room and works great, I even have a smart dimmer linked to them so if they are in any color but turned off, turning them on with the dimmer manually will change the color to daylight and 50% of brightness, works great because my family always use that dimmer.

Thank-You, yes re-creating group stopped error on heat beat.

My early simple setup was easy to go fix broken rule machine rules, I can see once more rules are created small changes could make lots of repair work.... I have so much to learn here lol

1 Like

Thanks HE Team for updating the Yeelight app to include the strips in 2.0.6. Works well. Love it!

(there was a slight error upon finding the strip, maybe because it had already found it months ago, but after fixing a few bits on the device page, it all works).

3 Likes

Same here! Big thanks to HE Team for the update. I uninstalled the yeelight app before running the 2.0.6 update. After the update, I installed and it found my lightstrip and was working right away.

Now to figure out how to turn off the auto on and off settings I configured in the yeelight android app 2 phones ago...

Any way to remove the flood of "ssdpTerm" events every 30mins in System Events? There's no description, not sure what it's doing or what the purpose of displaying it there is. @mike.maxwell

1 Like

It's keeping the device ips updated.

Hey Mike, actually I wanted to ask about this too, for example, I have 10 Yeelight, 4 more to be installed later, I seen those ssdpTerm for each bulb and for example, Sharptools receive a refresh for each too, is not slowing the hub all this talk? Is not better to have static ip and eliminate this? Or an option to control this if using static ip?

You can turn off the logging for Sharptools if it becomes annoying.

I was asking about the ssdpterm because it didn't seem to me in the same classification as a System Event. As you can see, my System Events are 99% yeelight chatter:


Not trying to be pedantic here, it's just something I've noticed.

I know turning off the Sharptools debug will help(with logs) but I just saying about the data in the background processed. Anyway, none of my ideas are good enough.

I just got the Yeelight 480MM (YLXD05YL) white ceiling light (220V sigh). Any plans for support?

I've written my own code based in an npm Yeelight library and it works fine with the YLXD05YL but it isn't being discovered.

Suggestion -- allow me to add bulbs by IP address instead of depending on discovery. I can assure that they have static addresses. While I prefer not to rely on static addresses they are an option.

1 Like

I know I read this somewhere but can't find it again. Do the YLDP04YL (color) and YLDP05YL (adj white) Yeelight bulbs come back up in their previous state when power is removed/restored? TIA