Home

Introduction

A new Dutch wiki page is available now as well. The original version of this is a Python3 based PV data logger with plugin support, is specifically build for the by Pascal Prins Omniksol-5k-TL2 but have been tested with a first generation inverter (Omniksol-3K-TL) as well. This datalogger can use data collected at the Solarman infrastructure, also available at solarmanpv. To fetch data pushed by the inverter I have adapted this project and tried it in combination with my Omniksol-3k-TL. This model datalogger cannot be accessed directly for data collection, so I started using the portal api, which has been renewed recently. Support has been added for MQTT and the integration with Home Assistent using the AppDaemon addon. Now the new version it also makes possible to process intercepted logger messages and integrate the processing with Home Assistant (localproxy client). Polling the inverter directly is also possible using the tcpclient, thanks to Han Lubach this method is working now as expected. Special thanks to Wouter van der Zwan for his code (https://github.com/Woutrrr/Omnik-Data-Logger) and t3kpunk (https://github.com/t3kpunk/Omniksol-PV-Logger) Also special thanks to lepirlouit for creating the basis for the new influxdb output plugin. The latest version supports integration of enery logging conform the Dutch Smart Meter Requirements (DSRM). These meters can be connected using the P1 port of your smart meter. Omnik data logger can either read the port using a USB-based serial ports or over tcp, using Nigel Dokters DSMR parser (https://github.com/ndokter/dsmr_parser). The integration gives live output at mqtt an influx db and calculates energy consumption against the solar data for the integration on pvoutput.org.

How can I use Omnik Data Logger

You can find severals apps for reading out Omnik solar inverters directly. But many inverters are older and cannot be read out directly in an easy way. If your solar system was connected to (https://www.omnikportal.com) then you can now integrate easy with Home Assistant and pvoutput.org. Since the omnikportal is down now, you can still access an alternative portal at SolarMAN where you can login with your existing account and all of your data is being preserved. This service is announced to be free till the end of 2021. But as the introduction already indicated, you can also intercept now the data traffic of your Omnik Wi-Fi module (and optional still forward the logging for the Solarmanpv portal). The code has a pluggable client module and two new modules (localproxy and tcpclient) have been developed. Make sure to update your configuration and configure the client key at the [plugins] section. The new module localproxy supports local captured logging. Access is not required, but you need accces to your router to add a static route to reroute the loggers traffic. This module disables logging to solarmanpv and captures the data in your local network by simulating the backend.

Check my script omnikloggerproxy.py and documentation for the interception of the inverter messages. This script makes it possible to intercept and forward at the same time. This meas you can still make use of the classic Omnik portal or Solarman PV portal. Forwaring and intercepting requires a server else where out of the intercepted routing, to be still be able to route to the logging servers as log thes are supported.

The Home Assistant output plugin integration requires the MQTT integration is set up. The application uses MQTT auto discovery, so the devices and entities will show up automatically at the MQTT integration. If you want to use the pvoutput output plugin, then you need to create an account first. Temperature can also be logged (a openweathermap account is needed). If you capture using the localproxy or tcpclient client you can also log the inverters temperature and net voltage. The new influxdb output plugin can now be used as well.

My inverter presents updates approximately updates every 300 seconds. Fore times clients the interval defaults to 360 seconds counts from the last valid update time read from the portal. This way you will not miss any updates.

Installation

Choose one of the following method's:

Install using pip

Choose this installation method if you want to run Omnik Datalogger as a stand-a-lone application.

Install using docker

Choose this installation method if you want to run Omnik Datalogger as a docker application.

Manual install using git or download (Windows/Linux)

Choose this installation method if you want to run Omnik Datalogger as a stand-a-lone application without pip.

Install with AppDaemon4 and Home Assistant

Choose this installation method if you want to install Omnik Datalogger without HACS.

Install using HACS (Home Assistant Community Store)

Choose this installation method if you want to use the Home Assistant Community Store.

---

DSMR integration

Connection to the P1 port of a Dutch Smart Meter Requirements compliant energy meter and enhance your solar logging with consumption data and use your net data (and gas usage) in over MQTT in Home Assistant or analyse through InfluxDB

---

Select a client for data collection

Read about the different client categories and choose the client that fits best.

Choose Local proxy client

This client is triggered (pushed) when the inverter logs it's data to the Omnik cloud servers.

Choose TCPclient as client

This client polls the inverter directly at a fixed interval. Use this client if your inverter can support this.

Choose Solarman PV

These clients get the data indirectly from the cloud services using your Solarman portal using your Omnik username and password.

---

Omnik data logger client setup

Configure localproxy client

Explained is to inverter traffic can be intercepted to be processed as a trigger.

Configure the TCPclient client

Explained is how to setup direct polling (if your inverter supports it)

Configure the SolarmanPV client

Explained is how to setup polling the using SolarmanPV API

---

Configure Omnik data logger output plugins

Configure pvoutput output plugin

This output plugin enables you to publish your logging data to pvoutput.org. Follow the linke to find out how to configure this.

Configure MQTT output plugin

This output plugin enables you to publish your logging data to MQTT. MQTT is an IoT protocol that can be used in combination with Home Assistant, Domoticz, OpenHab or Homey. The MQTT plugin publishes all elements using the MQTT Auto discovery guidelines. When used in combination with Home Assistant this wil automatically create all sensors with appropriate units and icons within Home Assistent using the standaard MQTT integration. Follow the link to find out how to configure this.

Configure InfluxDB output plugin

This output plugin enables direct logging to and InfluxDB database. If you are integrating Omnik data logger with Home Assistant you can also use the InfluxDB integration of Home Assistent as an alternative.

Configure CSVoutput output plugin

This output plugin enables direct logging to and a CSV file.

---

Customize publishing output

This information helps you to customize the output published through MQTT and InfluxDB output plugins.