Device_Tracker - position "at home"

Configuration
1

Hi there,
I have a question about some device trackers in my system:

I recognized, that the value of some device trackers are not identical and I don’t know, if I just forgot to setup the device tracker somewhere?

the behave is even more strange in my default language german:

  1. Car will be shown as “available” with integration A
  2. Car will be shown as “Home” with integration B

my Phone and the phone of my wife will show “Home”…

image
image999×1103 69.8 KB

image
image1003×1114 70.3 KB

2

The issue might stem from differences in how each integration defines and reports the status of the device tracker.
can you give us more info about the integration ?

3

Hi,

one is “skodaconnect” - which is no longer in development

→ here, the car is shown as “at home”

the other is “my skoda”, which will replace the other one and is still in an early stage of development.

→ here, the car is shown as “available”

When I use the english language in HomeAssistant, both integrations are showing the same information:

image
image1011×799 50.5 KB

image
image1006×807 49.2 KB

therefore, I don’t really understand the difference, when I switch the language to german.

Also, in the development tools, both device trackers are showing the state “home”

4

The solution is as follows: Navigate to HA > File Editor > custom_components/myskoda. Inside this directory, locate the folder named translations and open the file de.json. Search for the following section of the code:

"device_tracker": {
    "device_tracker": {
        "name": "Standort",
        "state": {
            "home": "Anwesend",
            "not_home": "Abwesend",
            "vehicle_in_motion": "Bewegung erkannt"
        }
    }
},

Replace Anwesend with Zuhause (the German word for “home”) and Abwesend with the German word for “away.” Save the file and restart HA for the changes to take effect. Additionally, it’s strongly recommended to open an issue on the GitHub repository so this update can be implemented for others.

1 Like
5

thanks - but:
wtf… since when are states translated in custom components… :thinking:

this is why I did not consider the translations for this :smiley:

1 Like
6

You’re welcome! However, consider opening an issue on GitHub to ensure the translation can be corrected for others. If you update the integration, remember to reapply the changes to the file until the issue is officially resolved.

7

already did this as a feature / change request.
In my opinion, default states shouldn’t be translated by the integration at all.

You can do this, when having some states, that are not available in homeassistant itself - but device tracker, some of the binary sensors should not be translated by the integration to be aligned with the default translations.

1 Like