X86 Problems

PapaLanc · April 13, 2025, 10:28pm

I moved from synolgy VM to an HP thin client t630 8gb ram 128gb ssd.

It seems like when I make it “think/do stuff” it reboots. I mean if I just look at overview pages sensors it is fine. But if I update something in ESPHome it reboots. And when it starts this it takes forever to settle back down…
I get this if I select to view addons

my uptime, you can see once it starts it is terrible.

I get connection lost reconnecting. Observer always says healthy. What is funny ha ha, is I have an addon, birdpi-net running on port 8082 and while HA seems to be rebooting I can still access the site on 8082?

I have disabling Bird-Pi and it does not seem to help.

I bought another T630 and put my ssd in there same issues.

Have ordered another ssd to try that.

Any ideas?

Thanks,
Gramps

nickrout · April 13, 2025, 11:18pm

Birdnet continues to run because it is a separate docker container. Restarting ha doesn’t restart add-ons.

Try actually rebooting the machine instead of just restarting ha. If the problem persists, show us your logs.

stevemann · April 14, 2025, 3:17am

Reboot or restart?
How have you installed Home Assistant?

PapaLanc · April 14, 2025, 2:05pm

I do reboots, but what is odd, when it is acting up the dropdown sometimes only says safemode.
Install using method 1

You mean logs from settings>system>logs?

nickrout · April 14, 2025, 8:02pm

Yes or simply look at the log file in config/home-assistant.log*

PapaLanc · April 14, 2025, 9:31pm

here are the log files (too big to post)

📜 Click to expand log

2025-04-14 17:00:58.778 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration webrtc 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-04-14 17:00:58.781 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration anniversaries 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-04-14 17:00:58.783 ERROR (SyncWorker_0) [homeassistant.loader] Error parsing manifest.json file at /config/custom_components/samsungtv_custom_old/manifest.json: unexpected character: line 10 column 3 (char 262)
2025-04-14 17:00:58.784 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration auto_backup 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-04-14 17:00:58.786 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration wyzeapi 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-04-14 17:00:58.788 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration samsungtv_tizen 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-04-14 17:00:58.791 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya 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-04-14 17:00:58.793 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration anniversary 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-04-14 17:00:58.795 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-04-14 17:00:58.796 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nodered 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-04-14 17:00:58.798 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-04-14 17:00:58.801 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration whatsigram_messenger 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-04-14 17:00:58.804 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sengledapi 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-04-14 17:00:58.805 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration openhasp 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-04-14 17:01:06.660 ERROR (MainThread) [homeassistant.components.sensor] Platform energy does not generate unique IDs. ID 05d33f5ef559bd56cf8a781c59847a51_grid_cost is already used by sensor.power_shop_123_1d_cost - ignoring sensor.power_shop_123_1d_cost
2025-04-14 17:01:08.578 WARNING (ImportExecutor_0) [homeassistant.components.media_player] DEVICE_CLASS_TV was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerDeviceClass.TV instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.583 WARNING (ImportExecutor_0) [homeassistant.components.media_player] DEVICE_CLASS_TV was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerDeviceClass.TV instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.588 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] MEDIA_TYPE_CHANNEL was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaType.CHANNEL instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.592 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_NEXT_TRACK was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.NEXT_TRACK instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.597 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_PAUSE was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.PAUSE instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.602 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_PLAY was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.PLAY instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.607 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_PLAY_MEDIA was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.PLAY_MEDIA instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.611 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_PREVIOUS_TRACK was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.PREVIOUS_TRACK instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.616 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_SELECT_SOURCE was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.SELECT_SOURCE instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.622 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_TURN_OFF was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.TURN_OFF instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.627 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_TURN_ON was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.TURN_ON instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.633 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_VOLUME_MUTE was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.VOLUME_MUTE instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.640 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_VOLUME_STEP was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.VOLUME_STEP instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.644 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] SUPPORT_VOLUME_SET was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaPlayerEntityFeature.VOLUME_SET instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.652 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] MEDIA_TYPE_APP was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaType.APP instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.656 WARNING (ImportExecutor_0) [homeassistant.components.media_player.const] MEDIA_TYPE_URL was used from samsungtv_tizen, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaType.URL instead, please report it to the author of the 'samsungtv_tizen' custom integration
2025-04-14 17:01:08.688 WARNING (MainThread) [py.warnings] /config/custom_components/samsungtv_tizen/media_player.py:703: RuntimeWarning: coroutine 'SamsungTVDevice._gen_installed_app_list' was never awaited
  self._gen_installed_app_list()

