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.
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
Seeing this also. Interested in the cause.
Anybody else seeing major issues with custom cards?
I couldn’t check all my dashboards before I had to roll back to 2022.6.7 due to a serious Sonoff issue, but these cards did not display properly:
- auto-entities
- frigate-card
- digital-clock
- slider-button-card
- more-info-card
- rgd-light-card
- flipdown-timer-card
- blind-card
- stack-in-card
- vacuum-card
1 Like
What exactly is ‘trashed’?
After several restarts, rolled back to 2022.6 and my thousands of entities have returned. Just about had a heart attack. I would suggest doing a full backup before attempting this one. Maybe even clone the card. 
1 Like
I have no issues with auto-entities
2 Likes
So much was wrong I didn’t know where to start. Volumes of scary logs like “couldn’t confirm db was closed properly” (not exact wording), all physical entities from various integrations missing, very long startup times, complaints about rest.notify config not being valid (I didn’t change any configs since last restart), “CHECK CONFIGURATION” spins forever–just a nightmare. It’s all good now with a rollback. Will attempt an upgrade at a later time with full PPE.
1 Like
Great the rollback worked for you - just had a similar experience 
Upgraded to a .0 version for the first time in quite a while - and I was promptly reminded why I’d skipped them for so long.
5 Likes