Home Assistant Cookbook - Discussion Thread

I agree with @stevemann! This just added confusion to new users in my opinion.

I would not think this should be a deciding factor. It is a limiter considering users may not be engaged via the forum yet. Decision should be made on potential new users, not what we have recently experienced. Cater to the non-experienced, not the experienced.

Just my opinion…

For a beginner to rebuild your system because they want to go from bare metal to virtualized is not that obvious.
On top of that, if you have automated your whole house, you want your HA to be available all the time so ‘starting over’ (how many of them know about the ability to restore a backup at onboarding…)

In the past I have given the advice to have a look at Proxmox because:

  1. I use it myself
  2. the benefits (specifically for HA: backups, setting up an additional test system, …)
  3. when the HW is capable, they can run other stuff/consolidate multiple systems
  4. using the late tteck his scripts make it as easy as installing HA

Of course, when virtualized, your HW/hypervisor becomes your SPOF.
I’m quite sure that more beginners run into issues with their HA compared to failing HW/hypervisor.

It all depends on the situation and having options is a strength with HA.

My suggestions:

For inclusion in posts referring to specific cookbook topics:

See the cookbook index for more topics you might be interested in or might like to contribute to.

For inclusion at the top of every cookbook topic:

This topic is part of the community-driven cookbook where you can find other topics you might be interested in or might like to contribute to.

1 Like

Lol, my comment was totally sarcastic. I’ve read too many “I don’t know anything but I’m in the middle of brain surgery and need help…” posts.

I don’t disagree with the first one, but I have been more prone to copy the link out of the cookbook so they don’t have to double click or pull a section link out of the cookbook (like zigbee section) if they have fewer clues.
I was counting on the lower level posts themselves to point back up for more info.

The second one is much better than mine.

I might’ve expressed myself not well enough: I meant to add that in addition to the specific cookbook topic linked to in response to a particular topic.

A more complete example:

User X:
Some random question about a YAML error…

User Y:
Your error is foo-bar-bas.

If you want to better understand how to read YAML errors, see this cookbook page.

See the cookbook index for more topics you might be interested in or might like to contribute to.

Basically, I’m trying to cover both angles: If someone gets a link to a specific cookbook page, make them aware of the index in the post, but also, if you’re on a cookbook page, make it clear that it’s part of the index.

OK