Release notes
Release date: 2026-03-04
Notes: This release introduces a new message format, Max flow, which includes the maximum flow rate during the last logging period, along with the date when it occurred. See Maximum flow for a complete message format specification.
Warning
This format is only useful in meters with FW version 3 or higher since it relies the logger functionality of the meter.
Note
The value/date of the maximum flow is taken from the meters log. The log can be configured in the meter for different intervals (hourly, daily, weekly, monthly etc.) and thus the value sent depends on how the meter is configured.
Table 338. Implemented changes
|
ID |
Description |
|---|---|
|
MCM-8576 |
Add new message format Max Flow |
|
MCM-7304 |
Add support for FW06 for Diehl Sharky without encryption |
Release date: 2025-05-13
Notes: This release address an issue that was introduced in FW 1.0.6 when dealing with tariffs. It also fixes an issue that could show up in certain LoRaWAN® network server environment, unexpectedly dropping telegrams. Lastly, it corrects the the encoding of the error codes received if the meter communication is not working.
Table 339. Implemented changes
|
ID |
Description |
|---|---|
|
MCM-7633 |
[SOLVED] Fix compatibility with some LoRa networks |
|
MCM-7402 |
[SOLVED] Tariff information still present in transmission payload after changing Tariff unit in meter |
|
MCM-7694 |
[SOLVED] Error codes wrongly encoded when meter communication is not working |
Release date: 2025-01-31
Notes: In previous releases, CMi4160 does not handle tariff registers other than energy. This release makes it possible to also handle volume and time tariffs. Please note! If changing tariff settings in the meter, make sure the CMi4160 is rebooted afterwards to ensure proper tariff handling. Reboot can be triggered either remotely via LoRaWAN downlink, or locally via the Elvaco OTC App.
Table 340. Implemented changes
|
ID |
Description |
|---|---|
|
MCM-7130 |
Handle tariff data with different units (Energy/Volume/Time) |
|
MCM-7387 |
[SOLVED] Messages sent at startup or manually triggered should not have timestamp rounding |
Release date: 2022-09-16
Notes: Implements a new message format, Schedule Extended+
Release date: 2020-11-23
Notes: Firmware change to comply with ETSI duty cycle requirements
Release date: 2020-05-06
Notes: Adjusted an error in the JSON message format.
Comments (0 comments)