TasmoAdmin

What is TasmoAdmin?

TasmoAdmin finds the Tasmota-flashed smart plugs, switches and sensors on your network and lets you update firmware, set configuration and control them all from one interface instead of visiting each device's own page.

Best for

Fleet management for Tasmota-flashed devices

Why choose TasmoAdmin

TasmoAdmin exists because managing a fleet of Tasmota-flashed devices by visiting each one's own web page is unbearable past about three devices. It discovers the Tasmota devices on your network and gives you one interface for firmware updates, configuration changes, group commands and monitoring across all of them. That centralisation is the whole value: upgrading firmware across twenty smart plugs becomes one action instead of twenty, and a device that has fallen off the network is visible as missing rather than discovered only when the light does not come on. It also handles the configuration templates that make identical devices truly identical, which is what prevents a slow drift into a network of subtly different setups.

Replaces

• Tuya Cloud
• SmartLife
• eWeLink

Key features

• Automatic device discovery
• Bulk firmware updates
• Timers and device configuration
• MQTT and Home Assistant integration

What to watch out for

It requires that devices be reachable and that it knows where to look — a segmented network or devices on a different subnet need explicit configuration, and discovery failing is the usual first obstacle. Bulk firmware updates are powerful and correspondingly risky: pushing a bad build to every device at once can take down the whole set, so staged rollouts matter. The interface is functional rather than polished, and security depends on how you deploy it, since it holds credentials for every device. Tasmota itself is a separate project with its own release cadence, and following one without the other leaves you on mismatched versions.

How to deploy

• Docker with access to the device subnet
• Scan for devices
• Configure MQTT for automation integration

Getting started

Deploy it on the same network segment as the devices and give it a scan range that matches your addressing rather than accepting a default. Confirm it discovers every device before doing any bulk operation, because a partial view makes group actions dangerous. Set up credentials and keep the interface off any public network, since it can control every device it sees. Update firmware on one device first and confirm it returns and works, then roll through a small group, and only then consider the whole fleet. Keep device configuration templates consistent so identical hardware stays identical.

Typical setup

It runs on the same network segment as the Tasmota devices with a scan range matching the actual addressing, and every device is confirmed discovered before any bulk operation, because a partial view makes group actions dangerous. Credentials are set and the interface stays off any public network, since it can control every device it sees. Firmware is updated on one device first and confirmed working, then a small group, and only then the whole fleet. Consistent configuration templates keep identical hardware identical, and Tasmota's own release notes are followed so device firmware and management stay roughly aligned.

Who should look elsewhere

Do not use it if you have a couple of Tasmota devices, where the individual web interfaces are honestly fine. Avoid it if you cannot keep it on the same network as the devices, because discovery and control both depend on reachability. And if you are not prepared to stage firmware updates carefully, centralised bulk updates turn a manageable risk into a single point of failure for your entire device fleet.

Project health

• GitHub stars: 974
• Last code push: 2026-10-01
• Open issues: 30
• Status: actively developed

Figures pulled from the GitHub API and refreshed periodically.