Saltar al contenido principal
Version: Next

SOS MQTT

SOS alerts ingested over MQTT (not HTTP). Uses the same broker gate as telemetry: MQTT_SOS_BROKER_URL must be non-empty (see eixam-platform .env.example). Configure the ingest topic with MQTT_SOS_TOPIC (default sos/alerts). The API subscribes to that topic only. Incident lifecycle notifications to mobile clients are published by the API under MQTT_SOS_EVENTS_TOPIC_PREFIX/{external_user_id} (default prefix sos/events; each {external_user_id} segment is URL path–encoded). That outbound path is for subscribers, not for ingest. Publishers send SOS JSON to MQTT_SOS_TOPIC (default sos/alerts). Body matches SOSMQTTAlert / SDKSOSTriggerRequest (required timestamp, latitude, longitude, altitude). QoS 1; retain false.