home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
70.91k stars 29.56k forks source link

TP-Link KL125 changing to unknown and unnamed unless powered on once #121270

Closed adarrous closed 3 weeks ago

adarrous commented 1 month ago

The problem

I'm currently and sadly using regular light switches my TP-Link KL125 aren't showing properly in home assistant unless powered on that day. This changes the device to unknown and unnamed unless powered on once during that day. As

Can be seen in the screenshot Screenshot from 2024-07-04 21-09-50

Device is named but since powered off is unable to show consumption. The device is still in use but powered down since the standard light switch is powered off. Screenshot from 2024-07-04 21-17-19

What version of Home Assistant Core has the issue?

core-2024.7.0

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

TP-Link Smart Home

Link to integration documentation on our website

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

Diagnostics information

home-assistant_tplink_2024-07-05T01-21-07.812Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 month ago

Hey there @rytilahti, @bdraco, @sdb9696, mind taking a look at this issue as it has been labeled with an integration (tplink) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `tplink` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tplink` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


tplink documentation tplink source (message by IssueLinks)

sdb9696 commented 1 month ago

I'm not completely clear on the issue here as the logs seem to show all the devices successfully connecting. Was this working differently in a previous release? Are you restarting HA daily?

sdb9696 commented 1 month ago

@home-assistant add-label needs-more-information

rytilahti commented 1 month ago

I think the device is reporting none when it hasn't been on for the day, iirc, there was a special handling for this but we forgot to add that?

adamzvolanek commented 1 month ago

A similar thing has happened to both my TPLink Kasa KP125M.

Screenshot_20240714-003200.png

Screenshot_20240714-003231.png

Data cut off at 7/7.

adarrous commented 1 month ago

The device names are only showing their names when they have consumed power that day. As far as I have had these in they've never properly displayed their names if powered off for the day.

Scenario A: Light turned on that day the name of the device will be populated into home assistant.

Scenario B: Light not turned on that day. Today's consumption is displayed instead of the actual device name.

image

Let me know if anymore clarification is needed.

sdb9696 commented 1 month ago

A similar thing has happened to both my TPLink Kasa KP125M.

@adamzvolanek this is a different issue to the OP. These devices used to incorrectly report total consumption when they don't actually provide it, hence this particular sensor is no longer provided by the integration.

@adarrous I'm still not clear on the issue. Are you saying it has always been like this and you would like it to be changed?

issue-triage-workflows[bot] commented 4 weeks ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.