Beta version 1.15.0

[tjorim]

Updated to the beta today and noticed that power and energy are (inter)changed. Entity with id _power is now named energy and measured in kWh, entity with id _energy is now unavailable. Also got a repair action for long term statistics. Is this expected or a bug? I don't see it mentioned in the release notes.

[tjorim]

Also set up a new integration entry to test. Only the energy sensor is created (with the correct id unlike the ones migrated).

[bramstroker]

That is definitely not correct and totally unexpected.
I'm not sure what causes it yet.
Did you set up some global configuration using the GUI already? Of do you have some global configuration in YAML?
Could you share diagnostics for one of the concerning configuration entries? You can do so by clicking the three dots, and Download diagnostics.

[tjorim]

YAML config is just powercalc:.
GUI global config now shows this:

I do notice some lights that are discovered and matched by library are fine.
So at first sight it's only manual virtual power sensors.
Disgnostics file attached.
config_entry-powercalc-3cd9f01bf02cae49838e7cb38285443d.json
Edit: my entry with daily fixed energy is also okay, so only the ones linked to a source entity with fixed power?

[bramstroker]

Gui global config will only be applied when you actually finish the configuration flow.

I don't see anything obvious at first glance.

Config entry data seems fine:

{
        "entity_id": "light.standing_lamp",
        "mode": "fixed",
        "create_energy_sensor": true,
        "create_utility_meters": false,
        "fixed": {
          "power": 11.0
        },
        "energy_integration_method": "left",
        "unique_id": "pc_91b5b2b04e889549cb19effa3dea97e1",
        "sensor_type": "virtual_power",
        "name": "Standing lamp",
        "_power_entity": "sensor.standing_lamp_power",
        "_energy_entity": "sensor.standing_lamp_power"
      }

Could you enable debug logging and check Creating power sensor and Creating energy sensor lines. Let's focus specifically on the Standing lamp entities for now.

[tjorim]

I see, I just created the global config via GUI.
I disabled the other entries with only Standing lamp (and a standing test lamp from before) left.
My statement it's just affects the manual virtual power sensors is wrong, Hallway light was set up with library profile and also affected.
I do notice the piece you pasted says

        "_power_entity": "sensor.standing_lamp_power",
        "_energy_entity": "sensor.standing_lamp_power"

which seems weird (I mean entity id is the same for both).
Here are the debug lines requested:

2024-10-13 11:42:45.123 DEBUG (MainThread) [custom_components.powercalc.discovery] Done auto discovering entities
2024-10-13 11:42:45.145 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] Creating daily_fixed_energy energy sensor (name=Standing lamp energy, entity_id=sensor.standing_lamp_power, unique_id=pc_91b5b2b04e889549cb19effa3dea97e1)
2024-10-13 11:42:45.147 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] sensor.standing_lamp_power: Restoring state: 0.2487
2024-10-13 11:42:45.154 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] Creating daily_fixed_energy energy sensor (name=Standing test lamp energy, entity_id=sensor.standing_test_lamp_energy, unique_id=pc_0xcc86ecfffeeab1b9_switch_zigbee2mqtt)
2024-10-13 11:42:45.155 DEBUG (MainThread) [custom_components.powercalc.sensors.daily_energy] sensor.standing_test_lamp_energy: Restoring state: 0.1922
2024-10-13 11:43:19.981 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor (entity_id=sensor.all_standby_energy, source_entity=sensor.all_standby_power, unit_prefix=k)

Further obervation:

• entity_id: standing_lamp_power
  • name: Standing lamp energy
  • value present: 0,2487 kWh
  • is NOT linked or shown in the source device
• entity_id: standing_lamp_energy
  • name: Standing lamp energy
  • value present: Unavailable
  • is linked and shown in the source device

[tjorim]

System info (not posted initially as this was intended to be a question instead of issue report 😅)

System Information

version	core-2024.10.2
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.4
os_name	Linux
os_version	6.6.31-haos-raspi
arch	aarch64
timezone	Europe/Brussels
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	4652
Installed Version	2.0.1
Stage	running
Available Repositories	1450
Downloaded Repositories	84

Home Assistant Cloud

logged_in	true
subscription_expiration	April 26, 2025 at 02:00
relayer_connected	true
relayer_region	eu-central-1
remote_enabled	true
remote_connected	true
alexa_enabled	false
google_enabled	true
remote_server	eu-central-1-7.ui.nabu.casa
certificate_status	ready
instance_id	98df8b6855fd40a682abea6ec3befbad
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 13.2.rc1
update_channel	beta
supervisor_version	supervisor-2024.10.2
agent_version	1.6.0
docker_version	27.2.0
disk_total	458.4 GB
disk_used	29.3 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	yellow
supervisor_api	ok
version_api	ok
installed_addons	Spotify Connect (0.13.0), Advanced SSH & Web Terminal (19.0.0), File editor (5.8.0), Zigbee2MQTT (1.40.2-1), Home Assistant Google Drive Backup (0.112.1), The Lounge (0.19.2), Glances (0.21.1), Uptime Kuma (0.12.4), ESPHome (2024.9.2), Mosquitto broker (6.4.1), Firefox (1.3.2), Silicon Labs Flasher (0.3.0), AirCast (4.2.2), eBUSd (23.2.5), Music Assistant Server (2.2.7), Studio Code Server (5.17.1), Get HACS (1.3.1), Tailscale (0.22.1), Zigbee2MQTT Edge (edge)

Dashboards

dashboards	3
resources	43
views	12
mode	storage

MercedesME 2020

api_endpoint_reachable	ok
websocket_connection_state	connected
cars_connected	1
version	v0.18.1

Recorder

oldest_recorder_run	October 4, 2024 at 11:25
current_recorder_run	October 13, 2024 at 11:42
estimated_db_size	1166.25 MiB
database_engine	sqlite
database_version	3.45.3

Spotify

api_endpoint_reachable	ok

[bramstroker]

Yes I also observed both _energy_entity and _power_entity has the same entity in the config entry data, which is wrong.
From the logs I see it's trying to create a Daily fixed energy sensor, Creating daily_fixed_energy energy, which is completely wrong sensor type.
I will have a further look later today.

[bramstroker]

I might need to add some extra debug logging in different places. Did you setup any daily fixed energy sensors https://docs.powercalc.nl/sensor-types/daily-energy/? Either in GUI or YAML?

[tjorim]

I had one which I disabled, but it does not show the issue. Here is the diagnostics for it.
config_entry-powercalc-d9ec8cdfcfe7dce5427d7bac56bd7d70.json

[bramstroker]

I think I have found the culprit. Standby for a little fix will be committed and released soon. Did a MacBook software upgrade and my command line is broken atm, so first need to fix that ;-)

[bramstroker]

Here you go: https://github.com/bramstroker/homeassistant-powercalc/releases/tag/v1.15.0-beta.2.
Thanks for the prompt reporting of the issue. Would have never known about the issue without you actually reporting.
Let me know if this solves for you. Fingers crossed.

[tjorim]

Thanks, all good!