[APP] Yeelights LAN

App Store Page: Yeelights LAN App for Homey | Homey

Description

This app enables seamless control of your Yeelights over your local network (LAN) using Homey. It supports all types of Yeelights that have LAN control functionality, allowing for reliable and efficient management of your smart lighting.

Whether you’re looking to integrate your Yeelights into a broader smart home ecosystem or automate them with Homey’s powerful flow system, this app ensures smooth compatibility and performance.

For CLOUD based control, please navigate yourself to Yeelight App for Homey | Homey

Adding Yeelights

Before adding your Yeelights to Homey, you must enable “Developer Mode” or “LAN control” in the official Yeelight smartphone app.

Steps to Enable LAN Control:

  1. Open the Yeelight app and navigate to the settings for your specific Yeelight device.
  2. Look for the “Developer Mode” or “LAN Control” option and enable it.

Important Note:

LAN Control might not be available in the latest versions of the Yeelight app for every light type. To enable this feature, you may need to downgrade to an earlier version of the Yeelight app that still supports LAN Control. This can typically be done by downloading an older APK version from a trusted source if you are using Android.

Troubleshooting

If you experience issues while setting up or using this app, refer to the following tips:

  • Device Not Found in Homey:
    • Ensure LAN Control is enabled for the device.
    • Check that the device is connected to the same local network as Homey.
    • Verify that your network allows communication between devices (disable client isolation if using Wi-Fi).
  • Cannot Enable LAN Control in Yeelight App:
    • Check if you are using the latest Yeelight app version. If LAN Control is unavailable, downgrade to an earlier version.
    • Ensure the device’s firmware supports LAN Control.
  • Yeelight Not Responding:
    • Reconnect power from the Yeelight device and ensure it’s properly connected to the network, eg. by PING command to the device

Donations

Developing and maintaining Homey apps requires significant time and effort. If you enjoy using this app, consider supporting the developer with a donation as a token of appreciation for the work and support provided.

3 Likes

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.

1 Like

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

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.

1 Like

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?

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.

1 Like

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

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).

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).

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

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=
─────────────── 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 } }

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

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 } }

You can ignore that, it’s not relevant.

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

1 Like

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

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

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 —

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

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
{}

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

1 Like