Re: [DigiPi] Webchat isn't working on Beta3

[Craig]

Cool - thanks for the observation.

Does your callsign start with a digit?  (UK amateur?)

you callsign should have been poked into /home/pi/.config/direwolf-dashboard.yaml
during Initialiation.  I'm assuming you Initialized and rebooted?

-craig
KM6LYW

On 4/27/26 12:45, William Tracy wrote:

I can't get webchat to work in Beta3

If I run it in the command line I get an owner_callsign error.

pi@digipi:~ $ ./webchat.sh
A Required option is missing in the config file : value required for option owner_callsign in group [DEFAULT]
The "owner_callsign" option is required. It is used to identify the licensed ham radio operator responsible for this APRSD instance, which may be different than the "callsign" used by APRSD for messaging.
pi@digipi:~ $

--
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/cd3c2b0a-33c3-4122-a64d-54664c6f5a27n%40googlegroups.com.

[Gwen Patton]

Is the user in the dialup group?

-=-=-=-=-=-=-=-=-

73,

Gwen, NG3P

To view this discussion visit https://groups.google.com/d/msgid/digipi/a656e426-7843-4e7e-98ea-87f89735882b%40gmail.com.

[William Tracy]

Craig,

config/direwolf-dashboard/config.yaml has your callsign, but my lat/long. Initialization must have put my lat/long there, but it didn't change the callsign to my callsign.

I changed it to my callsign in .config/direwolf-dashboard/config.yaml and saved configuration. 

[William Tracy]

I re-installed DigiPi 2.1BETA3 from the download, configured it with the initialization, and this time did not restore local, flrig, fldigi, and config from filezilla backup.

Maps, webchat and and everything worked the way it was intended.

Don't restore backups. It clobbers something.

[Walter Boring]

This is most likely due to the new required owner_callsign by aprsd.  If you restored from a backup that happened in an earlier aprsd that didn't require owner_callsign, it most likely is missing.

aprsd is used for many things, webchat is one of them, but it's also used as a responder/bot that can have a callsign that isn't associated with a ham license, re: REPEAT, so 

owner_callsign was added to identify what licensed callsign owns the service when registering with the APRS registry service here:
http://aprs.hemna.com

cheers,

Walt

WB4BOR

To view this discussion visit https://groups.google.com/d/msgid/digipi/9034615c-b71a-4718-b198-ad366c701867n%40googlegroups.com.