Closed KlaraJa closed 7 months ago
This is by design actually and intended behaviour. What would be the reason you don't want this?
In my case, I only want the lights to be added and not smart plugs (e.g.: I use them to track my computer). That's why I only have the lights configured.
And the description of the area in the GUI config says:
If this is intended, shouldn't it be "All power sensors" instead of "All powercalc sensors"?
This was added on multiple requests by users. Also see https://github.com/bramstroker/homeassistant-powercalc/issues/1741 I will update the documentation to make that more clear.
It's currently not possible to do what you want with the GUI configuration.
When you want more granular control and more possibilities I suggest to setup the group with YAML.
See https://homeassistant-powercalc.readthedocs.io/en/latest/sensor-types/group/include-entities.html.
You can combine area
or other options with one or more filters, and mix and match that.
See https://homeassistant-powercalc.readthedocs.io/en/latest/sensor-types/group/include-entities.html#filters
I have investigated adding certain complex configuration to the GUI but with the current possibilities for custom components it's impossible or require a massive amount of work. Also I want to keep the GUI more lean and mean.
I might consider adding a checkbox Add non powercalc sensors
to the GUI, which is defaulted to yes.
A checkbox would be really nice
I came here looking for the reason my turned off lights are suddenly reporting multiple kWh after adding a few S31's... It may have been requested but really doesn't make sense to me. A group should only include what I selected IMHO. A checkbox would be highly appreciated and I'd personally leave it unchecked by default.
@mkaltner this only applies to the option to automatically include entities from an area
(and all the other include options when using YAML configuration). It makes sense to also include potential other power sensor from the system, to get a complete perspective.
When you select your entities manually at the group there won't be magically added other entities in any way.
Anyways, I found some time today to work on implementing a toggle to control this behaviour.
See #2088, which is just merged in master and will be part of the upcoming release.
See the documentation which explains the new option: https://homeassistant-powercalc.readthedocs.io/en/latest/sensor-types/group/include-entities.html#exclude-non-powercalc-sensors There is also a toggle added to the GUI when setting up the group sensors.
Interesting, then for some reason my group with selected entities that are turned off is reporting a large amount of usage.
Note where it flattens out, that's when I removed the group from the area. So I think there must be a bug with groups with selected devices still including non powercalc entities.
@mkaltner So you are using the area option in the group settings? That one includes the non powercalc sensors as stated before.
That will be "fixed" in next version where this behaviour can be toggled.
When you don't use this "area" option and still experience issues please report a new issue with as much information as possible.
Btw. you can see which individual entities your group is composed of in the state attributes. So that would also help you when debugging.
I did, yes. I add all my devices and things to their appropriate area. Guess that means more in powercalc per the description. I removed it and for me it seems to work as expected now.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4849 Installed Version | 1.34.0 Stage | running Available Repositories | 1462 Downloaded Repositories | 27Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 11.5 -- | -- update_channel | stable supervisor_version | supervisor-2024.01.1 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 219.4 GB disk_used | 9.7 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Let's Encrypt (5.0.15), AirCast (4.2.0), WireGuard (0.10.2), Matter Server (5.1.1), Mosquitto broker (6.4.0), Studio Code Server (5.15.0), Advanced SSH & Web Terminal (17.1.0), Home Assistant Google Drive Backup (0.112.1), Samba NAS (12.2.0-nas1), InfluxDB (5.0.0), Grafana (9.1.3), iSponsorBlockTV add-on (2.0.10), Whisper (1.0.2)Dashboards
dashboards | 6 -- | -- resources | 14 views | 12 mode | storageRecorder
oldest_recorder_run | February 1, 2024 at 20:20 -- | -- current_recorder_run | February 9, 2024 at 11:11 estimated_db_size | 478.14 MiB database_engine | sqlite database_version | 3.44.2Spotify
api_endpoint_reachable | ok -- | --Checklist
Describe the issue
The description for Area says, that all powercalc sensors in this area will be added. But it also adds the power from real power meters. In my case it was the real power meter from my Aqara EU Plug, which I did not add to Powercalc.
Reproduction steps
Debug logs
Diagnostics dump or YAML config
No response