-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Add sensors to the Traccar Server documentation #31624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
ec27618
162ce11
1910854
900a6c7
429c129
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -80,6 +80,7 @@ These device representations in Home Assistant will have [entities](#entities) a | |||||
The traccar server integration will create entities in with the following domains: | ||||||
|
||||||
- [Device Tracker](/integrations/device_tracker) | ||||||
- [Sensor](/integrations/sensor) | ||||||
|
||||||
For more details about each of these, see the sections below. | ||||||
|
||||||
|
@@ -103,22 +104,10 @@ State: | |||||
In addition to the custom attributes you can define in the Traccar Server integration options, the device tracker entity will have the following attributes: | ||||||
|
||||||
{% configuration_basic %} | ||||||
Address: | ||||||
description: If a position update has an address associated with it, this will be the address. | ||||||
Altitude: | ||||||
description: The altitude of the position update. | ||||||
Battery Level: | ||||||
description: The battery level of the device if defined. | ||||||
Category: | ||||||
description: The category of the device in Traccar if defined. | ||||||
Geofence: | ||||||
description: The name of the geofence the device is located in. | ||||||
Motion: | ||||||
description: If the device is moving or not. | ||||||
Speed: | ||||||
description: The speed of the device. | ||||||
Status: | ||||||
description: The status of the device in Traccar. | ||||||
Traccar ID: | ||||||
description: The ID of the device in Traccar. | ||||||
Tracker: | ||||||
|
@@ -127,6 +116,120 @@ Tracker: | |||||
|
||||||
{% enddetails %} | ||||||
|
||||||
### Sensor - Address | ||||||
|
||||||
The Traccar Server integration will create a [sensor](/integrations/sensor) entity for each device registered in Traccar Server to show the address reported by the Traccar Server. | ||||||
|
||||||
This entity is disabled by default. | ||||||
|
||||||
{% configuration_basic %} | ||||||
Name: | ||||||
description: The name of the sensor will be set to what you have named it in Traccar Server followed by Address. If your device is named "Millennium Falcon", this will be "Millennium Falcon Address". | ||||||
Entity ID: | ||||||
description: This will be a slugified version of the name. | ||||||
Unique ID: | ||||||
description: This will be the unique ID of the device tracker in Traccar Server followed by `position_address`. | ||||||
State: | ||||||
description: This will be the address reported by the Traccar Server, if geo detection is not configured this will be unknown`. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Should this be geofence? This is the only occurrence of geo detection I find here. or is this something else? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Geo detection is a setting that needs to be enabled on the server. |
||||||
{% endconfiguration_basic %} | ||||||
|
||||||
This entity does not have any attributes. | ||||||
|
||||||
### Sensor - Altitude | ||||||
|
||||||
The Traccar Server integration will create a [sensor](/integrations/sensor) entity for each device registered in Traccar Server to show the altitude reported by the Traccar Server. | ||||||
|
||||||
This entity is disabled by default. | ||||||
|
||||||
{% configuration_basic %} | ||||||
Name: | ||||||
description: The name of the sensor will be set to what you have named it in Traccar Server followed by Altitude. If your device is named "Millennium Falcon", this will be "Millennium Falcon Altitude". | ||||||
Entity ID: | ||||||
description: This will be a slugified version of the name. | ||||||
Unique ID: | ||||||
description: This will be the unique ID of the device tracker in Traccar Server followed by `position_altitude`. | ||||||
State: | ||||||
description: This will be the altitude in meters. You can select a different unit in the entity options if you want. | ||||||
{% endconfiguration_basic %} | ||||||
|
||||||
This entity does not have any attributes. | ||||||
|
||||||
### Sensor - Battery | ||||||
|
||||||
The Traccar Server integration will create a [sensor](/integrations/sensor) entity for each device registered in Traccar Server to show the remaining battery percentage reported by the Traccar Server. | ||||||
|
||||||
This entity is disabled by default. | ||||||
|
||||||
{% configuration_basic %} | ||||||
Name: | ||||||
description: The name of the sensor will be set to what you have named it in Traccar Server followed by Battery. If your device is named "Millennium Falcon", this will be "Millennium Falcon Battery". | ||||||
Entity ID: | ||||||
description: This will be a slugified version of the name. | ||||||
Unique ID: | ||||||
description: This will be the unique ID of the device tracker in Traccar Server followed by `position_attributes.batteryLevel`. | ||||||
State: | ||||||
description: This will be the battery percentage (level) as reported by the tracked device, if the device does not have a battery this will be unknown. | ||||||
{% endconfiguration_basic %} | ||||||
|
||||||
This entity does not have any attributes. | ||||||
|
||||||
### Sensor - Geofence | ||||||
|
||||||
The Traccar Server integration will create a [sensor](/integrations/sensor) entity for each device registered in Traccar Server to show the geofence reported by the Traccar Server. | ||||||
|
||||||
This entity is disabled by default. | ||||||
|
||||||
{% configuration_basic %} | ||||||
Name: | ||||||
description: The name of the sensor will be set to what you have named it in Traccar Server followed by Geofence. If your device is named "Millennium Falcon", this will be "Millennium Falcon Geofence". | ||||||
Entity ID: | ||||||
description: This will be a slugified version of the name. | ||||||
Unique ID: | ||||||
description: This will be the unique ID of the device tracker in Traccar Server followed by `geofence_geofence`. | ||||||
State: | ||||||
description: This will be geofence that the device is in, if you have overlapping geofences it will show the first one as reported by the Traccar Server. | ||||||
{% endconfiguration_basic %} | ||||||
|
||||||
This entity does not have any attributes. | ||||||
|
||||||
### Sensor - Speed | ||||||
|
||||||
The Traccar Server integration will create a [sensor](/integrations/sensor) entity for each device registered in Traccar Server to show the speed reported by the Traccar Server. | ||||||
|
||||||
This entity is disabled by default. | ||||||
|
||||||
{% configuration_basic %} | ||||||
Name: | ||||||
description: The name of the sensor will be set to what you have named it in Traccar Server followed by Speed. If your device is named "Millennium Falcon", this will be "Millennium Falcon Speed". | ||||||
Entity ID: | ||||||
description: This will be a slugified version of the name. | ||||||
Unique ID: | ||||||
description: This will be the unique ID of the device tracker in Traccar Server followed by `position_speed`. | ||||||
State: | ||||||
description: This will be the speed of the device in knots. You can select a different unit in the entity options if you want. | ||||||
{% endconfiguration_basic %} | ||||||
|
||||||
This entity does not have any attributes. | ||||||
|
||||||
### Sensor - Status | ||||||
|
||||||
The Traccar Server integration will create a [sensor](/integrations/sensor) entity for each device registered in Traccar Server to show the status reported by the Traccar Server. | ||||||
|
||||||
This entity is disabled by default. | ||||||
|
||||||
{% configuration_basic %} | ||||||
Name: | ||||||
description: The name of the sensor will be set to what you have named it in Traccar Server followed by Status. If your device is named "Millennium Falcon", this will be "Millennium Falcon Status". | ||||||
Entity ID: | ||||||
description: This will be a slugified version of the name. | ||||||
Unique ID: | ||||||
description: This will be the unique ID of the device tracker in Traccar Server followed by `devcie_status`. | ||||||
State: | ||||||
description: This will be one of the following; `offline`, `unknown`, `online`. | ||||||
c0ffeeca7 marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
{% endconfiguration_basic %} | ||||||
|
||||||
This entity does not have any attributes. | ||||||
|
||||||
## Examples | ||||||
|
||||||
So you set up the integration and it pulled in all your devices. Now what? Below are some examples of what you can do with the data provided by Traccar Server integration. | ||||||
|
@@ -137,7 +240,7 @@ In this section you will find some example automations that you can use to get s | |||||
|
||||||
#### Do something when a device enters a geofence | ||||||
|
||||||
The allows you to do something when the device `device_tracker.millennium_falcon` enters the defined geofence. | ||||||
The allows you to do something when the device "Millennium Falcon" enters the defined geofence. | ||||||
|
||||||
{% my blueprint_import badge blueprint_url="https://www.home-assistant.io/blueprints/integrations/traccar_server_device_enter_geofence.yaml" %} | ||||||
|
||||||
|
@@ -146,8 +249,7 @@ The allows you to do something when the device `device_tracker.millennium_falcon | |||||
```yaml | ||||||
trigger: | ||||||
- platform: state | ||||||
entity_id: device_tracker.millennium_falcon | ||||||
attribute: geofence | ||||||
entity_id: sensor.millennium_falcon_geofence | ||||||
to: 'Tatooine' | ||||||
action: | ||||||
... | ||||||
|
@@ -157,7 +259,7 @@ action: | |||||
|
||||||
#### Do something when a device are speeding | ||||||
|
||||||
The allows you to do something when the device `device_tracker.millennium_falcon` exceeds a defined speed. | ||||||
The allows you to do something when the device "Millennium Falcon" exceeds a defined speed. | ||||||
|
||||||
{% my blueprint_import badge blueprint_url="https://www.home-assistant.io/blueprints/integrations/traccar_server_device_speed_limit.yaml" %} | ||||||
|
||||||
|
@@ -166,14 +268,13 @@ The allows you to do something when the device `device_tracker.millennium_falcon | |||||
```yaml | ||||||
trigger: | ||||||
- platform: numeric_state | ||||||
entity_id: device_tracker.millennium_falcon | ||||||
attribute: speed | ||||||
entity_id: sensor.millennium_falcon_speed | ||||||
above: 1337 | ||||||
action: | ||||||
... | ||||||
``` | ||||||
|
||||||
If you want to include the speed in a notification, you can use the `{{ trigger.to_state.attributes.speed }}` template. | ||||||
If you want to include the speed in a notification, you can use the `{{ trigger.to_state.state }}` template. | ||||||
|
||||||
Partial example: | ||||||
|
||||||
|
@@ -183,7 +284,7 @@ trigger: | |||||
action: | ||||||
- service: notify.notify | ||||||
data: | ||||||
message: "The current speed of the Millennium falcon is {{ trigger.to_state.attributes.speed }}!" | ||||||
message: "The current speed of the Millennium falcon is {{ trigger.to_state.state }}!" | ||||||
``` | ||||||
|
||||||
{% enddetails %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think an example could be helpful here, as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we can not guarantee this, I think adding that can cause more confusion.
If you have to sensors that want the same entity ID, the second one to be loaded will get a
_2
suffix.