# \[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:** 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:** [November 22, 2019, 10:13pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/1 "2019-11-22T22:13:16Z")

</div>

# Yeelights LAN for Homey

 ![Yeelights LAN](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/b/1bf376963ce7d9557001643f126a3c83a968c460.jpeg)

[**Production version**](https://homey.app/a/com.yeelight) · [**Test version**](https://homey.app/a/com.yeelight/test) · [**Source code**](https://github.com/shaarkys/com.yeelight)

## About this app

Yeelights LAN enables Homey to control compatible Yeelight Wi-Fi lighting directly over your local network.

Communication takes place locally between Homey and the light. Once the device has been configured and LAN Control enabled, normal operation does not depend on the Yeelight cloud.

The app supports many Yeelight lights that implement the Yeelight LAN protocol, including:

- White and dimmable bulbs
- Colour bulbs
- Colour-temperature lights
- Light strips
- Bedside and desk lamps
- Ceiling lights
- Selected lights with background or Ambilight control
- Yeelight Screen Bar Pro

Available capabilities depend on the exact Yeelight model. Depending on the device, these can include power, dimming, colour temperature, colour, night mode and background lighting.

> A Yeelight product name or Wi-Fi connection alone does not guarantee compatibility. The device must support the Yeelight LAN protocol and allow LAN Control to be enabled.

For cloud-based control, use the separate [Yeelight Cloud app](https://homey.app/a/com.yeelight.cloud).

## Current version

The current production version is **3.2.6** and requires Homey v5.0.0 or newer.

Recent development includes:

- Corrected the capabilities assigned to `yeelink.light.ceiling6`
- Improved device pairing and diagnostic logging
- Added light available and unavailable Flow cards
- Improved handling of incoming messages to prevent occasional parsing errors
- Added support for Yeelight Screen Bar Pro
- Added and improved support for newer ceiling-light models
- Prevented Night Mode from automatically switching on a light
- Fixed a crash affecting Homey Self-Hosted Server environments

## Before pairing: enable LAN Control

LAN Control must be enabled in the official Yeelight mobile application before Homey can discover the light.

Depending on the Yeelight app and device firmware, the setting may be called **LAN Control** or **Developer Mode**.

1. Open the official Yeelight app.
2. Select the light you want to add.
3. Open its settings.
4. Find **LAN Control** or **Developer Mode**.
5. Enable the option.
6. Leave the light powered on and connected to Wi-Fi.
7. Start pairing in Homey.

### LAN Control option not available

Not every Yeelight model or firmware version provides LAN access. Availability can also depend on the selected region in the Yeelight app.

If the option is missing:

- Confirm the exact device model.
- Check for device firmware and official Yeelight app updates.
- Verify that the correct region or server is selected.
- Check whether the manufacturer still allows LAN Control for that model.
- Consider using the [Yeelight Cloud app](https://homey.app/a/com.yeelight.cloud).

Installing an older Yeelight APK should only be considered as a last resort. Older or unofficial applications can contain security vulnerabilities and may expose your Yeelight account credentials. If you choose this approach, use a trusted source, verify the package and reinstall the current official version afterwards.

This Homey app cannot enable LAN access on a device that does not expose the Yeelight LAN protocol.

## Network requirements

Automatic discovery uses UDP multicast address `239.255.255.250` on port `1982`. Commands are subsequently sent directly to the light over TCP, normally using port `55443`.

For the most reliable operation:

- Connect Homey and the Yeelight device to the same local network.
- Using the same subnet is recommended.
- Disable Wi-Fi client or access-point isolation.
- Allow multicast traffic between Homey and the light.
- Allow local TCP communication to the device.
- Avoid guest networks that prevent communication between clients.
- Reserve a fixed IP address for each light in your DHCP server.

Advanced VLAN configurations can work, but multicast forwarding and the required firewall rules must be configured correctly. Yeelight discovery is not based on mDNS.

The app uses automatic LAN discovery. There is currently no manual-IP pairing option.

## Adding a Yeelight to Homey

1. Enable LAN Control in the official Yeelight app.
2. Confirm that the light is online and responds in the Yeelight app.
3. In Homey, select **Devices → Add device**.
4. Search for **Yeelights LAN**.
5. Select the appropriate device driver.
6. Wait for Homey to discover the light.
7. Select the device and complete pairing.

If a device was paired using an older app version and shows incorrect capabilities, re-pairing may be required after a model-mapping update. Removing a device can affect its existing Flows, so review them before doing so.

## Flow support

The available Flow cards depend on the capabilities of the paired light.

### When

- The light is turned on
- The light is turned off
- The dim level changes
- The light becomes available
- The light becomes unavailable

### And

- The light is on or off
- Night Mode is enabled or disabled
- The light is available or unavailable

### Then

- Turn the light on, off or toggle its state
- Set or change brightness
- Set colour temperature
- Set colour, hue or saturation
- Select a random colour
- Set the default power-on state
- Change brightness and colour temperature over a specified duration
- Set colour and brightness together
- Enable or disable Night Mode
- Save and restore the current light state
- Send an advanced custom command
- Control supported background or Ambilight functions

## Troubleshooting

### Device is not discovered

- Confirm that LAN Control is enabled.
- Ensure that Homey and the light can communicate locally.
- Check that UDP multicast on port `1982` is not blocked.
- Disable Wi-Fi client isolation.
- Avoid guest Wi-Fi networks.
- Temporarily test with Homey and the light on the same subnet.
- Restart the light by disconnecting and reconnecting its power.
- Confirm that the device responds to a ping from another device on the same network.

### Device is paired but unavailable

- Check whether its IP address has changed.
- Reserve a fixed IP address in your router.
- Confirm that TCP communication, normally on port `55443`, is allowed.
- Restart the light, Homey app and, if necessary, the network access point.
- Check whether the light still has LAN Control enabled.

### Incorrect or missing capabilities

The features exposed by Homey are based on the model information announced by the device.

When reporting an incorrectly identified device, include:

- Exact Yeelight model ID, such as `yeelink.light.ceiling6`
- Retail product name
- Device firmware version
- Yeelight app region
- Yeelights LAN app version
- Homey model and firmware version
- Capabilities that are missing or incorrectly displayed

## Support and diagnostics

Please use this forum topic for pairing questions, configuration help and general support.

For confirmed software defects, you can also open an issue on [GitHub](https://github.com/shaarkys/com.yeelight/issues).

When reporting a problem:

1. Reproduce the issue.
2. Send a diagnostic report from the Yeelights LAN app in Homey.
3. Post the diagnostic report ID together with the approximate time of the problem.
4. Include the exact device model, firmware and a clear description of what happened.
5. Explain how Homey and the light are connected to your network.

Please do not publish passwords, authentication details or other private information.

## Credits

Original app and development by **Jelger Haanstra**.

The app is currently maintained and extended as a community project. Thank you to everyone who contributes testing, model information, diagnostics and translations.

Yeelight, Homey and their respective trademarks belong to their owners. This community integration is not affiliated with or endorsed by Yeelight or Athom.

### Support the development

## ❤ Community apps and appreciation

These Homey Community apps are developed and maintained in my spare time.

**Did you know?** In my experience maintaining community Homey apps, only a very small proportion of users choose to support their development financially—even when a new device integration or specific feature has been implemented at their request.

Contributions are never required, but they are a meaningful way to recognise the time invested in development, testing, compatibility updates and ongoing user support. If one of my apps has been useful to you, you can optionally show your appreciation here:

### [❤ Send an optional thank-you via PayPal](https://www.paypal.me/bkubesa)

A contribution does not unlock additional features or affect the support you receive. It is simply a way to say _thank you_.

### My Homey apps

| | | | | | |
| --- | --- | --- | --- | --- | --- |
| [![Smart Presence | 72x72](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/5/5572294d53fb2189c45a72a9383363a452d463c1.png)](https://homey.app/a/nl.terryhendrix.smartpresence)  
[**Smart Presence**](https://homey.app/a/nl.terryhendrix.smartpresence)  
Wi-Fi presence detection | [![Xiaomi Mi Home | 72x72](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/e/de1dc51865d236d901288d617df6f988396b25f6.jpeg)](https://homey.app/a/com.xiaomi-miio)  
[**Xiaomi Mi Home**](https://homey.app/a/com.xiaomi-miio)  
Xiaomi Mi Home devices | [![Broadlink | 72x72](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/6/76034ca18b53c920f581b84b16735f02ada00fd8.jpeg)](https://homey.app/a/com.broadlink)  
[**Broadlink**](https://homey.app/a/com.broadlink)  
IR, RF and smart devices | | | |
| [![TP-Link KASA LAN | 72x72](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/7/c75e3118bdfa1181c879a8e594b3124b86e19636.png)](https://homey.app/a/nu.baretta.tplink)  
[**TP-Link KASA LAN**](https://homey.app/a/nu.baretta.tplink)  
Local Kasa control | [![Yeelights LAN | 72x72](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/b/1bf376963ce7d9557001643f126a3c83a968c460.jpeg)](https://homey.app/a/com.yeelight)  
[**Yeelights LAN**](https://homey.app/a/com.yeelight)  
Local Yeelight control | [![Xiaomi Miija | 72x72](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/7/970146bee00c1112556ff9ad9e7a127bd1f144ce.png)](https://homey.app/a/hu.corenet.mitemp)  
[**Xiaomi Miija**](https://homey.app/a/hu.corenet.mitemp)  
Temperature and humidity sensors | | | |
| [![Octoprint | 72x72](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/8/68c7dac99b9b3142e69c5b4d8703eaa963b15238.png)](https://homey.app/a/no.jonkristian.octoprint)  
[**Octoprint**](https://homey.app/a/no.jonkristian.octoprint)  
Monitor your 3D printer | [![Virtual Radar | 72x72](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/e/9e7cc61abfbfa7922163b466b9179e85496c7c34.jpeg)](https://homey.app/a/com.gruijter.virtualradar)  
[**Virtual Radar**](https://homey.app/a/com.gruijter.virtualradar)  
ADS-B aircraft tracking | [![enigma2 | 72x72](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/8/88d9a3cf5c03b83d34a6a6e3fd2c772c2223b190.png)](https://homey.app/a/eu.carp3-noctem.enigma2)  
[**enigma2**](https://homey.app/a/eu.carp3-noctem.enigma2)  
Control Enigma2 receivers | | | |

[**View all my Homey apps →**](https://homey.app/en-us/apps/author/5cc0b0a87a00d60e7682a494/page/0/)

---

<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 22, 2019, 10:13pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/2 "2019-11-22T22:13:26Z")

</div>

# Changelog

> ## v3.0.13 - 2021-09-27
> 
> Added support for model YLXD013-C (ceilc) - requires re-pairing

> ## v3.0.11 - 2021-07-14
> 
> Branding improvements, no functional changes.

> ## v3.0.10 - 2021-05-29
> 
> Fixed an issue with setting hue or saturation

> ## v3.0.9 - 2021-05-11
> 
> Fixed an issue where the color temperature wheel jumped to a different value after being set.

> ## v3.0.8 - 2021-04-28
> 
> - Fix some minor issues and some code improvements.

> ## v3.0.7 - 2021-04-27
> 
> - Fix some capabilities not updating when controlled from outside of Homey.
> - Added icon for the GU10 (needs repairing)

> ## v3.0.5 - 2021-04-13
> 
> - Fix for setting ambilight color on model ceiling 20 (YLXD50YL).

> ## v3.0.4 - 2021-04-12
> 
> - Add full support for ceiling20 (YLXD50YL).

> ## v3.0.3 - 2021-03-29
> 
> - Fix issue with pairing of (desk)lamps.

> ## v3.0.2 - 2021-02-22
> 
> - Update to SDK3 (requires Homey firmware 5.x)
> - Minor improvements

> ## v1.1.2 - 2020-05-18
> 
> Add support for YLXD42YL (ceiling15).

> ## v1.1.1 - 2020-03-01
> 
> Added action cards for saving and restoring the state of the light which is usefull for switching between scenes.

> ## v1.1.0 - 2020-02-13
> 
> Fixed issue with dim duration. Added action cards for onoff, dim and temperature for ambilight (ceiling 650 and meteorite).

> ## v1.0.5 - 2019-12-16
> 
> Fixed a bug where certain ceiling lights (ceiling4 and ceiling10) did not get the right capabilities during pairing. Please re-pair if you are missing color settings.

> ## v1.0.4 - 2019-12-11
> 
> Small improvements to avoid offline devices in certain cases like temporary unreachable devices due to bad WiFi.

> ## v1.0.3 - 2019-12-01
> 
> Small fixes to improve pairing process and avoid crashes when removing Yeelight devices.

> ## v1.0.2 - 2019-11-24
> 
> Fix for Yeelights that have been online and come online again.

> ## v1.0.1 - 2019-11-23
> 
> Initial version of a standalone app for Yeelights. Please migrate your devices from the Xiaomi Mi Home app to this dedicated Yeelights app.

---

<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 25, 2019, 11:21am UTC](https://community.homey.app/t/app-yeelights-lan/21134/3 "2019-11-25T11:21:07Z")

</div>

Hi, just a question - “migration” means here - remove from Xiaomi App, add to Yeelight and recreate all related flows, right ? 🙂

---

<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 25, 2019, 11:54am UTC](https://community.homey.app/t/app-yeelights-lan/21134/4 "2019-11-25T11:54:02Z")

</div>

Unfortunately yes, you can also add them first to the Yeelights app next to the Xiaomi app. And then remove them from the Xiaomi app. This might make it easier to update your flows with the new device.

---

<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 25, 2019, 4:34pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/5 "2019-11-25T16:34:16Z")

</div>

Actually it says “No new devices” … are you sure it can be added along to Xiaomi app? I don’t want to remove them, as you know I faced this issue with Yeelights even in previous Xiaomi app upon removal…  
Anyone else can confirm they can add lights in parallel to Xiaomi?

---

<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 26, 2019, 3:31pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/6 "2019-11-26T15:31:16Z")

</div>

I managed to add 4 of my 5 yeelights to the new yeelight app (alongside the Xiaomi app). The app does not recognise the 5th yeelight. It’s working in the xiaomi app, but in the yeelight app it also says “No new devices…” So for me the answer is yes and no. Some can be added parallel to Xiaomi, but not all.

---

<div class="post-metadata">

**Author:** ![Mariomark1541](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mariomark1541/32/178160_2.png) [@Mariomark1541](https://community.homey.app/u/Mariomark1541)\
**Post date:** [November 28, 2019, 9:37am UTC](https://community.homey.app/t/app-yeelights-lan/21134/7 "2019-11-28T09:37:50Z")

</div>

I have 2 LED strips and 2 led color bulbs.

All of them are added but at one LED bulb color homey say device not Available.

What must I do to add that light to

---

<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 28, 2019, 6:56pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/8 "2019-11-28T18:56:34Z")

</div>

I’m also getting this error when trying to add my Yeelight LED Bulb (Color) with the new app. The Yeelight is currently working fine with the “old” app (Xiaomi Mi Home).

 ![Screenshot_20191128-194950](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/0/e09ad1775088027889231335b0e841a0ebbb5190.png)

---

<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 28, 2019, 7:46pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/9 "2019-11-28T19:46:57Z")

</div>

About 60 users seem to have made the switch already but it seems a couple of you guys are experiencing the issue where the lights can not be found. I cant explain this and in my own tests it always discovers my lights which makes it hard to troubleshoot. Best advice I can give is to restart the app and try again.

If any of you guys know how to run the app from the command line you could try and run this debug version which should show the raw discovery result. That would at least tell me if the devices are not discovered or that they are not shown in the pairing wizard because they get filtered out (due to some incorrect filtering).

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

---

<div class="post-metadata">

**Author:** ![Geurti](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/geurti/32/8560_2.png) [@Geurti](https://community.homey.app/u/Geurti)\
**Post date:** [November 28, 2019, 9:20pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/10 "2019-11-28T21:20:26Z")

</div>

Reminder!  
Check your flow cards before removing the Xiao Mi Home lights.  
I experienced a lot of work when you don’t 🙈

---

<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, 9:19am UTC](https://community.homey.app/t/app-yeelights-lan/21134/11 "2019-11-29T09:19:32Z")

</div>

So when running debug, it list ALL devices (the list is quite huge) but it says anyway, no new devices found…

> — Profile your app’s performance at [https://go.athom.com/app-profiling?homey=](https://go.athom.com/app-profiling?homey=)  
> ─────────────── Logging stdout & stderr ───────────────  
> 2019-11-29 10:17:02 [log] [YeelightApp] Initializing Yeelight app …  
> broadcast returned no devices  
> broadcast advertisement result  
> { message\_type: ‘discover’,  
> device:  
> { id: ‘0x0000000007cd7235’,  
> address: ‘10.0.0.142’,  
> port: 55443,  
> model: ‘ceiling1’,  
> onoff: false,  
> dim: 1,  
> mode: 2,  
> temperature: 5200,  
> rgb: 0,  
> hue: 0,  
> saturation: 0,  
> connected: false } }  
> broadcast advertisement result  
> { message\_type: ‘discover’,  
> device:  
> { id: ‘0x0000000007cd7235’,  
> address: ‘10.0.0.142’,  
> port: 55443,  
> model: ‘ceiling1’,  
> onoff: false,  
> dim: 1,  
> mode: 2,  
> temperature: 5200,  
> rgb: 0,  
> hue: 0,  
> saturation: 0,  
> connected: false } }  
> broadcast advertisement result  
> { message\_type: ‘discover’,  
> device:  
> { id: ‘0x0000000007c87af2’,  
> address: ‘10.0.0.120’,  
> port: 55443,  
> model: ‘ceiling1’,  
> onoff: false,  
> dim: 1,  
> mode: 2,  
> temperature: 4000,  
> rgb: 0,  
> hue: 0,  
> saturation: 0,  
> connected: false } }  
> broadcast advertisement result  
> { message\_type: ‘discover’,  
> device:  
> { id: ‘0x0000000007c87af2’,  
> address: ‘10.0.0.120’,  
> port: 55443,  
> model: ‘ceiling1’,  
> onoff: false,  
> dim: 1,  
> mode: 2,  
> temperature: 4000,  
> rgb: 0,  
> 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 29, 2019, 9:20am UTC](https://community.homey.app/t/app-yeelights-lan/21134/12 "2019-11-29T09:20:50Z")

</div>

And btw it says Connected:false yet I can control them over Yeelight app and even previous Xiaomi app…

---

<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, 3:01pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/13 "2019-11-29T15:01:32Z")

</div>

Same result after restarting the app. Below is the output from the debug version when trying to add a device.

> ─────────────── Logging stdout & stderr ───────────────  
> 2019-11-29 15:51:48 [log] [YeelightApp] Initializing Yeelight app …  
> broadcast returned no devices  
> broadcast advertisement result  
> { message\_type: ‘discover’,  
> device:  
> { 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 } }  
> broadcast advertisement result  
> { message\_type: ‘discover’,  
> device:  
> { 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 } }  
> broadcast returned no devices  
> broadcast advertisement result  
> { message\_type: ‘discover’,  
> device:  
> { 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 } }  
> broadcast advertisement result  
> { message\_type: ‘discover’,  
> device:  
> { 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:** ![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, 4:16pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/14 "2019-11-29T16:16:36Z")

</div>

> [@Sharkys](#):
>
> And btw it says Connected:false yet I can control them over Yeelight app and even previous Xiaomi app

You can ignore that, it’s not relevant.

> [@mirius](#):
>
> Same result after restarting the app. Below is the output from the debug version when trying to add a device

Could you both try again, I pushed some changes to the debug branch on Github that will spit out some different debug logging.

---

<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, 4:30pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/15 "2019-11-29T16:30:49Z")

</div>

Are you sure Debug branch has been updated recently ? I see updates 21 hours ago…

---

<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, 5:14pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/16 "2019-11-29T17:14:17Z")

</div>

Whoops, forgot to push the changes. It’s updated now.

---

<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, 6:05pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/17 "2019-11-29T18:05:33Z")

</div>

I think there might be an error in the updated debug version. Please see the output below when running the app.

> ─────────────── Logging stdout & stderr ───────────────  
> /lib/util.js:74  
> console.log('Already in added devices: 'added\_devices.hasOwnProperty(result.device.id));  
> SyntaxError: missing ) after argument list  
> at createScript (vm.js:80:10)  
> at Object.runInThisContext (vm.js:139:10)  
> at Module.\_compile (module.js:617:28)  
> at Object.Module.\_extensions…js (module.js:664:10)  
> at Module.load (module.js:566:32)  
> at tryModuleLoad (module.js:506:12)  
> at Function.Module.\_load (module.js:498:3)  
> at Module.require (module.js:597:17)  
> at Module.require (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/index.js:1:253)  
> at require (internal/module.js:11:18)  
> — INFO: com.yeelight has been killed —

---

<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, 6:15pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/18 "2019-11-29T18:15:05Z")

</div>

> [@mirius](#):
>
> I think there might be an error in the updated debug version. Please see the output below when running the app

Ugh, I need more sleep. I fixed that now.

---

<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, 6:29pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/19 "2019-11-29T18:29:18Z")

</div>

Haha… Well, the app didn’t crash this time, but I guess the new logging was not as expected. Please see the log lines below.

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

---

<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, 7:34pm UTC](https://community.homey.app/t/app-yeelights-lan/21134/20 "2019-11-29T19:34:54Z")

</div>

Ok, that’s a little step closer. Could you run the updated version on Github again.

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