Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temperature Entity missing from Statistics card - Tapo T315 (via H100 hub) #128606

Open
longsh07 opened this issue Oct 17, 2024 · 2 comments · May be fixed by #128640
Open

Temperature Entity missing from Statistics card - Tapo T315 (via H100 hub) #128606

longsh07 opened this issue Oct 17, 2024 · 2 comments · May be fixed by #128640

Comments

@longsh07
Copy link

The problem

I have added a Tapo T315 temperature and humidity sensor to my home which communicates via a Tapo H100 hub using the TP-Link Smart Home integration. All entities current and historical data are reporting correctly, however, I would like to display a daily and monthly min/max temperature using a Statistics card. On the Statistics card, the T315's temperature entity is not an option (see screenshot), yet humidity and other entities are available and work. Statistics cards are working correctly for other brand temp/humidity devices using a different integration.

image

What version of Home Assistant Core has the issue?

core-2024.10.2

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

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)

@rytilahti rytilahti linked a pull request Oct 18, 2024 that will close this issue
19 tasks
@rytilahti
Copy link
Member

Thanks for reporting this @longsh07! The state class was forgotten when the sensor got added, so that's why it wasn't showing up. The linked PR should fix the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants