Skip to content

Something is blocking Home Assistant from wrapping up the start up phase #4347

@NigelNooNoo

Description

@NigelNooNoo

Describe the issue you are experiencing

Octopus energy “Failed to set up”. None of the Octopus devices are working, electricity meter, electricity meter export or gas meter. All of their sensors are showing unavailable. And the Octopus entities are not showing any data.
Not sure how to in-install or re-install and do not wish to loose any data either.

HA Core log:
——————-
Logger: homeassistant.core
Source: core.py:551
First occurred: 5 October 2025 at 00:07:26 (1 occurrence)
Last logged: 5 October 2025 at 00:07:26

Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: person, counter, ibeacon, blueprint, file_upload, meross_lan, system_log, wake_word, zha.update, upnp, zha.button, history, matter.switch, media_player, meross_lan.switch, persistent_notification, thread, ssdp, homeassistant_yellow, lock, http, esphome, homekit_controller.media_player, hacs.switch, frontend, matter.lock, matter.number, hardware, cover, meross_lan.update, intent, file, light, hassio.binary_sensor, number, script, matter.sensor, camera, sun.sensor, search, input_number, webostv, homeassistant.scene, repairs, matter.climate, zha.cover, vacuum, lovelace, zha.lock, device_automation, matter.light, matter.cover, input_button, siren, meross_lan.light, stt, analytics, androidtv_remote, backup, input_datetime, climate, zha.number, hacs, default_config, bluetooth_adapters, hacs.update, switch, trace, zha.switch, config, input_select, matter, logbook, sensor, binary_sensor, notify, zha.climate, auth, onboarding, meross_lan.button, zha.light, image_upload, zha.binary_sensor, zha, sun.binary_sensor, button, mqtt, mobile_app.device_tracker, hassio.update, assist_pipeline, media_source, zha.device_tracker, octopus_energy, fronius, api, tts, mobile_app.sensor, update, event, emulated_hue, zeroconf, conversation, backup.sensor, homeassistant, mobile_app.notify, meross_lan.sensor, webostv.notify, automation, yale_smart_alarm, esphome.sensor, matter.valve, mobile_app.binary_sensor, network, hassio, websocket_api, scene, hassio.switch, zha.alarm_control_panel, ibeacon.sensor, dhcp, my, zha.siren, homekit_controller.switch, alarm_control_panel, application_credentials, ibeacon.device_tracker, met, schedule, cast, usage_prediction, diagnostics, matter.select, homeassistant_hardware, homeassistant_alerts, matter.event, energy.sensor, oralb, backup.event, cloud.tts, stream, cast.media_player, go2rtc, sun, shelly, zone, select, matter.water_heater, recorder, fan, ipp, zha.fan, webhook, input_boolean, hassio.sensor, cloud, ffmpeg, fronius.sensor, webostv.media_player, matter.button, homekit_controller, forecast_solar, device_tracker, valve, matter.update, zha.sensor, matter.vacuum, system_health, homeassistant_yellow.update, timer, matter.fan, tag, energy, input_text, homekit, zha.select, bluetooth, oralb.sensor, usb, mobile_app, homekit_controller.button, water_heater, logger, matter.binary_sensor The system is waiting for tasks: {<Task pending name='Task-1345' coro=<HacsBase.startup_tasks() running at /config/custom_components/hacs/base.py:667> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}

HA Core log - Octopus energy
————————————————
Logger: homeassistant.config_entries
Source: config_entries.py:761
First occurred: 5 October 2025 at 00:06:52 (1 occurrence)
Last logged: 5 October 2025 at 00:06:52

Error setting up entry A-ABED6E49 for octopus_energy
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/aiohttp/resolver.py", line 117, in resolve
resp = await self._resolver.getaddrinfo(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<5 lines>...
)
^
aiodns.error.DNSError: (3, 'DNS server returned general failure')

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1532, in _create_direct_connection
hosts = await self._resolve_host(host, port, traces=traces)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1148, in _resolve_host
return await asyncio.shield(resolved_host_task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1179, in _resolve_host_with_throttle
addrs = await self._resolver.resolve(host, port, family=self._family)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/resolver.py", line 126, in resolve
raise OSError(None, msg) from exc
OSError: [Errno None] DNS server returned general failure

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 761, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/octopus_energy/init.py", line 159, in async_setup_entry
await async_setup_dependencies(hass, config)
File "/config/custom_components/octopus_energy/init.py", line 315, in async_setup_dependencies
account_info = await client.async_get_account(config[CONFIG_ACCOUNT_ID])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/octopus_energy/api_client/init.py", line 864, in async_get_account
await self.async_refresh_token()
File "/config/custom_components/octopus_energy/api_client/init.py", line 702, in async_refresh_token
await self.__async_fetch_token()
File "/config/custom_components/octopus_energy/api_client/init.py", line 722, in __async_fetch_token
async with client.post(url, headers=headers, json=payload) as token_response:
~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 1488, in aenter
self._resp: _RetType = await self._coro
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 770, in _request
resp = await handler(req)
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 725, in _connect_and_send_request
conn = await self._connector.connect(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
req, traces=traces, timeout=real_timeout
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 642, in connect
proto = await self._create_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1209, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1538, in _create_direct_connection
raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host api.octopus.energy:443 ssl:default [DNS server returned general failure]

What operating system image do you use?

yellow (Home Assistant Yellow)

What version of Home Assistant Operating System is installed?

6.12.34-haos-raspi

Did the problem occur after upgrading the Operating System?

No

Hardware details

Running on a Home Assistant Yellow

Steps to reproduce the issue

...

Anything in the Supervisor logs that might be useful for us?

2025-10-05 00:06:33.019 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2025-10-05 00:06:33.028 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='NOT_RUNNING', offline_db_migration=False)
2025-10-05 00:06:40.331 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f88f07230>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/
2025-10-05 00:06:45.336 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f81224e10>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/
2025-10-05 00:06:50.341 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f81224a50>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/
2025-10-05 00:07:13.337 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='STARTING', offline_db_migration=False)
2025-10-05 00:07:28.425 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='RUNNING', offline_db_migration=False)
2025-10-05 00:07:28.426 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance

Anything in the Host logs that might be useful for us?

2025-10-05 00:05:02.889 RPi-Yellow kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2025-10-05 00:05:02.890 RPi-Yellow kernel: usb 1-1.1: Product: ConBee II
2025-10-05 00:05:02.891 RPi-Yellow kernel: usb 1-1.1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
2025-10-05 00:05:02.892 RPi-Yellow kernel: usb 1-1.1: SerialNumber: DE2476979
2025-10-05 00:05:02.893 RPi-Yellow kernel: cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device
2025-10-05 01:05:04.488 RPi-Yellow kernel: usb 1-1.1: USB disconnect, device number 7
2025-10-05 01:05:04.810 RPi-Yellow kernel: usb 1-1.1: new full-speed USB device number 8 using dwc2
2025-10-05 01:05:05.014 RPi-Yellow kernel: usb 1-1.1: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
2025-10-05 01:05:05.017 RPi-Yellow kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2025-10-05 01:05:05.018 RPi-Yellow kernel: usb 1-1.1: Product: ConBee II
2025-10-05 01:05:05.019 RPi-Yellow kernel: usb 1-1.1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
2025-10-05 01:05:05.020 RPi-Yellow kernel: usb 1-1.1: SerialNumber: DE2476979
2025-10-05 01:05:05.021 RPi-Yellow kernel: cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device
2025-10-05 01:05:08.071 RPi-Yellow kernel: usb 1-1.1: USB disconnect, device number 8
2025-10-05 01:05:08.454 RPi-Yellow kernel: usb 1-1.1: new full-speed USB device number 9 using dwc2

System information

System Information

version core-2025.10.1
installation_type Home Assistant OS
dev false
hassio true
docker true
container_arch aarch64
user root
virtualenv false
python_version 3.13.7
os_name Linux
os_version 6.12.34-haos-raspi
arch aarch64
timezone Europe/London
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.5
Stage running
Available Repositories 2353
Downloaded Repositories 4
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 16.2
update_channel stable
supervisor_version supervisor-2025.10.0
agent_version 1.7.2
docker_version 28.3.3
disk_total 234.0 GB
disk_used 9.3 GB
nameservers 192.168.1.254, fe80::e8e:29ff:fe7e:8c1
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board yellow
supervisor_api ok
version_api ok
installed_addons File editor (5.8.0), Studio Code Server (5.19.3), Samba share (12.5.2), Terminal & SSH (9.20.1), Matter Server (8.1.1), Mosquitto broker (6.5.2)
Dashboards
dashboards 2
resources 1
views 2
mode storage
Network Configuration
adapters lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth58852d2 (disabled), vethb108bb1 (disabled), veth68a2c49 (disabled), veth38756a5 (disabled), veth3e7ddcb (disabled), veth614b8f5 (disabled), vethba2ce2f (disabled), veth9b4ebd7 (disabled), vethb4ea96b (disabled)
ipv4_addresses lo (127.0.0.1/8), end0 (192.168.1.32/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth58852d2 (), vethb108bb1 (), veth68a2c49 (), veth38756a5 (), veth3e7ddcb (), veth614b8f5 (), vethba2ce2f (), veth9b4ebd7 (), vethb4ea96b ()
ipv6_addresses lo (::1/128), end0 (fd68:4bee:6bf2:dc91:730a:257b:c879:3e0f/64, fe80::5719:e9ba:7362:f7c9/64), hassio (fe80::9407:12ff:feb7:a46c/64), docker0 (fe80::dc8d:47ff:fe12:eca4/64), veth58852d2 (fe80::f85d:63ff:feee:3e83/64), vethb108bb1 (fe80::1863:d3ff:fe75:7169/64), veth68a2c49 (fe80::882:23ff:fee1:f69/64), veth38756a5 (fe80::607e:d6ff:fee4:cf6f/64), veth3e7ddcb (fe80::6c8f:9ff:fe90:189/64), veth614b8f5 (fe80::9cc9:8dff:feaa:a5dc/64), vethba2ce2f (fe80::444d:54ff:fe73:f22c/64), veth9b4ebd7 (fe80::50bf:9bff:fe69:f1f2/64), vethb4ea96b (fe80::208c:91ff:fed7:1cec/64)
announce_addresses 192.168.1.32, fd68:4bee:6bf2:dc91:730a:257b:c879:3e0f, fe80::5719:e9ba:7362:f7c9
Recorder
oldest_recorder_run 27 September 2025 at 23:23
current_recorder_run 5 October 2025 at 00:06
estimated_db_size 310.57 MiB
database_engine sqlite
database_version 3.49.2

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions