State of zone entity should be friendly name when Privacy == Zone Name Only

[tom-parkinson]

The problem

If "Zone Name Only" is set under the "Location Sent" setting of the Companion app, then the entity name of the zone gets shown on the person entity cards on the dashboard. This behaviour is inconsistent with the "Exact" location sent setting, which shows the friendly name of the zone.

In this example, kids have the “Location Sent” to “Exact” under Privacy in the app and for adults to “Zone Name Only”.
The dashboard with simple person entities shows correctly “Home” and “Away” for all. However, once in a pre-configured zone:

• kids: it displays the zone’s friendly name, e.g. “School”
• adults: it displays the zone’s entity, like “kids_school” instead of “School”.

There's a forum discussion thread with several users about this. It was also submitted as an issue to the frontend repo but no problems reported there.

What version of Home Assistant Core has the issue?

2023.12.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

State and attributes of the privacy-enabled person as well as the zone when issue appears:

[s0ftice]

it seems the screenshot got lost when you copied the post from frontend. I added it here again for everyone's convenience.

[karwosts]

Just to let you know as this was filed without an integration URL it does not get tagged or notify codeowners and it will be less discoverable.

I'm not sure if this should be device_tracker or mobile_app, but either of those would probably have been better than nothing. I think the only way to fix would be to close and open a new ticket (or you can just wait and see).

[tom-parkinson]

Thanks @karwosts for the heads up. I've opened a new issue.