Upgrading past 1.26.0 (ASL3-Herald → AllStar-Herald rename): read this if anything broke

[N6LKA]

What changed

v1.26.0 renamed this repo from ASL3-Herald to AllStar-Herald (#47) and scrubbed the old asl3-herald naming out of every path/file on disk — install paths, config/state filenames, the systemd unit, sudoers file, and Allmon3/Supermon integration links all changed from asl3-herald to plain herald. Daemon code and config/state were also consolidated into one directory (/etc/asterisk/scripts/herald/, was two separate dirs before).

install.sh migrates all of this automatically. But a rename like this touches more than install.sh can reach on its own, and I hit every one of the gaps below live on my own node getting this out the door. If you installed or updated around 2026-08-09, please read through this list.

1. The in-app "Update" button silently did nothing on anything before 1.26.0

GitHub's tarball download always names the extracted folder after the current repo name, even through the old URL's redirect. Any pre-1.26.0 install has the old folder name hardcoded into its self-update step, so it can't find install.sh inside the tarball — the update does nothing, no error shown, and you're left on your old version.

Fix (one-time, can't be done from the Update button — has to be manual):

curl -fsSL -H "Cache-Control: no-cache" https://raw.githubusercontent.com/N6LKA/AllStar-Herald/main/install.sh | sudo bash

After this one run, the Update button works normally again going forward.

2. Allmon3 sidebar link broke after migrating (fixed in 1.26.2, but only for future migrations)

If you migrated on 1.26.0 or 1.26.1, install.sh correctly rewrote your menu.ini link target but never restarted Allmon3 to pick it up (Allmon3 caches menu.ini in memory at startup) — so the sidebar link 404'd, pointing at a page install.sh had already removed. 1.26.2 fixes this for anyone migrating from here on, but if you already migrated before 1.26.2, you need one manual restart to pick up the fix that's already sitting correctly in your menu.ini:

sudo systemctl restart allmon3

3. "File missing" errors on Tail Messages / Scheduled Announcements after migrating (also fixed in 1.26.2, same caveat as above)

Moving the config directory doesn't rewrite the absolute paths already stored inside herald.conf (each entry's File: line) or herald.state (playback history) — those still pointed at the old asl3-herald directory name even though the real WAV files had moved. 1.26.2 fixes this for future migrations. If you already migrated before 1.26.2, either:

• Edit and re-save each affected message in the web UI (regenerates the file and the path together), or
• Fix it directly:

sudo cp /etc/asterisk/scripts/herald/herald.conf /etc/asterisk/scripts/herald/herald.conf.bak
sudo sed -i "s#/etc/asterisk/scripts/asl3-herald/#/etc/asterisk/scripts/herald/#g" /etc/asterisk/scripts/herald/herald.conf
sudo sed -i "s#/etc/asterisk/scripts/asl3-herald/#/etc/asterisk/scripts/herald/#g" /etc/asterisk/scripts/herald/herald.state
sudo herald reload

4. Weather panel disappeared from Allmon3/Supermon if you use ASL3-SkywarnPlus-NG-Bridge

That's a separate project of mine with its own config pointing at Herald's weather.json — its default also referenced the old directory name. Already fixed there too (as of its own latest release). Either re-run its installer:

curl -fsSL https://raw.githubusercontent.com/N6LKA/ASL3-SkywarnPlus-NG-Bridge/main/install.sh | sudo bash

or edit /etc/asl3-swp-ng-bridge/config.yaml's JsonPath by hand and run sudo /usr/local/sbin/asl3-swp-ng-bridge.py once.

5. Node ID Generator — idrecording in rpt.conf

This one's entirely manual and always will be — it's your own edit to Asterisk's own config, install.sh has never touched it and never will. If you've got idrecording set pointing at Herald's node-id output, check it:

grep idrecording /etc/asterisk/rpt.conf

If it still says /etc/asterisk/scripts/asl3-herald/node-id/node-id, update it:

sudo sed -i "s#/etc/asterisk/scripts/asl3-herald/node-id/#/etc/asterisk/scripts/herald/node-id/#" /etc/asterisk/rpt.conf
sudo asterisk -rx "module reload app_rpt"

If that doesn't pick it up, a full sudo systemctl restart asterisk will.

The general pattern, if you've customized anything else

Herald's migration only rewrites what it directly manages (its own config and Allmon3/Supermon integration links) — not anything else you've pointed at a Herald-managed file using the old path. If you've got a script, cron job, or another program referencing /etc/asterisk/scripts/asl3-herald/... directly, it'll need the same one-time path update to /etc/asterisk/scripts/herald/....

Sorry for the bumpy rollout — happy to help if you get stuck, just open an issue or reply here.