Installing a kitchen and finding the units you bought don’t fit because it was ‘rigid thinking’ that the correct way round was to measure it before you bought the stuff?
Installing a pool in the back garden before you’ve dug the hole for it to go in?
Eating raw chicken because cooking it first is ‘rigid thinking’?
Clearly you don’t understand the difference between ‘rigid thinking’ and understanding that certain things have to be looked at in a certain order to get the correct results. Good luck to you sir.
All of your examples are of actions that require a specific order. But we’re talking about knowledge and you’re saying it’s wrong for me to ask a general question – that I need to start with what I want to do and see what it requires. I disagree.
My analogy would be, there is a town called Paris, Texas. Do any other states have a town called Paris? I don’t necessarily want to go there. I just want to know.
Anyway, the best solution would be if a search for service_data actually produced results.
And I apologize if “rigid thinking” offends. Perhaps it is not the best term for what I am trying to describe.
I did say that to find the answer to that question in the docs you had to phrase your question around the way the docs are organised. The docs are organised by major function, so you need to frame your question accordingly.
To use your example, if I google search “where is Paris?” I can guarantee you that the first result won’t be Texas (nor any other US state), so I would have to phrase my question correctly to narrow down the search to get the result I wanted.
Asking questions along with experimenting is how we learn. The op clearly wants to get a full grasp of yaml so he can get the most out of and make efficient use of it in ha.
To me it would make sense for the fields to be consistently named to make it intuitive to code. Why are there differences? I think the op was wondering the same
I agree that asking questions is how people learn. @petro answered the question in the very first reply to the thread, and I tried to explain how the documentation works so that the OP could efficiently find what he needed. Somehow that caused a tangent discussion.
As for why it’s different, you’d have to ask a frontend dev, but I think @petro’s explanation is likely to be correct.
It seems the rigidity is in the docs in that they can’t be effectively searched (except maybe by google). Not that I’m complaining. I appreciate everything that everyone does here, and I try to add whenever I can.
Read the docs, but don’t trust the search button.
It does seem counterintuitive that calling a service requires one thing in one place and something different elsewhere. It would be interesting to know if benefits for the current system exceed the benefits of uniformity, or if anyone has considered that question.
exactly this is a constant and continuous process and happening as we write this in many spots of the code, check the GitHub repo for issues, and discussion threads. Star, subscribe or what have you to see the notifications flooding your mailbox. Its what I do, and what I learn from the most, well, next to this community
The balance has to be found between improving code, which could have been there from HA’s early days, and hence the use of it in widespread user base, and the resulting breaking changes for that same user base when making that code more logical, or uniform.
So, don’t wonder if that’s happening, I’d counter: you bet!
