Thanks,
I recall the android action, yes sadly it doesn’t help here. I’ve just searched for anything related to markdown, however couldn’t find anything either. I’ve investigated the different areas of the Home Assistant UI (lovelace, developer tools > states, settings), there doesn’t seem to be a preexisting option (at least it is not used as far as I can see).
REST APIs return JSON. Not really the same thing.
Fwiw @ThomDietrich I can’t find the markdown thing either. Maybe I just imagined it. Sorry about that.
http://homeassistant:8123/history?entity_id=sensor.your_sensor&start_date=2022-09-19T14:00:00.000Z
You can get the link by right clicking on the show more(mehr anzeigen in the image in post before mine)
It can be logbook instead of history
its a shame you can’t use the “m” shortcut though
1 Like
Indeed! That is a good discovery.
Sadly still doesn’t solve my use case as I want to be able to control and manage the entity after following the link…
Hmm you could potentially go straight to the devices page… It’s just a url.
The popup window is different because it’s a popup…
http://homeassstant:8123/config/devices/device/deviceIDorsoemthign
Although at that point you could also go to a lovelace view…
Good idea, sadly I have an entity_id, not a device :-/
I think there are ways to programmatically identify the device an entity belongs. That would be a solution for me… if every entity indeed belonged to a device, which isn’t the case 
Thanks for all your suggestions! Feels like this is indeed not solved yet. If you believe it shouldn please Vote on this feature request 
hmm not sure I see the use-case honestly.
If it doesn’t have a device… make it a device?
It looks like a mqtt sensor, just make it auto discovery one, you will be able to link to the device page.
Or just set up what you want to see on a lovelace view and look at that
alert rpi is hot
goto
rpi-lovelace (view graph…Turn on server room fan)
you could even start here…
edit… you are basically requesting a deep link to developer state page… seems counter productive when you could actually make a nice lovelace view with all the info from different entities you want.
This went a bit off-topic. Yes your workaround would be a solution if all entities had a device and hopefully, eventually, the Home Assistant world will have matured that far. However clearly this shouldn’t block short-term quick wins. Let’s put your devices idea to the side for a second.
Even if there was an over-engineered workaround (devices, custom lovelace ui, some custom component, …), that’s hardly an adequate solution. The original request was for a “Direct URL to entity details”. I can think of numerous use cases why something as simple as that makes sense. I will intentionally only list one (not mine, but probably the one everyone can relate to):
“Hey Admin, I had to realize that this switch doesn’t work anymore. Could you have a look? Thanks”
2 Likes
I am the admin… in this case, as I look after the entities and home assistant.
I wouldn’t want to link this externally to say github, I would link to whatever the entity relates to eg. mosquitto or an addon.
on the other hand… my wife wouldn’t link it to me either. She would say the tv isn’t working you broke it again.
in fact she has limited access to this area as I wouldn’t want her to rename things etc.
She has her own lovelace page with stuff she uses.
I’m pretty sure they’re envisioning HA sending you (the admin) a notification with that link. Like if say a switch became unavailable for 5 minutes HA would send the admin of the system a notification like this
“Hey Admin, I had to realize that this switch doesn’t work anymore. Could you have a look? Thanks”
With a link that takes you to the more info view of the entity. To see when it broke and possibly fix it.
Or at least follow other links to fix it in the related tab. Not much fixing can be done from the more info popup unless the problem is that the name or icon changed randomly.
1 Like
Yeah i did get that impression…
It is sort of an compelling argument…
Except
-
It only applies to manual entities as the others can in theory do this…
-
if they are manual entities… Send me the yaml lol, assuming I was remote and not getting yelled at.
-
it would be from an admin account to admin account. Non admins don’t have access to developers/states. I actually have to check that, it has been ages since I logged into my wife’s account.
-
non admins are going to see the entity in lovelave to even notice it is broken… They could link the lovelace url… Or yell at me.
-
non admins like my kids shouldn’t be near stuff they can break.
-
any other reasons seem like they could be automated anyway
-
I certainly wouldn’t link an entity externally, even if someone else could log in.
I totally vote for this feature.
This could be implemented as an extension of the default action framework.
Basically to add an entry so that, when “more-info” or “toggle”, an attribute with the target entity for such actions can be defined.
By adding that, then there’s multiple ways to use that across Home Assistant, supporting hopefully OP use case and many more like post 84631 or 160476
Thanks!
These can already be done without this feature request. The posts have the answers in them.
84631 how-to-create-a-button-linking-to-another-ha-tab-or-view
160476 open-more-info-of-an-other-entity-climate-at-tap-on-a-glace-temp-sensor
Fair enough for the 84631 is slightly out of topic, but 160476 is a HACS solution, and is not a complete one as it only works on browser that have been “registered”, which is a browsermod only thingy.
The idea here would be to be able to develop a more-info home assistant standard action that instead of the parent entity opens another entity more-info popup. With the ‘proposal’ in the other thread the answers need to go device per device enabling the solution which creates a dependency on its implementation and is not scalable. Imagine all hass solutions required you to rework them for every single device accessing the lovelace dashboards!
So still thinking that should be solved through new feature only.
Just an FYI, this request is about being able to send someone a URL that when followed opens HA with a more-info pop-up of a particular entity in focus.
So I’m not entirely sure how actions in a card in a dashboard are related. You can certainly put a button in an HA dashboard that opens more-info or a particular dashboard/panel, that’s not what this is about.
This is about HA sending you a text message or something with a link. Receiving that link on some random non-HA channel and following it to a more-info pop-up.
Right. So like see here a link would’ve been really handy. Like the whole URL instead of just the random number at the end…
EDIT: I’m realizing this may have been you making a point. Like this is what we have to do today (text an entity ID to copy and paste) instead of sending a nice link. If so, props.
1 Like
What advantage does the url achieve here though(if it doesn’t exist). I could already link to something in my tap action. I may have to make it and it wouldn’t be scalable sure. I also don’t need someone to send me a link.
They can send the friendly name or entity_id and I can find what I need for debugging.
If it is for the intent of sending debug information to an external Admin… then to who and how much are they charging to supply a support and helpdesk feature?
The feature request could be … make custom-card an inbuilt-card. Pretty sure that has been covered.
It also goes back to my point of most of this request can already be done in lovelace.
type: custom:button-card
entity: switch.garage_reed
icon: mdi:garage
lock:
enabled: true
unlock: tap
show_state: true
state:
- color: rgb(255, 0, 0)
icon: mdi:garage-open
name: Garage Open
styles:
card:
- animation: blink 2s linear infinite
value: 'on'
- color: rgb(0, 205, 0)
icon: mdi:garage
name: Garage Closed
value: 'off'
- color: rgb(255, 0, 0)
icon: mdi:garage-alert
name: Garage Offline
spin: true
value: unavailable
tap_action:
action: call-service
service: switch.turn_on
service_data:
entity_id: switch.garage_door
@CentralCommand I was trying to avoid your edit of the link too…
Although enough info was actually given for me to quickly find it too…
Here is something that helped me Introduction | Home Assistant Companion Docs
The companion app on Android supports entityId:... URLs which do exactly what this topic is about - opens the specific entity more-info dialog in the app. Unfortunately it’s not a fully qualified URL like some people here are asking for but I’m sure it’s going to be good enough for some of you.
Wonder why the IOS app doesn’t support this, damn.
Sorry, not sure why I didn’t get a popup before about this replies and just came across this.
The thing is that the popup of more-info is that, a pop-up. As such, it requires to first navigate to some page, and then perform some action. your link would then need to navigate to some specific dashboard/view of your HA, and then open the popup. So your receiving users would still need to load such view first. I agree adding something like the ‘#entity-id’ at the end which is used in http to scroll to specific locations in a page would be something that could fit your case.
But then again, given you already have to navigate to a HA view, why not send your recipient a link to the history dashboard which allows for sharing specific entity ids if you don’t want users to interact with a lovelace dashboard?
Currently I can send the following https://homeassistant.mydomain.com/history?entity_id=sensor.aqara_temperature&start_date=2024-05-16T08%3A00%3A00.000Z&end_date=2024-05-16T11%3A00%3A00.000Z and that would navigate directly to the same data as in the more-info view (except attributes).
PD: Apologies, I didn’t add a link to those posts in my Original post because I didn’t had the forum rights to add multiple links.
1 Like