TasmoFleet

Current release: 0.17.0 (2026-10-29) · Release notes · Changelog

Description

TasmoFleet is a self-hosted web app for managing a fleet of Tasmota devices, an alternative to TasmoAdmin (it can import your TasmoAdmin device list).

• Configuration backups: scheduled and on demand for the whole fleet, diff between backups, restore with one click, also onto a replacement device.

• Settings policy: define the settings every device should have, see compliance per device, and fix deviations in one go ("Make compliant").

• Safe bulk firmware updates: server-side jobs with a chip-family safety check before every update; 1 MB ESP8266 devices go through tasmota-minimal automatically.

• Live status over MQTT, with HTTP polling as fallback.

• Bulk commands and a device console.

• Sign-in via OIDC/SSO or local accounts.

Project

• Project / docs: https://github.com/nofuturekid/tasmofleet

• Static demo (no install): https://nofuturekid.github.io/tasmofleet/

• Image: ghcr.io/nofuturekid/tasmofleet

• Template: https://github.com/nofuturekid/unraid-templates

Setup notes

• Web UI: container port 8080, host port 8443 by default (self-signed HTTPS; plain HTTP behind a reverse proxy, see the README). Upgrading from 0.16 or older: see the upgrade notes in the release.

• Firmware port (default host port 8081): your Tasmota devices download firmware from it during updates, so it must be reachable from their network/VLAN.

• Appdata (/mnt/user/appdata/tasmofleet) must be owned by 65532:65532.

• On first start the log prints a one-time setup link for the first admin account.

Status: pre-1.0, single maintainer. Breaking changes are to be expected before 1.0: read the release notes before updating. Built with Claude Code (AI-assisted) and reviewed and tested by me on my own fleet.

Please report bugs and feature requests as GitHub issues; this thread is for Unraid-specific questions.

Screenshots

Edited 2 hours ago2 hr by NoFutureKid
0.17.0

TasmoFleet 0.17.0

Upgrade notes

The Web UI now always runs on container port 8080, and TASMOFLEET_TLS_SELF_SIGNED is gone.

• Existing Unraid containers keep working, no change needed: Unraid keeps your saved settings. The log may warn about TASMOFLEET_TLS_SELF_SIGNED; you can delete that variable.

• Only breaks if you deleted the UI listen row from your template: set the Web UI container port to 8080.

• Reverse proxy with Self-signed TLS = true: TasmoFleet now serves plain HTTP, so point the proxy at http://.

• docker run / Compose without TASMOFLEET_LISTEN: change -p 8443:8443 to -p 8443:8080.

Optional clean-up: edit the container, delete UI listen, Self-signed TLS and Firmware listen, and set the Web UI container port to 8080. Step by step: Upgrading to 0.17

What's new

• Device page reworked: live tiles, relay box with per-channel watts, Identity next to Connection, one Activity list, offline banner; it updates live without a reload

• "Devices" breadcrumb returns to your filtered list

• Times in your browser's time zone (Today / Yesterday)

• More device facts: sensor readings, OTA URL, relay names, subnet, DNS

• Metrics token on the settings page

• All environment variables documented in one place: configuration.md

Release notes · Changelog

Edited 1 hour ago1 hr by NoFutureKid
Cleaner layout