New blog post: Introducing IoTaWatt

As I’m sure you are aware the IoTaWatt developed by @overeasy has reached production stage. The unit is now for sale in the OpenEnergyMonitor shop. I’ve just published a blog post to intrudcice the unit to new users:

Blog post has been copied below:

Introducing IoTaWatt

IotaWatttm is an open-hardware 14 channel WiFi connected electric power monitor. It’s based on the ESP8266 IoT platform using MCP3208 12 bit ADCs to sample AC voltage and current.

IoTaWatt can log data locally to on-board SD card and post directly to via WiFi.

There are no plans to discontinue the emonTx. Both the IoTaWatt and emonTx have advantages in key areas which complement each other.

IoTaWatt is fully open-source and has been developed by Bob Lemaire @overeasy in partnership with OpenEnergyMonitor.




The IoTaWatt uses the WiFi enabled ESP8266 (ESP-12S) microprocessor. The ESP8266 is mounted using NodeMCU adaptor, the decision was made to use the NodeMCU form-factor to allow flexibility for customisation and future upgrades e.g ESP32.

The onboard SD card allows data to be saved locally with high resolution and network resilience. If the IoTaWatt is posting to an Emoncms server and loses network connectivity data logged to the SD card will be bulk uploaded to Emoncms when a network connection is restored.

An on-board real-time clock (RTC) ensure the time-stamp is always correct. The RTC is set using NTP. Using the IoTaWatt on a WiFi network with a reliable internet connection is highly recommended, however, the IoTaWatt can operate without an internet connection once the RTC has been initially set via NTP.


The IoTaWatt is configured via a web interface served directly from the IoTaWatt ESP8266. See for a live demo of the interface.

The IoTaWatt supports automatic over the air (OTA) firmware updates.


IoTaWatt supports end-to-end encrypted connection to Emoncms using new Emoncms API transport layer encryption. Due to the limited resources of the ESP8266 microcontroller HTTPS connection is not possible. However, Emoncms offers an in-built transport layer encryption solution where the emoncms apikey is used as the pre-shared key for encrypting the data with AES-128-CBC.

Automatic OTA firmware updates ensure the IoTaWatt is always running the latest most secure version e.g a firmware update was released and automatically deployed to fix the KRACK WPA vulnerability. Firmware updates are digitally signed.

emonTx Vs. IoTaWatt

As I mentioned at the beginning of this post, there are no plans to discontinue the emonTx. The IoTaWatt is not designed to replace the emonTx, rather to complement it. Each unit has advantages in key areas:

emonTx Advantages

  • Low power: battery power / single AC-AC adaptor
  • No setup required
  • Supports multiple DS18B20 temperature sensors
  • Supports Optical Pulse sensor (interrupt input) to interface directly with utility meters
  • Approximate 3-phase with firmware update
  • Multiple emonTx’s can communicate with a single emonPi / emonBase
  • WiFi connection not required

IoTaWatt Advantages

  • Large number of CT sensor inputs
  • Flexible configuration (many different types of CT’s supported)
  • On-board SD card logging
  • OTA firmware updates
  • Direct posting via WiFi to

The obvious advantage of the IoTaWatt over the emonTx is the number of CT sensor inputs. Another key advantage is the flexibility of the IoTaWatt, each input channel (AC voltage & current) can be individually configured and calibrated. The IoTaWatt supports a number of different sizes of CT sensors with calibration presets for CT sensors e.g 20A, 100A (standard) and 200A.

It is possible to use an IoTaWatt together with an emonPi / emonBase, the IoTaWAtt can post to any Emoncms server including emonPi over a local network.

Is it using the standard API or does it have it’s own API?

It uses the standard Emoncms API which has been recently upgrade to support encrypted transport layer. See API docs:

1 Like

3 posts were split to a new topic: ESPproMon

This looks really great!

1 Like