POST /system/stop
Stop the current monitoring session and return to IDLE state. This allows recalibration without restarting the server.Response
Action status:
stoppedHuman-readable status message
New system state:
IDLEExample
cURL
Response
Behavior
When you call/system/stop:
- Stops background thread - Terminates calibration, monitoring, or fault injection
- Transitions to IDLE - System returns to initial state
- Resets metrics - Clears training samples and validation metrics
- Preserves data - Sensor history and models remain in memory
- Allows recalibration - You can now call
/system/calibrateagain
Non-Destructive:
/stop does NOT clear sensor data, baselines, or models. It only stops the active monitoring session. Use /system/purge for a complete reset.State Requirements
| Current State | Can Stop? |
|---|---|
IDLE | ❌ No (already idle) |
CALIBRATING | ❌ No (must complete) |
MONITORING_HEALTHY | ✅ Yes |
FAULT_INJECTION | ✅ Yes |
Status Codes
200- Session stopped successfully400- Invalid state (already IDLE or calibrating)
Use Cases
Session Management
End the current demo session cleanly
Recalibration
Prepare for a new calibration run
Testing Workflows
Reset between test scenarios
Dashboard Control
Stop button in the dashboard UI
State Transition Diagram
Comparison with Other Endpoints
| Endpoint | Stops Monitoring? | Resets DI? | Returns to State | Clears Data? |
|---|---|---|---|---|
/system/stop | ✅ Yes | ❌ No | IDLE | ❌ No |
/system/reset | ✅ Yes | ❌ No | MONITORING_HEALTHY | ❌ No |
/system/purge | ✅ Yes | ✅ Yes | IDLE | ✅ Yes |
/stop when you want to end the current session but keep data for analysis or reuse.
Related Endpoints
Calibrate
Start a new calibration session
Reset
Return to healthy monitoring
Purge
Complete system reset
System State
Check current state