Skip to content

Run your EchoLink server on a Raspberry Pi on BalenaOS.

Notifications You must be signed in to change notification settings

amingilani/PiLink

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

44 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

PARS EchoLink

BalenaCloud Push

This EchoLink Node Configuration is based on the article by AP2CJ.

Before running, ensure you have Docker installed. This build is meant to be deployed to a balenaOS host, and depends on a host with ALSA.

Required variables:

  • ECHOLINK_CALL: Echolink callsign
  • ECHOLINK_PASS: Echolink password
  • AUTH_KEY: The auth key for the device

Optional variables:

  • ENV: Set this to dev to trigger the station to call out its ID every 45 seconds
  • TIMEZONE: Set this to your local time. The default is PKT, but you may want UTC
  • PAPERTRAIL_HOST: Send logs to Papertrail for easier debugging.
  • PAPERTRAIL_PORT: Send logs to Papertrail for easier debugging.

Helpful commands:

  • aplay -l: to list available sound devices
  • dmesg | awk '/tty/ && /USB/ {print "/dev/"$10}'|tail -1: shows the USB device serial cable plugged in

Testing

Note that during testing you cannot run Balena Cloud environment variables. Pass them through docker compose or your Dockerfile.

Prelude:

  • Ensure you have a local development version of balena running
  • Ensure the local host has a USB sound card attached

To test, push to the host with:

balena push $balena_dev_device

TODO:

  • Fix environment variables in intermediate container
  • deploy via balena cloud
  • Finish dev
  • Expose public ports