… that’s a custom card…
that was custom… custom_ui… the code calling it was custom… everything about that is custom. I’m not sure what you aren’t understanding.
Firstlt, I’m not “man”, secondly where do you see the custom card mentioned? thirdly, how do you not understand the words “is no longer supported”. This means it WAS supported at some stage
1 Like
No, that is all under the hood code. There is no “supported” or “unsupported”. You’re original post was talking about using customize.yaml to define more info. That was 100% a custom card / code.
Also even if it was from custom-ui, it was in the core documentation at some point because that’s where I followed along from. It now being unsupported and the fact the custom-ui doesn’t offer this (from what I can tell) has remove that capability which would’ve resulted from under the hood changes
https://developers.home-assistant.io/docs/frontend_creating_custom_ui.html
The dead link was most likely the original I was folllowing many years ago
Sorry, you’re just not making any sense.
Here’s the current link to creating custom ui’s. The custom UI docs are now a whole section instead of just a page, so there’s no direct link. This links to the first section:
You can override more info if you know how to develop custom cards.
History explorer does just that with the history tab on more info.
No, I just think you like to spar…
I guess this guy makes no sense aswell.
I literally provided evidence that you’re ignoring. There was a thread from the official frontend repo supporting everything I’m saying. Because it doesn’t make sense to you then I guess you’re not the right person to respond. I’m not talking about documentation from 2023, there’s no need to provide information where I’m talking about things from years ago lol
1 Like
I also never said the core did, I said the core documentation did. I even said it could’ve possibly been from custom-ui but that point is moot. The documentation has wiped it off the map. Simple as that.
Call them random PR’s or whatever but they’re literally from the OFFICIAL repo with OFFICIAL staff responding 
You literally said none of that in that post. That’s why I’m having this convo with you. We wouldn’t be here if you said that.
Please step back and look at your original post. My response was to that. All my responses were to that.
Your responses and my responses has evolved from the original post and you still fixate on the original? wth
Because that was the topic… Yaml more info pages. You said it first. I replied, then you went on this ridiculous tangent trying to prove me wrong like it’s a game.
I honestly don’t know what you’re aruging at this point anymore.
I’m simply pointing out this was not correct. You were never able to do this.
This is what I’m talking about. These links to random PRs and Issues prove none of that. Home assistant core never provided a YAML way to define a custom more info page.
No i just think you tried beat a dead horse and being condescending and claiming I’m not making sense while ignoring everything shown. You continued to respond although you’re probably not the right person to respond to it when your not familiar with it. Fact is, it was supported and documented. SIMPLE AS THAT lol
Furthermore you seem to want to get the last word in, so I’ll give you that because I don’t play childish games in having to be the one having the last say
I’m 100% familar with it. I’ve been using this software since 2015. You’re referencing a custom solution that worked years ago, acting like it was “common”.
Oh grow up.
BTW
and that was the original post and supposedly I never said that
It never went anywhere. It never existed as a core option.
Don’t bother, they literally do not understand and they are here to argue. Just move on.
1 Like