Anyone else having problems with Philip HUE after updating to 2022.8.2?
I updated and my HUE lights were grayed out, not all of them but some, And when swiching them on with the HUE app they would return but disappear again after a short while.
Reverted back to 2022.8.1 and no issues anymore.
I’d like to know this, too! I’d like to play voice notifications and maybe stream the odd bit of music over a Bluetooth speaker, but I always gave up when I encountered horribly complicated tutorials all of which had a ton of people saying that it didn’t work for them.
I was stunned at how much simpler setting up a Miflora sensor became with this release. I’m hoping the same has/will happen(ed) for Bluetooth speakers, at last!
1 Like
I didn’t interpret it that way.
1 Like
Please add Bluetooth Presence Detection back. I’m still on 2022.06 because my setup requires that function. Thank you.
need to install usbip in the docker and open ports I guess
2022.8.1 (and 2022.8) doesn’t update my Xiaomi Mijia lywsd03mmc Bluetooth Temperature as often as it should.
With HACS, the update is done every 10 minutes (IF there is a change in the Xiaomi). With 2022.8 + BLE and without HACS-BLE add-on, the update is done randomly (from 10min to 1 hour, even if there are many change in the Xiaomi) …
Will try to go back with HACS add-on 
I just upgraded from 2022.7.x to 2022.8.2, and not seeing any issues with Philips HUE thus far.
2022.8.0 has been very unstable/buggy for me. HA was constantly unresponsive, falling off the network, automations not working etc. Emporia Vue custom integration was also broken.
I even tried to update to 8.2 multiple times, but it just would not happen.
Just rolled back to 2022.7.4 and everything is back to normal.
Hello, I am adding an Ip Camera via ONVIF integration. After adding the camera, I get an error, what could be the problem?
I am very positive, I have updated to 2022.8.2 two days ago. Last night, a new update of 2022.8.3 pop up. I even made a full backup naming it 2022.8.2 so I can update to 2022.8.3 the next day. It’s the next day and the new update is 2022.8.2.
Heck, I even saw the breaking changed dated for Aug 8 below yesterday. It’s not there any longer.
I have the same error, nothing so far works
Since Repairs is build in and warned me that Spotify should not be in YAML so I removed the lines. When I try to add the Spotify integration I get the warning: INVALID_CLIENT: Failed to get client
Steps I tried:
- remove app from spotify dev and re-create it
- remove home assistant from apps in your normal account.
- looked for .spotify-token-cache and media_player.py but could not find them.
- tried https:/ /my.home-assistant.io/redirect/oauth as well as https:/ /192.168.0.2:8123/auth/external/callback in the spotify dev app. (I broke the link with a space between the // to keep the link visible)
nothing seem to work and all result in the same error: INVALID_CLIENT: Failed to get client.
I have no clue where to look anymore. I run Home Assistant supervised through Docker on a Debian bullseye machine.
can anyone help?
found the solution:"Spotify configuration error (INVALID_CLIENT: Failed to get client) - #19 by Mijn.Handen
Other than this… keep up the great work, stuff is getting better and better.
Hi,
The folder sensor does not work anymore in HA 2022.8 … Folder - Home Assistant
- The configuration files
#-----------------------------------------
- platform: folder
folder: /config/media/camera
#------------------------------------
#----------------------------------
homeassistant:
media_dirs:
media: /config/media
allowlist_external_dirs:
- /config
- /config/media/camera
- /config/media/backup
#--------------------------
- the error log
Logger: homeassistant.components.websocket_api.http.connection
Source: components/hassio/__init__.py:705
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 12:33:12 PM (6 occurrences)
Last logged: 2:24:29 PM
[140284496455872] The system cannot restart because the configuration is not valid: Not a directory @ data['allowlist_external_dirs'][1] Invalid config for [sensor.folder]: not a directory for dictionary value @ data['folder']. Got '/config/media/camera'. (See ?, line ?).
[140284513768576] The system cannot restart because the configuration is not valid: Not a directory @ data['allowlist_external_dirs'][1] Invalid config for [sensor.folder]: not a directory for dictionary value @ data['folder']. Got '/config/media/camera'. (See ?, line ?).
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 199, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1713, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1750, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 705, in async_handle_core_service
raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: The system cannot restart because the configuration is not valid: Not a directory @ data['allowlist_external_dirs'][1]
Invalid config for [sensor.folder]: not a directory for dictionary value @ data['folder']. Got '/config/media/camera'. (See ?, line ?).
Is it a known issue ?
Thank you
EDIT : I responded to @beaulebens by mistake
Never mind, I tried the upgrade again, and everythings OK now… 
2022.8.3? Did I miss something?
I think 8.3 was merged with 8.2 or I was in a dream that lasted 24 hours.
2022.8.3 core isn’t out yet. That was likely a supervisor release
1 Like
Had the bluetooth_le integration working perfectly fine, since the update to this release, not getting a single scan happening.
OS is showing no issues and is able to scan quite happily.
Thoughts anyone?
I am also noticing the same thing. My Supervisor says there are no updates beyond 2022.7.0. Here is the output from CLI…
[core-ssh ~]$ ha supervisor update
Processing... Done.
Error: No supervisor update available - 2022.07.0
Have you figured anything out?