Light entity is no longer provided by the tapo integration

[naamah75]

Home Assistant

Core 2025.1.0
Supervisor 2024.12.3
Operating System 14.1
Frontend 20250103.0

Version of the integration

tapo 3.1.2

Configuration

L510
da TP-Link
Firmware: 1.1.9
Hardware: 3.0

Describe the bug

The tapo component is loaded and some integration entries are available (eg. overheat and signal level), but the main entry for the light component is missing.

Debug log

Questo errore ha avuto origine da un'integrazione personalizzata.

Registratore: custom_components.tapo.coordinators
Fonte: helpers/update_coordinator.py:411
Integrazione: TP-Link Tapo (documentazione, problemi)
Prima occorrenza: 08:49:43 (14 occorrenze)
Ultimo accesso: 09:53:41

Error fetching tapo data: Unexpected exception:

[viba1]

Hi,
Same problem here, since migrating to 2025.1.0.

Some logs:

ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception: [homeassistant.components.light] Error adding entity None for domain light with platform tapo

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 825, in _async_add_entity
capabilities=entity.capability_attributes,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 1116, in capability_attributes
if LightEntityFeature.EFFECT in supported_features:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'int' is not iterable

[PlanetCitizen1829381]

Device info
L535
by TP-Link
Firmware: 1.1.5
Hardware: 3.0

Same Issue for Tapo Smart Bulb L535.
Only occurred after updating HA to 2025.1.
Have restored HA to 2024.12.5 and devices are available again.
HA Core Update 2025.1 seems to break it.

[samuelepozzebon]

Same issue with a L630 (firmware 1.1.2).

HA version 2025.1.0

[TopoAS]

Same issue with a L530
HA version 2025.1.0

[indomitorum]

Exactly the same here. Light entity does not exist all of a sudden. 2025.1 has broken the custom tapo integration for lights

L530

[mcderd-coder]

Same for me today, HA 2025.1.0

L630 bulb (firmware 1.1.2) has become unavailable, my Tapo plugs are still working

[iDrunK65]

Same on this with HA 2025.1.0

L530
by TP-Link
Firmware: 1.1.9
Hardware: 3.0

[Clickfr]

Same here with two L530 but no issue so far with my L900.

No worry with the plugs.

[aidanharris]

I don't think we need all of the "Me too" comments, unless you have something new to add. Please subscribe to the issue instead.

The Tapo integration has had this deprecation WARNING for ages now. I'm guessing this is the culprit?

WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.tapo.light.TapoLightEntity'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 0> and color modes, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation

[Clickfr]

Hummm.... Surprisingly, same issue with my Govee H7020 it stopped working exactly at the same time as the Tapo L530: 23:24:43 on Jan 3rd.

And now both return the same error at statup:

TAPO:

Logger: homeassistant.components.light
Source: helpers/entity_platform.py:825
integration: Light (documentation, issues)
First occurred: 19:32:22 (2 occurrences)
Last logged: 19:32:22

Error adding entity None for domain light with platform tapo
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 825, in _async_add_entity
capabilities=entity.capability_attributes,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 1116, in capability_attributes
if LightEntityFeature.EFFECT in supported_features:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'int' is not iterable

GOVEE:

Logger: homeassistant.components.light
Source: helpers/entity_platform.py:608
integration: Light (documentation, issues)
First occurred: 19:32:23 (1 occurrences)
Last logged: 19:32:23

Error adding entity None for domain light with platform govee
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 608, in _async_add_entities
await coro
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 825, in _async_add_entity
capabilities=entity.capability_attributes,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 1116, in capability_attributes
if LightEntityFeature.EFFECT in supported_features:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'int' is not iterable

[Clickfr]

I don't think we need all of the "Me too" comments, unless you have something new to add. Please subscribe to the issue instead.

The Tapo integration has had this deprecation WARNING for ages now. I'm guessing this is the culprit?

