Add D-STAR presence alerts (QuadNet/ircDDB source) and local dev mode

[jbburns]

Implements the D-STAR side of https://github.com/orgs/hamalert/discussions/17 (presence alerts for D-STAR: "callsign X is active on, or linked to, repeater/reflector module Y"), plus a one-command local development mode that made it testable.

What's new

D-STAR presence source (dstar.js)

• Tails the public "last heard" logs of QuadNet (openquad.net/ics/ics, HTTP Range tail) and ircDDB (live.ircddb.net:8080/jj3.yaws, line-number poll). Both feeds are normalized into one record shape and go through one shared dedupe cache, so a dual-homed gateway never produces two alerts.
• Each transmission is classified: voice → active event; a link command in UR (e.g. REF030CL) → linked event (and also active if held long enough to be voice, which is common); info/echo/unlink and other control commands never alert. Directed (callsign-routed) calls are ignored by default (ignoreDirectedCalls).
• One spot per callsign + node + reflector + event within dedupeInterval (15 min). Node/reflector identifiers are W4HFH-C / REF030-C; the module letter is optional in trigger conditions (REF030 matches all modules).
• Spots: source: 'dstar', mode: 'dstar', new fields dvEvent, dvNode, dvReflector, plus dvSuffix, dvDuration, comment (TX message), spotter (reporting gateway, falling back to the node's callsign).
• Frequency and band (dstar_nodes.js): the heard records carry the repeater module but no frequency, so the server keeps a directory of module → registered frequency built from QuadNet's gateway.php (about 5100 modules) and ircDDB's repeater.php (about 490 more), refreshed hourly and persisted like the Club Log cache. normalizeSpot looks up dvNode and sets frequency (then band derives as usual; frequencySource: 'nodelist'). In a live sample all 270 recent QuadNet nodes resolved. If a node is unlisted the band is guessed from the module letter (A 23cm, B 70cm, C 2m) and flagged bandIsGuessed; failing that band is "unknown". npm run dstar-nodes -- <node>... exercises the directory.
• New matcher conditions dvEvent, dvNode, dvReflector; notification params include the new fields; the simulator accepts D-STAR spots with or without a frequency (resolved from the directory when omitted).
• Fixes found along the way: the telnet notifier threw on spots without a frequency/spotter and the exception was swallowed silently (D-STAR telnet alerts were dropped); the app notifier is now skipped when APNS/FCM config is absent so the server can start without push credentials; Club Log lookups are skipped when no API key is configured.

Local development mode

• config_loader.js: every module loads config through it; ./config.js stays the default, HAMALERT_CONFIG=<file> overrides.
• config-local.js: committed, credential-free config (local Mongo/Redis on non-default ports, no push, no RBN/cluster logins).
• npm run local-dev (tools/localDev.js): starts clean mongo:7 and redis:7 containers (Docker or Podman), seeds a test user + two D-STAR triggers, optionally builds and starts the hamalert-web dev image (hamalert/hamalert-web PR), prints how to connect, and runs the server. See LOCAL_DEV.md.

Design notes / open points for review

• Privacy: this is presence, not DX spotting. ircddb.net only publishes users who sent VIS ON; QuadNet publishes everything, so HamAlert exposes nothing that isn't already public. The CQCQCQ-only idea from the discussion doesn't distinguish a QSO on modern D-STAR (both sides keep UR=CQCQCQ through a reflector), so the filter is "voice vs. control traffic" instead; alert wording is "heard on", never "is talking to".
• Both feeds are volunteer-run; a courtesy note to the QuadNet and ircDDB teams before this runs in production is being sent. Polling is one small HTTP request every 15 s per feed (ircDDB's own live-log page polls every 5 s) plus the two repeater lists once an hour, all with a HamAlert User-Agent.
• Live coverage: hotspots and gateways on QuadNet/ircddb.net. US Icom G2/G3 repeaters that report only to dstarusers.org are not covered.
• Thresholds (minVoiceDuration, minVoiceDurationLinkCommand, dedupeInterval) are config values and will want tuning against real traffic.

Testing

• Offline replay of 8.5 h of QuadNet log: 3603 records → 318 spots (159 active, 159 linked).
• End to end with npm run local-dev (Docker and Podman): simulated D-STAR spots reach the telnet notifier, Mongo and the Redis stream; the module-less REF030 condition matches REF030-A; live QuadNet/ircDDB spots flow through the pipeline.
• Web trigger editor and simulate page exercised in a headless browser against this server (see the web PR).

Screenshots

Terminal captures (server startup with both feeds priming, live D-STAR spots, telnet session receiving simulated alerts, dstar-test on the live feed) are attached below.

Companion PRs: hamalert/hamalert-web (trigger editor, docs, Alerts page, dev image) and hamalert/hamalert-app (rendering of D-STAR spots).

🤖 Generated with Claude Code

[jbburns]

[jbburns]

Update: third feed, rate limiting, dedupe, per-feed sources

Testing against live REF030/REF058 traffic showed that QuadNet and ircDDB never see DPlus/REF reflector activity: stations connected through hotspots and dongles report to neither network (zero callsign overlap between the two worlds in the same hour). This batch of commits addresses that and a number of things found along the way.

New feed: dstarusers.org. dstar.js now also polls https://www.dstarusers.org/lastheard.php (every 30 s, ~100 KB, fed by DStarMonitor on REF reflectors and Icom gateways). Rows with a module ("REF030 C …", "NS9RC B 440 MHz") become spots on REF030-C / node NS9RC-B. "Dongle User" rows are dropped: they are DPlus logins reported without a module, not transmissions (64 such rows in one hour matched 2 entries in the reflector's own Last Heard; when a dongle user keys up a proper module row follows). Fixture + --dstarusers-file replay in tools/dstarTest.js.

Source names the feed. Spots now have source: quadnet | ircddb | dstarusers (mode stays dstar), consistent with how other sources are named. Triggers with no source condition match all three.

Dedupe. One alert per callsign, event and place (reflector without module, else node) per dedupeInterval, keyed so the same transmission reported by two feeds collapses. Entries are compared on the records' own timestamps, so records primed at startup only suppress within their remaining window (previously a station heard shortly before a restart was silenced for 15 min after it). dedupeInterval: 0 disables it.

Rate limiter. The per-callsign+frequency/band+mode limits now also key on the D-STAR event and place, so "linked to REF030-C" no longer suppresses "active on REF058-E" from the same hotspot (all its events resolve to one frequency). New config.rateLimit.disabled (false in the template) for local development.

Smaller items. Reflector-module rows carry no band (the module label says nothing about the operator's RF band) and no location comment (it was the reflector's town); node-less spots get band: 'unknown' and a spotter fallback; the console spot line prints the place instead of "unknown" for such spots. config-local.js disables rate limiting and uses a 2-minute dedupe window for testing; LOCAL_DEV.md and README updated.

Tried and dropped. Resolving the module of dongle rows from the reflector's own dashboard: the dashboards differ per reflector (REF030 serves a static page over http and a socket.io app over https) and list dongle users as "listening" without a module until they transmit, at which point dstarusers.org reports the module anyway.

Permission-request emails to QuadNet, ircDDB and dstarusers.org are drafted and will be sent before this goes live.