WTH is there no parent-child linkage scan feature prior to a delete operation

What I do miss most in HA is a tool with which checks and/or visualize the linkage between objects. Sort of a parent/child check/visualisation.

Important, for example, if you think that something is now superfluous and you can delete it, although it is unfortunately still needed as input for another object or is perhaps only displayed in the GUI.
At the moment you realize this after having deleted an entity, since something else fails.

Since so a popup in the delete process would be useful to indicate whether you are sure you want to delete the object since it got child object it serves.

Example: a power entity which is used as input for a riemann sum sensor. if yo delete the power entity you end up with a problem.
Getting the hint that the riemann does require the power entity might make you rethink about the delete operation.

Ideally, you would have a kind of tree view of which objects serve as input for other objects. This would also make it easy to recognize whether certain objects are created too laboriously and an unnecessarily large number of intermediate stations were required to create them, which increases the risk of errors as soon as one of them is unavailable.

That’s what Related entities are for.

image

Click the entity, click the 3 dots, click related entities.

Sort of a 1-way-street if I iddn’t miss something.

Tried it with a power entity.
it does show an automation which makes use of it.

But the other side was missing, the so called ‘parent’ linkage.

Same for the automation. It would have been nice to show all it’s parents utilised without the need to rush through the complete YAML code.

Relation isn’t a top-down thingy, is it?

They are shown in the automation, not sure where you were looking. 3 dots → info → 3 dots → related.

No, all my entities show their “parent” devices and associated automations. If anything, it’s a bottom-up relationship.

What they don’t show (at least for me) are their “siblings” - other entities under the same device. In the below example, there are 2 other entities (state & switch) which do not show up as related.

Well this is where things do differ on my end.

Things do work on one hand and do fail on the other which makes this feature something one can’t be sure, prior to deleting something.

This looks like a bug. I checked several entities in my insurance and I always get at least the integration. I haven’t found any that looks like in your example. Is this some kind of leftover after you somehow manually deleted things?

No I do think the locelace is simply not covered by the relation check, no matter from which side you look at it.

The cards in the daskboard won’t offer a relation check by their 3-dots menu nor does the relation check cover child links being inside the lovelace.

Means you could delete entities and find yourself with a broken dashboard.

Ah, you are talking specifically about the dashboards, yeah, I guess that one part is not covered in the “related”. I guess there could be a new section there, showing dashboard > view, where this entity is used. Indeed I don’t think this is listed anywhere at the moment.