Just updated to 2.2.0 and all my lights appear twice with one of them with a „main“ name. Controlling the lights is not possible.

Hello im using also the alexa Skill, and i get a Dublicate Error - i think thats because the light with the backlight ist 2 times in Homebridge and messes up Alexa

[6/5/2020, 14:05:56] [Alexa] WARNING: Duplicate device name GuangCan Ceiling Light
[6/5/2020, 14:05:56] [Alexa] ERROR: Parsing failed, removing duplicate endpointID => GuangCan Ceiling Light
[6/5/2020, 14:05:56] [Alexa] alexaDiscovery - returned 17 devices
[6/5/2020, 14:20:56] [Alexa] WARNING: Duplicate device name GuangCan Ceiling Light
[6/5/2020, 14:20:56] [Alexa] ERROR: Parsing failed, removing duplicate endpointID => GuangCan Ceiling Light

I cannot switch back to default white, or warm light with 100% brightness after I choose a color. I have to launch Home Assistant to switch back or the original app. Colors are working fine. With another plugin it worked exactly the opposite :)

Hello!

I'm sorry because I don't know if opening a ticket is the best way to communicate with you about yeelighter. If this is not an issue, please feel free to close it and let me know how to communicate correctly.

My question is if there is possible to set a fixed IP address for bulbs in Yeelighter.

I have several VLAN's and a Firewall between my network devices and my IoT devices. I noticed that yeelighter works using multicast to "find" the bulbs, but in my case, the Homebridge is on a different VLAN so multicast is not passing from Homebridge network to IoT network.

I have Avahi running for mDNS to work, but I noticed that yeelighter is using traditional multicast so I don't know if I build some PIM package on my pfsense firewall I could make this to work.

Anyway, do you think that it could be possible to "fix" the IP address of a bulb/lamp on yeelighter? For me it could do the trick 👍

Thanks!

Dear all,

I have three devices, and I want to hide two devices in HomeKit app.
I check yeelight app and verify that this devices has not been enabled control-in-lan
I added and array to my config with ignored parameter and restart homebridge but devices still appears.

I delete cached accessories and restart again but does not works.
Here's my config

{ "name": "Yeelighter", "timeout": 5000, "interval": 60000, "ctforcolor": true, "blocking": false, "split": false, "override": [ { "id": "0x0000000018374aef", "name": "Bedside_Lamp", "useNameAsId": false, "ignored": true }, { "id": "0x0000000064484a8", "name": "Entrance_Lamp", "useNameAsId": false, "ignored": true } ], "platform": "Yeelighter" }

What can I do to delete this two devices from homebridge ??
Thanks

Have problem, that nothing works in this plugin. In HB UI-X, and also on iPhone/iPad. On both, when I click on light are turned on, but in real nothing.

Tested reboot, nothing changes.

There is no errors in log:

...
[9/23/2020, 10:39:41 AM] Loaded plugin: [email protected]
[9/23/2020, 10:39:41 AM] Registering platform 'homebridge-yeelighter.Yeelighter'
[9/23/2020, 10:39:41 AM] ---
[9/23/2020, 10:39:41 AM] Loaded plugin: [email protected]
[9/23/2020, 10:39:41 AM] Registering platform 'homebridge-config-ui-x.config'
[9/23/2020, 10:39:41 AM] ---
[9/23/2020, 10:39:41 AM] Loading 5 platforms...
[9/23/2020, 10:39:41 AM] [Yeelighter] Initializing Yeelighter platform...
.......
[9/23/2020, 10:39:42 AM] [Yeelighter] Configure Accessory xXXXXXXX
[9/23/2020, 10:39:42 AM] [Yeelighter] Configure Accessory xXXXXXXX
[9/23/2020, 10:39:42 AM] [Yeelighter] Configure Accessory xXXXXXXX
[9/23/2020, 10:39:42 AM] [Yeelighter] Configure Accessory xXXXXXXX
[9/23/2020, 10:39:42 AM] [Yeelighter] Configure Accessory xXXXXXXX
[9/23/2020, 10:39:42 AM] [Yeelighter] Configure Accessory xXXXXXXX
[9/23/2020, 10:39:42 AM] [Yeelighter] Configure Accessory xXXXXXXX
[9/23/2020, 10:39:42 AM] [Yeelighter] Configure Accessory xXXXXXXX
[9/23/2020, 10:39:42 AM] [Yeelighter] Configure Accessory xXXXXXXX

Homebridge v1.2.3
Node.js v12.18.3
NPM v6.14.6

Thanks for this plugin. From what the description says, it perfectly fits my needs.
I have two 320mm without ambient light, two 480mm ceiling light with ambient lights and a meteorite (crystal pendant). All of them with Moonlight mode. The ceiling lamps are the new ones with native homekit, which doesn't help if you can't control moonlight mode and/or the ambient lights…

