Core: M眉ller-Licht (Aldi Tint) connected via Hue flickering

Created on 31 Jan 2019  路  10Comments  路  Source: home-assistant/core

I am using a Philips Hue hub.

I have a mix of Hue and other brand bulbs connected which all work fine.

I just purchased a couple of Aldi Tint ZigBee bulbs (manufactured by M眉ller-Licht).

When controlled via home assistant they flicker and go first briefly to full brightness and then adjust to the chosen colour temperature or brightness.

I'm not sure what additional information may be required for this.

Hue app reports the following info for the bulb:

Manufacturer: MLI
Model: ZBT-ColorTemperature
SW: 2.0

hue stale

Most helpful comment

So I think I found the issue. The Tint light doesn't like it when HA sends {"alert":"none"} to the Hue bridge. You can test it with the Hue "CLIP API Debugger" on the meethue developer website. To solve this i deleted in homeassistant/components/hue/light.py:

else:
    command['alert'] = 'none'

in the "async_turn_on" and "async_turn_off" functions

All 10 comments

Hey, I got exactly the same issue. If I control them through the hue app, they do flicker but don't turn to full brightness before adjusting. I got a color and a white bulb

They work perfetcly when I control them via the Hue app. No flickering at all with nice smooth transitions between on/off, color temp and brightness levels.

I had the same problems when using hue bulbs and the tint bulb in a group. color transitions where different to the hue bulbs, I'm using them now with zigbee2mqtt and there this behavior does not exist.
I think this is the hue hub itself

I have the same problem. Is there any progress for this issue without buying extra hardware? The problem only occurs when using "light.turn_on" or "light.turn_off". When i use "hue.hue_activate_scene" everything works fine

So I think I found the issue. The Tint light doesn't like it when HA sends {"alert":"none"} to the Hue bridge. You can test it with the Hue "CLIP API Debugger" on the meethue developer website. To solve this i deleted in homeassistant/components/hue/light.py:

else:
    command['alert'] = 'none'

in the "async_turn_on" and "async_turn_off" functions

I too have moved away from the Hue bridge and now use a Conbee. No more issues controlling them from HA.

@Philje123 I have fixed the lights with hue.hue_activate_scene and with edit light.py with @dynamiik tutorial

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

I had the same issue, @dynamiik's workaround did work for me as well. I see the issue is closed meanwhile w/o a remedy - is there a way to make that fix sticky ? I assume it is overwritten with the next hass.io update.

So I think I found the issue. The Tint light doesn't like it when HA sends {"alert":"none"} to the Hue bridge. You can test it with the Hue "CLIP API Debugger" on the meethue developer website. To solve this i deleted in homeassistant/components/hue/light.py:

else:
    command['alert'] = 'none'

in the "async_turn_on" and "async_turn_off" functions

Do you know how to access this folder on hassio?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

piitaya picture piitaya  路  3Comments

aweb-01 picture aweb-01  路  3Comments

coolriku picture coolriku  路  3Comments

sh0rez picture sh0rez  路  3Comments

Elmardus picture Elmardus  路  3Comments