Slot control

​

Switch device slot

​

Path parameters

​

Response

​

Example: Switch to secondary slot

curl -X POST "http://localhost:8080/api/slot/device123/secondary" \
  -H "X-API-Key: dev-api-key-12345"

{
  "success": true,
  "deviceId": "device123",
  "activeSlot": "secondary"
}

​

Example: Switch to primary slot

curl -X POST "http://localhost:8080/api/slot/device123/primary" \
  -H "X-API-Key: dev-api-key-12345"

{
  "success": true,
  "deviceId": "device123",
  "activeSlot": "primary"
}

​

Slot switching behavior

​

Pre-switch validation

1. Device exists - Device ID is valid and device exists in database
2. Slot configured - The target slot has connection details configured
3. Slot availability - The target slot is reachable and healthy

​

Post-switch actions

1. Database update - Device activeSlot field is updated
2. Stream URL update - PocketBase hook updates stream URLs to use new slot’s host
3. Notification sent - Users are notified about the slot change
4. Health check reset - Failure counters are reset for the new slot

​

Automatic failback

• Health checks continue on both slots
• System can automatically switch back if the original slot recovers
• Manual switches take precedence over automatic failover temporarily

​

Error responses

​

400 Invalid slot

{
  "success": false,
  "error": "Invalid slot: must be 'primary' or 'secondary'"
}

​

404 Device not found

{
  "success": false,
  "error": "Device not found: device123"
}

​

400 Slot not configured

{
  "success": false,
  "error": "Secondary slot not configured for device123"
}

​

503 Slot unavailable

{
  "success": false,
  "error": "Target slot is not responding to health checks"
}

​

Use cases

​

Testing failover

# Switch to secondary
curl -X POST "http://localhost:8080/api/slot/device123/secondary" \
  -H "X-API-Key: dev-api-key-12345"

# Verify stream is working
# ...

# Switch back to primary
curl -X POST "http://localhost:8080/api/slot/device123/primary" \
  -H "X-API-Key: dev-api-key-12345"

​

Maintenance mode

# Move to secondary before maintenance
curl -X POST "http://localhost:8080/api/slot/device123/secondary" \
  -H "X-API-Key: dev-api-key-12345"

# Perform maintenance on primary connection
# ...

# Return to primary after maintenance
curl -X POST "http://localhost:8080/api/slot/device123/primary" \
  -H "X-API-Key: dev-api-key-12345"

​

Load balancing

# Switch half of devices to secondary
for device in device1 device3 device5; do
  curl -X POST "http://localhost:8080/api/slot/$device/secondary" \
    -H "X-API-Key: dev-api-key-12345"
done

​

Integration with health checks

• Manual override - Manual switches are respected by health checks
• Continued monitoring - Health checks continue on both slots
• Automatic recovery - If enabled, system can auto-switch when conditions improve
• Status visibility - Use health check endpoints to monitor both slots

​

Slot configuration

​

Primary slot

• host - Primary connection hostname or IP
• phone - Primary phone number for cellular connection

​

Secondary slot

• secondSlotHost - Secondary connection hostname or IP
• secondSlotPhone - Secondary phone number for cellular connection
• autoSlotSwitch - Enable automatic failover (optional)