My issue is that my own beacon never shows up on aprs.fi, even though it transmits regularly.

[Sergej Beresteckij UA6ATG]

Hi Craig and the group,

I’ve set up a DigiPi digipeater running a very similar config to the template. The digipeating part works fine — I can see packets being repeated on RF. My issue is that my own beacon never shows up on aprs.fi, even though it transmits regularly.

Here are the relevant parts of my config:

text

MYCALL UA6ATG-2 IGSERVER noam.aprs2.net IGLOGIN UA6ATG-2 17573 PBEACON compress=1 delay=00:05 every=20:00 symbol="digi" overlay=1 \ lat=44.0909 long=39.1347 via=WIDE2-1 comment="UA6ATG WIDE1 Digi" DIGIPEAT 0 0 ^WIDE1-1$ ^WIDE1-1$ IGTXVIA 0 WIDE1-1,WIDE2-1 FILTER 0 0 ! d/UA6ATG-2 & ! b/UA6ATG-2 FILTER IG 0 ( t/m & ! g/BLN* ) IGFILTER t/m/UA6ATG-2/160 b/UA6ATG

My theory is that FILTER IG 0 ( t/m & ! g/BLN* ) is the culprit for two reasons:

1. The 0 timeout might disable the RF→IS IGate path entirely in DigiPi.

2. The expression only passes t/m (messages), but never t/p (position packets), so my beacon would never be gated to the internet even if it were heard.

I changed it to:

text

FILTER IG 30 t/p

and updated IGFILTER to:

text

IGFILTER t/p/UA6ATG-2/160

Am I on the right track? Is FILTER IG <timeout> t/p the correct DigiPi syntax for gating position packets from RF to IS? I couldn't find detailed documentation on the filter expression syntax specific to DigiPi.

Also, a small separate question: I noticed the config parser throws an error on IGATECALL — am I correct that DigiPi does not support this command and handles IGate activation differently from vanilla Direwolf?

Thank you for any clarification!

73,

[Craig]

the digipeater does not report itself over the internet (unlike the APRS TNC/igate) - it's
beacons go out on RF and depend on some remote station to gate it to aprs.fi .   Digipeater
is fully off-grid, but will igate stuff to the internet if internet is available.

if it helps,
-craig

[Scott Sheppard]

On a related note to this thread 

KJ4ZZB-8 audio level = 56(14/8)    ___||||__

[0.4] KJ4ZZB-8>APAT81-1,WIDE1-1,WIDE2-2:!3412.73N/10849.:0E&166/000/A=000000Thanksgiving half Marathon Pace KJ4ZZB

[0H] KJ4ZZB-8>APAT81-1,KJ4ZZB-2*,WIDE2-2:!3412.73N/10849.:0E&166/000/A=000000Thanksgiving half Marathon Pace KJ4ZZB 

So here I have a radio at KJZZB-8 HT sending an APRS packet line (0,4) . 

In this case the Digipi at KJ4ZZB-2 detects the packet and digipetes it. See line (0H) 

Since I gate is NOT enabled KJ4ZZB-8 is not sent to APRS-IS event thought the digipi is wi fi connected to a Starlink Lite. 

I have KJ4ZZB-2 on the dipipi

I think but am not 100% sure then that for KJ4ZZB-2 to show up on APRS.FI I need to be picked up on another I gate (say W4BOC-1) and then sent to APRS-IS -> APRS.FI 

This is shown as 

Last position:	2026-05-14 21:12:22 EDT (3m48s ago) 2026-05-14 21:12:22 EDT local time at Griffin, United States [?]
Device:	WB2OSZ: DireWolf
Last path:	KJ4ZZB-2>APDW18 via WIDE2-1,qAR,W4BOC-1  At the moment it is 21:12 as I write this.

Scott Sheppard

732 861 3383 

sshe...@bellsouth.net

KJ4ZZB Call Sign

--
You received this message because you are subscribed to the Google Groups "DigiPi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digipi+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digipi/584d2f4e-ec21-4dcd-9e2d-7c753ecdf247%40gmail.com.

[Craig]

Hi Scott,

Digipeater will gate to internet if there is an internet connection to the APRSIS
servers (northamerica round robin).  Many of these servers are full, so it can
take a few minutes to connect.  See PktLog for "now connected to".

W4BOC-1 hears your digipeater (KJ4ZZB-2) on RF and is gating your digipeater
beacon.

https://aprs.fi/?c=raw&call=KJ4ZZB-2

This is your APRS TNC/igate (route is TCPIP*):

2026-05-13 07:34:15 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2RDU:!R=Dc{92lK&  ! DigiPi http://digipi.org/
2026-05-13 09:35:00 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2MCI:!R=Dc{92lK&  ! DigiPi http://digipi.org/
2026-05-13 09:53:38 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2TEXAS:!R=Dc{92lK&  ! DigiPi http://digipi.org/
2026-05-13 10:02:42 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2VAN:!R=Dc{92lK&  ! DigiPi http://digipi.org/
2026-05-14 13:02:19 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2MCI:!R=bU192lm&  ! DigiPi http://digipi.org/
2026-05-14 13:51:14 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2LANE:!R=bU192lm&  ! DigiPi http://digipi.org/
2026-05-14 13:55:08 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2SJC:!R=bU192lm&  ! DigiPi http://digipi.org/
2026-05-14 14:00:25 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2LANE:!R=bU192lm&  ! DigiPi http://digipi.org/
2026-05-14 14:07:28 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2CAEAST:!R=bU192lm&  ! DigiPi http://digipi.org/
2026-05-14 14:19:19 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2LANE:!R=bU192lm&  ! DigiPi http://digipi.org/
2026-05-14 14:23:27 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2USANW:!R=bU192lm&  ! DigiPi http://digipi.org/
2026-05-14 15:22:01 PDT: KJ4ZZB-2>APDW18,TCPIP*,qAC,T2LANE:!R=bU192lm&  ! DigiPi http://digipi.org/


This is your APRS Digipeater (route is W4BOC-1 on RF)


2026-05-14 22:52:22 PDT: KJ4ZZB-2>APDW18,WIDE2-1,qAR,W4BOC-1:!b=bU192lm#  ! KJ4ZZB WIDE1 DigiPi http://digipi.org/
2026-05-14 23:12:21 PDT: KJ4ZZB-2>APDW18,WIDE2-1,qAR,W4BOC-1:!b=bU192lm#  ! KJ4ZZB WIDE1 DigiPi http://digipi.org/
2026-05-15 00:12:22 PDT: KJ4ZZB-2>APDW18,WIDE2-1,qAR,W4BOC-1:!b=bU192lm#  ! KJ4ZZB WIDE1 DigiPi http://digipi.org/
2026-05-15 02:12:21 PDT: KJ4ZZB-2>APDW18,WIDE2-1,qAR,W4BOC-1:!b=bU192lm#  ! KJ4ZZB WIDE1 DigiPi http://digipi.org/
2026-05-15 03:12:21 PDT: KJ4ZZB-2>APDW18,WIDE2-1,qAR,W4BOC-1:!b=bU192lm#  ! KJ4ZZB WIDE1 DigiPi http://digipi.org/
2026-05-15 04:12:22 PDT: KJ4ZZB-2>APDW18,WIDE2-1,qAR,W4BOC-1:!b=bU192lm#  ! KJ4ZZB WIDE1 DigiPi http://digipi.org/
2026-05-15 04:32:22 PDT: KJ4ZZB-2>APDW18,WIDE2-1,qAR,W4BOC-1:!b=bU192lm#  ! KJ4ZZB WIDE1 DigiPi http://digipi.org/


cool,
-craig
KM6LYW