Skip to content

Tapo P304M entities are always registered as unnamed_p304m_name_of_entity #138983

@nicosemp

Description

@nicosemp

The problem

Hello! I tried adding my Tapo P304M to HA through the integration, but both times all 64 entities have an id like entity_type.unnamed_p304m_name_of_entity which is a bit annoying as I would like to keep the id naming clean.

I believe the code is here https://github.com/home-assistant/core/blob/b35d252549c5f0964b1abfcf825ea21e5c7eafd2/homeassistant/components/tplink/entity.py however I'm not sure what's returned from Tapo (TP-Link) which makes it use the default "unnamed_device" translation key with the device model.

In the Tapo app I added the smart power strip but I can only see and rename the individual sockets (Plug 1 to Plug 4). I cannot see the parent smart strip device, and this is probably why it is unnamed when imported into HA. To further support this theory: I have another smart strip with the Tuya integration, and that one I can actually see and name in their app, which should be why it was imported with the correct name. I do like the P304M and its local polling integration a lot more.

Is it possible to add a field in the import procedure, to override the smart strip name before importing it?

Otherwise, can the integration have an extra check for the Tapo P304M to name it something like tapo_p304m (make and model) instead of unnamed_p304m? This is less ideal because I would actually name it something more specific like studio_smart_strip, but it's still a lot better than unnamed.

I'm available to re-import the device and capture logs if necessary.

cc @rytilahti @bdraco @sdb9696 as I understand you are codeowners.

Thank you!

What version of Home Assistant Core has the issue?

core-2025.2.4

What was the last working version of Home Assistant Core?

core-2025.2.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

TP-Link (Tapo)

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tplink/

Diagnostics information

There are no ids in the diagnostics (maybe redacted)

Example YAML snippet

n/a

Anything in the logs that might be useful for us?

n/a

Additional information

5 of the 64 entities, the parent name is unnamed_p304m while the child names are imported correctly (as set in the Tapo app):

Image

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions