Self-Hosted Home Energy Monitoring Platforms: emoncms, Home Assistant & Powerwall Dashboard Guide 2026

Tracking your home’s energy consumption has never been more important. Rising electricity costs, growing interest in solar installations, and the desire to reduce carbon footprints all demand better visibility into how and when your home uses power. While commercial energy monitors exist, they typically lock you into proprietary ecosystems and cloud-dependent dashboards.

Self-hosted energy monitoring platforms give you complete ownership of your data. You decide what to track, how long to store it, and which devices can access it — no subscriptions, no vendor lock-in, no telemetry sent to third-party servers.

In this guide, we compare three of the best open-source, self-hosted home energy monitoring platforms available in 2026: emoncms, Home Assistant with its built-in Energy Dashboard, and Powerwall-Dashboard for Tesla solar and battery systems. Each takes a different approach, and we will walk through feature comparisons, Docker Compose deployment guides, and help you choose the right platform for your setup.

If you are new to deploying services with Docker, our Docker Compose beginner’s guide walks through the fundamentals before you dive in.

Why Self-Host Your Energy Monitoring?

Commercial energy monitoring services offer polished interfaces, but they come with trade-offs that matter when you are collecting granular data about your home every few seconds:

• Data ownership — your consumption patterns, solar production numbers, and cost data never leave your network
• Long-term storage — no risk of a vendor sunsetting their service and losing years of historical readings
• Hardware flexibility — connect any sensor, smart meter, or inverter without waiting for official API support
• No recurring costs — once your hardware and server are set up, the software itself is free forever
• Integration freedom — pipe data into your existing monitoring stack, alerting systems, or home automation workflows

For related reading on building out a self-hosted infrastructure to support these platforms, see our guide to self-hosted NAS solutions for long-term data storage.

Quick Comparison Table

Before diving into each platform individually, here is how they stack up at a glance:

1. emoncms — The Dedicated Energy Monitoring Platform

emoncms is the flagship web application of the OpenEnergyMonitor project, a community-driven initiative that has been building open-source energy monitoring tools since 2009. It is purpose-built from the ground up for logging, processing, and visualizing energy and environmental data.

What Makes emoncms Stand Out

emoncms distinguishes itself by treating energy data as a first-class citizen. Every feature is designed around the workflow of an energy-conscious homeowner:

• Input processing pipeline — raw sensor readings pass through a configurable processing chain where you can apply scaling factors, cumulative-to-delta conversions (kWh), power factor corrections, and custom logic before storage
• Multiple feed engines — choose from fixed-interval time series, variable-interval logging, or MySQL storage depending on your resolution and retention needs
• Dashboard builder — a drag-and-drop interface for creating custom monitoring pages with real-time gauges, historical graphs, and KPI displays
• Module ecosystem — extend functionality with community modules for Octopus Agile tariffs, DemandShaper load control, MQTT integration, and more
• API-first design — every data operation is accessible via a clean REST API, making it straightforward to integrate with external tools or scripts

Architecture and Tech Stack

emoncms runs on a LAMP-style stack:

• PHP 8.1+ for the application layer
• MySQL or MariaDB for feed metadata and configuration
• Redis for input buffering (highly recommended to reduce disk writes, especially on SD cards)
• Apache as the web server (nginx also works)

The input processing architecture is particularly elegant. Data arrives as key-value pairs via HTTP POST, MQTT, or serial connections, passes through the Redis buffer for temporary storage, and is then processed by PHP workers that apply user-defined processing rules before committing to the database.

Docker Compose Setup for emoncms

The following Docker Compose configuration deploys emoncms with its full recommended stack:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

version: '3.8'

services:
  emoncms:
    image: emoncms/emoncms:latest
    container_name: emoncms
    restart: unless-stopped
    ports:
      - "8080:80"
    environment:
      - MYSQL_HOST=db
      - MYSQL_USER=emoncms
      - MYSQL_PASSWORD=emoncms_secure_password
      - MYSQL_DATABASE=emoncms
      - REDIS_HOST=redis
      - MQTT_ENABLE=true
      - MQTT_HOST=mqtt
    depends_on:
      - db
      - redis
      - mqtt
    volumes:
      - emoncms_data:/var/www/html

  db:
    image: mariadb:11
    container_name: emoncms-db
    restart: unless-stopped
    environment:
      - MYSQL_ROOT_PASSWORD=root_secure_password
      - MYSQL_DATABASE=emoncms
      - MYSQL_USER=emoncms
      - MYSQL_PASSWORD=emoncms_secure_password
    volumes:
      - emoncms_db_data:/var/lib/mysql

  redis:
    image: redis:7-alpine
    container_name: emoncms-redis
    restart: unless-stopped
    volumes:
      - emoncms_redis_data:/data

  mqtt:
    image: eclipse-mosquitto:2
    container_name: emoncms-mqtt
    restart: unless-stopped
    ports:
      - "1883:1883"
    volumes:
      - ./mosquitto.conf:/mosquitto/config/mosquitto.conf
      - emoncms_mqtt_data:/mosquitto/data

