can't reboot from UI

[goldbe4804]

The problem

since my update to 2023.6 when i try to restart from the UI nothing happens

What version of Home Assistant Core has the issue?

2023.6

What was the last working version of Home Assistant Core?

2023.5.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[frenck]

Anything in the logs?

[goldbe4804]

sorry forgot about that 2023-06-08 13:07:35.809 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall homeassistant.restart (c:01H2DZMC2MM3GJ8EYA15Z73G4V)>

[frenck]

What does the "Check configuration" report in the sidebar menu -> Developer tools -> YAML tab -> Select the Check Configuration button ?

[goldbe4804]

... just spinning

[frenck]

😕 There must be something in some log?

Supervisor logs maybe?

[goldbe4804]

i dont see anything ?? here they are

supervisor_2023-06-08T17-24-03.250Z.log](https://github.com/home-assistant/core/files/11691318/supervisor_2023-06-08T17-24-03.250Z.log)

[1001geri1]

I have the same issue here. After the 2023.6 update I can't restart my homeassistant. I am using the Home Assistant OS as a VM.

Error executing service: <ServiceCall homeassistant.restart (c:01H2E0TEG2NZTF20XMNAZJ08P1)> Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/core.py", line 1928, in catch_exceptions await coro_or_task File "/usr/src/homeassistant/homeassistant/core.py", line 1950, in _execute_service await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)( File "/usr/src/homeassistant/homeassistant/components/hassio/init.py", line 577, in async_handle_core_service raise HomeAssistantError( homeassistant.exceptions.HomeAssistantError: The system cannot restart because the configuration is not valid: Platform error device_tracker.bluetooth_tracker - Requirements for bluetooth_tracker not found: ['pybluez==0.22'].

[goldbe4804]

2023-06-08 13:07:35.809 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall homeassistant.restart (c:01H2DZMC2MM3GJ8EYA15Z73G4V)> Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/core.py", line 1928, in catch_exceptions await coro_or_task File "/usr/src/homeassistant/homeassistant/core.py", line 1950, in _execute_service await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)( File "/usr/src/homeassistant/homeassistant/components/hassio/init.py", line 563, in async_handle_core_service errors = await conf_util.async_check_ha_config_file(hass)

[PimDoos]

Same issue here. Check configuration keeps loading for half a minute, then I get an error about pybluez. Only way to reboot HA seems to be to restart HAOS. This log message seems related:

Logger: homeassistant.util.package
Source: util/package.py:107
First occurred: 10:03:17 (4 occurrences)
Last logged: 20:15:53

Unable to install package pybluez==0.22: error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [19 lines of output] running bdist_wheel running build running build_py creating build creating build/lib.linux-x86_64-cpython-311 creating build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/__init__.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/widcomm.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/osx.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/msbt.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/btcommon.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/bluez.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/ble.py -> build/lib.linux-x86_64-cpython-311/bluetooth running build_ext building 'bluetooth._bluetooth' extension creating build/temp.linux-x86_64-cpython-311 creating build/temp.linux-x86_64-cpython-311/bluez gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fno-semantic-interposition -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free -DTHREAD_STACK_SIZE=0x100000 -fPIC -I./port3 -I/usr/local/include/python3.11 -c bluez/btmodule.c -o build/temp.linux-x86_64-cpython-311/bluez/btmodule.o error: command 'gcc' failed: No such file or directory [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for pybluez ERROR: Could not build wheels for pybluez, which is required to install pyproject.toml-based projects

My deployment information: Home Assistant 2023.6.0 Supervisor 2023.06.1 Operating System 10.2 Frontend 20230607.0 - latest

Running Home Assistant OS on Proxmox VE 7.4-3

[Atari59]

I have the same issue. A workaround is to comment out in configuration.yaml - platform: bluetooth_tracker. After I did this I could check configuration and restart again

[goldbe4804]

funny you say that,- today my ck config says something about BT tracking, so i comment it out and then the config. ck worked and said all good and restarted - so same here-

A basic validation of the configuration is automatically done before restarting. The basic validation ensures the YAML configuration doesn't have errors which will prevent Home Assistant or any integration from starting. It's also possible to only do the basic validation check without restarting. Configuration invalid! Platform error device_tracker.bluetooth_tracker - Requirements for bluetooth_tracker not found: ['pybluez==0.22'].

[frenck]

Is the above mentioned by other the same issue for you @goldbe4804 ?

../Frenck

[goldbe4804]

so i have 2 instances both wont't restart 1 my main setup yes comment out BT Tracking seem to let it restart but on my tester setup it does not seem to matter still cant restart -- i will reboot that once more and see what happens ps hope your feeling better

[OldShaterhan]

Same issue here: https://github.com/home-assistant/core/issues/94311 and here https://github.com/home-assistant/core/issues/94380 .

For me the same issue:

Platform error device_tracker.bluetooth_tracker - Integration 'bluetooth_tracker' not found.

on config check.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[PimDoos]

Issue is still present in 2023.6.3

[Bung28]

Issue still present Supervisor 2023.07.1 Operating System 10.3 Frontend 20230705.1

[joostlek]

Do you see anything in the logs?

[Bung28]

Actually - I did. These two sections needed to be commented out:

tts: -platform: google_translate service_name: google_say cache: false language: fi base_url: xxxxxxxxxxxxx

spotify: client_id: xxxxxxx client_secret: xxxxxxxx

Everything seems to be working now.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[goldbe4804]

ok but Issue still present i have to reboot will not restart

[joostlek]

Did you see anything in the logs?

[PimDoos]

When clicking restart with - platform: bluetooth_tracker in configuration.yaml, I get this error:

Platform error device_tracker.bluetooth_tracker - Requirements for bluetooth_tracker not found: ['PyBluez==0.22'].

And in the logs:

Logger: homeassistant.util.package
Source: util/package.py:107
First occurred: 20:19:38 (1 occurrences)
Last logged: 20:19:38

Unable to install package PyBluez==0.22: error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [19 lines of output] running bdist_wheel running build running build_py creating build creating build/lib.linux-x86_64-cpython-311 creating build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/__init__.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/widcomm.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/osx.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/msbt.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/btcommon.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/bluez.py -> build/lib.linux-x86_64-cpython-311/bluetooth copying bluetooth/ble.py -> build/lib.linux-x86_64-cpython-311/bluetooth running build_ext building 'bluetooth._bluetooth' extension creating build/temp.linux-x86_64-cpython-311 creating build/temp.linux-x86_64-cpython-311/bluez gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fno-semantic-interposition -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free -DTHREAD_STACK_SIZE=0x100000 -fPIC -I./port3 -I/usr/local/include/python3.11 -c bluez/btmodule.c -o build/temp.linux-x86_64-cpython-311/bluez/btmodule.o error: command 'gcc' failed: No such file or directory [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for PyBluez ERROR: Could not build wheels for PyBluez, which is required to install pyproject.toml-based projects [notice] A new release of pip is available: 23.1.2 -> 23.2.1 [notice] To update, run: pip install --upgrade pip

My best guess is that the configuration check tries to install dependencies for bluetooth_tracker, which fails due to the issue described in #94189. I do question whether it should be expected behaviour to fail the config check in this way. bluetooth_tracker should probably be removed if it is no longer maintained.

The solution for now is to comment out the bluetooth_tracker entries in configuration.yaml.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[eZazDuTuitisme]

Hi,

Same problem here, for same reason :( I dont want to comment bluetooth_tracker since I use to activate my home alarm..

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.