DDI Developer Docs

DDI is the unified device interface and SDK family for FlexGalaxy.AI. Devices integrate once with DDI; the gateway authenticates them and routes each supported capability to the responsible platform service.

Bindings are available for Python, Android/Kotlin and C, plus an emulator for testing without hardware. Source access is granted to authorized OEM and platform developers as part of an integration agreement; ask your FlexGalaxy.AI contact rather than searching for a public repository, because there is not one. These pages are the contract — every wire detail a device depends on is documented here, so an integration can be written against them alone.

• Get started with a device
  • Choose an SDK
  • Integration sequence
  • First operational session
  • Retry rules
  • Manufacturing boundary
• Runtime surface
  • Public HTTPS
  • MQTT 5
  • OTA behavior
  • Non-device interfaces
• Device operations
  • Provision and rotate identity
  • Publish telemetry
  • Report device-owned attributes
  • Apply shared attributes
  • Receive and answer commands
  • Heartbeat and lifecycle
  • Poll and install OTA
  • Desired-state compatibility
• Composite robot terminal design
  • Recommended counts
  • Topology
  • Identity and ownership
  • Telemetry ownership
  • OTA ownership
  • When the count changes
  • Trade-offs
• How to integrate a composite robot
  • Prerequisites
  • 1. Register the asset and component graph
  • 2. Provision both DDI identities
  • 3. Connect two clients to the shared broker
  • 4. Publish ClearJanitor cleaning-job telemetry
  • 5. Publish runnerchecker and MCU telemetry
  • 6. Keep AOA local and identity-neutral
  • 7. Implement three installers behind two OTA targets
  • 8. Exercise replacement and failure paths
  • Troubleshooting
• SDK reference
  • Python 0.1.0
  • Android/Kotlin 1.1.0
  • C 1.0.0
  • Wire rules common to every binding
• Device licensing compatibility
  • Current availability
  • Android compatibility API
  • Offline status is not authorization
  • Target device contract
• Errors and recovery
  • Provisioning errors
  • Certificate rotation
  • MQTT connection loss
  • Inbound message failures
  • OTA failures
  • Licensing failures
  • Observability without secret leakage
• Device route architecture
  • What crosses the boundary, and what never does
  • Two planes that meet only behind the boundary
  • Composite products
  • Which calls use DDI

Choose a path

• Start a new integration with Get started with a device.

• Implement telemetry, attributes, commands, lifecycle, or OTA with Device operations.

• Design and implement a multi-computer terminal with Composite robot terminal design and How to integrate a composite robot.

• Look up exact Python, Android/Kotlin, and C entry points in the SDK reference.

• Check whether an SDK capability is actually enabled in the managed platform in Runtime surface.

• Design retry, certificate rotation, and recovery behavior with Errors and recovery.

Identity, provisioning, licensing status, MQTT telemetry, attributes, commands, twin, heartbeat, lifecycle, and Bazaar-authored OTA are documented as modules of the same unified DDI SDK and credential boundary.