Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot Upgrade to v2025.3.x - Supervisor crashes and rolls back. #5738

Open
rwatson2 opened this issue Mar 8, 2025 · 2 comments
Open

Cannot Upgrade to v2025.3.x - Supervisor crashes and rolls back. #5738

rwatson2 opened this issue Mar 8, 2025 · 2 comments
Labels

Comments

@rwatson2
Copy link

rwatson2 commented Mar 8, 2025

Describe the issue you are experiencing

Supervisor crashes and rolls back when attempting to upgrade core from 2025.2.5 to either 2025.3.0 or 2025.3.1.
I have disabled the unsupported integrations (even renamed custom configurations folder) - no change.
I did manage to force 2025.3.1 on via console (ha core update --version 2025.3.1) but supervisor kept crashing so I had to downgrade back to 2025.2.5.

Roll back log attached.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Steps to reproduce the issue

  1. Applying upgrade either through UI or shell.

...

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

HAOS VMware VM (ported from RPI5 several months ago).

supervisor log

2025-03-07 23:39:26.321 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API for a0d7b954_nodered closed
2025-03-07 23:39:40.812 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning homeassistant application
2025-03-07 23:39:41.211 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2025-03-07 23:39:41.753 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2025.3.1
2025-03-07 23:39:41.753 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2025-03-07 23:39:51.762 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
2025-03-07 23:39:51.763 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
2025-03-07 23:39:51.770 INFO (MainThread) [supervisor.homeassistant.core] A backup of the logfile is stored in /config/home-assistant-rollback.log
2025-03-07 23:39:51.771 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2025.2.5


