Entities not working on core 2025.1.0

[albcarr85]

Hi, from today, after the latest update of Home Assistant Core 2025.1.0, the entities provided by the integration are no longer available. I don't see anything in the logs that can help me understand the problem. No problems encountered with the previous version 2024.12.5. Thank you very much for your work

[magico13]

I am running 2025.1.0 as well so it's probably just a problem during startup and not an incompatibility with the update. Try reloading the integration or restarting Home Assistant and that'll hopefully be enough to fix it.

[Johndowne]

Having the same issue on 2025.1.0 with this integration. Have restarted HA and Emporia integration still no data.

[Johndowne]

Getting “no longer being provided” messages

[Johndowne]

Rolled back to 2024.12.5 HA and working fine again

[tpomerhn]

Mine are working, but perhaps a related data point, the folks using the HACS integration for VIctron had their app break in 2025.1.0, as well (including me). Something related to a python library. Not sure if this helps the devs or not. https://github.com/sfstar/hass-victron/issues/267

[magico13]

Looks like the Victron one is with a modbus library but that's not used here. For anyone seeing this issue, can you provide any relevant messages from the logs?

[Johndowne]

Is this any good from before I backed out the HA update...

2025-01-05 10:35:34.747 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration emporia_vue which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2025-01-05 10:36:26.961 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open with args ('/usr/share/zoneinfo/Europe/London', 'rb') inside the event loop by custom integration 'emporia_vue' at custom_components/emporia_vue/init.py, line 468: tz_info = dateutil.tz.gettz(tz_string) (offender: /usr/local/lib/python3.13/site-packages/dateutil/tz/tz.py, line 464: fileobj = open(fileobj, 'rb')), please create a bug report at https://github.com/magico13/ha-emporia-vue/issues File "/config/custom_components/emporia_vue/init.py", line 185, in async_setup_entry File "/config/custom_components/emporia_vue/init.py", line 126, in async_update_data_1min File "/config/custom_components/emporia_vue/init.py", line 336, in update_sensors File "/config/custom_components/emporia_vue/init.py", line 356, in recurse_usage_data File "/config/custom_components/emporia_vue/init.py", line 468, in change_time_to_local 2025-01-05 10:36:27.363 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'emporia_vue' calls async_forward_entry_setup for integration, emporia_vue with title: Emporia Power Monitor and entry_id: 7ef4124e7b04b618724659338cbfe9fd, which is deprecated, await async_forward_entry_setups instead at custom_components/emporia_vue/init.py, line 291: hass.async_create_task(. This will stop working in Home Assistant 2025.6, please create a bug report at https://github.com/magico13/ha-emporia-vue/issues 2025-01-05 10:36:27.387 WARNING (ImportExecutor_0) [homeassistant.const] POWER_WATT was used from emporia_vue, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead, please report it to the author of the 'emporia_vue' custom integration 2025-01-05 10:36:27.396 WARNING (ImportExecutor_0) [homeassistant.const] ENERGY_KILO_WATT_HOUR was used from emporia_vue, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead, please report it to the author of the 'emporia_vue' custom integration 2025-01-05 10:36:27.440 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration emporia_vue with title: Emporia Power Monitor and entry_id: 7ef4124e7b04b618724659338cbfe9fd, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1, please report this issue 2025-01-05 10:36:28.764 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration emporia_vue with title: Emporia Power Monitor and entry_id: 7ef4124e7b04b618724659338cbfe9fd, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1, please report this issue 2025-01-05 10:36:32.555 WARNING (SyncWorker_5) [homeassistant.helpers.service] Unable to parse services.yaml for the emporia_vue integration: extra keys not allowed @ data['set_charger_current']['target']['entity'][0]['manufacturer'] 2025-01-05 10:39:24.099 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration emporia_vue which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2025-01-05 10:39:33.921 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration emporia_vue which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2025-01-05 10:53:37.492 ERROR (MainThread) [custom_components.emporia_vue] Error communicating with Emporia API: HTTPSConnectionPool(host='api.emporiaenergy.com', port=443): Max retries exceeded with url: /AppAPI?apiMethod=getDeviceListUsages&deviceGids=97051+228977+228980+228983+228985+311266+311267&instant=2025-01-05T10:53:27.485236Z&scale=1MIN&energyUnit=KilowattHours (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa1527bf250>: Failed to establish a new connection: [Errno -3] Try again')) 2025-01-05 10:53:37.494 ERROR (MainThread) [custom_components.emporia_vue] Error fetching sensor data: Error communicating with Emporia API: HTTPSConnectionPool(host='api.emporiaenergy.com', port=443): Max retries exceeded with url: /AppAPI?apiMethod=getDeviceListUsages&deviceGids=97051+228977+228980+228983+228985+311266+311267&instant=2025-01-05T10:53:27.485236Z&scale=1MIN&energyUnit=KilowattHours (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa1527bf250>: Failed to establish a new connection: [Errno -3] Try again')) 2025-01-05 10:53:38.276 ERROR (MainThread) [custom_components.emporia_vue.switch] Error fetching switch data: Error communicating with Emporia API: HTTPSConnectionPool(host='api.emporiaenergy.com', port=443): Max retries exceeded with url: /customers/devices/status (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa1527bf390>: Failed to establish a new connection: [Errno -3] Try again')) 2025-01-05 12:38:17.531 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration emporia_vue which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

