Release notes - OneMeter Device¶
| version | published | milestone |
|---|---|---|
| 0.24.0 | 30 Aug 2024 | Device operating parameters configuration and several improvements. |
What's new?
Features¶
Device operating parameters configuration¶
Now you can set the reading period, discoverability and data accuracy. OneMeter 1.2.0 (or newer) app is required.
The configuration selected by the user will be applied by the device if possible and depending on the service type.
More information: Settings · Readout mode.
Improvement in meter communication protocol selection¶
From now on, you can inform the device that it has been placed on a LED of the meter blinking in tact of energy consumption instead of an optical port, allowing you to skip the blink detection step before installation when it may be difficult (e.g. the current power consumption measured by the meter is too low). OneMeter 1.2.0 (or newer) app is required.
Possibility to increase data accuracy¶
We have added the option to select precision of three or two decimal places (0.001 and 0.01 respectively). For example, if the meter provides a measurement of 123.456 kWh, in the cloud you will get a value accurate to 1 Wh (instead of 10 Wh), obtaining 123.456 kWh (instead of 123.45 kWh).
The use of higher data accuracy makes sense when the meter provides data with no worse accuracy. This can be important if so-called transformers are used and a multiplier (e.g. x10 or greater) is applied to the data.
The option is available depending on the service type.
More information: Accuracy.
Detection of reading value overflow¶
The device will signal when the most important reading values are overflowed (do not fit within the device data structure).
| State | Description |
|---|---|
 Value overflow | Some data from the last reading may have exceeded the maximum values allowed by the device. Ask your electrician about the use of so-called transformers and apply a multiplier to avoid this inconvenience. |
More information: Accuracy · Device status.
Simplified failed readout count¶
Previously, Failed readouts count could be confusing because it was related to the details of the communication protocol (number of failed readout attempts on the first / second message). We replaced it so that it is easy to understand. It currently means the number of failed reads since restart (e.g. battery change), so it is simply the opposite of the value Succeeded readouts.
More information: Special codes.
(Germany) Reactive energy reading for SML meters¶
If the SML meter (available in Germany) provides a reactive energy reading, it will be compatible with the device.
More information: Reactive energy · Meter protocols.
Fixes¶
Accelerated synchronization of reading history¶
Synchronization of readout history saved to the device memory should be slightly faster. OneMeter 1.2.0 (or newer) or OneMeter Lite 0.4.42 (or newer) app is required.
Adjusted device response time to meter response¶
This may positively affect compatibility with meters that were previously considered incompatible or on which installation failed.
The change will not provide compatibility with DLMS meters or meters that have their optical port blocked. More information: Meter protocols.
Easing energy optimization during meter communication¶
This may result in better communication with meters for which the device regularly required multiple reading attempts to successfully read the meter.
Faster termination of device connection after installation interruption¶
Previously, the device could continue to attempt to read the meter for a longer period of time despite the user cancelling the installation or cloud error occurred (for example), flashing a green LED as if it was still connected to the phone.
The device should now terminate the installation attempt more quickly, within a few seconds.
Improved installation errors¶
When an error occurs during installation, the device will provide slightly more specific information that may help determine the cause of the error.
(Czech) Added missing OBIS codes for tariff consumption charts¶
Some users in Czech Republic have reported a problem with the lack of a graph of energy consumed in the high tariff (VT) and low tariff (NT). Since now, the device can save and advertise the appropriate OBIS codes in memory so that the problem does not occur.
However, to fully remove the fault, it is necessary to reinstall the device or use the OneMeter gateway, because until OneMeter is reinstalled, new OBIS codes will not be saved in the device memory.
Fixes (invasive)¶
(Germany) Improved counter values for SML counters¶
The absolute value shown in the cloud could not match what was shown on the display of SML meters (available in Germany) that provided data with a large multiplier value (so-called scaler).
We have implemented a fix that could cause data discontinuity for some SML meters.
If a device with an older firmware version is currently installed on the meter in Germany, updating the firmware to this version may cause side effects
In this case, we suggest updating your device only after uninstalling it.
The issue and fix for this bug affects at most a few of the users who installed the device on the meter in Germany before the patch was released.
Potential data discontinuity - Information for users of devices installed in Germany
If you installed the device in a country other than Germany, this thread does not apply to you.
If you installed the device with firmware version 0.24.0 (or newer), this thread does not apply to you.
If your meter has a relatively low counter of the energy taken or given off (say < 100 MWh), then this thread does not apply to you.
If you are not a prosumer or a company, this thread rather does not apply to you.
If the value shown in the cloud does not match the value on the display of your SML meter (available in Germany), please read the information below.
Problem description
If the SML meter indicated a high counter value, e.g. energy consumption, the device could interpret it incorrectly. You could observe either a different value than on the meter display from the moment of installation or a sudden jump in value after some time from installation and then a linear, realistic increase in value. With this software, we correct the mentioned error of incorrect data interpretation, but there will be side effects.
If your meter showed a high enough value or the value available in cloud was different from the value on the meter display, then meter reading after the update may again show a different value than previously expected, which this time should be the same as the value available on the meter display (as long as it does not exceed the limitations of the maximum value processed by the OneMeter system). This may cause difficulties in accessing cloud charts and tables.
Currently, the maximum counter value allowed by the device is still limited. Exceeding the value will cause overflow and similar data discontinuity. If the counter measures very large changes in value, it is suggested to use so-called transformers and apply the multiplier in the cloud.
What to do next?
Continue using your device with a firmware version older than 0.24.0 or reinstall your device. During a new installation, the device will update to version 0.24.0 and after installation the problem should not occur (and any possible overflow of the counted value after exceeding the maximum value processed by the OneMeter system will take place in a more controlled manner).