Logbook: Device trackers should use "became unavailable" for that state

[NoRi2909]

Checklist

• I have updated to the latest available Home Assistant version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

Device Trackers have three special strings for their Logbook messages:

frontend/src/translations/en.json

Lines 455 to 456 in 231ef4b

	"was_away": "was detected away",
	"was_at_state": "was detected at {state}",

frontend/src/translations/en.json

Line 475 in 231ef4b

"was_at_home": "was detected at home",

But when their state becomes unavailable the Logbook uses the middle string above, which is actually meant to be used with zone names, so we get

Was detected at unavailable

Here in a screenshot:

Describe the behavior you expected

This should be fixed by using the general Logbook message for that state instead:

frontend/src/translations/en.json

Lines 483 to 484 in 231ef4b

	"became_unavailable": "became unavailable",
	"became_unknown": "became unknown",

I'm including 'unknown' above as this might currently produce the similar

 Was detected at unknown

if that state is possible (?). Then this needs to be included in the fix.

Also reporting this because in translations these message combinations often produce even stranger results.

What version of Home Assistant Core has the issue?

core-2024.11.3