has your IP been banned?
By HA you mean? I didnât know that could happen.
Where would I find that, please?
config\ip_bans.yaml
I was hoping for it, but it doesnât exist. HAOS wonât update to 2023.5.2 after several attempts. I just donât know what is going on.
Logs� (supervisor)
Going back to HAOS 9.5 solved the problem.
No more aggressive updating for me.
Only reverting to 2023.4 and rescanning all my Aqara devices fixed this. Upgrading to 2023.5 made all my Aqara zigbee devices become âunknownâ and any motion or door open/close was not noticed by Home Assistant. Since reverting to 2023.4 solved this, the problem is with the update and the update only. Do not suggest to me or anyone else that we need to move around hubs or radios, do not suggest that we reboot and run Scan Disk, do not tell us to call back on Monday. No, there are zero mentions of Aqara or Nortek or HUSBZB-1 in the update notes or breaking changes, so thatâs not it either.
HUSBZB-1 using ZHA is the Zigbee controller. Aqara door/window sensors and motion/light detectors are what stop working with 2023.5.
Is there any direct solution to this beside reverting to 2023.4? Will some newer version of 2023.5 either fix this problem or at minimum, no longer break what has been working up until this update?
Im trying to create a new workday sensor and its not working, throwing an unhelpful error.
Also the way the flow is created is severely in need of work. Why are the country codes and subdivisions all packed into one dropdown? Why not have two dropdowns? One for country and one for province that filters the list down. Its very messy right now!
System Logs
Logger: aiohttp.server
Source: components/workday/config_flow.py:56
First occurred: 1:02:55 PM (4 occurrences)
Last logged: 1:08:09 PM
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/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 85, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 227, 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 80, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 235, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 146, 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 72, 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 271, in async_configure
result = await self._async_handle_step(
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 187, in async_step_user
return await self.async_step_options()
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 233, in async_step_options
schema = await self.hass.async_add_executor_job(
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 56, in add_province_to_schema
if not obj_holidays.subdivisions:
AttributeError: 'CA' object has no attribute 'subdivisions'
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 187, in async_step_user
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 233, in async_step_options
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 56, in add_province_to_schema
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 187, in async_step_user
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 233, in async_step_options
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 56, in add_province_to_schema
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 187, in async_step_user
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 233, in async_step_options
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 56, in add_province_to_schema
Here is this issue on Github:
Workday Integration fails in add_province_to_schema · Issue #92827 · home-assistant/core (github.com)
Done, i deleted the old intergation, restart and setup the unifi protect in the integrations.
i can complete the setup with a HA user in Unifi. with full management. but the intergation show failed to setup
LOG:
Home Assistant Core
2023-05-09 20:35:54.200 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration unifiprotect which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-05-09 20:44:10.992 INFO (MainThread) [homeassistant.setup] Setting up unifiprotect
2023-05-09 20:44:10.993 INFO (MainThread) [homeassistant.setup] Setup of domain unifiprotect took 0.0 seconds
2023-05-09 20:44:14.284 INFO (MainThread) [pyunifiprotect.api] Websocket re-connected successfully
2023-05-09 20:44:14.501 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry XXXXXX for unifiprotect
File â/config/custom_components/unifiprotect/init.pyâ, line 198, in async_setup_entry
2023-05-09 20:45:13.550 INFO (MainThread) [pyunifiprotect.api] Websocket re-connected successfully
2023-05-09 20:45:14.220 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry XXXXXX for unifiprotect
File â/config/custom_components/unifiprotect/init.pyâ, line 198, in async_setup_entry
Hi,
I have this one (Respeaker 2-mics pi hat) and would like to make it work on HA OS, but I have hard time finding updated drivers. Would anyone have any clue to help me?
It looks like you still have the custom version installed.
I get that same error with Nest after moving to Home Assistant 2023.5.1 and .2. Iâve been reverting to 2023.4.6 and waiting.
AttributeError: 'ConfigEntries' object has no attribute 'async_setup_platforms'
how can i find the core version?
Setting the temperature / humidity of climate entities via Google Home is now broken in 2023.5.0 / 2023.5.1 / 2023.5.2
Unable to fix the issue with restarts and other standard troubleshooting.
Unfortunately, seems like 2023.5.x has been somewhat botched when it comes to integrating with Alexa / Google Home.
Just in case anyone runs into similar problems.
I attempted to upgrade to 2023.5.2 again. The DB was corrupted again. Went through the logs this time and there were several errors (abbreviated list below). Looks like my database was upgraded from version 35 to 41 (with every other version in between as steps).
Database is about to upgrade from schema version: 35 to: 41
Dropping index `ix_states_entity_id_last_updated_ts` from table `states`. Note: this can take several minutes on large databases and slow computers. Please be patient!
Dropping index `ix_events_context_id` from table `events`. Note: this can take several minutes on large databases and slow computers. Please be patient!
Dropping index `ix_states_context_id` from table `states`. Note: this can take several minutes on large databases and slow computers. Please be patient!
Dropping index `ix_statistics_short_term_metadata_id` from table `statistics_short_term`. Note: this can take several minutes on large databases and slow computers. Please be patient!
Adding index `ix_event_types_event_type` to table `event_types`. Note: this can take several minutes on large databases and slow computers. Please be patient!
Index ix_event_types_event_type already exists on event_types, continuing
Adding index `ix_states_meta_entity_id` to table `states_meta`. Note: this can take several minutes on large databases and slow computers. Please be patient!
Index ix_states_meta_entity_id already exists on states_meta, continuing
Unrecoverable sqlite3 database corruption detected: (sqlite3.IntegrityError) UNIQUE constraint failed: event_types.event_type [SQL: INSERT INTO event_types (event_type) VALUES (?) RETURNING event_type_id] [parameters: ('service_registered',)] (Background on this error at: https://sqlalche.me/e/20/gkpj)
Error executing query: (sqlite3.IntegrityError) UNIQUE constraint failed: event_types.event_type [SQL: INSERT INTO event_types (event_type) VALUES (?) RETURNING event_type_id] [parameters: ('service_registered',)] (Background on this error at: https://sqlalche.me/e/20/gkpj)
The system will rename the corrupt database file //config/home-assistant_v2.db to //config/home-assistant_v2.db.corrupt.2023-05-08T22:38:39.933528+00:00 in order to allow startup to proceed
I ended up following the steps from several posts (here, here, and here) on stopping HA, copying the corrupted database, running sqlite3 to repair it, and then reloading it into HA. I used the downtime to complete several updates on the system as well. Restarted HA and everything has been working since.
Most people here have issues with voice control etc - but I need to raise again a question about removing the old functionality on a âHistoryâ page.
In the ticket below we were told that someone (no names were reported) from Frontend decided to remove this functionality.
As it was discussed many times in Community, the new functionality (âno graphs are displayed by default, select particular entitiesâ) cannot replace the old one (âgraphs for predefined list of entities are displayed, you may select a particular entity insteadâ), it just merely an addition to the old one.
So, the perfect way is to keep the old functionality with a new possibility to show graphs for SEVERAL entities.
I would like to hear why the old functionality was removed.
I hoped that the old functionality will be re-added - but it seems that it was removed finally since the old yaml config became deprecated in 2023.5.
5 Likes
Did you run any dev version of ESPHOME on the devices? Also, did you hear the speakers âpopâ when you used them first? I think both of mine blew on first use. When I hold my ear on them, I hear something happening when playback starts - so it must be hardware really 
No, this is a new device, flashed for the first time straight to the provided voice assist firmware. I have not noticed the âpopâ but canât be sure that it was not there.
1 Like