Lesuzdar
April 2, 2024, 7:42am
1
Just heads up here if you are planning to buy some Ikea smart lights. Encountering it myself and doing research into this issue it seems like Ikea lights will by default give you a massive headache when you try to integrate them into your smart home system.
1 Like
Hi,
Which IKEA product exactly?
Which protocol (likely Zigbgee)?
Which HASS integration? (ZHA / Z2MQTT / other)?
Some Zigbee products require “quirks” files to make the device work despite incorrect or incomplete interface definitions in the device itself. Logging the manufacturer and device ID with the undesired behaviour can get the behaviour fixed - something that FOSS does very well.
Here’s an example of ZHA patching around a bad light with a quirk:
opened 07:36PM - 23 Jan 22 UTC
closed 06:21PM - 26 Aug 22 UTC
stale
ℹ️ The fix (custom quirk) is [further below](https://github.com/zigpy/zha-device… -handlers/issues/1303#issuecomment-1020371189) and [instructions a bit further](https://github.com/zigpy/zha-device-handlers/issues/1303#issuecomment-1039714323)
**Description of the behavior**
~"Unstable"~ Erratic ~UI~ behavior of LIDL TS0505A/_TZ3000_dbou1ap4 .
Edit: given the current state of analysis the On/Off attribute of the On/Off cluster is incorrectly representing the bulb's state.
**To Reproduce**
Pictures say more than 1000 words:
The UI switches the light to off when the intensity is changed (there are some other operations in this gif animation, but watch closely when the intensity changes);
The light can be switched on and off normally.
I tried another light (TI Sample Light) and that's behaving normally.
**Expected behavior**
The intensity change should not result in the device switching off
**Additional context**
I probably upgraded HAOS to 2021.12.3 a few days before reporting this in the Adaptive Lighting component.
I filed an [issue for the Adaptive Lighting component](https://github.com/basnijholt/adaptive-lighting/issues/245). The behavior is worse when that is enabled, but I think the core issue is not really there..
This might be related to the appearance of https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/lidl/rgbcct.py with #1177 .
These are the attributes available with their values (when they can be read) - [TS0505A__TZ3000_dbou1ap4_ff23a460_scan_results.txt](https://github.com/zigpy/zha-device-handlers/files/7921232/TS0505A__TZ3000_dbou1ap4_ff23a460_scan_results.txt)
The question now is:
- What kind of adjustment could be made to the quirk to cope with this;
- Are there FW updates for the bulb?
James
francisp
April 2, 2024, 8:40am
3
Never bothered me, but it obviously bothers you.
Lesuzdar
April 2, 2024, 9:08am
4
Hey, here are the details
It seems like all the smart light products by IKEA are affected. I have two Tradfri bulbs and ORMANÄS lightstrip. I’ve observe this behavior in all the products.
The protocol is Zigbee
I am currently using ZHA however I’ve been observing this issue before HA when I was adding the bulbs through my Hue Hub.
Here are some other observations of the issue I could found:
opened 05:33AM - 21 May 18 UTC
closed 08:11AM - 08 Jun 18 UTC
<!-- READ THIS FIRST:
- If you need additional help with this template please r… efer to https://www.home-assistant.io/help/reporting_issues/
- Make sure you are running the latest version of Home Assistant before reporting an issue: https://github.com/home-assistant/home-assistant/releases
- Do not report issues for components if you are using custom components: files in <config-dir>/custom_components
- This is for bugs only. Feature and enhancement requests should go in our community forum: https://community.home-assistant.io/c/feature-requests
- Provide as many details as possible. Paste logs, configuration sample and code into the backticks. Do not delete any text from this template!
-->
**Home Assistant release with the issue:**
<!--
- Frontend -> Developer tools -> Info
- Or use this command: hass --version
-->
0.68.1
**Last working Home Assistant release (if known):**
**Operating environment (Hass.io/Docker/Windows/etc.):**
<!--
Please provide details about your environment.
-->
Haspbian with a conbee stick, running deCONZ and a a single TRÅDFRI E27 980LM TL D/VI SP OP CCT paired with it.
**Component/platform:**
<!--
Please add the link to the documentation at https://www.home-assistant.io/components/ of the component/platform in question.
-->
deCONZ
**Description of problem:**
I can use homeassistant to change either brightness or color_temp, but if I try to change them at the same time, the bulb brightness seems to go about half-way and then fade back to it's original color. I have tried different variables for birghtness and temprature, (such as _pct), they all seem to have the same effect.
Maybe the brightness gets applied first and when the temprature get's applied, it sends a new command with the old brightness, thus turning the brightness back to it's original color.
**Problem-relevant `configuration.yaml` entries and (fill out even if it seems unimportant):**
This works
```
{
"entity_id": "light.ceiling",
"color_temp": 153,
}
{
"entity_id": "light.ceiling",
"brightness": 254,
}
```
This does not:
```
{
"entity_id": "light.ceiling",
"color_temp": 500,
"brightness": 1
}
```
**Traceback (if applicable):**
```
```
**Additional information:**
opened 04:18PM - 09 Jan 23 UTC
closed 08:06AM - 20 Aug 23 UTC
integration: zha
stale
### The problem
When changing more than one property (eg. Brightness & Color … Temp) at a time for any of my different Trådfri lights with a transition, only one of the properties are changed. If I wait for the duration of the transition and run it again, prop 2 gets applied.
- If you do the same without transition, there is no problem. I have no problem with the only Hue bulb that I own.
- It does not matter if I try to apply the changes using ZHA's "Detault Transition" or add it in YAML/Frontend.
- It does not matter which service I use to trigger the change, eg. scene.apply, scene.turn_on or light.turn_on.
I use a Conbee II as coordinator and from forum readings this problem seems to only affect ZHA and not deCONZ or Z2MQTT.
### What version of Home Assistant Core has the issue?
2023.1.2
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
ZHA
### Link to integration documentation on our website
_No response_
### Diagnostics information
[config_entry-zha-bf7ac3f7eab95eb66986b274934022bd.json.txt](https://github.com/home-assistant/core/files/10374914/config_entry-zha-bf7ac3f7eab95eb66986b274934022bd.json.txt)
### Example YAML snippet
```yaml
# Trying to change both brightness and temp at the same time will not work, scene made in Frontend.
name: Kontoret - TEST
entities:
light.kontoret_fonster:
min_color_temp_kelvin: 2202
max_color_temp_kelvin: 4000
min_mireds: 250
max_mireds: 454
supported_color_modes:
- color_temp
color_mode: color_temp
brightness: 178
color_temp_kelvin: 4000
color_temp: 250
hs_color:
- 26.812
- 34.87
rgb_color:
- 255
- 205
- 166
xy_color:
- 0.421
- 0.364
off_with_transition: false
off_brightness:
icon: mdi:lamp
friendly_name: Kontoret - Fönster
supported_features: 40
state: 'on'
```
### Anything in the logs that might be useful for us?
_No response_
### Additional information
Device info
TRADFRI bulb E14 WS opal 400lm
by IKEA of Sweden
Connected via [Zigbee Coordinator](http://homeassistant.local:8123/config/devices/device/864cad3381d77db1056ce2de198239c5)
Firmware: 0x23087631
Zigbee info
IEEE: d0:cf:5e:ff:fe:c0:a5:25
Nwk: 0x015c
Device Type: Router
LQI: 223
RSSI: -66
Last Seen: 2023-01-09T16:49:31
Power Source: Mains
Thank you for the link to quirks, I will look into them later.
Lesuzdar
April 2, 2024, 10:39am
6