Omnik datalogger is my solar project on Github that enables you te do more with your Omnik Solar System logging. The manual page/documentation has been updated and there is a now a wiki for more information (Note: The wiki is still onder development). Thanks to Pascal Prins who’s code base I have been using. His project uses the omnik portal API, discussed later. Many installed a Omniksolar PV system with a wireless datalogger to enable reporting at https://www.omnikportal.com. Over the years this portal did realy change much and had some serious outages. Many have users a home automation system installed and want to do more with their solar data. Others want to use other reportings tools te process there power data. Omnik datalogger can help you achieve this.
How does it work
Omnik datalogger can retrieve the data from Omnik portal. You need to register your inverter on Omnik portal to be able to use this software using the build-in the portal clients. Since the older Omnik inverters doe not have a possibility to get the data directly, the portal seems the only place you can collect the submitted data. My inverter (installed October 2012) is of that older type. What I have found out the inverter sends an update to a fixed IP ‘184.108.40.206’. This address seems to be part of infrastructure the SolarmanPV. This company provides the data logging for Omnikportal. The portal at SolarMAN can be accessed using the same login credentials, so it seems to me. There are 2 API’s Omnik datalogger supports to fetch the data collected from your inverter.
- omnikportal client https://api.omnikportal.com/v1
- solarmanpv client http://www.solarmanpv.com:18000/SolarmanApi/serverapi
As you can see the omnikportal API has a secure interface and is JSON based.. A disadvantage of this API is that the data fetched for current power is not always real time. This effects graphs based on this data. Further this API has been down time-to-time, The solarmanpv API is an alternative that gives better real time data for current power, is not secure, but not every API call, the password needs to be supplied. Furher this API enables to readout the inverters serial number. Another disadvantage is that you will need to specify the plant ID. Fortunately this value can be found in the URL when you log into the portal:
https://www.omnikportal.com/Terminal/TerminalMain.aspx?pid=plant_idFortunately this value can be found in the URL when you log into the portal
Getting your logger data using these API’s has some common advantages:
- You need to poll at an interval of about 310 seconds, but it make take longer before the data becomes available.
- The API might be down or show the last value.
Support voor Dutch Smart Meter (P1 port)
The latest version of Omnik data logger now has possibility to calculate consumption data using the DSMR P1 port. This meter is applied in the Netherland and Belgium and provides in my case net power statistics (every 10 seconds) and gas statistics (every 5 minutes). The combination with the omnik solar data makes it possible to calculate the enegry and power consumption. Additional direct use and total consumption can be calculated and published to Influx DB of MQTT. With MQTT Home Assistants MQTT auto discovery is supported.
Direct polling your inverter
If your Omnik WiFi logger is supported, you now can use the buit-in tcpclient to poll your inverter directly. Not all inverters support this method, but is worth it to try this method first before switching to interception. Thanks to Han Lubach this method could be tested. If you have any problems or questions, please let me know!
Intercept the logger data
The data send to the fixed IP ‘220.127.116.11’ can be intercepted on your local network. The traffic is not encrypted and seems to to be decodable using the Omnik-Data-Loger project of Wouter van der Zwan. The code to intercept I have adapted from t3kpunk at Github. A tutorial to set this up will follow on this site later. An additional proxy script will help to support this. My logger sends updates approximately every 305 seconds.
The new localproxy client together with this proxy script will help to set this up. This new client has 3 plugins (hassap, mqtt_proxy and tcp_proxy) and integrates with the proxy script through AppDaemon and Home Assistant with the hassapi client plugin. The mqtt_proxy client plugin allows to montor MQTT for the changes of the proxy script. Direct logging is supported using the tcp_proxy client plugin.
Another new client tcpclient allows direct access by accessing port 8899 of the inverter. I have not been able to test this, since my inverter does not have this interface. Set the interval for this client. Let me know if this client works for you.
PVoutput.org is modern and free portal for owners of a PV-system. It is quite popular, and many users send there solar data to this portal. Omnik data logger enables you to send your realtime data to pvoutput.org. With direct access inverter temperature and voltage can be supplied as well. With the brand new DSMR integration, now you can also send your energy consumption data!
When you have a home automation system setup like Home Assistant, OpenHAB or Domiticz your are probably familiar with MQTT. This IoT messaging bus protocal enables easy automation using your realtime data as a sensor. Omik datalogger can produce MQTT sensors (including DSMR en DSMR gas entities and combined consumption data) which automatically can be discovered by Home Assistance (MQTT auto discovery) and of course can be used with your favorite MQTT supporting home automation system
Support dor InfluxDB have been added, and is now available. Thanks to lepirlouit. DSMR data and combined consumption data can also be logged to InfluxDB.
Home Assistant Community Store is the community store plugin for Home Assistant. Omnik datalogger is included in the default HACS store. To install Omnik Datalogger with the Home Assistant Community Store HACS.
- Install HACS (see HACS website)
- Select Automations and add an automation.
- Find Omnik Data Logger and install it
Before you can use Omnik Data Logger via AppDaemon/HACS make sure you prepare the yaml configuration (/config/appdaemon/apps/apps.yaml). After performing updates to your configuration or after a software update do not forget to restart AppDaemon an check the log.
For more details on installation and configuration see the Github homepage and wiki of the project.