# \[APP\] Yeelights LAN

**URL:** <https://community.homey.app/t/app-yeelights-lan/21134>\
**Category:** Apps\
**Tags:** app, lights, yeelights\
**Created:** [November 22, 2019, 10:13pm UTC](https://community.homey.app/t/app-yeelights-lan/21134 "2019-11-22T22:13:16Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![mirius](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mirius/32/12478_2.png) [@mirius](https://community.homey.app/u/mirius)\
**Post date:** [November 29, 2019, 7:58pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/21 "2019-11-29T19:58:36Z")

</div>

Sure. Same result:

> ─────────────── Logging stdout & stderr ───────────────  
> 2019-11-29 20:57:09 [log] [YeelightApp] Initializing Yeelight app …  
> discovered and saved new devices  
> {}  
> Raw results after discovery  
> {}

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 29, 2019, 8:41pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/22 "2019-11-29T20:41:35Z")

</div>

See on [https://pastebin.com/3L5Lxedk](https://pastebin.com/3L5Lxedk) , it’s little bit longer

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [November 29, 2019, 9:47pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/23 "2019-11-29T21:47:30Z")

</div>

> [@mirius](#):
>
> Sure. Same result

Are you sure you have the latest debug version. Looking at the output from @Sharkys it is what I expected. Your output suggests no lights where discovered at all which would indicate network issues if the lights where powered on.

> [@Sharkys](#):
>
> See on [https://pastebin.com/3L5Lxedk](https://pastebin.com/3L5Lxedk)

Thanx, this all looks pretty good. Did you still not see any results in the pair wizard? I’ll check it in further detail later this weekend. Need to get some sleep.

---

<div class="post-metadata">

**Author:** ![mirius](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mirius/32/12478_2.png) [@mirius](https://community.homey.app/u/mirius)\
**Post date:** [November 29, 2019, 10:03pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/24 "2019-11-29T22:03:52Z")

</div>

Maybe I ran the wrong version the last time… I downloaded the app again from GitHub and the output looks more correct now. Still getting the “No new devices have been found” message when trying to add the Yeelight, but the log lines are pasted below.

> ─────────────── Logging stdout & stderr ───────────────  
> 2019-11-29 22:58:30 [log] [YeelightApp] Initializing Yeelight app …  
> processing id: 0x0000000007d13b3e with message type discover where id in new\_devices is false and where id in added\_devices is false  
> new device discovered and temporary saved  
> Device ID: 0x0000000007d13b3e  
> Device IP: 192.168.2.167  
> processing id: 0x0000000007d13b3e with message type discover where id in new\_devices is true and where id in added\_devices is false  
> new device discovered and not temporary saved  
> Device ID: 0x0000000007d13b3e  
> Device IP: 192.168.2.167  
> Already in new devices: true  
> Already in added devices: false  
> discovered and saved new devices  
> { ‘0x0000000007d13b3e’:  
> { id: ‘0x0000000007d13b3e’,  
> address: ‘192.168.2.167’,  
> port: 55443,  
> model: ‘color’,  
> onoff: true,  
> dim: 70,  
> mode: 1,  
> temperature: 5750,  
> rgb: 16777215,  
> hue: 0,  
> saturation: 0,  
> connected: false } }  
> Raw results after discovery  
> { ‘0x0000000007d13b3e’:  
> { id: ‘0x0000000007d13b3e’,  
> address: ‘192.168.2.167’,  
> port: 55443,  
> model: ‘color’,  
> onoff: true,  
> dim: 70,  
> mode: 1,  
> temperature: 5750,  
> rgb: 16777215,  
> hue: 0,  
> saturation: 0,  
> connected: false } }

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 30, 2019, 5:52am UTC](https://community.homey.app/t/app-yeelights-lan/21134/25 "2019-11-30T05:52:02Z")

</div>

Yep, still no new devices. No hurry, enjoy weekend !

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [November 30, 2019, 8:14am UTC](https://community.homey.app/t/app-yeelights-lan/21134/26 "2019-11-30T08:14:43Z")

</div>

Thanx guys, I think I nailed it. Could you test the **master** branch.

> **[jghaanstra/com.yeelight](https://github.com/jghaanstra/com.yeelight)**
>
> Homey app for controlling Yeelights. Contribute to jghaanstra/com.yeelight development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![mirius](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mirius/32/12478_2.png) [@mirius](https://community.homey.app/u/mirius)\
**Post date:** [November 30, 2019, 10:01am UTC](https://community.homey.app/t/app-yeelights-lan/21134/27 "2019-11-30T10:01:47Z")

</div>

Hi. Unfortunately, I have the same issue with the newest master branch at my end…

 ![Screenshot_20191130-105839](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/2/92b80e184257a7e9922c429333c286203811ecd3.png)

---

<div class="post-metadata">

**Author:** ![Marc\_H](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_h/32/9538_2.png) [@Marc\_H](https://community.homey.app/u/Marc_H)\
**Post date:** [November 30, 2019, 12:48pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/28 "2019-11-30T12:48:06Z")

</div>

Same here, unfortunately. Still “No new devices have been found” with the newest master branch…

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [November 30, 2019, 6:08pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/29 "2019-11-30T18:08:50Z")

</div>

Ok, the cause of the issue where Yeelights are not discovered had been found. It appears to be a bug in Homey core where certain device ID’s are not handled correctly. I’ll report it with Athom and I’ll see if I can come up with some sort of a fix.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [November 30, 2019, 8:46pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/30 "2019-11-30T20:46:13Z")

</div>

Jelger, does it mean please that if I delete Yeelights under Xiaomi, then with Yeelights it will work? Not sure if you recall how I had to repair LED Strip lights via “restore”, as even when deleted LED Stripe,it anyway said “No new device…”

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [November 30, 2019, 9:39pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/31 "2019-11-30T21:39:53Z")

</div>

No, wait until I have implemented a solution or Athom fixed this bug.

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [December 1, 2019, 9:06am UTC](https://community.homey.app/t/app-yeelights-lan/21134/32 "2019-12-01T09:06:08Z")

</div>

> [@Sharkys](#):
>
> Jelger, does it mean please that if I delete Yeelights under Xiaomi, then with Yeelights it will work? Not sure if you recall how I had to repair LED Strip lights via “restore”, as even when deleted LED Stripe,it anyway said “No new device…”

My initial no on this might be wrong. When I tested this I was able to add my own Yeelight under both apps so I concluded that it’s possible to add a device with the same device ID under different apps. But perhaps my Yeelight ID changed over time or was registered with a different ID. Would you be willing to test it by removing one of your devices under the Xiaomi Mi Home app and see if it gets discovered by the GitHub master branch version.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [December 1, 2019, 12:31pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/33 "2019-12-01T12:31:22Z")

</div>

Interesting, now all lights have been found in parallel to those loaded with Xiaomi APP with Master branch on GitHUB (not with version 1.0.2 on app store, so congrats of finding workaround / fix 🙂 )

… BUT - I removed by Yeelights LED stripe and still when searching for it, I’m getting - No new devices has been found (it was longer time offline before removal). Could there be anything specific to the LED Stripe ?  
Please note it is online and controllable with Yeelight app and YES, LAN mode is enabled, same as static IP address.

What is interesting, that previously LED Stripe did not appear even on DEBUG scan output : [https://pastebin.com/3L5Lxedk](https://pastebin.com/3L5Lxedk)

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [December 1, 2019, 2:03pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/34 "2019-12-01T14:03:32Z")

</div>

> [@Sharkys](#):
>
> What is interesting, that previously LED Stripe did not appear even on DEBUG scan output : [https://pastebin.com/3L5Lxedk](https://pastebin.com/3L5Lxedk)

If it’s not discovered here than it did not send a discovery message when searching for lights. Perhaps toggle the LAN mode to make sure it’s discoverable. When the light does not send a discovery message there is not much I can do.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [December 1, 2019, 2:23pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/35 "2019-12-01T14:23:47Z")

</div>

What is odd, last time I tried even resetting the strip, didn’t work either. Also LAN toggle on off tried alread before I wrote here ☹ Will be elaborating more, thank you

---

<div class="post-metadata">

**Author:** ![wvduffelen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/wvduffelen/32/34133_2.png) [@wvduffelen](https://community.homey.app/u/wvduffelen)\
**Post date:** [December 1, 2019, 3:02pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/36 "2019-12-01T15:02:11Z")

</div>

For what it’s worth, when I removed my devices from the old app the Yeelight app found them the first time!!

---

<div class="post-metadata">

**Author:** ![Phuturist](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/phuturist/32/49_2.png) [@Phuturist](https://community.homey.app/u/Phuturist)\
**Post date:** [December 1, 2019, 3:10pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/37 "2019-12-01T15:10:59Z")

</div>

Thanx to everyone who helped troubleshoot the pairing issues. I have made some improvements to to pairing process and published version 1.0.3 to the app store which is now pending approval.

Biggest learning however is that devices can not be paired when they have the same device ID even when paired in a different app. Thisis a [bug](https://github.com/athombv/homey-apps-sdk-issues/issues/107) in Homey core and has been reported and will be fixed in the next firware release of Homey. What it means is that you will have to remove your Yeelights from the Xiaomi Mi Home app before being able to pair them in this new Yeelights app on any firmware equal or lower than 3.1.1.

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [December 1, 2019, 6:07pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/38 "2019-12-01T18:07:38Z")

</div>

Another reset of LED strips and all is working fine 🙂

---

<div class="post-metadata">

**Author:** ![Marc\_H](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marc_h/32/9538_2.png) [@Marc\_H](https://community.homey.app/u/Marc_H)\
**Post date:** [December 2, 2019, 10:19am UTC](https://community.homey.app/t/app-yeelights-lan/21134/39 "2019-12-02T10:19:09Z")

</div>

Also removed the last undiscovered Yeelight from the Xiaomi app. That also solved the problem in the new app. Thanx to Jelger for troubleshooting this problem!

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [December 2, 2019, 11:06am UTC](https://community.homey.app/t/app-yeelights-lan/21134/40 "2019-12-02T11:06:21Z")

</div>

Ups, so LED stripe in Homey did work only till next day - again it’s unreachable while original app can control it fine ☹  
Is anyone experiencing the same?

Update - powering led stripe off/on (so that uptime gets to 0 minutes) resolved it again. It looks like some firmware issue to me

[Previous page](https://community.homey.app/t/app-yeelights-lan/21134.md?page=1)

[Next page](https://community.homey.app/t/app-yeelights-lan/21134.md?page=3)
