WebSocket Server

The dice-rs-ws crate provides a WebSocket and REST server for exposing GoDice events over a network API.

Running

cargo run -p dice-rs-ws

The server starts on 0.0.0.0:3000.

POST /api/scan

Returns a JSON array of discovered devices:

[
  {
    "address": "AA:BB:CC:DD:EE:FF",
    "name": "GoDice_AAABBCC_O_v04",
    "rssi": -45
  }
]

POST /api/connect
Content-Type: application/json

{
  "address": "AA:BB:CC:DD:EE:FF",
  "dice_type": "d6"
}

Returns a session ID:

{
  "session_id": "abc123"
}

dice_type is optional. Accepts: d6, d20, d10, d10x, d4, d8, d12.

POST /api/disconnect
Content-Type: application/json

{
  "session_id": "abc123"
}

POST /api/led
Content-Type: application/json

{
  "session_id": "abc123",
  "led1": "FF0000",
  "led2": "00FF00"
}

GET /api/battery/:session_id

GET /api/status/:session_id

POST /api/calibrate
Content-Type: application/json

{
  "session_id": "abc123"
}

Connect to ws://localhost:3000/ws to receive a real-time stream of DiceEvents as JSON:

{
  "kind": "Stable",
  "face": 6,
  "acceleration": { "x": 64, "y": 0, "z": 0 }
}

{
  "kind": "RollStart"
}

{
  "kind": "Disconnected"
}

The server uses axum with tokio. For production deployment, consider running behind a reverse proxy (e.g. nginx) with TLS termination.