Files
moonweb-site/smarthome/tasmota-energy/index.njk
T

71 lines
3.7 KiB
Plaintext

---
title: "Tasmota & Energy Monitoring"
section: "smarthome"
tags: "smarthome"
parent: "/smarthome/"
description: "Smart plugs and power monitoring across the flat with daily usage statistics."
layout: base.njk
---
<h1>Tasmota & Energy Monitoring</h1>
<div class="detail-content">
<p>Power monitoring across the flat runs on a mix of Tasmota-flashed smart
plugs, tracking accumulated kWh per device and feeding daily usage
figures into the home dashboard. The setup uses a number of Tasmota-enabled devices
covering kitchen appliances, office equipment, entertainment systems,
and LED matrix displays.</p>
<h2>What's metered</h2>
<table>
<tr><th>Device type</th><th>Typical use</th><th>Rough daily usage</th></tr>
<tr><td>Fridge plug</td><td>Kitchen appliance monitoring</td><td>~0.8 kWh/day (very stable)</td></tr>
<tr><td>Dishwasher plug</td><td>Appliance monitoring</td><td>~1.2 kWh/day (varies with use)</td></tr>
<tr><td>Office/desk plug</td><td>Workstation + peripherals</td><td>~1.2-1.7 kWh/day</td></tr>
<tr><td>Entertainment plugs (TV, Apple TV)</td><td>Media devices</td><td>Very low, Apple TV especially so</td></tr>
<tr><td>LED matrix displays</td><td>Ambient info displays</td><td>~0.04 kWh/day each</td></tr>
</table>
<h2>Multi-socket power strips</h2>
<p>Several rooms use multi-outlet smart power strips (each socket
individually switchable and metered) rather than single smart plugs. This
keeps things like "washing machine + dryer" or "office desk cluster" on
one strip while still tracking each socket's consumption separately.</p>
<h2>Flashing process</h2>
<p>New devices go through a standard conversion flow (from the
manufacturer's original cloud-dependent firmware to Tasmota) using a
well-documented community process. It occasionally fails on the first
attempt due to a transient Wi-Fi handshake issue, retrying resolves it
without any special handling.</p>
<h2>How the data flows</h2>
<p>Each Tasmota plug publishes its power readings to MQTT via the
Mosquitto broker running on the Docker host. A small subscription
service picks up the per-device topics and writes the values into
InfluxDB 2.x, tagged by device name, room, and measurement type
(power, energy, voltage). The home dashboard then queries InfluxDB
via Flux to display real-time and historical usage charts.</p>
<h2>What this data is used for</h2>
<ul>
<li>Spotting appliances with unexpectedly high standby draw.</li>
<li>Sanity-checking that "turned off" devices are actually drawing near-zero power.</li>
<li>Feeding the home dashboard's live power figures alongside the climate sensors.</li>
<li>Tracking long-term energy trends to identify efficiency improvements.</li>
<li>Alerting when a device draws significantly more than its baseline (e.g., a failing appliance).</li>
</ul>
<h2>Air quality and climate data</h2>
<p>The same InfluxDB instance also stores temperature and humidity readings from HomematicIP room sensors and ESP32 DHT22 devices. These feed the <a href="/smarthome/air-quality/">air quality dashboard</a>, which visualizes 24-hour climate history across 10 rooms. The energy and climate data share the MQTT-to-InfluxDB pipeline but live in separate measurement categories, keeping power monitoring and environmental sensing cleanly separated.</p>
<h2>Why Tasmota over alternatives</h2>
<p>Tasmota was chosen over alternatives like ESPHome or Tuya firmware for
several reasons. The local-only control means no cloud dependency, the
plugs work even if the internet is down. The MQTT integration is mature
and well-documented. The energy monitoring sensors are accurate enough
for home use (typically within 5% of a dedicated energy meter). And the
firmware supports a wide range of hardware, making it easy to find
compatible plugs at reasonable prices.</p>
</div>