A utility bill tells you how much electricity you used. It rarely tells you when the house started using more. If you already have a working P1 reader for a Kaifa MA309M, Home Assistant can help answer that second question. And if you built the reader last year, an ESPHome change makes the software worth a second look.
Why the original build used a custom parser
The P1 port sends a telegram: a recurring packet of meter readings. An ESP32 running ESPHome can read those values and publish them as Home Assistant sensors. The original Kaifa MA309M project targeted ESPHome 2025.11. At that baseline, its author used a custom parser on ESP-IDF because the built-in DSMR component required Arduino and did not expose the Israeli tariff registers the project needed. The parser checked each telegram’s checksum before publishing readings.
The dashboard is the part worth keeping. An instantaneous power reading in kW can show a load turning on. A cumulative energy reading in kWh tells you how much energy has passed over time. Home Assistant’s Utility Meter integration turns cumulative readings into daily or monthly totals. Keep grid import and export separate: a day with heavy export can still include a large evening import. And if you compare today with yesterday, compare at the same hour, not today so far against all of yesterday.
What changed in ESPHome
ESPHome 2026.1 added ESP-IDF support to the built-in DSMR component. The 2026.11.0 source exposes six Israeli tariff energy counters: three for grid import (called delivered in DSMR) and three for export (returned). That removes two reasons for keeping a custom parser. It doesn’t prove that the built-in component will reproduce every reading from a particular meter.
There’s also a subtle compatibility issue: native DSMR exposes the Israeli active tariff as text, while the original project represents it as a number. A Home Assistant template that expects a number can behave differently even if the display looks identical.
Test the reader before replacing it
- Compare the same input. On an isolated test setup, use a few representative telegrams from an existing reader and compare the two parsers. Keep raw captures private; redact identifiers before sharing any examples. If you edit a sample for replay, regenerate its checksum so it remains a valid test case.
- Check more than the headline number. Compare import and export totals by tariff, the per-phase readings you use, units and decimal precision, and the active-tariff value and type. With CRC checking enabled, also test a deliberately corrupted copy and make sure it does not become a valid reading. ESPHome’s DSMR reference documents the available sensors and CRC setting.
- Protect the dashboard. Start with separate test entities. Check which entity IDs and types feed your utility meters, templates, and charts. Keep a rollback copy and make sure the history and totals behave as expected before pointing the dashboard at a replacement reader.
My take: If the current reader works, leave it running. Try native DSMR on the bench first. The win is a simpler reader without losing the measurements or history you already trust.
This is a software comparison based on the project and ESPHome sources, not a hardware compatibility test or a wiring guide.
Comments