2022.7: A stunning performance

No. It wasnā€™t there after being skipped. I was able to clear the skipped version via the services though. Thanks!

You can show skipped in the over flow menu in the updates page.

1 Like

AKA ā€œThe meatball menu iconā€ (three dots top right).

3 Likes

What is preventing Sonoff from having a ā€˜realā€™ integration vs a ā€˜HACSā€™? These last few releases have been pretty painful, and AlexxIT is getting swamped for asks.

I have 2 they work with zha.

Think they might be two separate issues :thinking:ā€¦solutions for both in this thread

1 Like

I have the same issue jgosnell

1 Like

All my SensorPush temperature sensors switched from C to F after I upgraded to 2022.7. Is this some breaking change the integration needs to handle or is there some configuration I could do on my end thatā€™s not related to the integrations itself?

1 Like

After running

sudo docker pull homeassistant/home-assistant
sudo docker restart homeassistant

Should it say Home Assistant Core 2022.6.6 or Home Assistant Core 2022.7 in settings?

It should say core-2022.7.0

Where are you seeing that in Settings?

Have you cleared your web browser cache?

Have you checked that you have actually updated?

Iā€™m having issues with OpenWeatherMap onecall_hourly because the weather.openweathermap entity is no longer available after updating to 2022.7. onecall_daily works, and it doesnā€™t seem to be an issue with API rates or OpenWeatherMap because an older backup still works.

Looks like thereā€™s an open issue here https://github.com/home-assistant/core/issues/74527

1 Like

Thanks for the great update! It was nice to see that this thread wasnā€™t bombed with complaints within the first 4 hours of release.

1 Like

I fixed it for now by following the instructions in this Stack Overflow thread.
MySQL Native Password Mode
Post 110 in particular.

4 Likes

Getting multiple reports and have verified an integration I manage no longer works in 2022.7.0. It uses aiohttp to connect to local IP addresses of the devices and this connection fails. Any changes in the aiohttp layers that HA injects?


2022-07-06 15:58:21 ERROR (MainThread) [custom_components.lennoxs30.config_flow] Code [11] Reference [400] [login Client Connector Error - failed due host not reachable url [https://192.168.100.71/Endpoints/homeassistant/Connect]]

after the update Im forced to re-authenticate my NEST integration and after going through all to the end when Im asked to give access to HA for my Thermostat I get this error.

image

Absolute MADNESS!

Are we monsters?

8 Likes

I have also noticed the same thing on my Weather card, which stopped working.

Also a lot of entities for the Alexa Media Player have disappeared, see below.

I know this is a custom and unsupported integration, but perhaps the authors can take a look at it.

Last release 2022.6 the redirect url was changed. See the integration instructions which have troubleshooting details.

1 Like

Iā€™ll hold off on updating until you get this resolved.

Iā€™m stunned, alright. The vast majority of my system is trashed after the ā€œupgradeā€.

2 Likes