External integration: Yeelight

Configuration
1

I’m reviving this topic following the new external Yeelight plugin that just arrived!

My ceiling ambilight light is well recognized :slight_smile:

image
image423×560 22.6 KB

MODEL	ceiling10
FIRMWARE_VERSION	49
SUPPORTED_METHODS	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

image
image395×637 33.2 KB

After some testing, here are my remarks:

  • lighting color: matches the ambilight color, it should include the name ambient
  • lighting color: the color palette is functional :white_check_mark: but it doesn’t pick up the color when I modify it via the mobile app
  • lighting temperature: doesn’t control anything :cross_mark: but the level changes when modified via the app
  • lighting temperature: the slider and its warm/cold colors are reversed: if I modify to warm via the app, it sets cold on the slider, and vice versa
  • yeelight ceiling10 - ambient brightness: I don’t know why the device name is there and it’s in English
  • yeelight ceiling10 - ambient brightness: the slider is too small and it’s not possible to manage the level correctly
  • yeelight ceiling10 - ambient brightness: the level change works well :white_check_mark: and it modifies correctly when I modify via the app
  • yeelight ceiling10 - ambient light: I don’t know why the device name is there and it’s in English, it should be Ambiance On/Off
  • yeelight ceiling10 - ambient light:
    • if everything is off, I click On and the ambient light turns on, the main light’s On/Off activates, the main light does not turn on
    • if I click Off, the ambient light turns off, the main light switches to Off
    • if the main light (On), the ambient light turns on (On)
      • if I turn off the ambient light, it turns off physically but the button switches back to On
      • if I click again to turn off, the button switches to Off
      • if I click again to turn on, the ambient light turns on
  • yeelight ceiling10 - brightness: I don’t know why the device name is there and it’s in English
  • yeelight ceiling10 - brightness: the level change works well :white_check_mark: and it modifies correctly when I modify via the app
  • yeelight ceiling10 - night light: a small mode I didn’t know about in the app that dims both lights (main and ambient) :white_check_mark:
  • yeelight ceiling10 - on/off: I don’t know why the device name is there and it’s in English
  • yeelight ceiling10 - on/off:
    • if everything is off, I click On and the main light turns on as well as the ambiance
    • if everything is on or only the main light, if I turn off the main light it turns everything off.

I hope this is detailed enough for a future update.

In general, it’s either English or French.
No need to have the device name twice.
Have ambient for the ambilight and main for the main light (or in French).
Fix the On/Off button issue for the ambient light.

To go further:

  • turning on the main light only turns on the main light
  • turning on the ambiance only turns on the ambiance
  • add a global on/off button to turn on/off both
2

Okay, thanks for your feedback. I’ll look into it as soon as possible.
There’s one point I can answer right away: the slider issue is a front-end problem with Gladys, and the integration won’t change anything at that level.
Wait until you have the new Gladys theme and core to submit a feature request so that the slider with the % value is easier to handle.

I’ll keep you updated on the other points.

3

Thank you very much for your feedback, it was precise and helped identify a real underlying bug. A new version fixes most of what you reported.

The color temperature (your points 3 and 4)

The two symptoms were actually one. Gladys expects a color temperature in mired, not in Kelvin — that’s what the native integrations use (Philips Hue exposes 153–500, Tasmota 123–500). The slider has a fixed blue→orange gradient, so it assumes the value increases as the light warms up. Kelvin goes exactly the other way: hence your inverted slider. And since the returned values were read as Kelvin, they fell out of range — hence „it doesn’t control anything“.

The integration now converts in both directions, respecting the actual range of your model (2700–6500 K on a ceiling10).

:warning: Since the boundaries of this feature have changed, the cleanest solution is to remove and re-add the lamp after the update. The values already recorded in the history are in Kelvin and will remain inconsistent with the new ones.

The ambient color not updated from the app (your point 2)

Well spotted, it was a real bug. The main light managed the HSV mode, not the ambient — and that’s exactly the mode in which the Yeelight app leaves the ambient ring when you give it a color. The changes therefore never reached Gladys. This is fixed.

The names of the controls (your points 1 and 5)

The name of the lamp is no longer repeated: Gladys already displays it around the feature, which resulted in „Living Room - Living Room - brightness“. And on a ceiling light with backlighting, the labels now clearly indicate which light they control:

  • Main Light / Main Brightness / Main Color / Main Color Temperature
  • Ambient Light / Ambient Brightness / Ambient Color

On a lamp without backlighting, it remains simple: On/Off, Brightness, Color, Color Temperature.

Independent switching on (your point 7)

It already is: these are two distinct commands, and I checked that no particular mode is sent on the main switch. What you observe is the firmware restoring its last state. The new labels should already clear up much of the confusion — but if the behavior persists after the update, let me know, I’ll look at the lamp logs.

The inconsistent ambient button (your point 6)

I couldn’t find a certain cause in the code. My hypothesis is that it was a consequence of the ambient color bug above: the state was not reported, so the interface desynchronized. Can you confirm if it happens again after the update? I prefer not to fix blindly.

The global On/Off button

I can’t do it at the integration level: a feature that controls two others does not exist in Gladys’s model. The intended way is a scene that acts on both switches — it’s documented in the new version.

For the sliders, we remain as said on the wait for the new theme.

4

Update ok, deletion then reintegration as you suggested.

At startup, my lamp (main and ambient) is physically on, but nothing updates in Gladys:

image
image393×583 29.1 KB

However, it does change when I modify the settings from the app, but only on the features I modify, not the others.

On the Lighting Temperature side, it goes the right way (cold>cold, warm>warm) when I modify from the app, but when I control from Gladys, nothing happens.

image
image399×102 4.58 KB

If I turn ambient light on or off from the app, Gladys sets it to On and doesn’t move.
If I turn it off from Gladys, it works fine (off, then on, then off) but sometimes (no repetitive timing) it goes back to On directly while the light turns off.

Ambient brightness and Main brightness work well in control and update well when I modify from the app.

Lighting Color of the ambiance correctly retrieves the modifications made from the app and correctly modifies the light in control.
On the app, I can play with the ambiance color but also with the warmth of the ambiance light (warm/cold). We’ll see if we can have it in Gladys too; in any case, if I modify the warmth from the app, nothing happens in Gladys.

Well, that’s not at all what I wrote:

So I like it!
And for info, this small mode seems to only act on the main light, nothing on the ambiance.

We leave it as is.

I can’t wait to see this new theme :star_struck:

Additional information:

  • I just noticed that in my Yeelight app, I have enabled for the ambilight: « Auto On/Off with main light » → so completely normal behavior in Gladys. By disabling it, I can manage the on/off of each without modifying the other :stuck_out_tongue_winking_eye:
5

new release in progress, I hope it will be good, keep me posted