Appearance
SenCmd Protocol
SenCmd is the structured device protocol shared by SenCore, SenHub, SenCLI, and automation clients. This is the starting point for understanding how a command is addressed, how an event is reported, and where a message belongs in the versioned SenCore contract.
Current default release
Browse SenCore 0.3.0 by domain and service
Choose a Domain, then a Service. A Service page keeps every related command, request parameter, response field, error, example, and event on one page.
Choose what you need
- Find a command starts from an alias, code, domain, event, or release and ends at the exact versioned entity page.
- Protocol overview explains the model, transports, and control surfaces.
- Message format defines the envelope, fields, codes, and response rules.
- Command domains maps the namespace to system, motion, media, sensor, storage, debug, and platform capabilities.
- Event bands explains event code allocation and subscription semantics.
- SenCore Reference provides Domain and Service browsing plus stable standalone command and event pages for the current release.
- Error codes lists the complete result catalog for the current release.
Protocol and product workflows
Use the protocol pages to understand the wire and capability contract. Use the Device Operation model to understand how Web or CLI requests an outcome, how the shared platform service plans it, and how an eligible executor and SenCore report verifiable facts. A protocol command page does not replace the plan or grant access to a private capability.
Always choose the Reference page whose release matches the project or device artifact. The default release is a convenience entry point; it may change as the platform evolves and must not silently redefine an explicit historical URL.
If you arrived because something failed, preserve the release, command identity, response, event, device identity, and transport before using Troubleshooting.