[Johndowne]

This looks relevant to my uninformed eyes...

2025-01-05 10:36:27.387 WARNING (ImportExecutor_0) [homeassistant.const] POWER_WATT was used from emporia_vue, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead, please report it to the author of the 'emporia_vue' custom integration

[magico13]

Well that's very odd, that constant was updated to the new format in v0.9.1, which was Summer of 2023. Somehow you're running an ancient version. Please update it in HACS to a newer version, v0.10.1 has an issue with certain merged channels so v0.10.0 might be better if that applies to you.

Editing just to comment that I didn't actually release that version until February 2024, so it's still pretty outdated but not quite as outdated as I first thought.

[Johndowne]

Ah, I found that this Repository was not listed in HACS which I assume is why I hadn’t been notified of updates. No idea how that happened. Have now updated this integration and will update HA too

[Johndowne]

It’s all good thanks!

[magico13]

@albcarr85 any updates for your situation? Was a reboot sufficient, or is it a similar situation where the integration is outdated?

[morfeus02]

same issue here. Upgraded to 2025.1 and HACS to latest version and the integration stopped working with error "integration not loaded" and HASS displays "Wrapping up startup, not everything will be available until it is finished". Tried restarting, reinstalling the integration, nothing worked. Could not restore from previous backup untill i stopped manually the emporia integration because of this error: 'BackupManager.do_restore_partial' blocked from execution, system is not running - startup After restoring from partial backup still not working, could not downgrade the HACS version because i don't have a backup.

I looked in my log file and may have found the issue?

2025-01-06 12:58:16.765 ERROR (SyncWorker_0) [homeassistant.util.package] Unable to install package pyemvue==0.18.6: error: Failed to fetch: https://files.pythonhosted.org/packages/41/ab/cf5ae4ee005d4b45b5b8f229470713e83fb92f149d3f5ced831e4e07c8d6/pyemvue-0.18.6-py3-none-any.whl.metadata Caused by: Request failed after 3 retries Caused by: error sending request for url (https://files.pythonhosted.org/packages/41/ab/cf5ae4ee005d4b45b5b8f229470713e83fb92f149d3f5ced831e4e07c8d6/pyemvue-0.18.6-py3-none-any.whl.metadata) Caused by: operation timed out 2025-01-06 12:58:45.353 WARNING (MainThread) [homeassistant.components.netatmo] API error: 500 (Internal Server Error) 2025-01-06 13:00:06.638 WARNING (MainThread) [homeassistant.components.netatmo] API error: 500 (Internal Server Error) 2025-01-06 13:01:27.631 WARNING (MainThread) [homeassistant.components.netatmo] API error: 500 (Internal Server Error) 2025-01-06 13:02:21.492 ERROR (SyncWorker_0) [homeassistant.util.package] Unable to install package pyemvue==0.18.6: error: Failed to fetch: https://files.pythonhosted.org/packages/41/ab/cf5ae4ee005d4b45b5b8f229470713e83fb92f149d3f5ced831e4e07c8d6/pyemvue-0.18.6-py3-none-any.whl.metadata Caused by: Request failed after 3 retries Caused by: error sending request for url (https://files.pythonhosted.org/packages/41/ab/cf5ae4ee005d4b45b5b8f229470713e83fb92f149d3f5ced831e4e07c8d6/pyemvue-0.18.6-py3-none-any.whl.metadata) Caused by: operation timed out

[morfeus02]

restoring Vm from an old image (pre HACS and HAOS upgrade) fixed it, for now. Hope you can find the source of these issues!

[magico13]

@morfeus02 That's not a server I control, maybe PyPi had an issue or there's something between your server and there. I was able to hit that url just now without issue so maybe try again.

[morfeus02]

Found the source of the issue, snort on my pfsense router. i installed it a few days before the update. it was blocking traffic to pythonhosted, but only from homeassistant, still have no idea why.

[nate1232]

I'm having the POWER_WATT issue too. I'll investigate updates to see what is going on.