Sadly, i run into an error when starting the plugin on hoobs.

[Homebridge] [1/7/2020, 10:44:53 AM] [Yeelighter] Accessory created with UUID f3702fe0-951f-4051-868a-88efb04d067e
[Homebridge] [1/7/2020, 10:44:53 AM] [Yeelighter] light 0x0000000007c9d404 stripe created. It supports: 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 adjust_bright adjust_ct adjust_color set_music set_name
[Homebridge] [1/7/2020, 10:44:53 AM] [Yeelighter] Creating new service of subtype 'main' and adding it
[Homebridge] [1/7/2020, 10:44:53 AM] TypeError: Cannot read property 'name' of undefined
    at new LightService (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/lightservice.js:125:85)
    at new WhiteLightService (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/lightservice.js:165:9)
    at new Light (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/light.js:85:28)
    at Discovery.YeelighterPlatform.onDeviceDiscovery (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/index.js:57:31)
    at Discovery.emit (events.js:198:13)
    at Socket.Discovery.onMessage.response (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/yeediscovery.js:43:22)
    at Socket.emit (events.js:198:13)
    at UDP.onMessage [as onmessage] (dgram.js:628:8)```

Hi,
I'm trying to configure my Bedside Lamp. It seems to work fine in "override mode", but I would like to try an already tested configuration. Which is a suggested value for Minimal and Maximum Color temperature?
Thanks

Hi,

First thanks for your work.
I have my bedside lamps into a vlan.
The vlan is called smarthome and the Norma lan is acceable to this smarthome vlan.

Your plugin is in this case not possible to search for this device and will also not automatically add them.

Is it possible to add them manual to the config like the override?

Cheers Robert

Hi,
I have multiple LED strips and Ceiling lights 650 at home. From time to time my wife shutdown light with old school wall switch. So it means, that device is completely off and disconnected from network. Old plugin which i used yeeelight-platform showed "No answer" ony at that one device. I was able to control other devices.

But with your plugin, when one device is switched off by interrupting power, i can't control any other devices in Homebridge. All devices has "No answer" status. When i power on again last device, evreything works normally. Is there option how to manage that state? Thanx.

P.S.: I am planning to buy smart switches to avoid this problem.

I currently am using this plugin with the Yeelight bulb and bedside lamp.

I try to turn them on from config-ui-x, the lights turn on, however, the status still shows off.
On Home.app however, it shows the correct status. I also can't turn it off too from the platform.

If I turn them on from Home.app, it's working as expected and the correct status is also shown on config-ui-x

Hi, I have about 11 lights (650, 350 and led strips) and have problem with control from Homekit or Homebridge UI X. I migrated all lights to IoT VLAN (different subnet).

All lights are set correctly in config.json (override name, but in UI X is visible only model, not assigned name), also have on my router enable mDNS and IGMP Snooping. Pings from my LAN (also from RPi with Homebridge) to lights in IoT VLAN are OK.

If I turn on light in HomeKit, there is automatically turned on in Accessories in HomeBridge UI X, but real light is still turned off.

Tested also deleting my Home in HomeKit and creating new one. Same problem.

Where can be problem, please? Have also "log":true in config.json with every light, but there's no info in log.

Homebridge v1.0.4
Node.js v12.16.3
npm v6.14.4
homebridge-yeelighter v1.2.42

Sorry - I had the same issue. Version 1.3.1 should solve this.

Originally posted by @cellcortex in #27 (comment)

I already use 1.3.1 but it still cause a lots of warns. There is no update available. Can you ha a look into this, please.

Greets

Hi,

I have been using your plugin for a long time and I really thank you for all the work you have been doing.

This month I have been having these errors in the logs:
[25/06/2020, 12:30:08] [Yeelighter] [tetos] warning: no transation found for 31 [ { id: 31, result: [ 'ok' ] } ]
[25/06/2020, 12:30:17] [Yeelighter] [tetos] warning: no transation found for 50 [ { id: 50, result: [ 'ok' ] } ]
[25/06/2020, 12:30:20] [Yeelighter] [tetos] warning: no transation found for 53 [ { id: 53, result: [ 'ok' ] } ]
[25/06/2020, 12:30:22] [Yeelighter] [tetos] warning: no transation found for 56 [ { id: 56, result: [ 'ok' ] } ]
[25/06/2020, 12:30:25] [Yeelighter] [tetos] warning: no transation found for 59 [ { id: 59, result: [ 'ok' ] } ]
[25/06/2020, 12:30:28] [Yeelighter] [tetos] warning: no transation found for 64 [ { id: 64, result: [ 'ok' ] } ]
[25/06/2020, 12:30:29] [Yeelighter] [tetos] Error returned for request [66]: {"code":-1,"message":"client quota exceeded"} []
(node:1615) UnhandledPromiseRejectionWarning: #
(Use node --trace-warnings ... to show where the warning was created)
(node:1615) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1615) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

This happens when I change the brightness of my yeelight ceiling light

Is it related to this issue: #12 ?

Great plugin, thanks!

However.. I'm getting this error when ignoring specific light in the config

[02/12/2020, 11:38:07] [Yeelighter] Override config for 0x000000000796XXX: {"id":"0x0000000007968XXX","useNameAsId":false,"ignored":true}
[02/12/2020, 11:38:07] [Yeelighter] Ignoring 0x0000000007968XXX as configured. Removing from cache.
[02/12/2020, 11:38:07] ReferenceError: Cannot access 'uuid' before initialization
    at /usr/local/lib/node_modules/homebridge-yeelighter/src/platform.ts:67:93
    at Array.find (<anonymous>)
    at Discovery.YeelighterPlatform.onDeviceDiscovery (/usr/local/lib/node_modules/homebridge-yeelighter/src/platform.ts:67:56)
    at Discovery.emit (events.js:315:20)
    at Socket.Discovery.onMessage (/usr/local/lib/node_modules/homebridge-yeelighter/src/discovery.ts:69:12)
    at Socket.emit (events.js:315:20)
    at UDP.onMessage (dgram.js:919:8)
[02/12/2020, 11:38:07] [Yeelighter] Override config for 0x0000000007968XXX: {"id":"0x0000000007968XXX","useNameAsId":false,"ignored":true}
[02/12/2020, 11:38:07] [Yeelighter] Ignoring 0x0000000007968XXX as configured. Removing from cache.
[02/12/2020, 11:38:07] ReferenceError: Cannot access 'uuid' before initialization
    at /usr/local/lib/node_modules/homebridge-yeelighter/src/platform.ts:67:93
    at Array.find (<anonymous>)
    at Discovery.YeelighterPlatform.onDeviceDiscovery (/usr/local/lib/node_modules/homebridge-yeelighter/src/platform.ts:67:56)
    at Discovery.emit (events.js:315:20)
    at Socket.Discovery.onMessage (/usr/local/lib/node_modules/homebridge-yeelighter/src/discovery.ts:69:12)
    at Socket.emit (events.js:315:20)
    at UDP.onMessage (dgram.js:919:8)

Hi,
just because you wrote FeatureRequest welcome. I would love to be able to use my Yeelight Meteor Lights. Is there any hope for me?

As you can see from the above screenshot, my ceiling lamp is getting disconnected and reconnected. I tried to reset it and reconnect to the WiFi but doesn't seem to help at all. Any ideas?

[6/6/2020, 12:50:34 PM] [Yeelighter] Initializing Yeelighter platform...
[6/6/2020, 12:50:34 PM] Failed to find plugin to handle accessory ceiling20-xxxxx
[6/6/2020, 12:50:34 PM] Removing orphaned accessory ceiling20-xxxxx

These are the attributes I got from the discover_bulbs of Yeelight python package if that helps

[{'ip': 'XXXXXX', 'port': 55443, 'capabilities': {'id': '0x00000000XXXXXX', 'model': 'ceiling20', 'fw_ver': '20', 'support': 'get_prop set_default set_power toggle set_bright set_scene cron_add cron_get cron_del start_cf stop_cf set_ct_abx set_name set_adjust adjust_bright adjust_ct bg_set_rgb bg_set_hsv bg_set_ct_abx bg_start_cf bg_stop_cf set_scene_bundle bg_set_default bg_set_power bg_set_bright bg_set_adjust bg_adjust_bright bg_adjust_color bg_adjust_ct bg_toggle dev_toggle', 'power': 'on', 'bright': '100', 'color_mode': '2', 'ct': '6500', 'rgb': '0', 'hue': '0', 'sat': '0', 'name': ''}}]

Could you please elaborate on why I have now two of the controller per accessory?

Also just clicking the symbol to turn or off doesn't work anymore for me.

I have new issues with the Lightstrip Plus in Version 1.2.23:

[Homebridge] [1/15/2020, 8:59:13 AM] [homebridge-yeelighter.Yeelighter] Cached stripe [0x0000000007c9d404] found at yeelight://192.168.1.204:55443
[Homebridge] [1/15/2020, 8:59:13 AM] TypeError: Cannot read property 'saveDefault' of null
    at new LightService (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/lightservice.js:230:44)
    at new ColorLightService (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/colorlightservice.js:6:9)
    at new Light (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/light.js:148:32)
    at Discovery.YeelighterPlatform.onDeviceDiscovery (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/index.js:66:31)
    at Discovery.emit (events.js:198:13)
    at Socket.Discovery.onMessage.response (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/yeediscovery.js:43:22)
    at Socket.emit (events.js:198:13)
    at UDP.onMessage [as onmessage] (dgram.js:628:8)
[Homebridge] [1/15/2020, 8:59:13 AM] [homebridge-yeelighter.Yeelighter] Cached ceiling11 [0x00000000066a4346] found at yeelight://192.168.1.215:55443
[Homebridge] [1/15/2020, 8:59:13 AM] TypeError: Cannot read property 'saveDefault' of null
    at new LightService (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/lightservice.js:230:44)
    at new TemperatureLightService (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/temperaturelightservice.js:6:9)
    at new Light (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/light.js:157:36)
    at Discovery.YeelighterPlatform.onDeviceDiscovery (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/index.js:66:31)
    at Discovery.emit (events.js:198:13)
    at Socket.Discovery.onMessage.response (/home/hoobs/.hoobs/node_modules/homebridge-yeelighter/dist/yeediscovery.js:43:22)
    at Socket.emit (events.js:198:13)
    at UDP.onMessage [as onmessage] (dgram.js:628:8)
[Homebridge] [1/15/2020, 8:59:14 AM] Got SIGTERM, shutting down service...

ceiling11 is a YLXD41YL (320mm, homekit, white range)

Hi,

I am having trouble to get the option offOnDisconnect to work.
I have added the device id under the settings on the homebridge config ui x. Restarted the homebridge.

Steps:
Turned on the physical light switch and checked that the lights are showing ON in Home app.

Expected:
Turned off the physical light switch, expecting that the lights are changed to OFF.

Actual:
Waited for 5 mins and the lights were still showing as ON

Homebridge version 1.1.1
Yeelighter 1.5.12

I set up homebridge on raspberry pi 4 and installed yeelighter and I'm always seeing this error [0x0000000007c1d722] retrieving attributes failed. Using the last attributes. [ 'timeout' ], despite the light still works on the home app. I have also noticed that I can´t set any scene with my yeelight. I always get an error at the end.

The naming is a bit strange. I can change the name for the logs, but nut for anything else? I tried to use this plugin with alexa, but all the bulbs have the same name, so only one is available in alexa... Can you maybe fix this?

My ceiling light works just well, but my lamp no longer can adjust the color. Maybe the plugin can be design to work with the yeelight plugin.

Thanks to your work <3

Hey,
erased lights. will not be erased you see them always in Hoobs.
Please fix bug with sync with yeelight app.

In Yeelightight app are no lights. But you can not clear in Hoobs

Hello. I trying to get the moonlight working on my Mi LED Ceiling Light i get the folowing in the log when starting up homebridge. I can see that it's not detecting the model and defaults to non moonlight.

[Homebridge] [3/4/2020, 6:05:31 PM] [Yeelighter] [0x0000000007cbb39d] no specs for light 0x0000000007cbb39d ceiling5. It supports: get_prop set_default set_power toggle set_bright set_scene cron_add cron_get cron_del start_cf stop_cf set_ct_abx set_name set_adjust adjust_bright adjust_ct. Using fallback. This will not give you moonlight support. []

I triedto override with moonlight and i get the following

[Homebridge] [3/4/2020, 6:05:31 PM] [Yeelighter] Override config for 0x0000000007cbb39d: {"id":"0x0000000007cbb39d","moonlight":true,"log":true}

But when i turn down the brightness to below 50% it does not switch to moonlight.

I aslo cannot change the colour temperature even though the option is there nothiung happens.

Any ideas? :)

I can get the moonlight to work with this plugin https://www.npmjs.com/package/homebridge-yeelight-wifi

But i rather have your solution that switch auto below 50 instead of a separate switch for moonlight.

After upgrading to the latest version (v2.3.4), I have started receiving these errors:

TypeError: Cannot read property 'model' of undefined
    at YeelighterPlatform.configureAccessory (/homebridge/node_modules/homebridge-yeelighter/src/platform.ts:48:103)
    at /usr/local/lib/node_modules/homebridge/src/server.ts:307:25
    at Array.filter (<anonymous>)
    at Server.restoreCachedPlatformAccessories (/usr/local/lib/node_modules/homebridge/src/server.ts:270:69)
    at Server.start (/usr/local/lib/node_modules/homebridge/src/server.ts:158:10)
    at cli (/usr/local/lib/node_modules/homebridge/src/cli.ts:80:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:1138:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
    at Module.load (internal/modules/cjs/loader.js:986:32)

I have tried to re-install the plugin but didn't help.

My config file is:

{
   ...
   "accessories": [
       ...
       {
            "name": "Bedroom Light",
            "timeout": 5000,
            "interval": 60000,
            "ctforcolor": false,
            "blocking": false,
            "split": false,
            "platform": "Yeelighter"
        }
   ]
}

Any ideas what is wrong?

Hi,
I have to install and activate the plugin and then it should autodiscover my yeelights, right? I installed it with the "homebridge-config-ui-x" and I can see in the logs that it's loaded and that it's starting an "auto discovery". But after that I don't see anything else from the plugin in the logs and I don't get my lightstrip in homekit.
I have only one lightstrip, called "Original Xiaomi Yeelight Smart Light Strip - RGB Color". I'm using it since more than a year with an Amazon Echo and I can see it in the Yeelight app. LAN mode is activated.

Logs:
Feb 09 21:42:21 raspi4 homebridge[18347]: [2020-2-9 21:42:21] Loaded config.json with 0 accessories and 3 platforms.
Feb 09 21:42:21 raspi4 homebridge[18347]: [2020-2-9 21:42:21] ---
Feb 09 21:42:21 raspi4 homebridge[18347]: [2020-2-9 21:42:21] Loaded plugin: homebridge-config-ui-x
Feb 09 21:42:21 raspi4 homebridge[18347]: [2020-2-9 21:42:21] Registering platform 'homebridge-config-ui-x.config'
Feb 09 21:42:21 raspi4 homebridge[18347]: [2020-2-9 21:42:21] ---
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] Loaded plugin: homebridge-hue
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] Registering platform 'homebridge-hue.Hue'
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] ---
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] Loaded plugin: homebridge-yeelighter
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] Registering platform 'homebridge-yeelighter.Yeelighter'
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] ---
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] Loading 3 platforms...
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] [Config] Initializing config platform...
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] [Config] Spawning homebridge-config-ui-x with PID 18371
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] [Hue] Initializing Hue platform...
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] [Hue] homebridge-hue v0.11.52, node v12.15.0, homebridge v0.4.50
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] [Yeelighter] Initializing Yeelighter platform...
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] Loading 0 accessories...
Feb 09 21:42:22 raspi4 homebridge[18347]: [2020-2-9 21:42:22] [Yeelighter] ** Discovery Started **
Feb 09 21:42:25 raspi4 homebridge[18347]: [2020-2-9 21:42:25] [Config] Homebridge Config UI X v4.10.0 is listening on :: port 8080
Feb 09 21:42:27 raspi4 homebridge[18347]: [2020-2-9 21:42:27] [Hue] Philips hue: Philips BSB002 bridge v1935144040, api v1.35.0
Feb 09 21:42:28 raspi4 homebridge[18347]: [2020-2-9 21:42:28] [Hue] Philips hue: 4 accessories
Feb 09 21:42:28 raspi4 homebridge[18347]: [2020-2-9 21:42:28] [Hue] masked debug info dumped to /var/homebridge/homebridge-hue.json.gz
Feb 09 21:42:28 raspi4 homebridge[18347]: [2020-2-9 21:42:28] [Hue] Initializing platform accessory 'Philips hue'...
Feb 09 21:42:28 raspi4 homebridge[18347]: [2020-2-9 21:42:28] [Hue] Philips hue: 2 services
Feb 09 21:42:28 raspi4 homebridge[18347]: [2020-2-9 21:42:28] [Hue] Initializing platform accessory 'Flur2'...
Feb 09 21:42:28 raspi4 homebridge[18347]: [2020-2-9 21:42:28] [Hue] Initializing platform accessory 'VorneLinks'...
Feb 09 21:42:28 raspi4 homebridge[18347]: [2020-2-9 21:42:28] [Hue] Initializing platform accessory 'Flur1'...
Feb 09 21:42:28 raspi4 homebridge[18347]: Setup Payload:
Feb 09 21:42:28 raspi4 homebridge[18347]: X-HM://0023MNTMY8EC3
Feb 09 21:42:28 raspi4 homebridge[18347]: Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
...

Hello,

I installed the latest update (2.2.11) and cannot control my yeelight 480 anymore. But I have a new strange device with the name
"0x0000000007c55bb7 main". In Homebridge itself I can turn on and off the yeelight with this. But with the Apple Homekit I can change the color (white only) but the light did not turn on.

Therefore I go back to the 1.5.16 and the good old yeelight 480 apears again and I am able to control via homebridge and apple homekit. But the strange device "0x0000000007c55bb7 main" is still there?!?

I removed the cachedaccesories folder allready but strange device is still there (in Homebridge as in Apple Homekit).

Do have anyone a tip if I do anything wrong or is that a bug?

Your Plugin works very well. Thanks so far.
I figured out that the White Ambience Down light can not switch color ranges...please see attached image

Hi,
Would it be possible to add the new Apple feature that automatically sets the colour temperature depending on the time?
That would be amazing.

Thanks
Alessandro

Does this plugin supports WiFi Xiaomi Philips LED Ceiling Lamp with tocken received?
Or you plan to support it?

Hi,

I am facing issue since the last update. It is no longer working.
I can slide the light power but it won't even turn on.
The custom name that I set in Home will also always gets reset.

I can see it in the console:

[12/2/2020, 12:56:36 PM] [Yeelighter] [GuangCan Ceiling Light 2 main#main] setConfiguredName [ 'GuangCan Ceiling Light 2 main' ]
[12/2/2020, 12:56:36 PM] [Yeelighter] [GuangCan Ceiling Light 2 main#main] setConfiguredName [ 'GuangCan Ceiling Light 2 main' ]
[12/2/2020, 12:56:36 PM] [Yeelighter] [GuangCan Ceiling Light 2 main#main] setConfiguredName [ 'GuangCan Ceiling Light 2 main' ]

[12/2/2020, 12:56:36 PM] [Yeelighter] [GuangCan Ceiling Light 3#main] setConfiguredName [ 'GuangCan Ceiling Light 3 main' ]

[12/2/2020, 12:56:36 PM] [Yeelighter] [GuangCan Ceiling Light 3 main#main] setConfiguredName [ 'GuangCan Ceiling Light 3 main' ]

[12/2/2020, 12:56:36 PM] [Yeelighter] [GuangCan Ceiling Light 3 main#main] setConfiguredName [ 'GuangCan Ceiling Light 3 main' ]
[12/2/2020, 12:56:36 PM] [Yeelighter] [GuangCan Ceiling Light 3 main#main] setConfiguredName [ 'GuangCan Ceiling Light 3 main' ]
[12/2/2020, 12:56:40 PM] [Yeelighter] [0x00000000101cc163] ceiling20 Connected []
[12/2/2020, 12:56:40 PM] [Yeelighter] [0x00000000101cc163] requesting attributes. Transactions: 5 []
[12/2/2020, 12:56:40 PM] [Yeelighter] [GuangCan Ceiling Light 3 main#main] temperature light updated {"power":true,"color_mode":2,"bright":94,"hue":0,"sat":0,"ct":2703,"bg_power":false,"bg_bright":100,"bg_hue":6,"bg_sat":100,"bg_ct":4000,"bg_lmode":3,"nl_br":22,"active_mode":1,"name":""} []

I tried to removed all cached accessories, restart, etc.

I get this on the log non-stop and it fill my log
yeelight bulb S1

Hey,

thank your for the lots of updated today. I like your plug-in.

With the latest plug-in version 1.3.1 I have some issues. My log is full with WARN messages. I restarted my homebridge, but it still full after 10 - 15 Minutes.

I can controll the Yeelight Ceiling Light in Apple Homekit without any problems. But Du you have a clou how I can avoid all the WARN messages?

[5/23/2020, 13:58:18] [Yeelighter] [0x0000000007c55bb7] No update received within 59.979s - switching to unreachable [] [5/23/2020, 13:58:18] [Yeelighter] [0x0000000007c55bb7] WARN: send command but device doesn't seem connected [] [5/23/2020, 13:58:18] [Yeelighter] [0x0000000007c55bb7] WARN: send command but device doesn't seem reachable [] [5/23/2020, 13:59:18] [Yeelighter] [0x0000000007c55bb7] No update received within 59.984s - switching to unreachable [] [5/23/2020, 13:59:18] [Yeelighter] [0x0000000007c55bb7] WARN: send command but device doesn't seem connected [] [5/23/2020, 13:59:18] [Yeelighter] [0x0000000007c55bb7] WARN: send command but device doesn't seem reachable [] [5/23/2020, 14:00:18] [Yeelighter] [0x0000000007c55bb7] No update received within 59.988s - switching to unreachable [] [5/23/2020, 14:00:18] [Yeelighter] [0x0000000007c55bb7] WARN: send command but device doesn't seem connected [] [5/23/2020, 14:00:18] [Yeelighter] [0x0000000007c55bb7] WARN: send command but device doesn't seem reachable [] [5/23/2020, 14:01:18] [Yeelighter] [0x0000000007c55bb7] No update received within 59.981s - switching to unreachable [] [5/23/2020, 14:01:18] [Yeelighter] [0x0000000007c55bb7] WARN: send command but device doesn't seem connected [] [5/23/2020, 14:01:18] [Yeelighter] [0x0000000007c55bb7] WARN: send command but device doesn't seem reachable []

Cloud you use the override.name as default display name?

If user have defined "name" in override light option in config.json, is possible to add this name also to "Name" in UI-X? And the same name is visible in HomeKit.

Now shows Serial Number in Name and also in HomeKit..

Hi,

Following update 2.3.6, all lights stopped working. I have removed the previous ones from the cache and restarted HomeBridge. Getting this error:

[12/13/2020, 3:23:01 AM] [Yeelighter] [0x00000000079798c9] Error returned for request [5]: {"code":-1,"message":"client quota exceeded"} []
(node:417) UnhandledPromiseRejectionWarning: #
(node:417) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)

As mentioned at the title, ceiling13, ceiling14, ceiling18 is not fully supported by the plugin.

• Color temputure adjustment is not working at all model
• Moonlight mode is not working at ceiling18. If the moonlight mode is enabled in override config, all controls for ceiling18 will not be affected.
• For 13 and 14, the moonlight mode can be activated, but after that, I can't change it back to normal mode in Homekit by pulling up the lightness, the light will just blink one time, and the lightness shown in Homekit will changed back to original one after few secs.

So please add supported for ceiling13, ceiling14 and ceiling18 model if possible, thx a lot!

[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] debug: sendCommand(28, set_power, ["on","sudden",0,5]) []
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] sent command 28: set_power []
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] debug: sendCommand(29, set_power, ["on","smooth",500,1]) []
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] sent command 29: set_power []
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] debug: transaction 28 took 0.194s [ { id: 28, result: [ 'ok' ] } ]
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] debug: received 28: OK []
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] debug: Moonlight on []
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] debug: sendCommand(30, set_bright, [62,"sudden",0]) []
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] sent command 30: set_bright []
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] debug: transaction 29 took 0.215s [ { id: 29, result: [ 'ok' ] } ]
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] debug: received 29: OK []
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] debug: transaction 30 took 0.089s [ { id: 30, result: [ 'ok' ] } ]
[11/24/2020, 12:01:11 AM] [Yeelighter] [BedroomLight] debug: received 30: OK []

It seems like a async concurrent issue, the command 30 set brightness will execute before command29's execution.

Originally posted by @ProphetRush in #46 (comment)

All the lights that use the plug in
After the update there were duplicated and showed and single tile

Is there any way I can change device name in config file and show in Home App, rather than just log message name?

I'm try to using Mi Bedside Lamp with yeelighter plugin, lamp discovered and works Ok.
config is here
{
"name": "Yeelighter",
"ctforcolor": true,
"nonblocking": false,
"timeout": 5000,
"interval": 60000,
"platform": "Yeelighter"
}
starting log is here

[5/8/2020, 4:46:17 PM] [Yeelighter] Cached bslamp1 [0x0000000005464227] found at yeelight://192.168.88.161:55443
[5/8/2020, 4:46:17 PM] [Yeelighter] [0x0000000005464227] Re-using service of subtype 'main'. []
[5/8/2020, 4:46:17 PM] [Yeelighter] [0x0000000005464227] installed as Color light []
[5/8/2020, 4:46:17 PM] [Yeelighter] [0x0000000005464227] Connected []

but the messages are constantly being displayed
}
[5/8/2020, 4:49:55 PM] [Yeelighter] [0x0000000005464227] Disconnected []
[5/8/2020, 4:50:00 PM] [Yeelighter] [0x0000000005464227] Connected []
[5/8/2020, 4:50:00 PM] [Yeelighter] [0x0000000005464227] WARN: send command but device doesn't seem reachable []
Socket Closed false
Socket Closed, reconnecting in 5s Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:205:27) {
errno: 'ECONNRESET',
code: 'ECONNRESET',
syscall: 'read'
}
[5/8/2020, 4:51:00 PM] [Yeelighter] [0x0000000005464227] Disconnected []
[5/8/2020, 4:51:05 PM] [Yeelighter] [0x0000000005464227] Connected []
[5/8/2020, 4:51:05 PM] [Yeelighter] [0x0000000005464227] WARN: send command but device doesn't seem reachable []
Socket Closed false
Socket Closed, reconnecting in 5s Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:205:27) {
errno: 'ECONNRESET',
code: 'ECONNRESET',
syscall: 'read'
}
[5/8/2020, 4:51:27 PM] [Yeelighter] [0x0000000005464227] Disconnected []
[5/8/2020, 4:51:33 PM] [Yeelighter] [0x0000000005464227] Connected []
[5/8/2020, 4:51:33 PM] [Yeelighter] [0x0000000005464227] WARN: send command but device doesn't seem reachable []
Socket Closed false
Socket Closed, reconnecting in 5s Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:205:27) {
errno: 'ECONNRESET',
code: 'ECONNRESET',
syscall: 'read'
}
[5/8/2020, 4:52:27 PM] [Yeelighter] [0x0000000005464227] Disconnected []
[5/8/2020, 4:52:33 PM] [Yeelighter] [0x0000000005464227] Connected []
[5/8/2020, 4:52:33 PM] [Yeelighter] [0x0000000005464227] WARN: send command but device doesn't seem reachable []
Socket Closed false
Socket Closed, reconnecting in 5s Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:205:27) {
errno: 'ECONNRESET',
code: 'ECONNRESET',
syscall: 'read'

==
what am I doing wrong?

Good Morning,

since two days I have an issue with the Plugin without any changes of the Homebridge.

My Yeelight (Ceiling 480) did not Response. I did not can turn on or off the light via Homebridge / Yeelighter Plugin. In the log of the homebridge it is reported:

`
[3/14/2020, 18:40:13] [Yeelighter] [0x0000000007c55bb7] Error returned for request [2]: {"code":-1,"message":"client quota exceeded"} []

