Changed: aprs_status (published on the MQTT broker) now returns actual state of transmision (sending, retrying, send or failed) instead if just 'ready' and 'busy'.
Changed: aprs_status (published on the MQTT broker) now returns actual state of transmision (sending, retrying, send or failed) instead if just 'ready' and 'busy'.
## [1.1.0] - 2023-07-08
Added: APRS nodes can now be polled to get there actual status. An extra section in the YAML configuration file is added for this functionality.
#beacon_program: /usr/sbin/beacon # The external AX.25 beacon program => obsolete
#beacon_program: /usr/sbin/beacon # The external AX.25 beacon program => obsolete
# Poll the status af these clients (IMPORTANT: the calls must also be defined in the topics section)
poll:
- call: PE1RXF-5
- call: PE1RXF-6
- call: PE1RXF-8
topics:
topics:
# MQTT topic: 5GHz dish at workshop (must be unique name)
# MQTT topic: 5GHz dish at workshop (must be unique name)
@ -54,7 +60,7 @@ topics:
```
```
The configuration entry 'global:retry' sets the amount of APRS message retries we attempt before giving up. The configuration entry 'global:transmit_rate' sets the time between retries.
The configuration entry 'global:retry' sets the amount of APRS message retries we attempt before giving up. The configuration entry 'global:transmit_rate' sets the time between retries.
For now, the state of the outputs of the APRS nodes is not published to the MQTT broker. In the future, this could be implemented in the software. It is possible to poll the nodes via command '06' to get the current state of the outputs.
When a node is added to the poll: call: entry its status will be polled on a regular base. The poll rate is set in the global entry. This is the poll interval between every transmision. When three nodes are defined, a node is polled every 3*poll_rate seconds.