I kind of hope never. 18° according to what sensor? Turn on heat to what? Which heat device?
I adopted HA back in 0.30 because it let me make sure things only do exactly what I tell them to. Now they want to to give area ideas of what to do, and I'm not OK with that.
I see you can exclude them via configuration.yaml file but not from UI.
I don't use areas, I wish I could remove a single area I am forced to have in HA (from hue integration)..
The new documentation is great, but why must we have two links to:
Triggers:
Conditions:
Actions:
I include a logbook.yaml from configuration, with the following:
exclude:
entities:
- sensor.date
- sensor.date_time
Maybe I will do the same. I haven't used Activity before.
Is anyone else having issues with plugins unable to contact resources hosted on https://wheels.home-assistant.io/ ? Several of my HACS plugins, including Toyota and Emporia Vue are failing due to timeouts on this cloud service.
Also, why would my local install need to access a cloud webserver? Is this a one time upgrade thing, or will this happen all the time if I happen to not be connected to the Internet when my HA restarts?
It looks like this is trying to get precompiled python dependencies:
* Unable to install package portion==2.4.0: error: Request failed after 3 retries in 87.7s Caused by: Failed to fetch: `https://wheels.home-assistant.io/musllinux-index/portion/` Caused by: HTTP status server error (522 <unknown status code>) for url (https://wheels.home-assistant.io/musllinux-index/portion/)
* Unable to install package portion==2.4.0: error: Request failed after 3 retries in 88.6s Caused by: Failed to fetch: `https://wheels.home-assistant.io/musllinux-index/portion/` Caused by: HTTP status server error (522 <unknown status code>) for url (https://wheels.home-assistant.io/musllinux-index/portion/)
* Unable to install package portion==2.4.0: error: Request failed after 3 retries in 89.9s Caused by: Failed to fetch: `https://wheels.home-assistant.io/musllinux-index/portion/` Caused by: HTTP status server error (522 <unknown status code>) for url (https://wheels.home-assistant.io/musllinux-index/portion/)
* Unable to install package ruamel.yaml>=0.18.0: error: Request failed after 3 retries in 87.0s Caused by: Failed to fetch: `https://wheels.home-assistant.io/musllinux-index/ruamel-yaml/` Caused by: HTTP status server error (522 <unknown status code>) for url (https://wheels.home-assistant.io/musllinux-index/ruamel-yaml/)
* Unable to install package ruamel.yaml>=0.18.0: error: Request failed after 3 retries in 88.6s Caused by: Failed to fetch: `https://wheels.home-assistant.io/musllinux-index/ruamel-yaml/` Caused by: HTTP status server error (522 <unknown status code>) for url (https://wheels.home-assistant.io/musllinux-index/ruamel-yaml/)
Someone forget to pay their Cloudflare bill?
For me, this is blocking the upgrade entirely since it's timing out when trying to set up the backup integration, whose failure then cascades on and makes the setup of almost every other integration fail in turn.
ETA: Oh, delightful. I cannot even revert to 2026.6.4 because it has now started throwing the same error on startup. Along with its cascading cousins
asyncio.exceptions.CancelledError: Global task timeout: Bootstrap stage 1 timeout
for almost every other integration. Even really simple ones like "Time & Date". What, with all due respect, the hell?
Same here, some of my intergrations is not loading now (Frigate, Amcrest, Proxmox, Emporia). And it takes forever to start up
You're definitely not the only one. Same issues here. What a time to upgrade and restart...
Yep - I have never had an issue with rolling back a failed upgrade until today. Guess we wait until somebody fixes it.
same issues here, even a roll back to 2026.6.4 does not fixed it.....
Restart takes up to 5 min or more
After updating the OS and from 2026.6.4 to 2026.7: none of the Addons/Apps show in the sidebar. Z-Wave JS UI requires an update, but no update button to be found (only Stop and Restart). I am now restoring my much valued backup. Too bad this...
There's something really odd with this update. I get repeated warnings that I should remove smtp from configuration.yaml...I have no smtp set there...or anywhere AFAIK? Unless they mean platform: smtp in notify?
And I changed the behavior: any to behavior: each as requested as it will be deprecated in 2027.1, and it broke those automations and I was instructed in the Automations to set it back to behavior: any!
Weird error about 'null' not accepted by behavior in the messages, and then in the Automation itself a red bar saying that only any or all are accepted, and to click here to change it back....
Yes I have restarted many times.
Like...which is correct? Seems like the two systems are fighting each other...
Yep, I rolled back to previous version through Proxmox and things still break (HomeKit, Emporia), guess we need some wait
I also have multiple integrations "not loaded", yamaha (YNCA), phillips airpurifier, huesyncbox, dyson_local.
Same here, I have logs saying 'https://wheels.home-assistant.io/' is not reachable. I guess that's the problem. Anyone else have the same logs?
Three in the case of Conditions & Actions
yes https://wheels.home-assistant.io is down and it breaks the update 
And yes just checked - if I resave the automation as requested in the alert - then look at the yaml - it says behavior: any not behavior: each
