Create and manage a Zigbee2MQTT group to control multiple devices as one

domain: iot · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Create a group via the frontend, MQTT, or a numbered entry (friendly_name, retain, transition, optimistic, off_state) under groups: in configuration.yaml
  2. Add a device (optionally a specific endpoint) by publishing {"group": GROUP, "device": DEVICE[, "endpoint": ENDPOINT]} to zigbee2mqtt/bridge/request/group/members/add
  3. Control every member at once by publishing a normal payload (e.g. {"state":"ON"}) to zigbee2mqtt/[GROUP_FRIENDLY_NAME]/set
  4. Remove a device with zigbee2mqtt/bridge/request/group/members/remove, or from all groups with .../remove_all (omit "group" for remove_all)
  5. Choose off_state: all_members_off (group state stays ON while any member is ON) or last_member_state (mirrors whichever member last changed)

Known gotchas

Related routes

create, recall, and rename zigbee2mqtt scenes for a device or group over mqtt
zigbee2mqtt.io · 5 steps · unrated
configure zigbee2mqtt's pan_id, ext_pan_id, channel, and network_key advanced settings
zigbee2mqtt.io · 5 steps · unrated
enable and tune zigbee2mqtt's device availability feature to detect offline zigbee devices
zigbee2mqtt.io · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans