2022.5: Streamlining settings

Blog
49

Currently recieving the followinng error, on Home Assistant OS. Am i right suggesting the image needs time to populate??

22-05-04 21:42:33 ERROR (SyncWorker_5) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/qemux86-64-homeassistant:2022.5.0: 404 Client Error for http+docker://localhost/v1.41/images/ghcr.io/home-assistant/qemux86-64-homeassistant:2022.5.0/json: Not Found ("no such image: ghcr.io/home-assistant/qemux86-64-homeassistant:2022.5.0: No such image: ghcr.io/home-assistant/qemux86-64-homeassistant:2022.5.0")
50

Give it some time.

51

Continue on error
Will continue on error works on (individual actions) in parallel Actions ?

52

yes it does

2 Likes
53

Hey guys, I absolutely appreciate the amount of updates and improvements. Strangely, I updated (my config says 2022.5.0) but I do not see anything change in the configuration menu (which should now be settings). What happend? Thanks in advance, SilentScreamer

1 Like
54

Type ‘c’ from anywhere then type ‘restart server’ and press enter
Screen Shot 2022-05-04 at 4.58.05 PM

There’s no reason to navigate to any particular page.

1 Like
55

You may need to do ctrl + F5 or cmd + R to hard refresh the browser

2 Likes
56

Awesome looking release. Nervous to upgrade on a .0 release but it has so much!

57

And I already learned something new! Thanks cryznik, that worked!

58

No, they tried a fix of rebuilding the numpy wheels for the final release but it ended up still being present. As @frenck said it was not related to a HASS code change:

I don’t see any reason why this happens:

  • Our Numpy wheel is built on 6 Jan, and hasn’t changed since then.
  • Our Python version and base image haven’t changed in the past releases.
  • Nothing in b6 → b7 is (or can be) NumPy related.
1 Like
59

Disabling stuff in automations YESS! I have proposed that multiple times and was declined as it was deemed too complex for little use.

60

What is the usecase? Why one might need a trigger or condition in automation that is disabled? Shouldnt it be removed/deleted/commented if its disabled?

61

As the release notes say:

Sometimes, you may want to disable a specific trigger, action, or condition, whether this is for testing, a temporary workaround, or any other reason.

In YAML, you’d comment out parts of your automation, but if you wanted to do that in the UI, the only option you have is to delete it from the automation or script.

62

Aaah. Sorry. Missed this one - using yaml only.

63

This release looks absolutely great, amazing work to all the Devs and the community that feed them.

1 Like
64

I just started testing the 2022.5 rev.
And the first thing I checked is the new UI.

I am using Dev tools a lot.
Well, I am tired of reminding how uncomfortable is “not showing entity_id” in the “Set state” panel (as well as in History and some other places) - time flows, this functionality is not being fixed. OK, what can I say…

But I wonder why the RESTART button was hidden so deep?
Where is a logical connection between “YAML”, “Dev tools” & “Restart” ?
Move all Automations, Blueprints - everything low-level - to the Dev tools then…

image
image560×581 27.9 KB

OK, there is one more Restart button:
image
But for me “Check config”, “Restart”, “Reload yaml stuff” are commands which are used very often.

11 Likes
65

Well restarting is something you shouldn’t need to do too often, only when changing things… as the ‘dev’ of your system…

1 Like
66

Since many things are changing, I am in a constant “development mode”…
And I am still learning too.

3 Likes
67

The entire page has to do with yaml configuration except for the reload button… Reload individual integrations that are yaml only, or checking your configuration. The restart being there is/was a bonus. The restart button is also accessible via the search button, the c hotkey, the settings → system menu, and the services tab.

1 Like
68

As was mentioned in the Community many times, people are very sensitive to UI changes.
This particular change (Check config, Reload yaml staff moved to Dev tools) is not critical at all.
Moreover, I appreciate moving Blueprints to Automations, Helpers to Entities.