Not sure why I embroiled myself in this release thread anyway, since I don’t use GPIO, nor do I anticipate any issues with this release. I did, however, take issue with the responses provided by some individuals here who, purposely or otherwise, belittled those who expressed concern. I don’t think that’s acceptable. But I yield. I’m both tired and disgusted.
5 Likes
No problem
1 Like
Anyone attempt to upgrade to HA 2022.2.2? Had issues in the logs related to HACS and other things immediately. Wondering if I am the only one.
EDIT: Actually I think I am rate limited on HACS causing that issue. Might all be well. idk.
Just done the upgrade and i cant see anything in the logs related to HACS or other stuff,
What are logs showing?
Disregard. I think its rate limiting. I’ll check later when its lifted.
Traceback (most recent call last):
File "/config/custom_components/hacs/base.py", line 463, in async_github_api_method
return await method(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/aiogithubapi/namespaces/contents.py", line 50, in get
response = await self._client.async_call_api(
File "/usr/local/lib/python3.9/site-packages/aiogithubapi/client.py", line 124, in async_call_api
response.data = await result.json()
File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 1098, in json
await self.read()
File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 1036, in read
self._body = await self.content.read()
File "/usr/local/lib/python3.9/site-packages/aiohttp/streams.py", line 375, in read
block = await self.readany()
File "/usr/local/lib/python3.9/site-packages/aiohttp/streams.py", line 397, in readany
await self._wait("readany")
File "/usr/local/lib/python3.9/site-packages/aiohttp/streams.py", line 304, in _wait
await waiter
File "/usr/local/lib/python3.9/site-packages/aiohttp/helpers.py", line 721, in __exit__
raise asyncio.TimeoutError from None
asyncio.exceptions.TimeoutError
I thought it was a specific error message mentioning rate limiting when it was.
someone posted a command a while back to test how to check if your hitting it, i’ll see if i bookmarked it
Have a look in this post and especially post from fanuch on how to check
Github rate limit error HACS - Configuration - Home Assistant Community (home-assistant.io)
I thought so too but I am not sure if that is the same as when you upgrade/downgrade. I saw that post actually and I am under but it may have reset. I just restart HA and no more messages either. So all good.
I have the same error and situation. No idea how to proceed yet. Have tried re-start of HA and Host, and install of update ignoring this with no success so far.
Where is this error seen and is it actually preventing you upgrading to 2022.2.2?
What is your install type (see in the info page).
It is shown by the check_config add on. I don’t know if it is preventing the upgrade, but the upgrade isn’t happening. I tried to upgrade, and it seemed to start the process but after a while just reverted to the config screen again, showing the upgrade available. I checked the backups and no new backup. Supervisor log seems to indicate a backup starting, but it doesn’t seem to finish.
I am running HAOS 7.2 on Raspberry Pi 4.
Supervisor is at 2022.1.1
Core is at 2021.12.10 showing 2022.2.1 available.
I tried a manual backup but is says backups are not available, system is in a freeze state. I restarted core, no change. I restarted Host, no change.
Not sure what to try next?
Just noted that Supervisor Log now includes:
22-02-05 13:30:49 INFO (MainThread) [supervisor.homeassistant.module] Backing up Home Assistant Core config folder
22-02-05 13:56:32 INFO (MainThread) [supervisor.backups.manager] Found 4 backup files
22-02-05 13:56:32 INFO (MainThread) [supervisor.backups.manager] Found 4 backup files
22-02-05 13:59:22 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
22-02-05 13:59:22 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.FREEZE
22-02-05 13:59:22 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-02-05 13:59:22 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
22-02-05 13:59:33 WARNING (MainThread) [supervisor.jobs] ‘Supervisor.restart’ blocked from execution, system is not running - CoreState.FREEZE
22-02-05 13:59:50 ERROR (MainThread) [supervisor.utils] Can’t execute restart while a task is in progress
And now it seems to have completed a backup and is moving on to the upgrade…. Will go mow the lawn and come back and see how its going…
No automation for that?
3 Likes
No reason to switch from homebridge but the setup was cut by 50% (no more url setup or pubsub config). Check out the integration video which takes about 15 minutes to get it set up.
Just notice that a button entity has been created for all my aqara devices: contact sensors, motion sensors, buttons, weather senor. These showed up as a result of updating to latest version. I was a couple versions back so the creation of the devices might be related to the release that had the button update. They popped out because they all have a state of unknown associated with the latest release. They all have the long device name like:
button.lumi_lumi_sensor_magnet_aq2_16ebe401_identify
The names I assigned to all of these devices are more readable. These just seem like needless entities with useless unknown state. They can’t be deleted via the GUI. Anyway to remove them? Is there any good reason they were created?
Nope, and it seems patience was the key. After mowing the lawn, the update was completed successfully it seems. Haven’t tested everything yet, but the basics seem OK.
Thanks.
It was mentioned in the release notes. Some devices had an identify button added to assist with distinguishing them. This is most helpful with lights.
The file name you posted starts with the device make/name, and ends with identify.
I don’t think there is a way to remove it, but you can disable it.
It can quickly get heated, especially in such release note threads. As long as we all can calm down eventually and refrain from attacking each other personally no harm is done.
That aside, feel free to join the beta and help out by providing feedback early on. The more the merrier.
2 Likes
Agreed. I’ve joined the beta, reloaded Supervisor and look forward to what’s coming down the pike.
Are the beta versions noted as such when an update appears in Configuration? I assume I can choose to skip versions as in the stable channel? Right now Configuration says OS 7.3 is available, but when I click on it, it says No update available for Home Assistant Operating System. Actually, I think I’ve experienced that before with the last OS update. Cheers.
1 Like