Iotwerk
sensor i2c strap address collisions
Compute supplied seven-bit I2C strap addresses and identify bus-local address collisions.
POST https://iot.halowerk.com/v1/sensor-i2c-strap-address-collisionsInputs
| Field | Type | Required | Description |
|---|---|---|---|
| devices | array | Yes |
Show full input schema
{
"type": "object",
"properties": {
"devices": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"bus": {
"type": "string",
"maxLength": 64,
"minLength": 1
},
"base": {
"type": "integer",
"minimum": 0,
"maximum": 127
},
"strap_mask": {
"type": "integer",
"minimum": 0,
"maximum": 127
},
"strap_value": {
"type": "integer",
"minimum": 0,
"maximum": 127
}
},
"required": [
"id",
"bus",
"base",
"strap_mask",
"strap_value"
],
"additionalProperties": false
},
"maxItems": 200,
"minItems": 1
}
},
"required": [
"devices"
],
"additionalProperties": false
}Published input example
{
"devices": [
{
"id": "temp_A",
"bus": "bus0",
"base": 72,
"strap_mask": 7,
"strap_value": 1
},
{
"id": "temp_B",
"bus": "bus0",
"base": 72,
"strap_mask": 7,
"strap_value": 1
}
]
}Result & documentation
Machine-readable documentation of this hub
Source of this page: the published HALOWERK catalog. Updated: 2026-11-18 UTC.
More endpoints in this hub
- Iotwerk0.003 USDC
battery degradation
POSThttps://iot.halowerk.com/v1/battery-degradationApplies a transparent heuristic: cycle fade scales with equivalent full cycles and depth-of-discharge exponent; calendar fade scales with square-root time and a temperature factor. Coefficients are caller supplied or declared defaults. This
- Iotwerk0.002 USDC
device auth
POSThttps://iot.halowerk.com/v1/device-authCanonicalizes device_id, nonce and message, computes an HMAC-SHA256 tag with caller-supplied ephemeral key material, and optionally compares a claimed tag in constant time. It does not provision devices, store keys or replace asymmetric dev
- Iotwerk0.004 USDC
digital twin sync
POSThttps://iot.halowerk.com/v1/digital-twin-syncGroups caller-supplied scalar field changes by field name, selects the highest version, and reports a conflict when equal-version values differ. It does not connect to a twin platform, merge nested documents or resolve semantic conflicts.