volumes:
  emoncms_data:
  emoncms_db_data:
  emoncms_redis_data:
  emoncms_mqtt_data:

After starting the stack with docker compose up -d, access emoncms at http://your-server:8080 and complete the setup wizard to create your admin account and configure feeds.

Ideal Use Cases for emoncms

emoncms excels when you want a dedicated platform for energy data without the overhead of a full home automation system. It is especially well-suited for:

• DIY energy monitoring with CT clamps and the OpenEnergyMonitor hardware ecosystem
• Tracking multiple energy circuits (solar PV, grid import/export, individual appliance circuits)
• Long-term historical analysis with the ability to export data as CSV
• Users who want to build custom dashboards tailored to their specific energy setup

2. Home Assistant — All-in-One Home Automation with Energy Dashboard

Home Assistant is the most popular open-source home automation platform in the world, with over 86,000 GitHub stars and a massive community of contributors. While it handles lights, locks, thermostats, and media, its built-in Energy Dashboard has become one of the most compelling reasons to adopt it.

The Energy Dashboard

Introduced in 2021 and continuously improved since, Home Assistant’s Energy Dashboard provides a comprehensive view of your home’s energy flows:

• Grid consumption and return — track kWh imported from and exported to the grid, with configurable cost tracking per tariff
• Solar production — monitor PV panel output in real time and compare against consumption
• Battery systems — track charge/discharge cycles for compatible battery storage systems
• Individual device tracking — assign energy meters to specific appliances or rooms for granular analysis
• Cost forecasting — set electricity prices (flat, time-of-use, or net-metering) to see real-time cost impact
• Gas and water — extend beyond electricity to track other utilities if you have compatible sensors

The dashboard integrates seamlessly with Home Assistant’s broader ecosystem. You can create automations based on energy data — for example, running the dishwasher when solar production exceeds consumption, or sending a notification via our recommended self-hosted notification infrastructure when energy usage spikes unexpectedly.

Integration Ecosystem

Home Assistant’s true strength is its integration catalog, with support for over 2,000 devices and services. For energy monitoring specifically:

• Smart meter integrations — direct connections to utility meters via DSMR (Netherlands/Belgium), IEC 62056-21, and various manufacturer APIs
• Solar inverter support — native integrations for Fronius, SolarEdge, Enphase, Huawei, Sungrow, and many more
• Smart plug monitoring — track individual device consumption through Shelly, TP-Link Kasa, Tasmota, and ESPHome devices
• EV charger tracking — monitor electric vehicle charging with Wallbox, Tesla, and OpenEVSE integrations
• Weather correlation — overlay weather data to understand how temperature and cloud cover affect your solar production and heating/cooling loads

Docker Compose Setup for Home Assistant

Home Assistant provides an official Docker image. Here is a production-ready Compose configuration:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

version: '3.8'

services:
  homeassistant:
    image: ghcr.io/home-assistant/home-assistant:stable
    container_name: homeassistant
    restart: unless-stopped
    network_mode: host
    environment:
      - TZ=America/New_York
    volumes:
      - ha_config:/config
      - /etc/localtime:/etc/localtime:ro
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0  # Z-Wave/Zigbee dongle (optional)

  # Optional: InfluxDB for long-term energy data storage
  influxdb:
    image: influxdb:2
    container_name: ha-influxdb
    restart: unless-stopped
    ports:
      - "8086:8086"
    environment:
      - DOCKER_INFLUXDB_INIT_MODE=setup
      - DOCKER_INFLUXDB_INIT_USERNAME=homeassistant
      - DOCKER_INFLUXDB_INIT_PASSWORD=influx_secure_password
      - DOCKER_INFLUXDB_INIT_ORG=home
      - DOCKER_INFLUXDB_INIT_BUCKET=energy
    volumes:
      - influxdb_data:/var/lib/influxdb2

  # Optional: Grafana for advanced energy dashboards
  grafana:
    image: grafana/grafana:latest
    container_name: ha-grafana
    restart: unless-stopped
    ports:
      - "3000:3000"
    environment:
      - GF_SECURITY_ADMIN_PASSWORD=grafana_secure_password
    volumes:
      - grafana_data:/var/lib/grafana
    depends_on:
      - influxdb

volumes:
  ha_config:
  influxdb_data:
  grafana_data:

Note that Home Assistant uses network_mode: host by default for optimal device discovery. After the container starts, access the web UI at http://your-server:8123 and navigate to Settings → Dashboards → Energy to configure your energy entities.

Ideal Use Cases for Home Assistant

Home Assistant is the best choice when you want energy monitoring as part of a broader home automation strategy:

• You already have (or plan to have) smart home devices beyond energy monitoring
• You want to create automations triggered by energy data (e.g., load shedding, time-of-use optimization)
• You value the massive community and the thousands of available integrations
• You want a mobile app with push notifications and remote access

3. Powerwall-Dashboard — Grafana-Powered Tesla Solar and Battery Monitoring

Powerwall-Dashboard is a specialized monitoring solution built on the proven Grafana, InfluxDB, and Telegraf stack. While it is designed specifically for Tesla Solar and Powerwall systems, the underlying architecture is applicable to any energy monitoring scenario where you want professional-grade Grafana dashboards with minimal configuration.

Architecture Overview

Powerwall-Dashboard uses a multi-container approach with five coordinated services:

• pyPowerwall — a Python API proxy that communicates with the Tesla Powerwall Gateway, handling authentication, rate limiting, and data normalization
• Telegraf — an agent-based metrics collector that polls pyPowerwall at configurable intervals and writes time-series data to InfluxDB
• InfluxDB 1.8 — the time-series database optimized for high-frequency sensor data with automatic downsampling
• Grafana — the visualization layer with pre-built dashboards showing solar production, battery state of charge, grid flows, and historical trends
• Weather411 — an optional weather data service that enriches the dashboard with solar irradiance, temperature, and cloud cover data

This architecture follows the industry-standard TIG (Telegraf-InfluxDB-Grafana) monitoring stack, making it familiar to anyone who has worked with observability tooling. If you want to explore metrics storage alternatives, our VictoriaMetrics vs Thanos vs Cortex comparison covers the broader landscape.

Docker Compose Setup

The project uses its own Compose file (powerwall.yml). Here is a simplified version for clarity:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79

version: '3.8'

services:
  influxdb:
    image: influxdb:1.8
    container_name: influxdb
    restart: unless-stopped
    ulimits:
      nofile:
        soft: 65536
        hard: 65536
    volumes:
      - ./influxdb.conf:/etc/influxdb/influxdb.conf:ro
      - ./influxdb:/var/lib/influxdb
    ports:
      - "8086:8086"
    env_file:
      - influxdb.env
    healthcheck:
      test: curl -f http://influxdb:8086/health || exit 1
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 60s

  pypowerwall:
    image: jasonacox/pypowerwall:latest
    container_name: pypowerwall
    restart: unless-stopped
    volumes:
      - ./.auth:/app/.auth
    ports:
      - "8675:8675"
    environment:
      - PW_AUTH_PATH=.auth
    env_file:
      - pypowerwall.env
    healthcheck:
      test: wget --spider -q http://pypowerwall:8675/api/site_info || exit 1
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 60s

  telegraf:
    image: telegraf:1.28
    container_name: telegraf
    restart: unless-stopped
    command:
      - "telegraf"
      - "--config"
      - "/etc/telegraf/telegraf.conf"
      - "--config-directory"
      - "/etc/telegraf/telegraf.d"
    volumes:
      - ./telegraf.conf:/etc/telegraf/telegraf.conf:ro
      - ./telegraf.local:/etc/telegraf/telegraf.d/local.conf:ro
    depends_on:
      - influxdb
      - pypowerwall

  grafana:
    image: grafana/grafana:latest
    container_name: grafana
    restart: unless-stopped
    volumes:
      - ./grafana:/var/lib/grafana
    ports:
      - "9000:9000"
    env_file:
      - grafana.env
    depends_on:
      - influxdb
    healthcheck:
      test: curl -f http://grafana:9000/api/health || exit 1
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 60s

After starting the stack, Grafana becomes available at http://your-server:9000 with pre-configured dashboards that display real-time power flows, daily energy summaries, battery cycle analysis, and historical performance charts.

Ideal Use Cases for Powerwall-Dashboard

Powerwall-Dashboard is the right choice when:

• You own a Tesla Powerwall and/or Tesla Solar installation
• You prefer Grafana’s visualization capabilities over custom-built dashboards
• You want a battle-tested TIG stack that can be extended to monitor other systems
• You need high-frequency data polling (every few seconds) with efficient time-series storage

Choosing the Right Platform

Your decision depends primarily on three factors:

Hardware ecosystem: If you have a Tesla Powerwall, Powerwall-Dashboard provides the deepest integration out of the box. For DIY sensor setups with CT clamps and ESP devices, emoncms offers the most flexible input pipeline. For a mix of commercial smart devices and sensors, Home Assistant’s integration catalog is unmatched.

Scope of monitoring: Want to track energy alongside lights, thermostats, security cameras, and automations? Home Assistant handles everything in one platform. Focused exclusively on energy data? emoncms or Powerwall-Dashboard keep things simpler.

Visualization preference: Grafana enthusiasts will feel at home with Powerwall-Dashboard. Users who prefer a dedicated energy-focused web interface should look at emoncms. Home Assistant’s Energy Dashboard sits in the middle — functional and integrated, but not as visually customizable as Grafana.

Frequently Asked Questions

FAQ

Can I run multiple energy monitoring platforms simultaneously?

Yes. Many users run emoncms for dedicated energy logging alongside Home Assistant for automation and control. The platforms can share the same hardware and even the same data sources via MQTT. emoncms can subscribe to MQTT topics that Home Assistant publishes, giving you the best of both worlds. Just ensure your server has sufficient resources — 4 GB of RAM and a quad-core processor is a comfortable baseline for running both.

What hardware do I need to get started with self-hosted energy monitoring?

The minimum requirements vary by platform. emoncms can run on a Raspberry Pi 4 with 2 GB of RAM. Home Assistant officially recommends at least 4 GB of RAM and recommends an SSD for database performance. Powerwall-Dashboard runs comfortably on any machine with 2 GB of RAM. Beyond the server, you need energy sensors — these range from simple plug-in power meters (like Shelly EM or Emporia Vue) to whole-home CT clamp monitors that connect to your electrical panel.

How much historical energy data should I keep?

This depends on your analysis needs. Monthly summaries and daily totals are useful for year-over-year comparisons, so keeping at least 2-3 years of aggregated data is recommended. Raw high-frequency data (readings every few seconds) consumes significant storage and can be downsampled after a few weeks. emoncms handles this with multiple feed engines, InfluxDB supports continuous queries for downsampling, and Home Assistant lets you configure recorder purge intervals.

Is it safe to expose energy monitoring dashboards to the internet?

With proper security hardening, yes. All three platforms support reverse proxy setups with HTTPS. Use a reverse proxy like Caddy or nginx with TLS termination, enable authentication, and consider placing the dashboard behind a VPN (WireGuard or Tailscale) rather than exposing it directly. Never expose database ports (MySQL, InfluxDB) to the public internet. For additional endpoint monitoring of your energy infrastructure, tools like those covered in our endpoint monitoring comparison can alert you if your monitoring stack goes offline.

Can these platforms integrate with utility smart meters?

emoncms supports DSMR smart meter readings (common in the Netherlands and Belgium) via serial or network connections. Home Assistant has integrations for utility meters in multiple regions, including DSMR, IEC 62056-21, and various manufacturer-specific APIs. Powerwall-Dashboard reads data directly from the Tesla Gateway, which aggregates whole-home consumption including the utility feed. If your utility provides an API, you can often write a custom script to pull data and feed it into any of these platforms via their APIs or MQTT.

Do I need solar panels to benefit from home energy monitoring?

Absolutely not. Energy monitoring is valuable whether or not you generate your own power. Tracking consumption helps identify energy-hungry appliances, verify the impact of efficiency upgrades, detect abnormal usage patterns that may indicate equipment problems, and understand how time-of-use pricing affects your bills. All three platforms support consumption-only setups without any solar or battery components.