2022.7: A stunning performance

Blog
620

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.

621

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
622

Maybe has a stunning performance it were run. :slight_smile:

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
623

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 :slight_smile:

624

just updated here as well and it stopped working :frowning:

625

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 :slight_smile:

626

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
627

I just upgraded to 2022.7.7 and having this issue. Did you ever find a resolution?

628
1 Like
629

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.

630

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.

631

Have you updated unifios as well?

1 Like
632

Of course I hadnā€™t! :laughing:

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!

633

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
634

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.

635

Yes something like that should be done. ā€œAlways run latest stable of controller and UniFi OSā€

1 Like
636

Same issue for me, CPU increases since yesterday. Whatā€™s the next?

637

brok my virtualbox vm 2 times unavalable wen upgraded from core 2022.6.7. to 2022.7.7 os 8.4 please fix

638

Hmā€¦ it works perfectly here. VM on Synology, haos 8.4 and lateset core versionā€¦

639

I had to uninstall mariadb, I wasnt using it however it was in my installed addons. Once removed, mysql worked fine!