WARNING (MainThread) [homeassistant.components.light] Entity None (<class 'custom_components.tapo.light.TapoLightEntity'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature: 0> and color modes, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation

Yep, the Govee case would confirm your assumption.

[edgicat]

Can confirm same issue with HA Container 2025.1.0. Rolling HA back to 2024.12.0 does fix the issue.

FYI The Tapo HAC displays as version 3.1.2 & 3.1.4 in different menus, see images

[djhworld]

This seems to fix the issue for me, my light is working again, raised a PR #826

[edgicat]

This seems to fix the issue for me, my light is working again, raised a PR #826

Confirmed works for me

Interesting light brightness percentage glitch on HA Gui, I take it that's an HA issue

[boblemus]

@djhworld Sadly the control is completely disabled and cannot be toggled by me (everything same version as you, except L530 HW is 3.0 and FW is 1.1.9)

[edgicat]

@djhworld Sadly the control is completely disabled and cannot be toggled by me (everything same version as you, except L530 HW is 3.0 and FW is 1.1.9)

Hey boblemus,

Have you updated the python script and restarted HA, as per:
#826

If not you will need to wait for HACS component update to come through.

[boblemus]

@edgicat Ahh - I missed the part about modifying the Python script. Apparently that did the trick - thank you!!

[mcderd-coder]

Thank you, I made the change, it's now working fine again 👍

[bobfoyers]

Same issue with a L630 (firmware 1.1.2).

HA version 2025.1.0

[Av4K100]

Have implemented the change mentioned in PR 826 however with this change it seems to be affecting light groups in homeassistant, for example i have three bathroom lights combined into a bathroom lights group and after this change i can no longer group these lights together for them to work (the entity shows as unavailable, have deleted and readded and still the same). Rolling back the update and changes to light.py resolve the issue

[Av4K100]

Changing lines 54-56 in light.py to self._attr_supported_features = (LightEntityFeature.EFFECT) as mentioned by pgarciafc on PR #826 has fixed the light group and entity issues on L630 bulbs for myself

[djhworld]

@Av4K100 I've updated the PR with a similar change - does this fix the group issue?

[Adagis-MC]

@djhworld I've retested this on with my P100s in a group. The error still occurs.

[boblemus]

I have 2 groups, a generic group with 3 L530 and 1 P110, and a light group with the same 3 L530. light.py has been modified as such: # self._attr_supported_features = ( # LightEntityFeature.EFFECT if self._effects else [] # ) self._attr_supported_features = (LightEntityFeature.EFFECT) if self._effects else () Prior to commenting the above out and adding the one line the generic group worked and the light group didn't (unavailable). No change to this behaviour can be observed after modifying as above and restarting HA.

…

On Sun, Jan 5, 2025 at 11:21 AM Daniel Harper ***@***.***> wrote: @Av4K100 <https://github.com/Av4K100> I've updated the PR with a similar change - does this fix the group issue? — Reply to this email directly, view it on GitHub <#825 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFPHUT44CTKYOYBKEYZPLJD2JEBRVAVCNFSM6AAAAABUS5ONMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRGU3TKNRTGY> . You are receiving this because you commented.Message ID: ***@***.***>

[Av4K100]

@boblemus removing the if self._effects else () at the end of the code should allow the groups to work however as noted in PR #826 by pgarciafc there could be other issues, might be worth giving a try for yourself to see if that sorts the problem for you until there is a full fix implemented

[boblemus]

@boblemus removing the if self._effects else () at the end of the code should allow the groups to work however as noted in PR #826 by pgarciafc there could be other issues, might be worth giving a try for yourself to see if that sorts the problem for you until there is a full fix implemented

Can confirm. Removing "if self._effects else ()" made both generic and light groups work.

[djhworld]

Looks like we have a fix in #826 to return LightEntityFeature(0) instead of 0 which seems promising for both the ungrouped and grouped cases

[djhworld]

For reference looks like this issue was caused by this home-assistant/core#132371

[carvan]

Just applied this fix:

But the light entity looks to be unavailable still:

Did I make something wrong?

[Adagis-MC]

@carvan. Yes.

The
else set()
should be
else LightEntityFeature(0)

as shown in theatest commit.

[carvan]

@carvan. Yes.

The

else set()

should be

else LightEntityFeature(0)

as shown in theatest commit.

Oh ok that makes sense then. I honestly just copied it from the other post without even reading it assuming it was correct. Thank you

[dimitrispili]

Does anyone knows if Home Assistant Core 2025.1.2 version, solve the problem or we have to do it manually again?

[Lockie85]

I'm on latest everything and all seems good for me now.