I moved it myself, but he needs to make it a wiki since it was created outside Community Guides.
Guys, don’t move pinned topics. I’m going to move it back so that it has optics on it during this release. Configuration has the most traffic, that’s where people will head when encountering an issue with 2024.5.
We can make a separate cookbook post if needed at a later date.
1 Like
Sorry… I didn’t read this first… I changed the category…
I didn’t notice the pin. Have to start looking for that I guess.
Added a link for this in getting started HA
1 Like
can we add this to the troubleshooting section: Instructions to install Py-spy on HAOS
yep we can… added as number 8 there
Hmm, yeah that is really, really unfortunate! I haven’t thought about that. 
I need to check, if Discourse doesn’t offer anything for that.
So, for the time being, we best leave it as is. 
I’d say so! Maintainance is a nightmare otherwise. I have that in another forum at the moment, you’re only allowed to edit your own posts after three months of membership and I haven’t reached that… Writing sometimes twice a day to a moderator isn’t a funny thing to do. And after the update you see two or three typos, so you write again to a moderator… We need the possibility for others to edit these posts, otherwise I wouldn’t use for the Cookbook.
Taking this into account, is there a possibility to make use of a “special account”? Something like a user called “CookbookAuthor” and we share the password for this account? It’s not really a good idea, but if we could limit the rights to editing posts in one category, it should work.
Or would it make sense, to open a new category in the forum “Cookbook”, where we could grant or limit access to all different things?
I’m just throwing in ideas here… 
Back to topics to list in the Cookbook:
List it or not?
Are you asking in reference to the topic of Sunrise/sunset automations or Combining/Refining automations. For the cookbook, I think both would be good topics… but that particular post might not be the best way to show and explain either of them.
That post is from before trigger IDs and conditions existed and when the Sun conditions were only kind of functional. A new user setting up the automation is likely just going to type “sun” into the trigger search, so any guide should include that method.
1 Like
I like it.
I’d agree that the post itself can be evolved too. 
2 Likes
Not; the concepts it presents are valid but its examples are outdated.
2 Likes
Ok, ok, I’ll admit defeat! 
I just love the concept it shows, it’s a very good and elegant example, on how to evolve ones automations. But yes, the examples are outdated.
Maybe someone would be willing to re-write or update it? 
hint hint
1 Like
What on earth is Py-spy? 
A live profiling tool GitHub - benfred/py-spy: Sampling profiler for Python programs Used for debugging slow code?
Not sure where you’re going with this…
My feeling is that Cookbook posts do need to be in Community Guides, so that anyone can edit them. Do you want to restrict editing to “team Cookbook”?
Does it belong in “A collection of posts on how to perform common tasks and deal with common problems”? The Cookbook’s going to end up just another Community Guides if we’re not careful. Also, isn’t it a custom add-on?
I’m trying to find a way, to use a bit more than the first post of a topic, as I think, we loose people, if we can’t find a way to make it more newbie friendly.
My personal not-good example is the start page of ESPHome. I can’t find anything, the sheer mass of devices, components and what not overwhelms me sometimes.
As the name says, Cookbook, and we need to find a way, to bring that into a topic or something similar.
No. It’s for development and as nothing to do with a Cookbook. It would belong to a dev category or even better, to a dev cookbook.
Yep, as I said above. That’s why I’m looking for ways around these limits, but keeping in mind, that we don’t want to loose the audience - new and not experienced users.
its The tool that Nick (Bdraco) always asks you to run if you have performance issues and troubleshooting is required … and refers to this Guide.
(its not for developing, it really is for troubleshooting to be able to hand the devs the numbers to actually do that for your instance)
since it needs to be done on the container and not from inside the generic HAOS command line, people always have trouble installing it.
hence the community guide to make life a bit easier
It essentially is an extension of Nicks own post Home Assistant Cookbook - Discussion Thread - #147 by MaxK
A fine community guide, but isn’t this well outside the scope of a cookbook? As well as being a custom add-on, which we agreed quite early on shouldn’t be included.
For this series we are limiting topics to items directly related to Home Assistant Core & Frontend, and not individual Custom Integrations, Custom Themes, Dashboard Items, Add-ons or Blueprints. Consider starting other lists for those.
Anyone else have any thoughts?
4 Likes
Maybe the problem is that we’ve been recycling too many posts from elsewhere, when in fact they need to be specially written.
2 Likes
Im fine with leaving it out.
its not strictly an add-on though (at least in the Add-on definition of the add-on store).
Maybe that is even the whole point of adding it, because if it were an add-on, it would have been much simpler…
Ill leave the decision up to you, and apologize for being too fast to add in that case