Release notes
Release date: 2025-10-03
Note
Upgrading from previous versions of the FW will delete all stored meter data. So, before starting a remote update, ensure that all data has been collected to avoid losing it.
Background: Due to a bug that was identified at a late stage, the FW 1.4.0 was never practically released to the market. To keep traceability, it's however noted here as well. This new FW introduces several new features, focusing on improving the device and meter monitoring. The firmware is also adapted to make CMi6110 G2 RED Cyber Security compliant. Highlighted features:
Push of alarms: Having this feature enabled, the device can push alarms appearing in the meter. This enables quick response to issues in field.
Dynamic message format: Using the newly introduced Measurement mode Transparent, the module will transparently forward the customer defined telegram from the meter. Thanks to this, you no longer need to rely on the already defined message formats in the module.
Automatic configuration lock: To improve the security and access control to the device, the NFC configuration lock is automatically applied after activation. This prevents unauthorized access to the device.
Note
The automatic configuration lock is enabled by default with a 15 min timeout counting down from activation. To get access to the device once locked, local access requires possession of the product access key (PAK).
Syslog capabilities: Thanks to the syslog, events over the lifetime of the module and meter can be traced. The feature can be helpful when assessing the overall performance/health of the device
Configuration changes: No changes to the default configuration have been made, but several new configuration possibilities have been added. The list below specifies the new parameters. Default values for the new parameters are given within parenthesis "()":
|
Related feature |
New parameter(s) |
Default value |
|---|---|---|
|
NFC Autolock |
NFCAutoLockEnable |
Enabled |
|
NfcAutoLockTimeout |
15 min |
|
|
Improved bootstrap |
BootstrapServerURIStaging |
Empty (used for remote updates of bootstrap URI) |
|
Measurement mode (transparent forwarding) |
MeasurementMode |
Preset mode (i.e. not using transparent forwarding) NoteWhen changing Measurement Mode (between Preset/Transparent) the module will only send data stored in the configured mode. Historic readout of old values will only send data stored in the currently configured mode. |
|
System logger |
SyslogLevel |
INFO |
|
SyslogMqttSnTopic |
elvaco/#P/cbor/syslog/#D |
|
|
SyslogAutoUploadLevel |
NOTICE |
|
|
SyslogAutoUploadAgeLimit |
14 days |
Note
The parameters to control what bootstrap to connect to have been updated in the Elvaco OTC App. Instead of defining BS port + BS IP (or BS hostname) + BS security, all of this is now given in a complete BS URI. Previous settings will become obsolete.
Integration considerations:
-
MCM Config (33906 v2.4 → v2.12
-
New resources added for supporting new functionality (resource 61 - 72)
-
-
Elvaco Meter Info (33908 v2.0 → v2.4)
-
Clarification of range of resource 2 (Communication status)
-
Additional resource 4 for Extended Error Codes (used in conjunction with Alarm)
-
-
Elvaco NB-IoT Status (33907 v2.0 → v2.4)
-
Additional resource 12 (Current Access Technology)
-
-
Elvaco syslog config (33918 v1.0)
-
New object
-
Table 167. Implemented changes
|
ID |
Description |
|---|---|
|
MCM-7960 |
Factory reset deletes meter data, syslog and credentials |
|
MCM-7959 |
Factory reset resumption after interruption |
|
MCM-7561 |
Automatically lock NFC configuration after activation |
|
MCM-7332 |
Persistent user defined credentials for BS+DM+MDM |
|
MCM-7304 |
Support FW06 for Diehl Sharky without encryption |
|
MCM-7302 |
Support observations based on value changes |
|
MCM-7275 |
Push of alarms CMi6160 |
|
MCM-7184 |
Syslog for CMi6160 |
|
MCM-7130 |
Handle tariff data with different units (Energy/Volume/Time) |
|
MCM-5126 |
Add NFC command to force DM Registration Update |
|
MCM-3961 |
Transparent M-Bus format CMi6160 |
|
MCM-3733 |
Change bootstrap server via DM |
|
MCM-3477 |
Set user defined credentials via NFC for BS+DM+MDM |
|
MCM-8227 |
[SOLVED] BCD conversion not correctly handling non-numeric values from meter |
|
MCM-8202 |
[SOLVED] Fix correctly detecting FW-02 in Sharky |
|
MCM-8106 |
[SOLVED] NFC write to UTC offset is very slow when no meter is attached |
|
MCM-7682 |
[SOLVED] Fix large NFC writes not being applied |
|
MCM-7643 |
[SOLVED] Buffer for MDM server is too small for writing hostname |
|
MCM-7556 |
[SOLVED] Pressing button in Standby mode does not check AAF state |
|
MCM-7555 |
[SOLVED] Message after activation at flow missing values |
|
MCM-7542 |
[SOLVED] Config not applied in device even if DM receive write response 2.04 changed |
|
MCM-7412 |
[SOLVED] Refresh data model gives error on Meter Data object 33911 |
|
MCM-7395 |
[SOLVED] Fix disconnect from MQTT-SN server not handled correctly |
|
MCM-7387 |
[SOLVED] Messages sent at startup or manually triggered should not have timestamp rounding |
|
MCM-7354 |
[SOLVED] RSRP not scaled correctly in LwM2M Connectivity Monitoring object |
|
MCM-7335 |
[SOLVED] NFC write of MQTT-SN topic not working |
|
MCM-7121 |
[SOLVED] No valid meter time after brown-out and stores the first readout wrong |
|
MCM-4400 |
[SOLVED] Fix showing meter com OK before module has initiated meter communication |
|
MCM-8309 |
[SOLVED] Timestamp included in LwM2M Send not correctly handling UTC time |
|
MCM-6463 |
[SOLVED] Improve Bootstrap URI string validation |
|
MCM-3293 |
[SOLVED] Meter ID in JSON does not contain all information |
Warning
There's a known bug in the FW 1.3.2 making devices being unreachable in case of doing a firmware over the air update to this firmware in case using manual APN. Thus, Elvaco strongly advises to not do FOTA till FW 1.3.2. Devices successfully updated to 1.3.2 will operate normally.
Release date: 2025-03-04
Configuration changes: This release includes two changes in the default settings.
Note
Pay extra attention to MCM-7113 where the default settings have been updated. Change details:
Tx Offset: 30 min → 45 min
Tx Delay: 240 min → 125 min
These settings will improve the delivery of meter data occurring on top the hour.
Note
Pay extra attention to MCM-7070 where the default settings have been updated. Change details:
Message format: Tariff → Standard
By convenience, the default message format has been changed to Standard.
Integration considerations: Two new parameters have been added:
-
DTLS max rewind: 10 - Limits the number of restarts of DTLS handshake in case of server errors
-
Home PLMN search: 0b10 (feature turned off) - The home PLMN search will search for the SIM home network periodically. This is detrimental to battery lifetime and therefore turned off by default.
The MCM Config object increased version 2.4 → 2.8 with the two added parameters above.
Background: The main feature of this release is the automatic activation at flow feature, allowing the module to automatically active when enough water has flowed through the meter. This allows a more efficient yet battery friendly installation procedure.
Table 168. Implemented changes
|
Change ID |
Description |
|---|---|
|
MCM-7113 |
Change default transmit offset/delay to improve delivery performance |
|
MCM-7070 |
Factory default message format set to Standard |
|
MCM-6950 |
Read power source from meter |
|
MCM-6829 |
Upgrade LwM2M stack (IOWA) to 2023-09.2 |
|
MCM-6358 |
Product activation at detection of water flow |
|
MCM-5812 |
DTLS handshake supervision |
|
MCM-2769 |
Send additional readout only when time sync moves time past planned readout |
|
MCM-6716 |
[SOLVED] L4 Auto PLMN issue |
|
MCM-6343 |
[SOLVED] Handle error code 03 on MQTT-SN Publish |
|
MCM-6299 |
[SOLVED] Process PLMN code as per the 3GPP standard (leading zeroes considered as significant) |
Release date: 2024-03-18
Configuration changes: No changed configuration parameters.
Integration considerations: Object versions for 33905 and 33906 changed due to changes in definitions/descriptions, see ID MCM-6359 and MCM-6214 below.
Background: This release mainly fixes an issue related to LwM2M send, detected in the previous firmware release of CMi6160. If not using the LwM2M send feature, devices are operating as they are intended to do. In addition to adding some general improvements and fixing some bugs, it also adds the possibility to manually configure PLMN using NFC.
Table 169. Implemented changes
|
ID |
Description |
|---|---|
|
MCM-6367 |
Possibility to manually configure PLMN via NFC added |
|
MCM-6406 |
[SOLVED] Value sometimes sent with wrong timestamp in CBOR payload |
|
MCM-6381 |
[SOLVED] Previous manual PLMN configuration could lead to lost network connection |
|
MCM-6359 |
[SOLVED] LwM2M resource 33906/0/57 defined as bool instead of integer |
|
MCM-6308 |
[SOLVED] Possible error when reading entire object 33906 (MCM Config) if having resource(s) not implemented within the object |
|
MCM-6277 |
[SOLVED] LwM2M Send transmitted at the same time as Reg Update fails |
|
MCM-6214 |
[SOLVED] Misleading information in LwM2M XML for objects 33905 and 33906. Range for /33905/../2 updated to 0..3 to match implementation. Object versions incremented to indicate change. |
|
MCM-5924 |
[SOLVED] Device could send zero energy value if unable to read meter |
Release date: 2024-01-05
Configuration changes:
-
Added Bootstrap URI as alternative to bootstrap IP
-
Added Manual PLMN with staging for setting PLMN in device
-
Added MQTT keep alive timeout (was previously hard coded to ~18h)
-
Added LwM2M force queue mode setting to control if queue mode is used.
Notes New LwM2M object version set for /33906/x/x/ (MCM Config)
Background: This new firmware comes with several new features improving the overall performance of the CMi6160, see list of implemented features below. Please note that the new firmware name is 1.3.0, replacing 1.1.0. To harmonize the naming of products using the Elvaco NB-IoT platform, the sequentially correct naming, 1.2.0, has been skipped intentionally.
Table 170. Implemented changes
|
ID |
Description |
|---|---|
|
MCM-6182 |
Object version for MCM Config Object (33906) updated to 2.2 |
|
MCM-5610 |
Added configuration to manually select network (PLMN) |
|
MCM-5608 |
RTC timestamp is used for LwM2M Send |
|
MCM-5580 |
Configure client usage of LwM2M Queue Mode |
|
MCM-5554 |
Modem IMSI is now readable in production |
|
MCM-5372 |
DTLS Connection ID (53->54) updated according to DTLS 1.2 (RFC 9146) |
|
MCM-5102 |
Added Release Assistance Indication (RAI) support for LwM2M |
|
MCM-4735 |
Possible to configure bootstrap server using URI |
|
MCM-3871 |
MQTT-SN Compliant timeout is now configurable |
|
MCM-6099 |
[Solved] Allow correct maximum values for T3412 and T3324 according to 3GPP TS 24.008 |
|
MCM-6047 |
[Solved] Bad range/description for XML resource /33906/0/51 Enable RAI |
|
MCM-5922 |
[Solved] MD Upload via LwM2M does not work when same Tx Interval and DM Lifetime |
|
MCM-5403 |
[Solved] BC66 modem driver misses incoming back-to-back packets |
|
MCM-5119 |
[Solved] Resource changes from DM not always applied in device |
|
MCM-4759 |
[Solved] Readouts and uploads can be accidentally started via NFC in inactive mode, leading to unplanned meter readouts and higher power consumption |
|
MCM-4533 |
[Solved] Registation Uptime resource (/33909/0/6) is reset by PSM |
|
MCM-4356 |
[Solved] Trigger sending of readouts using LwM2M in Queue mode not working |
|
MCM-3916 |
[Solved] Factory reset via LwM2M not supported |
|
MCM-3736 |
[Solved] MDM Uploads stopped working in Compliant mode |
|
MCM-3735 |
[Solved] MQTT-SN Compliant mode not working |
|
MCM-3697 |
[Solved] In conversion from BTU to Wh, large BTU values causes overflow to negative Wh values |
Comments (0 comments)