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

Entities from Configuration and Diagnostic not visible when showing all entities via History -> Choose device ->DeviceName #104451

Closed
HansRemmerswaal opened this issue Nov 24, 2023 · 5 comments

Comments

@HansRemmerswaal
Copy link

The problem

  1. I have a device called ems-esp Boiler
  2. When I go to Settings -> Devices & Services -> Devices -> ems-esp Boiler I see all the entities
  3. The list of entities are shown in 4 groups; Controls, Sensors, Configuration and Diagnostic
  4. When I go to History -> Choose device -> ems-esp Boiler then I do not see the entities of the group Configuration and Diagnostic

What version of Home Assistant Core has the issue?

2023.11.3

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

No response

Link to integration documentation on our website

No response

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

@HansRemmerswaal
Copy link
Author

See also the ticket I raised for the device itself.
If it's correct that those 2 groups are excluded in HA then it's an issue in EMS-ESP32 sending the data incorrect to HA.

emsesp/EMS-ESP32#1459

@elupus
Copy link
Contributor

elupus commented Nov 25, 2023

This is by design. They will not be considered for history data.

@HansRemmerswaal
Copy link
Author

But all the sensor values of this device are recently moved to Configuration and Diagnostic by the developers. So that then sounds like a mistake?

@elupus
Copy link
Contributor

elupus commented Nov 25, 2023

Then you need to take that up with the developer of that integration / device.

@HansRemmerswaal
Copy link
Author

Ok, thanks for your help.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants