Homelab Server Power Consumption Monitoring with PZEM Sensors and ESPHome

Why Monitor Power Consumption in Your Homelab

Running a home IT lab (homelab) 24 hours a day often brings an unpleasant surprise on the utility bill at the end of the month. Repurposed older servers, loud storage arrays, and network switches consume power constantly and silently. Knowing exactly how much electricity each device uses is no longer just an enthusiast hobby, but a financial and thermal planning necessity.

Commercial smart plugs work fine for ordinary home appliances, but they usually fail in dense environments with power strips crowded with power supplies. Furthermore, many rely on third-party clouds or proprietary protocols that break if the internet drops. Building your own solution ensures total data control and maximum local operational reliability.

Hardware Architecture with the PZEM-004T Module

The heart of current and voltage measurement in this architecture is the PZEM-004T, a specialized integrated circuit that measures active power, voltage, current, frequency, and power factor. It communicates via a serial port (UART), meaning it sends raw electricity data directly to a microcontroller in a simple and reliable way without requiring complex electrical trigonometry calculations in the main code.

For safety, the module features total galvanic isolation, a physical and magnetic barrier that prevents high-voltage mains electricity (120V or 240V) from reaching the lower section where the control electronics reside. In practice, this means that even if a short circuit occurs on the main power line, your microcontroller and computer USB port remain fully protected against damage.

The Role of the ESP32 and ESPHome Firmware

The microcontroller chosen to read data from the PZEM sensor and transmit it to the network is the ESP32, a tiny and inexpensive chip featuring built-in Wi-Fi and Bluetooth. Instead of writing hundreds of lines of C code to configure wireless networking and handle connection errors, we use ESPHome, a lightweight operating system that turns simple text files into ready-to-run firmware for the hardware.

ESPHome makes life easier by handling automatic reconnection to your Wi-Fi router if the signal drops, while also sending collected data directly to your home automation hub. Configuration is done by declaring physical connection pins directly inside a structured YAML file, where we define data refresh rates and filters to prevent minor screen jitter.

Practical Implementation and Physical Connections

To assemble the circuit on your workbench, you must exercise extreme caution with electricity since you are dealing with wall voltage that can cause severe shocks. Assembly requires turning off the main breaker before handling any wires, ensuring that the live wire of your server power strip passes properly through the current sensor.

Below is a sample YAML configuration file that you should input into ESPHome to read the PZEM sensor through the standard serial port of the ESP32 microcontroller:

esphome:
  name: homelab-power-monitor
esp32:
  board: devkitv1
logger:
uart:
  - id: uart_pzem
    tx_pin: GPIO1
    rx_pin: GPIO3
    baud_rate: 9600
sensor:
  - platform: pzemac
    voltage:
      name: "Server Voltage"
    current:
      name: "Server Current"
    power:
      name: "Server Power"
    energy:
      name: "Energy Consumed"
    update_interval: 5s

After validating the code and flashing the firmware to the ESP32 via a USB cable, the device will connect to your local Wi-Fi network autonomously. Open your central automation manager interface and you will see the new sensors appear automatically, ready to be added to your monitoring dashboards.

Data Processing and Visualization in Home Assistant

With data flowing in real-time to Home Assistant, the next step is creating visual dashboards showing the financial impact of your homelab. We can configure virtual sensors called templates to calculate currency costs per kilowatt-hour based on your local utility provider tariff, displaying accumulated daily, weekly, and monthly expenses.

Another useful feature is creating automation rules based on power consumption reported by the servers. If power consumption drops below a minimum threshold during the night, for example, the system can send an alert indicating that a critical virtualization service crashed and the main container stopped responding.

Final Thoughts

Building a dedicated power meter using PZEM sensors and the ESPHome ecosystem combines the best of low-cost electronics with the freedom of open-source software. You gain total visibility over your servers' energy consumption, learn valuable lessons in electrical safety and physical infrastructure, and optimize your test lab operating costs without relying on external cloud services.