Questions and answers
Most questions about an energy module arrive before the module does: is it safe this close to mains, will it read the load I actually have, what does the accuracy rating promise. Each answer here is one page and starts with the answer rather than the background — and where it touches wiring or safety, it links to the chapter in the documentation that shows it.
Power & hardware
Is the rbAmp module isolated from mains?
Yes — and the reason is the architecture, not a barrier bolted on: the module itself is all low-voltage. Current is measured with a clamp that closes around the outside of the insulated conductor — magnetic coupling only, so nothing at line potential enters the module. The UI variants have exactly one mains reference, the L – N voltage sense, and it goes through a galvanically isolated divider; the ampere-only variants have no mains connection at all. Your GND is the host's ground, not mains neutral, so wiring the I2C side to an Arduino or an ESP32 is safe. Don't open the enclosure — it voids the factory calibration. Read the full answer
Why is rbAmp 5 V-powered but the I²C bus is 3.3 V?
The module has its own microcontroller doing the measurement, and it needs clean, stable power to keep the ADC readings accurate. So the module takes 5 V on VCC and runs it through an on-board low-noise regulator that derives the 3.3 V its MCU actually runs on. Because the MCU is a 3.3 V part, the I²C lines (SDA/SCL) operate at 3.3 V logic — they're 5 V-tolerant, but they idle at the host's 3.3 V level. In short: power the module at 5 V (4.5–5.5 V; below 4.5 V the ADC loses accuracy), wire the I²C bus at 3.3 V logic. On an ESP32 or classic Arduino that's automatic — the bus follows the host's 3.3 V rail, independent of the 5 V supply. Read the full answer
Do I need external I²C pull-up resistors for rbAmp?
For one module, no — the rbAmp PCB carries built-in 4.7 kΩ pull-ups on SDA/SCL to 3.3 V. With 2 or 3 modules on a bus up to 15 cm, leave the built-in pull-ups on every module — nothing to cut (3 modules measured: 15 cm leads, 50 kHz). From 4 modules, or on a longer bus, disable them on all modules (a solder jumper) and fit one external pair near the master; values are in the multi-module build . Read the full answer
Accuracy
How accurate is rbAmp?
It depends on the current sensor, so the figure has two parts: the module's class with the SCT-013 rating you use, and the clamp's own tolerance added on top. Both are given per rating — together with the floor below which a current is seen but not measured to that class — in the SCT-013 accuracy table . In the working range (5–100 % of the rating) the class is ≤ 0.5 % for most ratings. Read the full answer
Does rbAmp measure real power or just current?
Real (active) power, in watts, computed on the module per channel — plus voltage, current, power factor, and frequency. Because it has both the voltage and the current for each channel, reactive and low-power-factor loads read honestly; you're not multiplying current by an assumed voltage. Read the full answer
I²C & boards
Which boards and frameworks can I use with rbAmp?
Anything that speaks I²C: ESPHome / Home Assistant , Arduino / C++ (ESP32, Uno, Nano, STM32, RP2040…), Python on a Raspberry Pi or other Linux SBC, and ESP-IDF . All four client libraries are open and local — no cloud, no lock-in — over a documented I²C protocol. Read the full answer
What I²C bus speed should I use, and why 50 kHz on ESP32?
It depends on the host driver , not the board brand: Read the full answer
Addressing & multi-module
Can I put several rbAmp modules on one I²C bus?
Yes — that's a core feature. Modules share one I²C bus and differ only by address. Add circuits by adding modules on the same two wires, behind one host — no extra microcontroller, no serial-port juggling. For coherent energy across modules, one broadcast latch snapshots them all on the same instant. See the builds: whole panel on one ESP32 and multi-module Arduino bus . Read the full answer
How do I change an rbAmp module's I²C address?
On current firmware it's a plain, production-ready operation — no special mode, jumper, or factory tooling . You stage the new address, arm the change, and commit it (a two-phase, magic-armed sequence so an address can't change by accident); the module reboots at its new address. Do it one module at a time, with the others disconnected , so there's no address clash. Your library exposes it directly (e.g. prepareAddressChange() / commitAddressChange() , or a fleet-provisioning helper). Read the full answer
Energy
How does rbAmp handle energy (Wh), and does it survive a reboot?
Energy is integrated over exact wall-clock intervals: the module latches a measurement window atomically and the host integrates true active power over the elapsed time, so there's no on-device counter to quantize or drift. In the ESPHome component, the accumulated energy is persisted to the ESP32's NVS, so an energy total survives a reboot or brownout without a gap or reset in Home Assistant. In a bare-Arduino sketch, the host owns the running total — persist it yourself (e.g. to an SD card) if you need it across power cycles. Read the full answer
Integration
Does rbAmp work with the Home Assistant Energy Dashboard?
Yes — via ESPHome the module's energy sensor lands in the Energy Dashboard out of the box. See the Home Assistant setup . Read the full answer
Does rbAmp need the cloud or a subscription?
No. It's fully local and open — a documented I²C protocol with open ESPHome, Arduino, Python, and ESP-IDF libraries. Nothing phones home; you own your data. Read the full answer