Release Notes

The following release notes apply to Veva III - E01 and W01 models.

5.3.27 (October 8, 2026)¶

• FIX: MQTT publishing of peak data is occasionally missing data samples. The modem lost connection, requiring a restart and a purge of the MQTT message queue. The purge was removed so MQTT can continue to queue messages until it is able to recover.
• FIX: Improved handling of MQTT network issues. Added code to handle all possible MQTT network events. When packet errors are experienced, device retries up to 5 times with delays in between attempts. Other types of errors (i.e. Authentication, Server, Protocol, Unauthorized, etc.) triggers a MQTT initialization after 5 minutes.

• FIX: Improved handling of FTP uploads. The device now sends files in 512KB chunks rather then 16KB chunks. The wait timeout on the FTP server response increased from 60 seconds to 180 seconds. Uploads should be faster and smoother as the FTP server does not have to append data to the files. This should also reduce battery power required to transfer the data.

5.3.21 (February 3, 2026)¶

• FIX: Defensive fix implemented to prevent a rare occurrence where the vibration data appears to switch axes, then back (e.g. data from Z and Y axes switches) This issue was usually triggered when the histogram file upload cycle timer expired.
• FIX: Defensive fix implemented to prevent the timezone offset of the alarm trigger time in an MQTT alert message from differing by one hour from the alarm trigger time in the waveform data file. This causes the alarm record to be duplicated in Inzwa Cloud.
• KNOWN ISSUE: When audio alert is enabled, the audio alert file may contain Lmax value that is lower than the trigger level. For example, Trig Level=80, but Lmax=73.97.

5.3.20 (December 23, 2025)¶

• FIX: When MQTT is disabled because of connection error, MQTT will be enabled when the cellular communication module is periodically reset during the "Modem Reset Cycle." Prior to this fix, MQTT was enabled only when the device was reset or power cycled.
• FIX: Fixes issue where device produces histogram data with zero values when the sensor is idled by running the 'sensor idle' command.

5.3.19 (December 12, 2025)¶

• FIX: In the event of the device losing contact with the accelerometer, the device will reset itself.
• KNOWN ISSUE: When the accelerometer is idled by running the 'sensor idle' command, the device generates vibration peak data with zero values.