It seems like the title of this post should be “2022.8.0 breaks due to custom component”, because your issue isn’t with HA directly, it’s with a custom component which likely wasn’t created by the HA folks. That being said, somewhere around those log entries should give you information about which component is complaining, go check to see if there is an update to it that is required on 2022.8.0 or ask the dev to investigate why it’s breaking your HA in the first place.
I removed the folder custom_components and blueprints temporarily by moving them into a different folder. Now I don’t get any logs (home-assistant.log is empty).
Launchd logs:
2022-08-05 07:49:13.742554 (gui/501/org.homeassistant [46640]) <Notice>: exited due to exit(1)
2022-08-05 07:49:13.742584 (gui/501/org.homeassistant [46640]) <Notice>: service state: exited
2022-08-05 07:49:13.742590 (gui/501/org.homeassistant [46640]) <Notice>: internal event: EXITED, code = 0
2022-08-05 07:49:13.742596 (gui/501 [100005]) <Notice>: service inactive: org.homeassistant
2022-08-05 07:49:13.742604 (gui/501/org.homeassistant [46640]) <Notice>: service state: not running
2022-08-05 07:49:13.742614 (gui/501/org.homeassistant) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
2022-08-05 07:49:13.742635 (gui/501/org.homeassistant) <Notice>: internal event: WILL_SPAWN, code = 0
2022-08-05 07:49:13.742650 (gui/501/org.homeassistant) <Notice>: service state: spawn scheduled
2022-08-05 07:49:13.742654 (gui/501/org.homeassistant) <Notice>: service throttled by 10 seconds
2022-08-05 11:50:27.658 ERROR (MainThread) [root] Uncaught exception
Traceback (most recent call last):
File "/Users/server/Steuerung/homeassistant/bin/hass", line 8, in <module>
sys.exit(main())
File "/Users/server/Steuerung/homeassistant/lib/python3.9/site-packages/homeassistant/__main__.py", line 191, in main
exit_code = runner.run(runtime_conf)
File "/Users/server/Steuerung/homeassistant/lib/python3.9/site-packages/homeassistant/runner.py", line 119, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/opt/homebrew/Cellar/[email protected]/3.9.13_1/Frameworks/Python.framework/Versions/3.9/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
return future.result()
File "/Users/server/Steuerung/homeassistant/lib/python3.9/site-packages/homeassistant/runner.py", line 101, in setup_and_run_hass
hass = await bootstrap.async_setup_hass(runtime_config)
File "/Users/server/Steuerung/homeassistant/lib/python3.9/site-packages/homeassistant/bootstrap.py", line 143, in async_setup_hass
await async_from_config_dict(config_dict, hass) is not None
File "/Users/server/Steuerung/homeassistant/lib/python3.9/site-packages/homeassistant/bootstrap.py", line 256, in async_from_config_dict
await _async_set_up_integrations(hass, config)
File "/Users/server/Steuerung/homeassistant/lib/python3.9/site-packages/homeassistant/bootstrap.py", line 532, in _async_set_up_integrations
recorder.async_initialize_recorder(hass)
File "/Users/server/Steuerung/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/recorder.py", line 22, in async_initialize_recorder
from homeassistant.components.recorder import const, models
File "/Users/server/Steuerung/homeassistant/lib/python3.9/site-packages/homeassistant/components/recorder/__init__.py", line 23, in <module>
from . import statistics, websocket_api
File "/Users/server/Steuerung/homeassistant/lib/python3.9/site-packages/homeassistant/components/recorder/statistics.py", line 17, in <module>
from sqlalchemy import bindparam, func, lambda_stmt, select
ModuleNotFoundError: No module named 'sqlalchemy'
After I install sqlalchemy it still crashes.
I can’t really see the cause, because the log is overwritten as soon as HA restarts.
If it’s bailing before any logs appear, it’s very early in the HA startup process.
It’s most likely related to your install process which doesn’t appear to be a supported install method from what I can tell. You’re most likely on your own on this one
I don’t believe you can, you can see if it’s in default config. You could try to put empty py files with a manifest in it replacing the Bluetooth integration.
I understand, but as it looks, you’re the one with the most knowledge on that os/setup… all you can really do is make a debug version and latch on to the process as it starts. Hopefully you can attach before it crashes. The debug integration doesn’t start exactly on startup, it’s close though.
worked for me. My manual development environment (venv) was broken in the same way. Make sure you’re running pip install inside your Python environment.
I would never use a Core install for my production system.
Yea, it sounds like something to do with your recorder/database/SQL. Maybe it wasnt running when you restarted or updated. For whatever reason, my MariaDB add-on did not automatically start as it was supposed to after the last two updates.
