No Description

CaCO3 22ef80db37 fix define 3 years ago
.github 17d85ae523 Update label-commenter-config.yml 3 years ago
code 22ef80db37 fix define 3 years ago
docs b9abbafefc Update SoftAP 3 years ago
firmware 228a87038e Link to the installtion guide in firmware-Readme. It will packed into the initial-setup.zip 3 years ago
images 6b84eb0290 Replace alert boxes with overlay info boxes (#1742) 3 years ago
releases 67ff06f64e Update WebInstaller 3 years ago
sd-card 60ce08e331 Show ways to get notified about new releases 3 years ago
tools 62ec8d76c6 Update LogDownloader 3 years ago
.gitignore d11ee2a4cf Rolling 20220925 3 years ago
.gitmodules fc4f3eebb6 fixed rebase conflicts 3 years ago
Changelog.md 04f2f23931 Update Changelog.md 3 years ago
FeatureRequest.md 6868bfe84a Update FeatureRequest.md (#1591) 3 years ago
README.md ec8de6287f Update README.md 3 years ago

README.md

Welcome to the AI-on-the-edge-device

Artificial intelligence based systems have been established in our every days live. Just think of speech or image recognition. Most of the systems relay on either powerful processors or a direct connection to the cloud for doing the calculations up there. With the increasing power of modern processors the AI systems are coming closer to the end user - which is usually called edge computing. Here this edge computing is brought into a practical oriented example, where a AI network is implemented on a ESP32 device so: AI on the edge.

This projects allows you to digitalize your analoge water, gas, power and other meters using cheap and easily available hardware.

All you need is an ESP32 board with a supported camera and a bit of a practical hand.

Key features

  • Tensorflow Lite (TFlite) integration - including easy to use wrapper
  • Inline Image processing (feature detection, alignment, ROI extraction)
  • Small and cheap device (3x4.5x2 cm³, < 10 EUR)
  • camera and illumination integrated
  • Web surface to administrate and control
  • OTA-Interface to update directly through the web interface
  • Full integration into Homeassistant
  • Support for Influx DB 1
  • MQTT
  • REST API

Workflow

The device takes a photo of your meter at a defined interval. It then extracts the Regions of Interest (ROI's) out of it and runs them through an artificial inteligence. As a result, you get the digitalized value of your meter.

There are several options what to do with that value. Either send it to a MQTT broker, write it to an InfluxDb or simply provide it throug a REST API.

Impressions

AI-on-the-edge-device on a Water Meter

Web Interface (Water Meter)

AI-on-the-edge-device on a Electrical Power Meter

Setup

There is a growing documentation which provides you with a lot of information. Head there to get a start, set it up and configure it.

There are also a articles in the German Heise magazine "make:" about the setup and the technical background (behind a paywall) : DIY - Setup

For further background information, head to Neural Networks, Training Neural Networks and Programming on the ESP32

Download

The latest available version is available on the Releases page.

Flashing of the ESP32

Initially you will have to flash the ESP32 through an USB connection. Later an update is possible directly over the Air (OTA).

There are different ways to flash your ESP32:

  • Web Installer and Console (Webbrowser based tool to flash the ESP32 and extract the Log over USB)
  • Flash Tool from Espressif
  • ESPtool (Command Line Tool)

See the Docu for more information.

Flashing the SD-Card

The SD-Card must be flashed separately, see the Docu for details.

Casing

A 3d-printable housing can be found here:

Build it yourself

See Build Instructions.

Donate

If you would like to support the developer with a cup of coffee you can do that via Paypal.

If you have any technical topics, you can create an Issue.

In other cases you can contact the developer via email:

Changes and History

See Changelog

Tools

Additional Ideas

There are some ideas and feature requests which are not followed currently - mainly due to capacity reasons on side of the developer. They are collected here: FeatureRequest.md