thowie
28. MĂ€rz 2026 um 12:03
192
@totow Danke!
Mir war tatsÀchlich nicht bewusst das man es da umschalten kann
PS: jetzt Àrgere ich mich schon ein wenig den Wald vor lauter BÀumen nicht gesehen zu haben :o
Moin, seit meinem Update auf HA Core 2026.3.3 (22.3.2026 von 2026.2.3)habe ich ein interessantes Verhalten bei der Tibber Integration. Der Strompreis (nur diese EntitĂ€t) ist ca. alle 15 Minuten ânicht verfĂŒgbarâ. das sieht dann ungefĂ€hr so aus:
Auch 2026.3.4 hat daran nichts geÀndert. Bisher habe ich keine Ursache analysieren können. Gibt es hier schon Erfahrung damit?
FrankP
29. MĂ€rz 2026 um 14:32
194
Hallo.
Das ist seit 2026.3.3 ein Problem. Es wird aber wohl daran schon gearbeitet.Link zu GitHub
Danke, hatte ich bis gestern nicht gefunden.
1 âGefĂ€llt mirâ
Die Farbtemperaturregelung auf HA 2026.3 ist defekt
offen 09:07AM - 06 Mar 26 UTC
bug
## The problem
After updating to Home Assistant Core 2026.3, all LocalTuya ligh⊠t entities no longer respond to color temperature commands. Brightness control still works, but `color_temp_kelvin` is completely ignored.
When calling `light.turn_on` with `color_temp_kelvin`, the light turns on and applies brightness correctly, but the state reports `color_temp_kelvin: None` â even though `color_mode` is `color_temp`. Some lights even revert to an incorrect HS color (e.g. red `hs_color: (6, 100.0)`) instead of the requested warm white.
This is caused by the [HA 2026.3 breaking change that removed deprecated mired-based light features](https://developers.home-assistant.io/blog/2026/02/23/remove-deprecate-light-features):
- Removed `LightEntity.color_temp`, `LightEntity.min_mireds`, `LightEntity.max_mireds` properties
- Removed `ATTR_COLOR_TEMP` and `ATTR_KELVIN` from `light.turn_on` service
- Only `color_temp_kelvin`, `min_color_temp_kelvin`, `max_color_temp_kelvin` are now supported
LocalTuya's light platform likely still uses the removed mired-based properties (`_attr_color_temp`, `min_mireds`, `max_mireds`) internally. These need to be migrated to their kelvin equivalents (`_attr_color_temp_kelvin`, `_attr_min_color_temp_kelvin`, `_attr_max_color_temp_kelvin`).
Additionally, all LocalTuya light entities log `DPS index 21` warnings at startup, which may be related.
ZHA lights on the same HA instance work perfectly with the same `color_temp_kelvin` calls, confirming the issue is specific to LocalTuya.
## Environment
- Localtuya version:
- Home Assistant Core version: 2026.3.0
- [ ] Does the device work using the Home Assistant Tuya Cloud component?
- [ ] Does the device work using the Tinytuya (https://github.com/jasonacox/tinytuya) command line tool?
- [x] Was the device working with earlier versions of localtuya? Everything worked perfectly on HA 2026.2.x and prior.
- [ ] Are you using the Tuya/SmartLife App in parallel?
## Steps to reproduce
1. Update Home Assistant Core to 2026.3.0
2. Call `light.turn_on` on any LocalTuya light entity with `color_temp_kelvin` parameter (e.g. `color_temp_kelvin: 3200`)
3. Observe that brightness is applied correctly, but `color_temp_kelvin` remains `None` in the entity state. The light does not change color temperature.
## DP dump
N/A â the issue is not device-specific. All LocalTuya lights with color temperature support are affected. The DPs themselves are correct; the problem is in how the HA `LightEntity` properties are implemented.
## Provide Home Assistant traceback/logs
```
DPS index 21 warnings at startup for every LocalTuya light:
2026-03-05 18:00:42.540 WARNING (MainThread) [custom_components.localtuya.light] [bf0...nah] Entity None is requesting unknown DPS index 21
2026-03-05 18:00:42.541 WARNING (MainThread) [custom_components.localtuya.light] [bf0...nah] Entity light.lampadario_cucina_up is requesting unknown DPS index 21
2026-03-05 18:00:42.542 WARNING (MainThread) [custom_components.localtuya.light] [bf1...2gk] Entity light.lampada_piccola is requesting unknown DPS index 21
2026-03-05 18:00:42.543 WARNING (MainThread) [custom_components.localtuya.light] [bf4...4im] Entity light.campingaz is requesting unknown DPS index 21
2026-03-05 18:00:42.544 WARNING (MainThread) [custom_components.localtuya.light] [bf9...a7d] Entity light.lampada is requesting unknown DPS index 21
2026-03-05 18:00:42.544 WARNING (MainThread) [custom_components.localtuya.light] [bfb...0c9] Entity light.bajour is requesting unknown DPS index 21
2026-03-05 18:00:42.545 WARNING (MainThread) [custom_components.localtuya.light] [bfc...0xc] Entity light.lampadario_cucina is requesting unknown DPS index 21
2026-03-05 18:00:42.546 WARNING (MainThread) [custom_components.localtuya.light] [bfd...nil] Entity light.faretto is requesting unknown DPS index 21
```
Example: light.turn_on sends color_temp_kelvin but light ignores it:
Service call:
`light.turn_on: {'entity_id': 'light.faretto', 'brightness': 215, 'color_temp_kelvin': 3215}
`
Resulting state â brightness applied, color_temp_kelvin is None:
```
state light.faretto=on; min_color_temp_kelvin=2000, max_color_temp_kelvin=6535,
supported_color_modes=[ColorMode.COLOR_TEMP, ColorMode.HS],
color_mode=color_temp, brightness=216, color_temp_kelvin=None,
hs_color=None, rgb_color=None, xy_color=None
```
Another light turns RED instead of warm white:
Service call:
`light.turn_on: {'entity_id': 'light.lampada_piccola', 'brightness': 215, 'color_temp_kelvin': 3210}
`
Resulting state â switches to HS mode with red color:
```
state light.lampada_piccola=on; color_mode=hs, brightness=216,
color_temp_kelvin=None, hs_color=(6, 100.0), rgb_color=(255, 25, 0)
```
For comparison, a ZHA light on the same system works correctly:
Service call:
`light.turn_on: {'entity_id': 'light.spot_2', 'brightness': 218, 'color_temp_kelvin': 3295}
`
Resulting state â color_temp_kelvin correctly applied:
```
state light.spot_2=on; color_mode=color_temp, brightness=218,
color_temp_kelvin=3300
```
## Additional information
The root cause is the [HA 2026.3 removal of deprecated light entity properties](https://developers.home-assistant.io/blog/2026/02/23/remove-deprecate-light-features). LocalTuya's `light.py` needs to migrate from:
- `_attr_color_temp` â `_attr_color_temp_kelvin`
- `_attr_min_mireds` / `_attr_max_mireds` â `_attr_min_color_temp_kelvin` / `_attr_max_color_temp_kelvin`
- `LightEntity.color_temp` property â `LightEntity.color_temp_kelvin`
- `ATTR_COLOR_TEMP` in `turn_on` kwargs â `ATTR_COLOR_TEMP_KELVIN`
See the [migration examples in the HA developer blog](https://developers.home-assistant.io/blog/2026/02/23/remove-deprecate-light-features#examples) for the required changes.
**Affected devices:** All LocalTuya lights with color temperature support (tested with 8 different Tuya devices â all broken).
Ganz unten ist ein Link wo die gepatchte light.py Datei herunter geladen werden kann
funktioniert bei mir einwandfrei
Habe mir nun erst mal fĂŒr Tibber eine kleine Automatik gebaut, die die Integration neu lĂ€dt, wenn die Preis-EntitĂ€t ânicht verfĂŒgbarâ wir. Somit immer nur ca. 1 Minute keinen Preis/30 Min.
FrankP
31. MĂ€rz 2026 um 09:18
198
Zum aktuellen Tibber-Problem habe ich was, das man durchaus als Workaround nutzen kann.
Ich habe mir einen Sensor gebaut, der die 15minĂŒtigen Tibberpreise beinhaltet. Vorteil ist, dass nicht permanent abgefragt wird, sondern, sobald die Preise verfĂŒgbar sind, wird der Sensor mit Daten gefĂŒllt.
# Tibber Preise 15 Minuten
- platform: rest
name: "Tibber Preis 15min"
unique_id: sensor.tibber_price_15min
resource: https://api.tibber.com/v1-beta/gql
method: POST
payload: >
{
"query": "{ viewer { homes { currentSubscription { status priceInfo (resolution: QUARTER_HOURLY) { current { total } today { total } tomorrow { total } } } } } }"
}
json_attributes_path: "$.data.viewer.homes[0].currentSubscription.priceInfo"
json_attributes:
- today
- tomorrow
value_template: >
{{ value_json.data.viewer.homes[0].currentSubscription.priceInfo.current.total | float }}
scan_interval: 300
headers:
Authorization: !secret tibber_api_key
Content-Type: application/json
User-Agent: REST
unit_of_measurement: EUR/kWh
Ăberall, wo ich normalerweise mit dem Strompreis-Sensor gearbeitet habe, der aktuell Probleme verursacht, habe ich durch den Sensor sensor.tibber_preis_15min ersetzt.
1 âGefĂ€llt mirâ
harryp
1. April 2026 um 12:55
199
