Custom sensor names or customizable placeholder for notifications

[we5]

Checklist

• I checked for similar existing requests (both open and closed) before posting.
• My request is generic, other users may benefit from it too.

Proposal

I use the built-in Automation to send notifications of arming went wrong. Up until recently I included the room in the entity names, but started to get rid of it for showing it without redundancy on automatic dashboards.

Unfortunately I cannot rename the sensors for use in Alarmo and there is also no way of defining the naming scheme for the open_sensors variable.

So my proposal is to have:

• An Alarmo-specific name for the sensor
• A general template for the open_sensors variable

Additional info

It would be nice to decide for example a scheme like: {name} ({arrea})

[nico97118]

Hi @we5

This has been proposed in #1404 and @nielsfaber explained he didn't want to add such a feature in alarmo.
Concerning the open_sensors scheme, I am not sure it would make sense to add this in open_sensor and make this attribute more complex

I'll wait and see @nielsfaber 's follow up on this

[we5]

Sorry, I totally missed this one. I only searched for open issues. My bad.

However the point is quite the same. Originally I used a custom automation and template for the open sensors but switched to the Alarmo thing for sake of simplicity. Guess i have to go back then, because „window prevented arming“ is not a good hint in the notification. And renaming is not an option because the new dynamic dashboards also do not allow that.

I wish HA would come up with a global way to get such a name. Like „Fully qualified entity name“ which holds all infos that are now only shown correct in dropdowns and such. And they should have a scheme customization for that FQEN

Sorry again for not checking twice.

[nico97118]

@we5 no worries, it happens sometimes. It's already nice that you tried to verify 😄

Concerning your point. I understand it's tempting to simplify "friendly name" to things as simple as "window" and rely to their area to identify them more precisely.

However, the data structure of HA is not really designed this way .. Entities does not contain the area they are affected to. so you need to search all areas and check if the entity you're looking for is inside.

Well, it's doable, but it's a bit tricky and annoying to resolve this on Alarmo's side.

I'll wait to know @nielsfaber thoughts about this. May be he is interested in creating a new wildcard {{ open_sensor_with_area}} (or something like that) that would contains the friendly name of sensor beside the area it is in.