2025-04-14 17:01:11.948 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'webrtc' accessed lovelace_data['resources'] instead of lovelace_data.resources at custom_components/webrtc/utils.py, line 129: resources: ResourceStorageCollection = hass.data["lovelace"]["resources"]. This will stop working in Home Assistant 2026.2, please create a bug report at https://github.com/AlexxIT/WebRTC/issues
2025-04-14 17:01:12.664 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_61201F3A-if00-port0', 's0_legacy_key': 'E0A2D013D3D95C0DFC2B42C5E50650A4', 's2_access_control_key': 'A579D5283916F3715B87D684BA91FAE8', 's2_authenticated_key': 'EB8515D4264B1E05A41B0161CB4C926A', 's2_unauthenticated_key': 'B7B4B0600A51CFD41D926C3F6D8C2BA0', 'lr_s2_access_control_key': '620ECE416CA651BB4DE9D0386373826A', 'lr_s2_authenticated_key': '9421F1B7AEAC2EE77377EDC8C43D771A'}
2025-04-14 17:01:18.908 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_default_certs with args (<ssl.SSLContext object at 0x7fe48a9d05f0>, <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 custom integration 'sengledapi' at custom_components/sengledapi/sengledapi/sengledapi.py, line 288: SESSION.mqtt_client.tls_set_context() (offender: /usr/local/lib/python3.13/ssl.py, line 722: context.load_default_certs(purpose)), please report it to the author of the 'sengledapi' custom integration
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_default_certs
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 712, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 683, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2040, 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/setup.py", line 171, in async_setup_component
    result = await _async_setup_component(hass, domain, config)
  File "/usr/src/homeassistant/homeassistant/setup.py", line 422, in _async_setup_component
    result = await task
  File "/config/custom_components/sengledapi/__init__.py", line 54, in async_setup
    await sengledapi_account.async_init()
  File "/config/custom_components/sengledapi/sengledapi/sengledapi.py", line 53, in async_init
    self._access_token = await self.async_login(
  File "/config/custom_components/sengledapi/sengledapi/sengledapi.py", line 91, in async_login
    self.initialize_mqtt()
  File "/config/custom_components/sengledapi/sengledapi/sengledapi.py", line 288, in initialize_mqtt
    SESSION.mqtt_client.tls_set_context()

2025-04-14 17:01:18.918 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to set_default_verify_paths with args (<ssl.SSLContext object at 0x7fe48a9d05f0>,) inside the event loop by custom integration 'sengledapi' at custom_components/sengledapi/sengledapi/sengledapi.py, line 288: SESSION.mqtt_client.tls_set_context() (offender: /usr/local/lib/python3.13/ssl.py, line 534: self.set_default_verify_paths()), please report it to the author of the 'sengledapi' custom integration
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#set_default_verify_paths
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 712, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 683, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2040, 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/setup.py", line 171, in async_setup_component
    result = await _async_setup_component(hass, domain, config)
  File "/usr/src/homeassistant/homeassistant/setup.py", line 422, in _async_setup_component
    result = await task
  File "/config/custom_components/sengledapi/__init__.py", line 54, in async_setup
    await sengledapi_account.async_init()
  File "/config/custom_components/sengledapi/sengledapi/sengledapi.py", line 53, in async_init
    self._access_token = await self.async_login(
  File "/config/custom_components/sengledapi/sengledapi/sengledapi.py", line 91, in async_login
    self.initialize_mqtt()
  File "/config/custom_components/sengledapi/sengledapi/sengledapi.py", line 288, in initialize_mqtt
    SESSION.mqtt_client.tls_set_context()

2025-04-14 17:01:22.979 WARNING (MainThread) [homeassistant.config_entries] Config entry '[email protected]' for tuya integration could not authenticate: Authentication failed. Please re-authenticate
2025-04-14 17:01:24.042 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls `async_add_job`, which should be reviewed against https://developers.home-assistant.io/blog/2024/03/13/deprecate_add_run_job for replacement options. This will stop working in Home Assistant 2025.4, please report this issue
Stack (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 712, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 683, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2040, 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/util/async_.py", line 68, in run_callback
    future.set_result(callback(*args))
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 243, in _report_usage
    _report_usage_no_integration(what, core_behavior, breaks_in_ha_version, err)
  File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 380, in _report_usage_no_integration
    _LOGGER.warning(msg, stack_info=True)
2025-04-14 17:01:24.045 WARNING (MainThread) [py.warnings] /config/custom_components/samsungtv_tizen/media_player.py:703: RuntimeWarning: coroutine 'SamsungTVDevice._gen_installed_app_list' was never awaited
  self._gen_installed_app_list()

2025-04-14 17:01:27.811 WARNING (ImportExecutor_0) [homeassistant.components.light] ATTR_COLOR_TEMP was used from sengledapi, this is a deprecated constant which will be removed in HA Core 2026.1. Use kelvin equivalent (ATTR_COLOR_TEMP_KELVIN) instead, please report it to the author of the 'sengledapi' custom integration
2025-04-14 17:01:27.824 WARNING (ImportExecutor_0) [homeassistant.components.light] ATTR_COLOR_TEMP was used from sengledapi, this is a deprecated constant which will be removed in HA Core 2026.1. Use kelvin equivalent (ATTR_COLOR_TEMP_KELVIN) instead, please report it to the author of the 'sengledapi' custom integration
2025-04-14 17:01:27.833 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.sengledapi.light.SengledBulb'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.BRIGHTNESS: 'brightness'>, <ColorMode.HS: 'hs'>}, this will stop working in Home Assistant Core 2025.3, please report it to the author of the 'sengledapi' custom integration
2025-04-14 17:01:27.834 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'sengledapi' is using mireds for warmest light color temperature, when it should be adjusted to use the kelvin attribute `_attr_min_color_temp_kelvin` or override the kelvin property `min_color_temp_kelvin`, possibly with default DEFAULT_MIN_KELVIN (see https://github.com/home-assistant/core/pull/79591). This will stop working in Home Assistant 2026.1, please report it to the author of the 'sengledapi' custom integration
2025-04-14 17:01:27.834 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'sengledapi' is using mireds for coldest light color temperature, when it should be adjusted to use the kelvin attribute `_attr_max_color_temp_kelvin` or override the kelvin property `max_color_temp_kelvin`, possibly with default DEFAULT_MAX_KELVIN (see https://github.com/home-assistant/core/pull/79591). This will stop working in Home Assistant 2026.1, please report it to the author of the 'sengledapi' custom integration
2025-04-14 17:01:27.835 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.sengledapi.light.SengledBulb'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.BRIGHTNESS: 'brightness'>, <ColorMode.HS: 'hs'>}, this will stop working in Home Assistant Core 2025.3, please report it to the author of the 'sengledapi' custom integration
2025-04-14 17:01:28.559 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.water_heater_day (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using state class 'total_increasing' which is impossible considering device class ('current') it is using; expected None or one of 'measurement'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22
2025-04-14 17:01:28.559 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.water_heater_day (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using native unit of measurement 'watts' which is not a valid unit for the device class ('current') it is using; expected one of ['mA', 'A']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22
2025-04-14 17:01:28.562 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.water_heater_month (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using state class 'total_increasing' which is impossible considering device class ('current') it is using; expected None or one of 'measurement'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22
2025-04-14 17:01:28.562 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.water_heater_month (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using native unit of measurement 'watts' which is not a valid unit for the device class ('current') it is using; expected one of ['mA', 'A']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22
2025-04-14 17:01:28.566 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.water_heater_year (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using state class 'total_increasing' which is impossible considering device class ('current') it is using; expected None or one of 'measurement'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22
2025-04-14 17:01:28.566 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.water_heater_year (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using native unit of measurement 'watts' which is not a valid unit for the device class ('current') it is using; expected one of ['mA', 'A']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22
2025-04-14 17:01:29.115 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.sengledapi.light.SengledBulb'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.BRIGHTNESS: 'brightness'>, <ColorMode.HS: 'hs'>}, this will stop working in Home Assistant Core 2025.3, please report it to the author of the 'sengledapi' custom integration
2025-04-14 17:01:29.236 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.sengledapi.light.SengledBulb'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.BRIGHTNESS: 'brightness'>, <ColorMode.HS: 'hs'>}, this will stop working in Home Assistant Core 2025.3, please report it to the author of the 'sengledapi' custom integration
2025-04-14 17:01:29.256 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.sengledapi.light.SengledBulb'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.BRIGHTNESS: 'brightness'>, <ColorMode.HS: 'hs'>}, this will stop working in Home Assistant Core 2025.3, please report it to the author of the 'sengledapi' custom integration
2025-04-14 17:01:29.620 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-web-c0223c @ 192.168.1.219: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.219', port=6053))]: [Errno 111] Connect call failed ('192.168.1.219', 6053) (SocketAPIError)
2025-04-14 17:01:29.683 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform esphome does not generate unique IDs. ID 4C:75:25:D6:73:A8-binary_sensor-brl already exists - ignoring binary_sensor.brl_2
2025-04-14 17:01:29.683 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform esphome does not generate unique IDs. ID 4C:75:25:D6:73:A8-binary_sensor-rc522_rfid_tag already exists - ignoring binary_sensor.rc522_rfid_tag
2025-04-14 17:01:29.748 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-web-fa9c88 @ 192.168.1.196: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.196', port=6053))]: [Errno 111] Connect call failed ('192.168.1.196', 6053) (SocketAPIError)
2025-04-14 17:01:29.750 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-web-0bdc36 @ 192.168.1.187: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.187', port=6053))]: [Errno 111] Connect call failed ('192.168.1.187', 6053) (SocketAPIError)
2025-04-14 17:01:29.751 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-web-ce50c4 @ 192.168.1.171: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.171', port=6053))]: [Errno 111] Connect call failed ('192.168.1.171', 6053) (SocketAPIError)
2025-04-14 17:01:29.756 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-web-ecaf14 @ 192.168.1.171: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.171', port=6053))]: [Errno 111] Connect call failed ('192.168.1.171', 6053) (SocketAPIError)
2025-04-14 17:01:29.763 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-web-a37f48 @ 192.168.1.219: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.219', port=6053))]: [Errno 111] Connect call failed ('192.168.1.219', 6053) (SocketAPIError)
2025-04-14 17:01:29.780 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for 192.168.1.66: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.66', port=6053))]: [Errno 113] Connect call failed ('192.168.1.66', 6053) (SocketAPIError)
2025-04-14 17:01:29.808 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-web-f846c8 @ 192.168.1.196: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.196', port=6053))]: [Errno 111] Connect call failed ('192.168.1.196', 6053) (SocketAPIError)

PapaLanc · April 14, 2025, 9:53pm

II cannot see any entities

nickrout · April 14, 2025, 9:56pm

Maybe because you are filtering?

PapaLanc · April 14, 2025, 10:11pm

yes now it shows stuff. My Ha is just weird, were did that odd filter come from

mcarty · April 14, 2025, 10:17pm

You have a lot of custom integrations (not official).
Do you need all of them?
You could try to disable some and try to find the culprit.
Have you updated to the latest version of haos and core?

PapaLanc · April 14, 2025, 10:21pm

Everything worked fine in the synolgy vm, my prob is the x86 on the hp t630 Pretty sure everything is latest and greatest

mcarty · April 14, 2025, 10:37pm

Go to System, repairs, three dots, integration startup time

Maybe you can find there wich one is taking more time and causing trouble

PapaLanc · April 14, 2025, 10:52pm

thanks i will disable emporira and see what happens

PapaLanc · April 16, 2025, 8:59pm

upgraded to 15.2 and it seems fine now.

github.com/home-assistant/operating-system

Disable amdgpu SI/CIK support and backport upstream patch to prevent crashes

dev ← amdgpu-backport-graceful-amdgpu-si-cik-ignore-patch

opened 02:55PM - 09 Apr 25 UTC

sairon

+119 -2

As we enabled SI/CIK support to fix crashes on bunch of AMD SoCs in #3957, the a…mdgpu driver still crashes on some hardware. It seems to be some GX-217GA SoCs or even GX-425GA in Fujitsu thin clients (even though the same SoC is fine on T620). To get to the state before update to kernel 6.12, disable amdgpu for these platforms again (as it couldn't work properly there before OS 15.0) and just backport the patch that fixes the crashes during probing when the driver isn't compiled with SI/CIK support. Fixes #4012 ## Summary by CodeRabbit - **Chores** - Removed legacy support for older AMD GPU architectures (Southern Islands and Sea Islands) from the configuration. - **Bug Fixes** - Enhanced error handling to display clear messages when attempting to initialize AMD GPU features that are no longer supported.