Nothing at all if I am on my desktop, but this is for my mobile menu and the side menu is hidden most of the time in mobile.
1 Like
I was already getting tired of adding everything to the group, so I think I may go this route instead. Thank you!!!
1 Like
And it works perfectly for what I want! That area of my screen are all conditional cards that only provide info when needed. Lights that are on, doors and windows that are open, etc. I can now navigate to a page dedicated to system admin just by tapping on that icon.
Thanks for the help on this to all of you!!
I do like the move towards more simplicity for beginners.
But I do not quite understand why more and more configurations are now forced away from yaml files. Why not store the configuration from the UI in yaml files?
The current backup system is not really nice. If you setup a new system, restoring a backup is usually not the nicest way to go. Nor the safest.
But a copy&paste of yaml files was simple and fast and worked.
I am having to delete more and more yaml files because they are no longer supported. I am being forced to use a UI that is 10 times the work. Configuring brokers etc. seems like a small task, but the sum of tasks gets bigger and bigger the more is moved to the UI.
I hat eto imagine what would happen if I had to re-make all my automations via the UI everytime my RPI crashes and I did not have a backup.
UI is nice, but disallowing yaml files is starting to feel forced and disadvantages, even to beginners like me.
we have been told that yaml will not go away for automations, so that is good!
The requirement got downgraded to fix a memory leak. Not sure what you did in terms of upgrades or which installation method you use, but you could manually downgrade pyav.
But we might get forced into automations.yaml. And that would not be good. We are already being forced to use automations.yaml and scripts.yaml if we want to use the editor. The logical next step is to remove all independent yaml files and force the user to use huge single file systems.
1 Like
Hi I have the message that there is a new release of Home Assistant 2022.4.2 to be updated but I cannot find the Update function as before in the “CONFIGURATION” function on the left panel of Home Assistant. How do I update the release?
I’ve never used openhome and got the same error starting 2022.4. After some investigations I found that most likely it is indeed related to false discovery of volumio as opehub player. I remediated it by edding following code to configuration.yaml:
discovery:
ignore:
- openhome
3 Likes
going to check that blueprint 
was experimenting with templates like this myself:
{{states.binary_sensor
|selectattr('entity_id','search','update_available')
|selectattr('state','eq','on')
|map(attribute='name')|list}}
mainly because if you skip an update, the update entity will turn ‘off’ and you can not ‘trust’ the template based on that entity for available updates.
combining these in a Markdown card can be very useful.
thanks for your ongoing effort to keep up that set of templates btw, really appreciated!
You can find the backup dashboard in the configuration menu, or, if you have upgraded already, click the my button below to create a new backup right away
In my Core installation of 2022.4.2 I am not seeing anything regarding backups in the Configuration. Following the “my” button results in “404: Not Found”. Is there anything needed to enable this?
If you do not have default_config: in your configuration.yaml, you’ll need to put backup: in there.
No… that is an incorrect assumption.
1 Like
8.1.0 fails to install. If I just install 9.1.1 the camera doesn’t work and the error still shows up.
Do you have a link to any recent discussions about this. I’m not able to find any discussions on MariaDB not being recommended anymore.
If it’s worth it I’ll revert back to SQLite, although I’m unfamiliar with how to transfer long term statistics, which will take some time to figure out. Do I want to make sure it’s worth doing this.
Thanks, that was indeed the issue here!
I prefer not to use default_config because it is a massive list which also includes things I’m not using. Bu t adding backup: works fine 
thats what I thought in the beginning, but checking the integrations that are configured by default_config: I see all of the integrations that are in my current self curated list of installed integrations… except for 1:
map:
and that’s only because I dont want the map in the left side menu column… other than that, I would be happy to use default_config:
except I dont use:
stream:
backup:
usb:
tag:
webhook:
either 
What we need is this for automations
Best of both worlds if this gets implemented. We will have much better GUI experience and still full flexibility to edit YAML.
If the GUI automations editor cannot figure out an advanced YAML automations it can always fall back to only offer YAML editing in the browser. I would love that. I would love to be able to create the basic automation in the GUI and then when needed enhance it in YAML mode.
What prevents me today is that it can only happen if you accept to work with all your automations in one long horror list with 100s of automations. I cannot wrap my head around that. I have my automations organized in files today with between 1 and 5 automations in each file and even that has grown to a number where I consider putting them in sub-directories.
I really think this UI area needs to be the next big thing.
And please - do not start using JSON instead of YAML as storage format for the automations and scripts files. It will still be needed to edit files directory. When you need to do something bigger or something repetitive (like a major refactoring of your automations - I have done that more than once) the GUI approach takes far too long time. I was really sad to see the helpers now saved in JSON instead of YAML which makes quick hacking much more difficult.