Iâve resolved my issue, it was changes in the user (location) and HA network configurations ( I changed from DHCP to static ip with the broadcast and DNS entry, once I added the missing info everything started working and polling correct. Why it broke that only the coders know. But mine is fixed.
Please donât post off-topic things. This is the thread for 2022.12 release and nothing changed in the 2022.12 with history labels.
No need to post here if you already posted an issue on GitHub 
1 Like
I didnât read through all the comments, so maybe this has already been asked, but is there any chance that the Local Calander Integration can be set up to allow setting a monthly event based on day of the week and specific week of the month? As it currently stands, I have a month event that I have to configure for each month of the year because the current implementation only allows by date.
I observed these changes THIS release.
And this is related to your recent color chages:
in English we have âDisconnectedâ for âOffâ; in some cases the long word âDisconnectedâ is not displayed, so a user should distinguish states by colors - which are soooo similar for âOffâ and âunknownâ these days.
So, a simple option like âshow_native_statesâ (call it as you like) to show native âon/offâ could be a good choice.
A github issue is for you, a post here is for users.
We should listen to as many opinions as possible.
Update: the issue was closed by this Dev. Not a surprise.
3 Likes
I have got the same error, but I canât fix it. It worked great before version 2022.12 , but then it screwed.
I donât use bluetooth, but esphome stopped work too:
ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration esphome: cannot import name 'BluetoothServiceInfoBleak' from 'home_assistant_bluetooth' (/var/lib/hass/.homeassistant/deps/lib/python3.10/site-packages/home_assistant_bluetooth/__init__.py)
Help me, please
You (and everyone else 
) should vote for this:
1 Like
You need to update the base requirements in your venv
Hello everybody,
anyone have my same problem? when I click on a âbuttonâ on the dashboard, it flashes the whole map
Tnks.
Itâs ZHA integration issue, no plugins or add-ons were used.
Iâve already reported it, but it just gets ignored or closed.
That does not make sense if you also say you run native ZHA. What github issue was closed? If you report ZHA issue with a Sonoff bridge running Tasmota then it makes sense it gets closed.
1 Like
I was referring to this wording
anyone else with this problem?
Does anyone have an issue with their LG WebOS TV?
Logger: aiohttp.server
Source: components/webostv/__init__.py:133
First occurred: 5:36:26 PM (3 occurrences)
Last logged: 5:37:47 PM
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/websockets/legacy/client.py", line 138, in read_http_response
status_code, reason, headers = await read_response(self.reader)
File "/usr/local/lib/python3.10/site-packages/websockets/legacy/http.py", line 120, in read_response
status_line = await read_line(stream)
File "/usr/local/lib/python3.10/site-packages/websockets/legacy/http.py", line 194, in read_line
line = await stream.readline()
File "/usr/local/lib/python3.10/asyncio/streams.py", line 525, in readline
line = await self.readuntil(sep)
File "/usr/local/lib/python3.10/asyncio/streams.py", line 617, in readuntil
await self._wait_for_data('readuntil')
File "/usr/local/lib/python3.10/asyncio/streams.py", line 502, in _wait_for_data
await self._waiter
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 854, in _read_ready__data_received
data = self._sock.recv(self.max_size)
ConnectionResetError: [Errno 104] Connection reset by peer
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
resp = await request_handler(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/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 81, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 180, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
result = await method(view, request, data, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 281, in async_configure
result = await self._async_handle_step(
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 368, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File "/usr/src/homeassistant/homeassistant/components/webostv/config_flow.py", line 98, in async_step_pairing
client = await async_control_connect(self._host, None)
File "/usr/src/homeassistant/homeassistant/components/webostv/__init__.py", line 133, in async_control_connect
await client.connect()
File "/usr/local/lib/python3.10/site-packages/aiowebostv/webos_client.py", line 73, in connect
return await self.connect_result
File "/usr/local/lib/python3.10/site-packages/aiowebostv/webos_client.py", line 105, in connect_handler
main_ws = await asyncio.wait_for(
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 650, in _wrap_awaitable
return (yield from awaitable.__await__())
File "/usr/local/lib/python3.10/site-packages/websockets/legacy/client.py", line 659, in __await_impl_timeout__
return await asyncio.wait_for(self.__await_impl__(), self.open_timeout)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
return fut.result()
File "/usr/local/lib/python3.10/site-packages/websockets/legacy/client.py", line 666, in __await_impl__
await protocol.handshake(
File "/usr/local/lib/python3.10/site-packages/websockets/legacy/client.py", line 326, in handshake
status_code, response_headers = await self.read_http_response()
File "/usr/local/lib/python3.10/site-packages/websockets/legacy/client.py", line 144, in read_http_response
raise InvalidMessage("did not receive a valid HTTP response") from exc
websockets.exceptions.InvalidMessage: did not receive a valid HTTP response
Not that I have noticed, if I remember Iâll test tomorrow.
2 Likes
hi version 2022.12.9 is available for me since today (2023-01-03) , but it refuses to install, popup keeps spinning, and after 1 hour waiting, refreshing the page still shows it is available, opening the page will show âinstallingâ
rebooted HA, did not help, after that it shows 2022.12.9 is available again, and 2nd time installing it gets same loop.
any ideas?
I have no idea, but the latest releases (12.8 and 12.9) seems to have resolved the issues for me.
If you are using an original ZBridge connected via WLAN, your problems are likely deeper than 2022.12.*:
Mine didnât last longer than a week before needing a hardware reset and binding restart, and the ZHA docs suggest the ZBridge Pro likely has the same design issue - which could explain closed issues.
No problem here with my one, although I am running 2023.1 beta, so there may be a fix included, but I canât see anything in the source that (on my quick) glance seems to be relevant.
No worries nick, thanks for checking anyhow. Do you by any chance know what the error message I pasted is pointing to? I canât understand what the issue is even to start to find out.
Thank you for pointing this out my bad