Zum Hauptinhalt springen

IOmeter Smart-Home-Integration, kostenlos und Open Source

IOmeter-Integration für Gladys Assistant

Unofficial: IOmeter smart meter reader on your network: power, consumption and injection indexes.

Info

Die Dokumentation dieser Integration wird von ihrem Autor geschrieben und ist bisher nur auf Englisch verfügbar.

Unofficial integration, not affiliated with IOmeter GmbH. Never tested with a real IOmeter: built from the client library published by the maker. Please report what you see.

What it does​

IOmeter is a reader clipped on the optical port of a German smart meter (moderne Messeinrichtung or smart meter gateway), with a Wi-Fi bridge on your network. This integration reads the local API of the bridge, without any cloud nor account, and is read only: it never writes anything to the bridge nor to the meter.

ValueIn GladysWhen
Power taken from the grid (W)energy sensor, powerevery 10 s
Net power, negative when injecting (W)sensorevery 10 s
Consumption index 1.8.0 (kWh)energy sensor, index: the energy monitoringevery minute
Tariff 1 and 2 indexes, injection index 2.8.0 (kWh)sensorsevery minute
Power of each phase (W)sensorsevery 10 s
Reader battery (%), bridge and reader signals (dBm), reader connected and attached (1/0)sensorsevery minute

Only the values your meter gives are created. Gladys derives the consumption and its cost from the consumption index by itself. The injection is never in it: it is a plain sensor. This is not the Discovergy (inexogy) integration, which reads the cloud of the metering operator.

Setup​

  1. Set up your IOmeter with its app, so that the bridge is on your Wi-Fi.
  2. Find the IP address of the bridge in your router or in the IOmeter app. You can also leave the address empty and open the Discover tab: the bridges announced on your network are listed in the status of the integration (nothing is read until you enter an address).
  3. Enter the address in the configuration of the integration and save. Click Test the connection: it reads the net power and the consumption index once.
  4. In the Discover tab, create the IOmeter device.

Give the bridge a fixed address in your router. If it changes, enter the new one: the device and its history are kept.

The consumption index guard​

The consumption index is billed by Gladys: a wrong jump would count kWh that were never used. So the integration publishes a new index only when it is plausible after the last one (not lower, not more than 100 kW on average since then). A jump or a drop is held back: the last accepted value is sent again, the status of the integration says what is held, and it stays held across restarts. Nothing confirms it by time nor by repetition.

If the value is right (a new meter, a reset, a long outage), click Accept the held index twice in the configuration: the first click lists the value and accepts nothing, the second one, a few seconds later and within 5 minutes, takes exactly that value. A jump is then counted at once as consumption; a drop bills nothing and the consumption goes on from there. Saving the configuration accepts nothing.

The tariff and injection indexes are never published lower than before nor at 0; accepting a drop of the consumption index (a new meter) lets them start again from the new values. A jump of one of them further than a home can use is held too (it never becomes the new floor): it is taken back as soon as the meter gives a plausible value again, or once the meter has kept giving the new value, each reading plausible after the one before, for an hour (these indexes are not billed). On a new device, their first value is sent once a second reading agrees with it.

What the status says​

  • Connected, with notes: the status page not answering (the reading goes on), no new reading of the meter for 5 minutes (the power is then no longer sent: reader off the meter, battery empty or out of radio range), a reading more than 2 hours old, judged on the clock of the bridge when it gives one (then nothing of it is sent, the indexes neither), no index register, a counter read lower than before, an index held back.
  • Could not be read: no answer, unreachable, HTTP error, an answer too large (over 64 KiB) or that is not an IOmeter one, no reading yet. The integration tries again after 10 s, then waits twice as long each time, up to 5 minutes.
  • When Gladys does not give the configuration at a connection, the integration tries again the same way, without end.

The Test the connection button and the Discover tab read the bridge at once, outside the 10-second rhythm and without waiting for a retry delay (one request at a time).

Privacy​

The meter number, the installation id and the id of the bridge are ignored by the integration (never taken out of the answers): they reach no log, status nor file. /data holds only the reference of the consumption index and the value held back.

Limits​

  • Never tested with a real IOmeter: the pages, units and OBIS codes are those of the maker's library (version 1.0.3).
  • The bridge also offers a stream (Server-Sent Events); this integration polls every 10 seconds instead.
  • One bridge per integration.

Konfigurationseinstellungen​

Diese Einstellungen fragt IOmeter in seinem Konfigurationsbildschirm in Gladys ab.

EinstellungTypPflichtfeldBeschreibung
IOmetersectionNeinUnofficial connector, not affiliated with IOmeter GmbH. It reads your IOmeter (the reader clipped on the optical port of a German smart meter, and its Wi-Fi bridge) through the local API of the bridge, without any cloud: the power every 10 seconds, the consumption index (1.8.0) every minute for the Gladys energy monitoring, and, when the meter gives them, the tariff and injection indexes, the power of each phase, the battery and the signal of the reader. Read only. Not the Discovergy (inexogy) integration. Never tested with a real IOmeter.
IOmeter bridge addressstringJaThe IP address of the IOmeter bridge on your network (shown by your router or the IOmeter app; with no address, the Discover tab looks for it on the network), with a port only if it is not 80. Preferably give it a fixed address in your router; if it changes, enter the new one: the device and its history are kept.

So installierst du IOmeter in Gladys​

  1. Öffne in Gladys Integrationen: IOmeter erscheint im Katalog neben den nativen Integrationen, mit einem Community-Badge.
  2. Klicke auf Installieren. Gladys lädt das Docker-Image (ghcr.io/lm1lc3n7/gladys-iometer:0.1.1) herunter, startet es in einer vom Kern isolierten Sandbox und erzeugt die Oberfläche der Integration (Geräte, Erkennung und Konfiguration).
  3. Öffne den Bildschirm Konfiguration der Integration, fülle die Einstellungen aus und speichere.
  4. Du kannst sie auch direkt über die URL ihres Repositorys installieren: https://github.com/LM1LC3N7/gladys-iometer.

IOmeter benötigt Gladys >=5.1.0. Der Katalog in Gladys wird stündlich aktualisiert, eine neue Version ist also spätestens eine Stunde nach ihrer Veröffentlichung verfügbar.

Du nutzt Gladys noch nicht? Es ist kostenlos und Open Source: folge der Installationsanleitung, um loszulegen.

Über externe Integrationen​

IOmeter ist eine externe Integration: eine Community-Integration, die als Docker-Container verpackt und auf GitHub veröffentlicht wird. Gladys installiert sie mit einem Klick und führt sie in einer vom Kern isolierten Sandbox aus. Sie wird von LM1LC3N7 veröffentlicht und gepflegt, nicht vom Gladys-Kernteam.

Abonniere den Newsletter von Gladys Assistant

Ein paar E-Mails im Monat zu neuen Releases und Neuigkeiten aus dem Projekt. Verschickt von Pierre-Gilles Leymarie, dem Gründer des Projekts. Jederzeit abbestellbar 🙂