Skip to content

Device groups

A device group is a static, many-to-many tag for organizing devices.

Use groups to express anything that isn't already covered by hardware compatibility:

  • Customer / tenant: customer-acme, customer-zenith
  • Geography: region-eu, region-us-east
  • Role: gateway, sensor-leaf
  • Lifecycle: pilot, internal-qa, field

Groups are explicit memberships: you decide which devices belong to which groups. Rule-based or tag-expression groups are not currently supported.

Many-to-many

A device can belong to any number of groups simultaneously. A deployment that targets multiple groups is the union of those group's members.

Managing membership

  • Dashboard: open the device from the project's Devices card, set its groups, then Save membership. There is no bulk row selection, so for more than a handful of devices use the API.
  • API: POST /api/v1/projects/{id}/groups/{group}/members/, and DELETE /api/v1/projects/{id}/groups/{group}/members/{device_id}/ to remove one.

Compared with channels

Groups Channels
Many per device One per device
Static, explicit Static, explicit
Express who Express which release stream
Used for audience scoping Used for stable / beta / dev

A typical deployment targets both axes at once, which narrows to their intersection: channel = stable and group = customer-acme reaches only Acme's devices on stable. See release channels.