rollback log
2025-03-07 22:20:19.988 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration miele 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-03-07 22:20:19.989 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pod_point 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-03-07 22:20:19.990 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs 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-03-07 22:20:19.990 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media 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-03-07 22:20:19.991 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tesla_serve_key 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-03-07 22:20:19.991 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration octopus_energy 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-03-07 22:20:19.992 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hildebrandglow_dcc 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-03-07 22:20:33.696 WARNING (MainThread) [homeassistant.helpers.frame] Detected that integration 'hive' calls `device_registry.async_get_or_create` referencing a non existing `via_device` ('hive', '7415484b-c0c1-458d-8d24-330616d639b9'), with device info: {'identifiers': {('hive', '4b5c31e2-78c9-4356-aa13-2c0813795ebb')}, 'manufacturer': 'Computime', 'model': 'SLT3', 'name': 'Your Thermostat', 'sw_version': '03130406', 'via_device': ('hive', '7415484b-c0c1-458d-8d24-330616d639b9')} at homeassistant/components/hive/binary_sensor.py, line 95: async_add_entities(sensors, True). This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+hive%22
2025-03-07 22:20:33.804 WARNING (MainThread) [homeassistant.helpers.frame] Detected that integration 'hive' calls `device_registry.async_get_or_create` referencing a non existing `via_device` ('hive', '7415484b-c0c1-458d-8d24-330616d639b9'), with device info: {'identifiers': {('hive', '4b5c31e2-78c9-4356-aa13-2c0813795ebb')}, 'manufacturer': 'Computime', 'model': 'SLT3', 'name': 'Your Thermostat', 'sw_version': '03130406', 'via_device': ('hive', '7415484b-c0c1-458d-8d24-330616d639b9')} at homeassistant/components/hive/climate.py, line 68: async_add_entities((HiveClimateEntity(hive, dev) for dev in devices), True). This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+hive%22
2025-03-07 22:20:33.852 WARNING (MainThread) [homeassistant.helpers.frame] Detected that integration 'hive' calls `device_registry.async_get_or_create` referencing a non existing `via_device` ('hive', '7415484b-c0c1-458d-8d24-330616d639b9'), with device info: {'identifiers': {('hive', '4b5c31e2-78c9-4356-aa13-2c0813795ebb')}, 'manufacturer': 'Computime', 'model': 'SLT3', 'name': 'Your Thermostat', 'sw_version': '03130406', 'via_device': ('hive', '7415484b-c0c1-458d-8d24-330616d639b9')} at homeassistant/components/hive/sensor.py, line 99: async_add_entities(. This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+hive%22
2025-03-07 22:20:33.985 WARNING (MainThread) [homeassistant.helpers.frame] Detected that integration 'hive' calls `device_registry.async_get_or_create` referencing a non existing `via_device` ('hive', '7415484b-c0c1-458d-8d24-330616d639b9'), with device info: {'identifiers': {('hive', '4b5c31e2-78c9-4356-aa13-2c0813795ebb')}, 'manufacturer': 'Computime', 'model': 'SLT3', 'name': 'Your Thermostat', 'sw_version': '03130406', 'via_device': ('hive', '7415484b-c0c1-458d-8d24-330616d639b9')} at homeassistant/components/hive/switch.py, line 44: async_add_entities(. This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+hive%22
2025-03-07 22:20:34.035 WARNING (MainThread) [homeassistant.helpers.frame] Detected that integration 'hive' calls `device_registry.async_get_or_create` referencing a non existing `via_device` ('hive', '7415484b-c0c1-458d-8d24-330616d639b9'), with device info: {'identifiers': {('hive', '4b5c31e2-78c9-4356-aa13-2c0813795ebb')}, 'manufacturer': 'Computime', 'model': 'SLT3', 'name': 'Your Thermostat', 'sw_version': '03130406', 'via_device': ('hive', '7415484b-c0c1-458d-8d24-330616d639b9')} at homeassistant/components/hive/water_heater.py, line 55: async_add_entities((HiveWaterHeater(hive, dev) for dev in devices), True). This will stop working in Home Assistant 2025.12.0, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+hive%22
2025-03-07 22:20:36.028 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dcc_sourced_smart_electricity_meter_cost_today (<class 'custom_components.hildebrandglow_dcc.sensor.Cost'>) is using state class 'total_increasing' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/HandyHat/ha-hildebrandglow-dcc/issues
2025-03-07 22:20:36.394 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dcc_sourced_smart_gas_meter_cost_today (<class 'custom_components.hildebrandglow_dcc.sensor.Cost'>) is using state class 'total_increasing' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/HandyHat/ha-hildebrandglow-dcc/issues
2025-03-07 22:20:42.696 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform miele does not generate unique IDs. ID door-000106571429 already exists - ignoring binary_sensor.dishwasher_door
2025-03-07 22:20:42.696 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform miele does not generate unique IDs. ID info-000106571429 already exists - ignoring binary_sensor.dishwasher_info
2025-03-07 22:20:42.696 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform miele does not generate unique IDs. ID failure-000106571429 already exists - ignoring binary_sensor.dishwasher_failure
2025-03-07 22:20:42.696 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform miele does not generate unique IDs. ID remoteEnable-000106571429 already exists - ignoring binary_sensor.dishwasher_remote_control
2025-03-07 22:20:42.696 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform miele does not generate unique IDs. ID smartGrid-000106571429 already exists - ignoring binary_sensor.dishwasher_smart_grid
2025-03-07 22:20:42.696 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform miele does not generate unique IDs. ID mobileStart-000106571429 already exists - ignoring binary_sensor.dishwasher_mobile_start
2025-03-07 22:20:42.697 ERROR (MainThread) [homeassistant.components.button] Platform miele does not generate unique IDs. ID start-000106571429 already exists - ignoring button.dishwasher_start
2025-03-07 22:20:42.697 ERROR (MainThread) [homeassistant.components.button] Platform miele does not generate unique IDs. ID stop-000106571429 already exists - ignoring button.dishwasher_stop
2025-03-07 22:20:42.699 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateStatus-000106571429 already exists - ignoring sensor.dishwasher_status
2025-03-07 22:20:42.699 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateProgramId-000106571429 already exists - ignoring sensor.dishwasher_program
2025-03-07 22:20:42.699 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateProgramType-000106571429 already exists - ignoring sensor.dishwasher_program_type
2025-03-07 22:20:42.700 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateProgramPhase-000106571429 already exists - ignoring sensor.dishwasher_program_phase
2025-03-07 22:20:42.700 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateRemainingTime-000106571429 already exists - ignoring sensor.dishwasher_remaining_time
2025-03-07 22:20:42.700 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateRemainingTimeAbs-000106571429 already exists - ignoring sensor.dishwasher_finish_at
2025-03-07 22:20:42.700 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateStartTime-000106571429 already exists - ignoring sensor.dishwasher_start_time
2025-03-07 22:20:42.700 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateStartTimeAbs-000106571429 already exists - ignoring sensor.dishwasher_start_at
2025-03-07 22:20:42.700 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateElapsedTime-000106571429 already exists - ignoring sensor.dishwasher_elapsed_time
2025-03-07 22:20:42.700 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateElapsedTimeAbs-000106571429 already exists - ignoring sensor.dishwasher_started_at
2025-03-07 22:20:42.700 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateCurrentWaterConsumption-000106571429 already exists - ignoring sensor.dishwasher_water_consumption
2025-03-07 22:20:42.700 ERROR (MainThread) [homeassistant.components.sensor] Platform miele does not generate unique IDs. ID stateCurrentEnergyConsumption-000106571429 already exists - ignoring sensor.dishwasher_energy_consumption
2025-03-07 22:20:42.701 ERROR (MainThread) [homeassistant.components.switch] Platform miele does not generate unique IDs. ID poweronoff-000106571429 already exists - ignoring switch.dishwasher_power_on
2025-03-07 22:20:43.045 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'Grid Power Notification' trigger: In 'numeric_state' condition: unknown entity sensor.tesla_powerwall_grid_power
2025-03-07 22:21:27.504 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to import_module with args ('custom_components.pod_point',) inside the event loop by integration 'config' at homeassistant/components/config/config_entries.py, line 422: success = await hass.config_entries.async_set_disabled_by( (offender: /usr/src/homeassistant/homeassistant/loader.py, line 1075: ComponentProtocol, importlib.import_module(self.pkg_path)), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+config%22
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#import_module
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 227, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 213, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 707, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 678, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2033, in _run_once
    handle._run()
  File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 28, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 422, in config_entry_disable
    success = await hass.config_entries.async_set_disabled_by(

2025-03-07 22:21:27.521 WARNING (ImportExecutor_0) [homeassistant.components.dhcp] DhcpServiceInfo was used from pod_point, this is a deprecated constant which will be removed in HA Core 2026.2. Use homeassistant.helpers.service_info.dhcp.DhcpServiceInfo instead, please report it to the author of the 'pod_point' custom integration
2025-03-07 23:00:38.901 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.53.4 for modules 'Time, AutoOff, DeviceModule, Energy, PowerProtection' after first update: ('Unable to query the device: 192.168.53.4: ', TimeoutError())
2025-03-07 23:00:44.900 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.53.4 individually for module query 'get_device_time' after first update: ('Unable to query the device: 192.168.53.4: ', TimeoutError())
2025-03-07 23:00:50.904 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.53.4 individually for module query 'get_auto_off_config' after first update: ('Unable to query the device: 192.168.53.4: ', TimeoutError())
2025-03-07 23:00:56.899 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.53.4 individually for module query 'get_device_info' after first update: ('Unable to query the device: 192.168.53.4: ', TimeoutError())
2025-03-07 23:01:01.607 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.53.4 data: Unable to communicate with the device update: get_device_info not found in {'get_device_time': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_auto_off_config': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_device_info': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_device_usage': {'time_usage': {'today': 421, 'past7': 421, 'past30': 16185}, 'power_usage': {'today': 12, 'past7': 12, 'past30': 24639}, 'saved_power': {'today': 409, 'past7': 409, 'past30': 0}}, 'get_energy_usage': {'today_runtime': 421, 'month_runtime': 421, 'today_energy': 12, 'month_energy': 12, 'local_time': '2025-03-07 23:01:01', 'electricity_charge': [4115, 4288, 1], 'current_power': 848}, 'get_current_power': {'current_power': 0}, 'get_emeter_data': {'current_ma': 6, 'voltage_mv': 246223, 'power_mw': 848, 'energy_wh': 12}, 'get_emeter_vgain_igain': {'vgain': 126211, 'igain': 11454}, 'get_protection_power': {'protection_power': 0, 'enabled': False}, 'get_max_power': {'max_power': 3393}} for device 192.168.53.4
2025-03-07 23:39:31.018 ERROR (MainThread) [homeassistant.components.ipp.coordinator] Unexpected error fetching ipp data
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 380, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/ipp/coordinator.py", line 56, in _async_update_data
    return await self.ipp.printer()
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pyipp/ipp.py", line 224, in printer
    response_data = await self.execute(
                    ^^^^^^^^^^^^^^^^^^^
    ...<6 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/pyipp/ipp.py", line 193, in execute
    response = await self._request(data=message)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pyipp/ipp.py", line 121, in _request
    response = await self.session.request(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 512, in _request
    raise RuntimeError("Session is closed")
RuntimeError: Session is closed
2025-03-07 23:39:32.062 ERROR (MainThread) [homeassistant.components.nanoleaf.coordinator] Unexpected error fetching Nanoleaf data
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 380, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/nanoleaf/coordinator.py", line 27, in _async_update_data
    await self.nanoleaf.get_info()
  File "/usr/local/lib/python3.13/site-packages/aionanoleaf/nanoleaf.py", line 284, in get_info
    resp = await self._request("get", "")
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aionanoleaf/nanoleaf.py", line 247, in _request
    raise err
  File "/usr/local/lib/python3.13/site-packages/aionanoleaf/nanoleaf.py", line 231, in _request
    resp = await self._session.request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        method, url, data=json_data, timeout=self._REQUEST_TIMEOUT
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 512, in _request
    raise RuntimeError("Session is closed")
RuntimeError: Session is closed
2025-03-07 23:39:34.977 WARNING (MainThread) [homeassistant.runner] Task could not be canceled and was still running after shutdown: <Task cancelling name='Task-654' coro=<FcmPushClient._listen() running at /usr/local/lib/python3.13/site-packages/firebase_messaging/fcmpushclient.py:722> wait_for=<Future pending cb=[Task.task_wakeup()]>>
2025-03-07 23:39:35.099 WARNING (Thread-192 (_do_shutdown)) [homeassistant.util.executor] Thread[SyncWorker_26] is still running at shutdown: File "/usr/local/lib/python3.13/threading.py", line 1012, in _bootstrap
    self._bootstrap_inner()
  File "/usr/local/lib/python3.13/threading.py", line 1041, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.13/threading.py", line 992, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 90, in _worker
    work_item = work_queue.get(block=True)
2025-03-07 23:39:35.072 ERROR (MainThread) [homeassistant.components.spotify.coordinator] Unexpected error fetching spotify data
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 380, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/spotify/coordinator.py", line 81, in _async_update_data
    current = await self.client.get_playback()
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/spotifyaio/spotify.py", line 326, in get_playback
    response = await self._get(
               ^^^^^^^^^^^^^^^^
        "v1/me/player", params={"additional_types": "track,episode"}
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/spotifyaio/spotify.py", line 147, in _get
    return await self._request(METH_GET, uri, params=params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/spotifyaio/spotify.py", line 119, in _request
    response = await self.session.request(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<5 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 512, in _request
    raise RuntimeError("Session is closed")
RuntimeError: Session is closed

System information

System Information

version core-2025.2.5
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.1
os_name Linux
os_version 6.6.73-haos
arch x86_64
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 1574
Downloaded Repositories 8
Home Assistant Cloud
logged_in true
subscription_expiration 9 December 2025 at 00:00
relayer_connected true
relayer_region eu-central-1
remote_enabled true
remote_connected true
alexa_enabled true
google_enabled false
cloud_ice_servers_enabled true
remote_server eu-central-1-18.ui.nabu.casa
certificate_status ready
instance_id 48d604ec0a7946b3a7fb9b5b35413f34
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 14.2
update_channel stable
supervisor_version supervisor-2025.03.2
agent_version 1.6.0
docker_version 27.2.0
disk_total 129.2 GB
disk_used 17.0 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization vmware
board ova
supervisor_api ok
version_api ok
installed_addons Terminal & SSH (9.16.0), Node-RED (19.0.2), Studio Code Server (5.18.3), ESPHome Device Builder (2025.2.2), Let's Encrypt (5.4.3), Get HACS (1.3.1), Mosquitto broker (6.5.0), Tesla HTTP Proxy (2.2.8)
Dashboards
dashboards 19
resources 2
views 17
mode storage
Miele
component_version 2025.1.1
reach_miele_cloud failed to load: timeout
Network Configuration
adapters lo (disabled), enp2s1 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth39ecce2 (disabled), veth17be46d (disabled), veth66d4cae (disabled), vethca201f5 (disabled), veth92b202c (disabled), veth2f914dd (disabled), veth11fa55b (disabled), vethf7eefe5 (disabled), veth5a07423 (disabled)
ipv4_addresses lo (127.0.0.1/8), enp2s1 (192.168.51.201/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth39ecce2 (), veth17be46d (), veth66d4cae (), vethca201f5 (), veth92b202c (), veth2f914dd (), veth11fa55b (), vethf7eefe5 (), veth5a07423 ()
ipv6_addresses lo (::1/128), enp2s1 (fe80::2999:57b1:dcff:c69a/64), docker0 (fe80::42:d0ff:fe75:ee81/64), hassio (fe80::42:11ff:fe52:5776/64), veth39ecce2 (fe80::1059:1aff:fea6:e754/64), veth17be46d (fe80::f050:f7ff:fe6b:119f/64), veth66d4cae (fe80::80bc:56ff:fe06:5d96/64), vethca201f5 (fe80::f4db:81ff:fe0c:eeae/64), veth92b202c (fe80::e88b:d8ff:fe08:d340/64), veth2f914dd (fe80::1ce8:d6ff:fe11:decb/64), veth11fa55b (fe80::b8ba:ff:fea4:3765/64), vethf7eefe5 (fe80::4c4a:fbff:fee2:cf3c/64), veth5a07423 (fe80::84ce:a4ff:fe48:16c5/64)
announce_addresses 192.168.51.201, fe80::2999:57b1:dcff:c69a
Recorder
oldest_recorder_run 9 February 2025 at 04:12
current_recorder_run 7 March 2025 at 23:39
estimated_db_size 3040.06 MiB
database_engine sqlite
database_version 3.47.1
Spotify
api_endpoint_reachable ok

Supervisor diagnostics

No response

Additional information

No response

@rwatson2 rwatson2 added the bug label Mar 8, 2025
@tomatenkopp
Copy link

tomatenkopp commented Mar 9, 2025

same here, without any hint for the reason
even after clean Power off and on, still no update
running on a Raspi 4/8GB/SSD

home-assistant-rollback.log

2025-03-09 09:48:44.405 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration candy 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-03-09 09:48:44.408 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tigo 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-03-09 09:48:44.410 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration local_luftdaten 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-03-09 09:48:44.411 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration rpi_gpio 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-03-09 09:48:44.414 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration gardena_smart_system 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-03-09 09:48:44.416 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration browser_mod 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-03-09 09:48:44.418 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration thermal_comfort 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-03-09 09:48:44.420 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration robonect 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-03-09 09:48:44.422 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman 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-03-09 09:48:44.425 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs 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-03-09 09:48:48.320 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2025-03-09 09:48:48.435 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=981 from 2025-03-09 08:41:27.850975)
2025-03-09 09:48:58.698 WARNING (MainThread) [homeassistant.components.onvif] The date/time on Pool (UTC) is '2025-03-09 08:49:07+00:00', which is different from the system '2025-03-09 08:48:58.322901+00:00', this could lead to authentication issues
2025-03-09 09:48:58.705 WARNING (MainThread) [homeassistant.components.onvif] The date/time on Webcam Keller (UTC) is '2025-03-09 08:49:08+00:00', which is different from the system '2025-03-09 08:48:58.312191+00:00', this could lead to authentication issues
2025-03-09 09:49:02.068 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'browser_mod' accessed lovelace_data['resources'] instead of lovelace_data.resources at custom_components/browser_mod/mod_view.py, line 59: resources = hass.data["lovelace"]["resources"]. This will stop working in Home Assistant 2026.2, please report it to the author of the 'browser_mod' custom integration
2025-03-09 09:49:04.455 WARNING (MainThread) [homematicip.base.enums] 'HEAT_DEMAND_RULE_WITH_LEAD_ROOM' isn't a valid option for class 'GroupType'
2025-03-09 09:49:04.455 WARNING (MainThread) [homematicip.home] There is no class for group 'HEAT_DEMAND_RULE_WITH_LEAD_ROOM' yet
2025-03-09 09:49:04.457 WARNING (MainThread) [homematicip.base.enums] 'HEAT_DEMAND_RULE_WITH_LEAD_ROOM' isn't a valid option for class 'GroupType'
2025-03-09 09:49:04.457 WARNING (MainThread) [homematicip.home] There is no class for group 'HEAT_DEMAND_RULE_WITH_LEAD_ROOM' yet
2025-03-09 09:49:04.613 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_default_certs with args (<ssl.SSLContext object at 0x7f50f15a30>, <Purpose.SERVER_AUTH: _ASN1Object(nid=129, shortname='serverAuth', longname='TLS Web Server Authentication', oid='1.3.6.1.5.5.7.3.1')>) inside the event loop by integration 'homematicip_cloud' at homeassistant/components/homematicip_cloud/hap.py, line 191: hmip_events = await self.home.enable_events() (offender: /usr/local/lib/python3.13/ssl.py, line 722: context.load_default_certs(purpose)), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+homematicip_cloud%22
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_default_certs
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 227, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 213, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.13/asyncio/base_events.py", line 707, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.13/asyncio/base_events.py", line 678, in run_forever
self._run_once()
File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2033, in _run_once
handle._run()
File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/components/homematicip_cloud/hap.py", line 191, in async_connect
hmip_events = await self.home.enable_events()

2025-03-09 09:49:12.512 WARNING (MainThread) [homeassistant.setup] Setup of homematic is taking over 10 seconds.
2025-03-09 09:49:17.824 WARNING (MainThread) [homeassistant.helpers.entity] Entity homematic.ccu (<class 'homeassistant.components.homematic.entity.HMHub'>) does not have a platform, this may be caused by adding it manually instead of with an EntityComponent helper, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue
2025-03-09 09:49:17.901 ERROR (MainThread) [homeassistant.components.automation] Automation with alias 'Briefkasten prüfen' failed to setup triggers and has been disabled: Unknown device 'da06ba1dd8d44953402e913f13d8cd9f'
2025-03-09 09:49:17.903 ERROR (MainThread) [homeassistant.components.automation] Automation with alias 'Briefkasten ruht' failed to setup triggers and has been disabled: Unknown device 'da06ba1dd8d44953402e913f13d8cd9f'
2025-03-09 09:49:27.889 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform homematic is taking over 10 seconds.
2025-03-09 09:49:27.995 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform homematic is taking over 10 seconds.
2025-03-09 09:49:51.742 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('homematic', '546817506176'): 148.406798212, ('homematic', '546821694848'): 148.406988864}
2025-03-09 09:49:56.921 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'Rolladen ECO aufwärmen' trigger: In 'numeric_state' condition: entity sensor.rolladen_licht_current_illumination state 'False' cannot be processed as a number
2025-03-09 09:49:56.922 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'Rolladen ECO Kälteschutz' trigger: In 'numeric_state' condition: entity sensor.rolladen_licht_current_illumination state 'False' cannot be processed as a number
2025-03-09 09:49:57.049 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: list object has no element 1 when rendering '{{
timezone.split('(')[1]|replace(')', '')
if timezone.split('(') | count > 0
else timezone
}}'
2025-03-09 09:56:02.544 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error in 'Rolladen ECO aufwärmen' trigger: In 'numeric_state' condition: entity sensor.rolladen_licht_current_illumination state 'False' cannot be processed as a number
2025-03-09 09:56:02.544 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error in 'Rolladen ECO Kälteschutz' trigger: In 'numeric_state' condition: entity sensor.rolladen_licht_current_illumination state 'False' cannot be processed as a number
2025-03-09 10:00:08.384 WARNING (MainThread) [homeassistant.components.utility_meter.sensor] Strom L3 Energy Counter received an invalid new state from sensor.strom_l3_energie : unknown
2025-03-09 10:00:08.384 WARNING (MainThread) [homeassistant.components.utility_meter.sensor] Strom L2 Energycounter received an invalid new state from sensor.strom_l2_energie : unknown
2025-03-09 10:00:08.385 WARNING (MainThread) [homeassistant.components.utility_meter.sensor] Strom L1 Energy Counter received an invalid new state from sensor.strom_l1_energie : unknown
2025-03-09 10:00:08.393 ERROR (MainThread) [homeassistant.components.homematicip_cloud.hap] Error connecting to HomematicIP with HAP 3014F711A00003D70994CDEE. Retrying in 1 seconds

@mdegat01
Copy link
Contributor

mdegat01 commented Mar 10, 2025

I'm not seeing a supervisor crash anywhere in either logs. When supervisor is asked to update core it waits and watches to make sure it comes back online after the update. If it does not then it rolls back the update.

Both of you appear to be showing a core crash on update. This is then followed by a rollback to keep your systems in the functional form they were in. All this seems like correct behavior from Supervisor's perspective. Unless one of you has logs from Supervisor showing a crash or other issue along the way in Supervisor?

Assuming this is the case I'd suggest following up on home-assistant/core#140098 . As it seems like both of you are having an issue with updating to the latest version of core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants