Release notes - OneMeter Device¶
| version | published | milestone |
|---|---|---|
| 0.20.6-cz | 24 Jul 2023 | iOS support and more. |
What's new?
Features¶
iOS support¶
If you want to update firmware of the device to this version, then uninstall it with the recently used mobile app and start installation using the latest OneMeter application (not older than 0.4.25). During installation, the firmware will be automatically updated to a compatible version. Compatibility details below.
| mobile app | firmware | limitations |
|---|---|---|
| ≥ 1.1.0 (iOS) | < 0.20.6-cz | no access on iOS to installed device (please uninstall it with Android app and install again using iOS app) |
| ≥ 1.1.0 (iOS) | ≥ 0.20.6-cz | no |
| ≥ 0.4.25 (Android) | any modern | no |
| < 0.4.25 (Android) | < 0.20.6-cz | no access to firmware update to version ≥ 0.20.6-cz |
| < 0.4.25 (Android) | ≥ 0.20.6-cz | no access to firmware update to version ≥ 0.20.6-cz, device installation impossible |
Increase device discoverability¶
Being aware of the difficulties with connection to the device some clients may encounter, we have added the ability to configure the discoverability level of the OneMeter device. You can change it in the mobile app.
See: Select device discoverability.
LED state during booting and automatic protocol detection¶
Since now, booting procedure (e.g. after uninstallation) is signalized by white color blinking instead of green. When detecting the meter protocol before installation, white color is also used. This way you can simpler distinguish this state from Bluetooth connection state (in which the LED blinks green usually).
More information: Device state.
 | Blinking white | Loading data and device state. Wait a while. |
| Blinking white | The device is preparing for the installation process. Do not remove the battery at this point. |
| Dimming white faster | The meter communication protocol has been detected potentially. Wait a moment. |
 | 1 blink red | Error in meter communication protocol detection. The device will come back to waiting for meter communication protocol detection. |
 | Blinking green | Loading data and device state. Wait a while. |
| Blinking green | The device is preparing for the installation process. Do not remove the battery at this point. |
| Dimming green faster | The meter communication protocol has been detected potentially. Wait a moment. |
| | 1 blink red | Error in meter communication protocol detection. The device will come back to waiting for meter communication protocol detection. |
LED state for exceptional errors¶
The device is indicating exceptional errors during its operation. Device restart is a standard reaction for such cases.
| 3x blink red (fast) | Device state loading failed. The device may require a service. |
| 5x blink red (fast) | Invalid device state or unexpected operation. Contact us if the problem is recurrent. |
Other errors
Apart from the mentioned errors, there are other errors related to the same blink dynamic, but with more blinks. Contact us if you encounter any of them.
Diagnostic information¶
Diagnostic data about the device has been added and will be delivered to the technical support team after the synchronization. This data is necessary to determine the status of the device during troubleshooting.
Fixes¶
Stabilize the speed of data synchronization¶
Until now, synchronization of data stored on the device was slowed down from time to time. After the change, the sync speed should be stabilized.
Advertising > 20 OBIS codes¶
Previously, due to the error, the maximal number of OBIS codes advertised per reading was 20 (approx.). After the change, the device can transfer around 40 OBIS codes to the cloud (depending on processing policy).
Not sending data from last readout after it fails¶
Previously, some data was sent to the cloud during synchronization after a failed readout. This could result in incorrect values (not often). Since now, the device only uploads metadata and diagnostic data to the cloud in such a situation.
More frequent update of device battery state¶
The device updates the battery status every 24 hours at midnight. Previously, if the midnight readout failed, the battery status was not updated.
Note that the user has access to a rough estimate of the battery condition. The improved battery health measurement of the device will be available soon.
Known issues¶
Energy consumption readings not stored in device memory¶
The device with this version of the software did not keep a full history of energy consumption readings in memory available for synchronization, which resulted in data gaps.
The new version with the fix was deployed on 2023-09-06. Please update the firmware.