|0.20.3||2 Apr 2021||Resolving OBIS 1.8.1, 1.8.2 and last readout synchronization issues.|
Resolving last readout synchronization issues.
During synchronization, the phone asks OneMeter device for the last reading data first. This data has not been synchronized since the 0.20.0 firmware. Fortunately, though, the most of data was coming to the server, because either were advertised by the device or sent during the further phase of the synchronization.
OBIS codes 1.8.1 and 1.8.2 will be stored more frequently.
Until now, the
1.8.2 OBIS codes were stored in the memory of the device if and only if both were non-zero and shared by the meter during installation. Since now, if any of them has non-zero value (during installation), it will be stored in memory, i.e. synchronized.
More information: Processing policy of OBIS codes.
Resolved special codes synchronization issues.
The special codes (e.g. number of successful readouts, battery state) have been synchronized improperly. However, the advertising process was not affected. Since now, you should see less "holes" in your readings table on Cloud.
Decreased power consumption during a readout.
The power consumption in readout has been reduced by a few percent. The light levels of infrared transmission have been distributed evenly.