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

Area card: Temperature shown 10 °C too high #21049

Closed
3 of 4 tasks
AleXSR700 opened this issue Jun 9, 2024 · 7 comments
Closed
3 of 4 tasks

Area card: Temperature shown 10 °C too high #21049

AleXSR700 opened this issue Jun 9, 2024 · 7 comments

Comments

@AleXSR700
Copy link

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

The area card is showing the temperature sensor value 10 °C higher than actual value.

Card:
image

Sensor entity value:
image

Describe the behavior you expected

Displayed value = sensor value

Steps to reproduce the issue

  1. Install temperature sensor
  2. Add sensor to area
  3. Add area card
    ...

What version of Home Assistant Core has the issue?

2024.6.1

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

@karwosts
Copy link
Contributor

karwosts commented Jun 9, 2024

You've certainly got a second sensor with device_class: temperature somewhere in that area, that's reporting a higher value. The area card will average together all temperature sensors in the area.

@AleXSR700
Copy link
Author

AleXSR700 commented Jun 9, 2024

Interesting idea.
There is no other sensor that is part of a climate device. There are temperature entities in the power sockets which of course have higher values.

Is there a way then to select which sensor is being used?

EDIT:
Seems that maybe the problem is really that the card assumes that all temperature devices are equal. I cannot find a documentation that suggests that this behaviour can be changed.
Nor that e.g. switches are not shown.

The switches part actually being very risky because that triggers all power sockets etc. at the same time, shutting down anything that is in that room without any confirmation. That seems a bit risky to me 🙈

@karwosts
Copy link
Contributor

karwosts commented Jun 9, 2024

No for area card there's not currently a way to select entities. That may change someday in the future.

It's somewhat simplistic card that isn't going to be appropriate for everyone's usecase.

If you want an entity to not be used for Area card, the best you can do is mark that entity as Hidden, and then it will not be considered for calculations.

@AleXSR700
Copy link
Author

thank you for your support :)

Hiding entities that are useful is not really a good solution just because of a broken card.
I will just remove the card until it is fixed :)

@karwosts
Copy link
Contributor

karwosts commented Jun 9, 2024

Sure that's fine. Though "hiding" is not as severe as it sounds, I think the only difference is they don't show up on autogenerated dashboards. They're still fully useable and visible everywhere else.

@karwosts
Copy link
Contributor

Closing for now as the card is operating as intended. Certainly additional functionality could be desired, but those desires are probably well covered by existing feature requests, or you can make a new one if you wish.

@karwosts karwosts closed this as not planned Won't fix, can't repro, duplicate, stale Jun 10, 2024
@AleXSR700
Copy link
Author

No, that is fine, thank you.

This is one of the cases where a feature is actually a bug declared as a feature to make it look like it is working as intended 😄

So, since it is a nice-to-have card rather than must-have card, I will keep my fingers crossed and wait :)

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

No branches or pull requests

2 participants