Block a user
A failed upload permanently deletes the recording: no retry, no disk spool
Edge dashboard can't tell 'broker refused' from 'broker unreachable' — mqtt_manager exposes no last connect error
Fixed in 1b4fcef, merged as c57a5b9 (PR #47).
Upload spool + retry, analog noise squelch, MQTT error, Discord pause (node-26#44 #46 #21 #34)
c57a5b9068
Merge pull request 'Upload spool + retry, analog noise squelch, MQTT error, Discord pause (node-26#44 #46 #21 #34)' (#47) from fix/44-upload-spool into main
5983ae27be
Fix stale log text for rejected uploads: 403 is now retried, so only 400/413 reach it (node-26#44)
a4a575ec9f
op25: pin gr310 to 5b58335; analog defaults to OP25 noise squelch (node-26#46, node-26#29)
5983ae27be
Fix stale log text for rejected uploads: 403 is now retried, so only 400/413 reach it (node-26#44)
a4a575ec9f
op25: pin gr310 to 5b58335; analog defaults to OP25 noise squelch (node-26#46, node-26#29)
1b4fcefbf2
mqtt_manager: expose last connect error; health tells refused from unreachable (node-26#21)
Upload spool + retry, analog noise squelch, MQTT error, Discord pause (node-26#44 #46 #21 #34)
call_start overwrites the call doc (merge=False) and can erase audio_gcs_uri when it lands after /upload
LLM-orphan gate's "type" veto fires on visibly content-free chatter (18/22 this window)
incident_correlator fast/thin path has the same dispatch/tactical name-guess as the #115 escape hatch, but it changes link decisions
LLM correlation tier sees the whole-call transcript for every scene, so it cannot separate scenes and pays N times for one prompt
Already fixed on main in ef1e3d7 (server-26#102): the LLM tier now reads the scene's transcript, not the whole call.
LLM correlation tier sees the whole-call transcript for every scene, so it cannot separate scenes and pays N times for one prompt
LLM-orphan gate's "type" veto fires on visibly content-free chatter (18/22 this window)
Already fixed on main in 3f69879: the police-channel default no longer types content-free chatter.
incident_correlator fast/thin path has the same dispatch/tactical name-guess as the #115 escape hatch, but it changes link decisions
Already fixed on main in b188485 (removed is_dispatch and the tactical fit path). Found during the 2026-10-27 correlation simplification.
Calls recorded during a local override upload under the C2-assigned system_id
Not fixed on branch fix/44-upload-spool: a node-only fix can't be complete. C2's mqtt_handler._on_call_start sets the call doc's system_id from the node doc's assigned_system_id, not from anything…
/upload: a late (spooled) upload is correlated against now, not the call's started_at
/upload has no idempotency: a retried upload re-runs Whisper/Gemini/correlation on the same call_id
Correlation: rules first, one cheap LLM call only when ambiguous; remove the cheap/smart consensus tiebreak
Alerts: confidence gate before any push alert (Discord/webhook) — avoid the CrimeRadar false shots-fired failure
Transcription: move to an OpenAI-compatible cheaper provider (Groq whisper-large-v3-turbo) with a domain vocabulary prompt