Im upgrading via pip3 install homeassistant==2022.7.6
its the same with any 2022.7 version connection refused
go back to 2022.6.7 and its working fine
got it working by installing orjson 3.7.7
now fixed in 2022.8.0.b0
1 Like
I’m at 2022.7.7 and haveibeenpwned is still broken for me.
Recorder function is still broken in the latest release 22.7.7. If I upgrade to any version of 22.7.x recorder is broken for mysql. Opened a ticket only to have it immediately closed because they said it was fixed in 22.7.4. I have tried each July release only to have it still fail on the recorder function
Error during connection setup: (MySQLdb.OperationalError) (1045, ‘Plugin caching_sha2_password could not be loaded: Error loading shared library /usr/lib/mariadb/plugin/caching_sha2_password.so: No such file or directory’) (Background on this error at: Error Messages — SQLAlchemy 1.4 Documentation) (retrying in 3 seconds)
Not sure what’s going on or if anyone can point me in the right direction but I updated to 2022.7.7 and the OS to 8.4 a few hours ago (both updates came in at the same time) and now I’m seeing my CPU and network with something that looks like a heartbeat. Functionality is totally fine but this is very strange. I’ve rebooted the server multiple times (shutdown the host) but the behavior has not changed. I’ve been chasing this down for two hours and it’s driving me nuts. See the attached charts starting around 10:42am. Does anyone have any guidance?
hmmm… interesting. I decided to shutdown my ad-ons one by one to see if it’s one of those. I started with AppDaemon and sure enough that was the culprit. Something must have changed on the latest HassOS or Core versions that’s affecting AppDaemon.
Update: It was the py3-scipy package.
Anyone else has an issue with Xiaomi Aqara gateway and all zigbee devices attached to it? After upgrading to 2022.7 it stopped working for me and reverting back to 2022.6 fixed it. I didn’t bother to try debugging, needed to make everything back to normal ASAP because I have a lot of Xiaomi devices. Only thing I saw in logs was error: Logger: xiaomi_gateway cannot connect to gateway
I’m using hassos 8.2, haven’t upgraded to 8.4 yet.
Was there a breaking change to the Unifi Network integration that I missed?
I just updated from 2022.6.6 (Unifi working) to 2022.7.7 (unifi fails to connect). Rolling back to 2022.6.6 allows Unifi to work again.
I tried it on two different HA instances and both give the same results.
nothing in the logs but this:
2022-07-27 00:49:12 ERROR (MainThread) [homeassistant.components.unifi] Error connecting to the UniFi Network at 192.168.1.4: Call https://192.168.1.4:443/api/auth/login received 404 Not Found
EDIT:
adding debugging to the logger i get this:
2022-07-27 00:58:02 DEBUG (MainThread) [aiounifi.controller] https://192.168.1.4:443
2022-07-27 00:58:02 DEBUG (MainThread) [aiounifi.controller] 200 text/html <ClientResponse(https://192.168.1.4:443) [200 OK]>
<CIMultiDictProxy('Vary': 'Origin', 'X-DNS-Prefetch-Control': 'off', 'X-Frame-Options': 'SAMEORIGIN', 'Strict-Transport-Security': 'max-age=15552000; includeSubDomains', 'X-Download-Options': 'noopen', 'X-Content-Type-Options': 'nosniff', 'X-XSS-Protection': '1; mode=block', 'Accept-Ranges': 'bytes', 'X-CSRF-Token': '956e578f-a7e5-410e-a74c-85d7e06bdcb0', 'Content-Type': 'text/html; charset=utf-8', 'Content-Length': '447', 'X-Response-Time': '11ms', 'Set-Cookie': 'TOKEN=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJjc3JmVG9rZW4iOiI5NTZlNTc4Zi1hN2U1LTQxMGUtYTc0Yy04YXQiOjE2NTg4OTc4OTEsImV4cCI6MTY1ODkwMTQ5MX0.Q5RccaQ1J9rAubDQH9xP7hHdwJo0KcvOSfC1cd7zZdo; path=/; samesite=strict; secure; httponly', 'Date': 'Wed, 27 Jul 2022 04:58:11 GMT', 'Connection': 'keep-alive')>
2022-07-27 00:58:02 DEBUG (MainThread) [aiounifi.controller] https://192.168.1.4:443/api/auth/login
2022-07-27 00:58:02 DEBUG (MainThread) [aiounifi.controller] 404 text/plain <ClientResponse(https://192.168.1.4:443/api/auth/login) [404 Not Found]>
<CIMultiDictProxy('Vary': 'Origin', 'X-DNS-Prefetch-Control': 'off', 'X-Frame-Options': 'SAMEORIGIN', 'Strict-Transport-Security': 'max-age=15552000; includeSubDomains', 'X-Download-Options': 'noopen', 'X-Content-Type-Options': 'nosniff', 'X-XSS-Protection': '1; mode=block', 'Accept-Ranges': 'bytes', 'X-Response-Time': '5ms', 'Content-Type': 'text/plain; charset=utf-8', 'Content-Length': '9', 'Date': 'Wed, 27 Jul 2022 04:58:11 GMT', 'Connection': 'keep-alive')>
2022-07-27 00:58:02 ERROR (MainThread) [homeassistant.components.unifi] Error connecting to the UniFi Network at 192.168.1.4: Call https://192.168.1.4:443/api/auth/login received 404 Not Found
Maybe has a stunning performance it were run. 
Every subversion in 2022.7 is failed to start after installation on Docker (QNAP).
The same error message is occured.
[14:44:09] INFO: Home Assistant Core finish process exit code 256
[14:44:09] INFO: Home Assistant Core finish process received signal 11
[14:44:10] INFO: Home Assistant Core finish process exit code 256
[14:44:10] INFO: Home Assistant Core finish process received signal 11
[14:44:11] INFO: Home Assistant Core finish process exit code 256
[14:44:11] INFO: Home Assistant Core finish process received signal 11
It is looping infinitely.
There is no resolution in any discussion only reverting to a lower version.
1 Like
Moi Temu,
I would really appreciate if the eq3 could be integrated again and I am actually happy to support the developer if there are any options to donate a bit
just updated here as well and it stopped working 
Moi, the fix for eq3btsmart is already in the 2022.8 beta, so if you have a chance please try it out to see if it works for you now
The biggest issue for me in this July cycle has been the loss of the Russound integration related to the Python upgrade. While the dependent library has been updated, Core has yet to include it in a patch update. I suspect this Python upgrade may be just as problematic for a number of other components failing to start up.
HA updates have been rock solid for quite awhile before this one. I had become too trusting after such a long period of easy updates. I’ve reverted back to 2022.6.7 and will stay there for the near term until things catch up with the “Stunning Performance” of this less than stable update.
This is just a little reminder that caution should be exercised when updating a live system, especially if you don’t dedicate the time required to fix the potential failed outcome.
The frequency of HA updates with all the cool and interesting/intoxicating additions each month comes with a very sharp double edged sword.
1 Like
I just upgraded to 2022.7.7 and having this issue. Did you ever find a resolution?
1 Like
Make sure to update your system to latest stable releases. If that doesn’t work doing a proper power down and then start it up again should work.
I’m on 2022.7.7 right now which is the latest.
I’ve restarted HA a few times already. I haven’t restarted the cloud-key tho. What should I be restarting?
But it works fine as is on 2022.6.6 without restarting anything.
Have you updated unifios as well?
1 Like
Of course I hadn’t! 
but I just did now and it’s all working now.
Maybe I could recommend putting a minimum OS version in the docs/release notes?
thanks for the help!
Same issue when using the latest docker image.
Solution is to open terminal of container and run apk add mariadb-connector-c and restart container.
Need to do this after recreation of container also, as the component is missing in the image.
1 Like
Workaround until they fix this properly:
Assuming you are using docker:
Open terminal and enter container, and run apk add mariadb-connector-c and restart.
Should be OK. Also repeat this if you ever recreate your container and see the same error.