configure tasmota's cmnd/stat/tele mqtt topic prefixes and control a device over mqtt
domain: tasmota.github.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Note the three default topic prefixes: cmnd (Prefix1), stat (Prefix2), and tele (Prefix3), each combined with the device's %topic%.
Send commands to the device by publishing to cmnd/<topic>/<command> with the parameter as payload, e.g. cmnd/tasmota/POWER with payload ON.
Subscribe to stat/<topic>/<command> to receive the device's confirmation of a command, e.g. stat/tasmota/POWER reporting ON.
Subscribe to tele/<topic>/... to receive periodic telemetry (default every 300 seconds via TelePeriod) such as sensor readings or state.
Customize the topic string and prefixes via the device's MQTT configuration page or Prefix1/Prefix2/Prefix3/Topic commands if the defaults collide with other devices.
Known gotchas
stat/tele topics are not retained by default, so a freshly subscribed client won't see the last-known state until the next telemetry cycle or command response.
Two devices sharing the same %topic% value will collide on the same cmnd/stat/tele topics and both react to each other's commands.
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?