Omnikdatalogger

Latest version: v1.14.5.post1

Safety actively analyzes 688126 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 11

1.6.7

Not secure
- Use local time zone for `last_reset` attribute.

1.6.6

Not secure
- Fix: make `last_reset` attribute timezone aware for `today_energy`.

1.6.5.1

- Fix: publish `last_reset` attribute before sending MQTT value payload.

1.6.4

Not secure
The measurements published through MQTT do now have a required `state_class` attribute set to `measurement`
The device classes in `data_fields.json` have been updated.
The MQTT module has been adapted to publish the `last_reset` attribute, which is needed to make the omnikdatalogger integrate with Home Assistant.

You can set the `last_reset` payload by setting the `start_date` at the install date of your smart meter (DSMR terminal settings) and for your inverter setting `start_date` at the plant specific configuration section.

P.S. This release resolves issues with sensor entities not shown in the energy dashboard.

1.6.0

Not secure
The measurements published through MQTT do now have a required `state_class` attribute set to `measurement`
The device classes in `data_fields.json` have been updated.
The MQTT module has been adapted to publish the `last_reset` attribute, which is needed to make the omnikdatalogger integrate with Home Assistant.

1.5.7

Not secure
This minor update fixes a problem where omnikdatalogger will crash on a fatal first MQTT connection.
With this update omnikdatalogger will keep retrying the connection until a successful connection loop is set up.

Page 9 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.