I seem to have lost access to HA from both phone and computer. My installation is on a RPi4 and have both the internal and external links set via duckdns.org. When I try the usual link in my browser I get “Unable to connect to Home Assistant.” and if I click rety I get “403: Forbidden”.
I am able to ssh into HA and have tried restarting HA core and host, unfortunately without effect. I’m tempted to try and revert to 2022.10 but will see if anyone has any ideas I can test. Thanks!
edit: I fixed it by removing ip_bans.yaml. Somehow some IP’s got added during the update?
Core 2022.11.1 broke my people locations. My person.xxx entities were not updating, and were not shown anywhere on the map. Rolling back to yesterday’s backup fixed the issue.
hm… what tracker are you using?
I have three location tracking entities - two times mobile and one other gps tracker - all three are working as expected with this version.
So I don’t expect this to be a general issue
fixed this: we have to re-configure the integration, and can only do that by re-installing, or by manually editing the config_entry. I did the latter and it is fixed. No release issue.
I updated from 2022.11 to 2022.11.1 and my system never came back up afterward. The web UI won’t load. Anyone have tips to troubleshoot? I’m running a NUC with Home Assistant OS.
➜ ~ ha core restart
Processing... Done.
Post "http://supervisor/core/restart": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
➜ ~ ha core stop
Processing... Done.
Error: Unknown error, see supervisor
➜ ~ ha core start
Processing... Done.
Error: Unknown error, see supervisor
➜ ~ ha supervisor logs
[...]
22-11-04 07:47:14 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-04 07:47:44 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-04 07:47:48 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-04 07:47:50 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-04 07:49:32 ERROR (MainThread) [supervisor.auth] None as password is not supported!
22-11-04 07:49:33 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.10/site-packages/sentry_sdk/integrations/aiohttp.py", line 126, in sentry_app_handle
reraise(*_capture_exception(hub))
File "/usr/local/lib/python3.10/site-packages/sentry_sdk/_compat.py", line 56, in reraise
raise value
File "/usr/local/lib/python3.10/site-packages/sentry_sdk/integrations/aiohttp.py", line 116, in sentry_app_handle
response = await old_handle(self, request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 138, in system_validation
return await handler(request)
File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 204, in token_validation
return await handler(request)
File "/usr/src/supervisor/supervisor/api/utils.py", line 60, in wrap_api
answer = await method(api, *args, **kwargs)
File "/usr/src/supervisor/supervisor/api/auth.py", line 64, in auth
if not await self._process_basic(request, addon):
File "/usr/src/supervisor/supervisor/api/auth.py", line 39, in _process_basic
auth = BasicAuth.decode(request.headers[AUTHORIZATION])
File "/usr/local/lib/python3.10/site-packages/aiohttp/helpers.py", line 154, in decode
raise ValueError("Unknown authorization method %s" % auth_type)
ValueError: Unknown authorization method NTLM
Bluetooth LE doesn’t poll, it’s push… sort of. The system is basically just listens to broadcasts, and the devices broadcast regardless of someone listening.
understood. sort of… so, when the entities are unavailable, the HA system does actually do nothing, until some sort of push signals it to change to something else?
Ive now disabled the Oral B integration to prevent anything from happening.
Seems a terrible and undesirable privacy breach though… wonder what others ‘see’ of our own instances/devices…
yay
Getting information when and how often your neighours brush their teeth…
That’s the side-effect of “not so smart” smarthome-stuff…
just think, what you could discover in an appartment with ~40 other parties… I am question myself atm, if I SHOULD start with the bloothooth stuff at all…
What I found out …
after clicking the glance card the stream shows in the same size as the glance card. If you hover it you see a small rectangle bottom right. Clicking on this gives fullscreen.
So far so good. Is it possible to start the streaming window fullscreen or with a given size?
Since upgrading to 2022.11 ZHA has failed to start with reloads of HA (including with the update). A full reboot of the host more often works, but not every time.
Here is a sample log entry relating to the issue:
Logger: homeassistant.components.zha.core.gateway
Source: components/zha/core/gateway.py:172
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 18:17:55 (5 occurrences)
Last logged: 22:42:47
Couldn't start ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2 coordinator (attempt 1 of 3)
Couldn't start ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2 coordinator (attempt 2 of 3)
Couldn't start ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2 coordinator (attempt 3 of 3)
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 664, in _skip_bootloader
result = await responses.get()
File "/usr/local/lib/python3.10/asyncio/queues.py", line 159, in get
await getter
asyncio.exceptions.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 172, in async_initialize
self.application_controller = await app_controller_cls.new(
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 144, in new
await app.startup(auto_form=auto_form)
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 124, in startup
await self.connect()
File "/usr/local/lib/python3.10/site-packages/zigpy_znp/zigbee/application.py", line 106, in connect
await znp.connect()
File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 706, in connect
self.capabilities = (await self._skip_bootloader()).Capabilities
File "/usr/local/lib/python3.10/site-packages/zigpy_znp/api.py", line 663, in _skip_bootloader
async with async_timeout.timeout(CONNECT_PROBE_TIMEOUT):
File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line 129, in __aexit__
self._do_exit(exc_type)
File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line 212, in _do_exit
raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError
I’m running HA OS 2022.11.1 installed on a RPi 4. Issue started with 2022.11.
Yes, i upgraded to 2022.11.1 today, noticed 30 minutes ago that my cards with tap actions on pictures (transparent btw.) does not work anymore.
In my opinion this has to be a bug… did you solve it yet withouth changing/reposition images/click spot?
