Skip to main content
Use the @bijection/connectors/iot entrypoint to declare Connected equipment resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Equipment

changeFeed: changeFeed

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: iot/equipment/changeFeed/standard. Connection and resource configuration are declared by this exact case. Credential kind: http. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

iotGateway({ configuration, access, policy }) declares source-owned device observations and a typed applyConfiguration command. The gateway must serve /v1/identity, complete history at /v1/changes?after=..., and original-request receipts under /v1/devices/:key/requests/:request_id. Configuration send uses POST /v1/devices/:key/configuration. The native complete-prefix change feed enforces ordering. Device event time is separate from gateway observation and native acquisition time. Commands retain native request identity, destination-enforced arrival expiry, exact configuration revision and installation epoch. Only applied evidence confirms a command; receipt or timeout alone does not. The destination must retain receipts and complete source history for at least seven days. Compose this resource with @bijection/iot for installation, intention resolution, rollout and incident behavior. That repository owns the complete wire schema and a durable reference receiver. Credentials and endpoints remain deployment bindings; capability declarations are contracts, not remote attestation or hosted qualification.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.