Repository navigation
2026.1 incompatible mireds/kelvin #921
Unanswered
ArndBrugman
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
Today I've started using this Custom Tapo Integration because the Standard Tapo Integration keeps screwing with subnet discoveries. I'm on HA 2026.1 and am unable to update the color temp via the UI of my Tapo 530e bulbs. I've noticed the message below stating this is a new and breaking change in HA 2026.1. I'm unable to return to earlier version to validate. Am I the only one having this issue? I was unable to find any other issues or discussions mentioning this but I thought opening the discussion would probably be better than immediately dropping an Issue as a fresh user ;)
Message:
Detected that custom integration 'tapo' is using mireds for current light color temperature, when it should be adjusted to use the kelvin attribute_attr_color_temp_kelvinor override the kelvin propertycolor_temp_kelvin(see https://github.com/home-assistant/core/pull/79591). This will stop working in Home Assistant 2026.1, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issuesAll reactions