Category: Anouncements

The last release of Omnikdatalogger supports logging to a CSV file. Additional the local time, date and temperature (Openweathermap) can be logged. CSV logging can be configured per inverter or aggregated.

To already try the new feature download the new release.

Omnikatalogger’s tcpclient suports direct connection over port 8899 to fetch the data using Wouter van der Zwan’s library. Not all inverters support this way of connecting. Some inverters support collecting the inverter data over HTTP. With the new release the tcpclient will fallback to this http method when it fails to fetch the data over port 8899. Omnikdatalogger will try to fetch http://{inverter_ip}:80/js/status.js and will try to extract the data. A new setting http_only at the plant specific settings will allow to configure tcpclient only to use this method.

A disadvantage of this method is that it contains less details about the inverter and misses info about the PV DC strings.

The last release of Omnikdatalogger will have MQTT TLS support and implements the new Solarman API.

MQTT TLS support

The MQTT output client and mqtt_proxy plugin for the localproxy client now can use TLS. The use of client certificates and the use of an alternative ca is supported now.

Example of the new settings:

output.mqtt:
    tls: true
    ca_certs: ./.omnik/ca/mosquitto.org.crt
    client_cert: ./.omnik/client.crt
    client_key: ./.omnik/client.key

All new settings are optional.

TLS support was also added to Omnikdatalogger proxy.

new Solarman API

The last solarmanpv client does not work any more, because it was based on an old API that has been taken down. A brand new implementation of the solarmanpv client is now available. The client needs credentials to work. Visit https://home.solarmanpv.com to register. You can request customer support to migrate your previous collected data. The new portal and API has assigned a different plant_id, assigning a serial number is no longer needed.

The new API it self performs well and is secured, but data collection and processing is still buggy and slow. Hopefully this will improve shortly.

Big advantage is that you will regain access to your historical data.

Omnikdataloggers solarmanpv client does not longer seem to work. Users have received mails indication the service is to be discontinued. The portal functionality has been moved to https://home.solarmanpv.com/. I was successful in enabling the new UI by requesting a new password where I used the same email address I used before. While writing this my data still needs to be migrated. You can contact customerservice@solarmanpv.com for assistance with the data migration. You can add your inverter by supplying the serial number of your WiFi logger. That should not be necessary if your data is migrated correctly. Solarman also introduced a new API. I will update the omnikdatalogger solarmanpv plugin to support the new solarman API, but that will take some time. You will need to create an account to be able to use the portal. There is a link on the login page for ‘old’ Solarman users.

My aim is to regain access to your real time data with the solarmanpv client using the new API.

See you soon.

To support the Dutch Omnik users I have started some more accessible wiki page in Dutch. Enjoy!

Omnikdatalogger has been stabilized and updated to run stable with HACS and docker now. There were some problems during restarts, especially with HACS that now have been solved. Some parts of the DSMR integration did not shutdown properly. That is all solved now. I am curious to know how what your experience is with omnikdatalogger. Let me know using the comments.

Wiki udated

The omnikdatalogger wikipages have been updated and are completed now.