APRS
The aprs (Automatic Packet Reporting System)
Configuration
To enable APRS tracking in Home Assistant, add the following section to configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file.
After changing the configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file, restart Home Assistant to apply the changes. The integration is now shown on the integrations page under Settings > Devices & services. Its entities are listed on the integration card itself and on the Entities tab.
# Example configuration.yaml entry
device_tracker:
- platform: aprs
username: FO0BAR # or FO0BAR-1 to FO0BAR-15
callsigns:
- 'XX0FOO*'
- 'YY0BAR-1'
Configuration Variables
Your callsign (or callsign-SSID combination). This is used to connect to the host. Note: Do not use the same callsign or callsign-SSID combination as a device you intend to track: the APRS-IS network will not route the packets to Home Assistant. This is a known limitation of APRS packet routing.
A list of callsigns you wish to track. Wildcard * is allowed. Any callsigns that match will be added as devices.
Verified connections are only required to send data to the APRS-IS network, which the aprs platform does not yet do.
However, you are free to verify your connection if you know your APRS password.