create, recall, and rename zigbee2mqtt scenes for a device or group over mqtt
domain: zigbee2mqtt.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Put the target device or group into the desired state (on/off, brightness, color, etc.).
Publish {"scene_store": SCENE_ID} (or {"scene_store": {"ID": SCENE_ID, "name": "..."}}) to zigbee2mqtt/[FRIENDLY_NAME]/set to save the current state as a scene.
Publish {"scene_recall": SCENE_ID} to the same set topic to apply a previously stored scene.
Use {"scene_rename": {"ID": SCENE_ID, "name": "..."}} to rename an existing scene, or {"scene_remove": SCENE_ID} to delete one.
Apply scenes to a Zigbee2MQTT group topic (not just an individual device) to control multiple devices with one recall.
Known gotchas
scene_store overwrites all stored values for that scene ID except the transition value, so partial updates to a scene aren't possible without restoring the rest of the state first.
Recalling a scene ID that was never stored on that device (an "unknown scene was recalled" case) fails without a clear error from the automation's perspective.
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?