[3/14/2020, 18:40:13] [Yeelighter] [0x0000000007c55bb7] retrieving attributes failed. Using last attributes. [ undefined ]

[3/14/2020, 18:40:13] [Yeelighter] [0x0000000007c55bb7] retrieving attributes failed. Using last attributes. [ undefined ]

[3/14/2020, 18:40:13] [Yeelighter] [0x0000000007c55bb7] retrieving attributes failed. Using last attributes. [ undefined ]

[3/14/2020, 18:40:16] [Yeelighter] [0x0000000007c55bb7] Error returned for request [3]: {"code":-1,"message":"client quota exceeded"} []

[3/14/2020, 18:40:16] [Yeelighter] [0x0000000007c55bb7] retrieving attributes failed. Using last attributes. [ undefined ]

[3/14/2020, 18:40:16] [Yeelighter] [0x0000000007c55bb7] retrieving attributes failed. Using last attributes. [ undefined ]

[3/14/2020, 18:40:16] [Yeelighter] [0x0000000007c55bb7] retrieving attributes failed. Using last attributes. [ undefined ]

[3/14/2020, 18:40:20] [Yeelighter] [0x0000000007c55bb7] Error returned for request [4]: {"code":-1,"message":"client quota exceeded"} []

[3/14/2020, 18:40:20] [Yeelighter] [0x0000000007c55bb7] Error returned for request [5]: {"code":-1,"message":"client quota exceeded"} []

[3/14/2020, 18:40:20] [Yeelighter] [0x0000000007c55bb7] retrieving attributes failed. Using last attributes. [ undefined ]

[3/14/2020, 18:40:21] [Yeelighter] [0x0000000007c55bb7] Error returned for request [6]: {"code":-1,"message":"client quota exceeded"} []

[3/14/2020, 18:40:21] [Yeelighter] [0x0000000007c55bb7] retrieving attributes failed. Using last attributes. [ undefined ]

[3/14/2020, 18:40:21] [Yeelighter] [0x0000000007c55bb7] retrieving attributes failed. Using last attributes. [ undefined ]`

I waited for two day and hoped that this will solved. But it did not help. Fuhrtermore I revomed the Plugin and re-installed. Some error occurs.

At leat I delete persit and application Folder and must re-connect the homebridge to Apple Home App, but the above Errors still there.

I can Control the Yeelight with the remote and the Yeelight App without any Problems.

Is there any idea?

I added LAN control to a Halo ceiling lamp.
When switching it off, the accessory still appears in Home but is not functional.
It should not appear anymore.

I saw on NPM tag that this package supports Bedside Lamp.
I want to know if it's possible to get working the only BLE version not Wi-Fi.

I am experiencing exactly this "bug" / behaviour of HomeKit:

home-assistant/core#30756

This problem causes the ambient light control to be not reliable. It forgets the presets etc.

A solution would be to just disable the ColorTemperature characteristic for the background light. I think this is the best solution because you typically only use the color feature and not the temperature feature of the background light.

What about reading data from Mi Hygrothermograph connected via Mi Bedside Lamp BLE gateway?

If I set bulb color to white (Temperature), when I shut off the bulb and proceed to turn it on I turn on red.
And if I set a color purple (Color) for example, everything works perfect.

The problem is when you set Temperature light, on Color light is fine.

I'm not exactly sure what the onDeviceUpdate function of the Light class is supposed to do, but the three input parameters (id, result, error) always seem to be undefined. Because this function gets called when the yeelight sends a notification to the socket, there only really should be one input parameter: the message.

I managed to get the function working by replacing it with the following implementation:

this.onDeviceUpdate = (result) => {
    if (result["params"] === undefined) {
        return;
    }

     // Copy the current attributes, because the yeelight message only contains the attributes that changed.
    const newAttributes = JSON.parse(JSON.stringify(this.attributes));
    for (const key of Object.keys(this.attributes)) {
        if (!(key in result["params"])) {
            continue;
        }

        switch (typeof lightservice_1.EMPTY_ATTRIBUTES[key]) {
            case "number":
                newAttributes[key] = Number(result["params"][key]);
                break;
            case "boolean":
                newAttributes[key] = result["params"][key] == "on";
                break;
            default:
                newAttributes[key] = result["params"][key];
                break;
        }
    }

    this.updateTimestamp = Date.now();
    this.onUpdateAttributes(newAttributes);
};

Because I'm not very familiar with the codebase and have not experience with javascript / typescript, it would be best, if someone who knows how js works, could reimplement this cleanly.