Missing additional entities on HomeWizard meter

geertdoornbos commented 3 months ago

The problem

Naming has changes for several entities of homewizard integration https://github.com/home-assistant/core/pull/108854 I missed the breaking changes message for this. After manually removing two 't1' entities for import and export energy, errors were gone. 20 additional entities (like voltage per phase) are turned off.

The api to the device works fine. Logging shows no issues.

Is there a migration for the renamed entities (to keep their data?). What to do to get the additional entities back?

What version of Home Assistant Core has the issue?

core-2024.7.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

HomeWizard

Link to integration documentation on our website

https://www.home-assistant.io/integrations/homewizard/

Diagnostics information

2024-07-18 13:17:58.421 DEBUG (MainThread) [homewizard_energy.homewizard_energy] GET, http://192.168.1.71/api, None
2024-07-18 13:17:58.439 DEBUG (MainThread) [homewizard_energy.homewizard_energy] 200, {"product_name":"KWh Meter 3-phase","product_type":"SDM630-wifi","serial":"3c39e72e02c0","firmware_version":"4.06","api_version":"v1"}
2024-07-18 13:17:58.440 DEBUG (MainThread) [homewizard_energy.homewizard_energy] GET, http://192.168.1.71/api/v1/data, None
2024-07-18 13:17:58.609 DEBUG (MainThread) [homewizard_energy.homewizard_energy] 200, {"wifi_ssid":"WVB2","wifi_strength":74,"total_power_import_kwh":72.654,"total_power_import_t1_kwh":72.654,"total_power_export_kwh":14667.798,"total_power_export_t1_kwh":14667.798,"active_power_w":-6259.442,"active_power_l1_w":-2030.728,"active_power_l2_w":-2134.947,"active_power_l3_w":-2093.767,"active_voltage_l1_v":233.692,"active_voltage_l2_v":245.472,"active_voltage_l3_v":238.865,"active_current_a":26.129,"active_current_l1_a":8.687,"active_current_l2_a":8.692,"active_current_l3_a":8.75,"active_apparent_current_a":26.146,"active_apparent_current_l1_a":8.688,"active_apparent_current_l2_a":8.698,"active_apparent_current_l3_a":8.76,"active_reactive_current_a":0.86,"active_reactive_current_l1_a":0.136,"active_reactive_current_l2_a":0.303,"active_reactive_current_l3_a":0.421,"active_apparent_power_va":6257.837,"active_apparent_power_l1_va":2030.283,"active_apparent_power_l2_va":2135.036,"active_apparent_power_l3_va":2092.519,"active_reactive_power_var":-206.792,"active_reactive_power_l1_var":-31.814,"active_reactive_power_l2_var":-74.353,"active_reactive_power_l3_var":-100.625,"active_power_factor_l1":1,"active_power_factor_l2":0.999,"active_power_factor_l3":0.999,"active_frequency_hz":49.945}
2024-07-18 13:17:58.610 DEBUG (MainThread) [homewizard_energy.homewizard_energy] GET, http://192.168.1.71/api/v1/system, None
2024-07-18 13:17:58.666 DEBUG (MainThread) [homewizard_energy.homewizard_energy] 200, {"cloud_enabled":true}
2024-07-18 13:17:58.667 DEBUG (MainThread) [homeassistant.components.homewizard.coordinator] Finished fetching homewizard data in 0.246 seconds (success: True)

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 3 months ago

Hey there @dcsbl, mind taking a look at this issue as it has been labeled with an integration (homewizard) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `homewizard` 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 homewizard` 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)}}

homewizard documentation homewizard source _{^{(message by IssueLinks)}}

DCSBL commented 3 months ago

Can you add the diagnostics file? https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics

geertdoornbos commented 3 months ago

config_entry-homewizard-01J32R3G5JQ380VPHAWCG6M0T1.json

DCSBL commented 3 months ago

Okay weird, can you send a full screenshot of the 'device' page (as example)? Feel free to redact same information if you wish.

geertdoornbos commented 3 months ago

DCSBL commented 3 months ago

This looks normal to me; it is the out-of-the-box experience. The grayed-out sensors seem to be disabled. Click on them, press the ⚙️ icon, and then turn on 'Enabled' and 'visable' if they are disabled or hidden.

Please let me know it this was the case 😇

geertdoornbos commented 3 months ago

'this was the case', but ... 😄 why were they disabled? I did not disable them by hand like I did now to enable them.

Other side effect, I also see units now.

Up and running now, thanks!

DCSBL commented 3 months ago

Awesome to hear!

Sensors are disabled by default if they are not used/important for most users and/or 'noisy'. They pollute the database without any use for most users. They are available for those who are interested, but not enabled by default.

home-assistant / core