Release Notes

March 16th, 2019

--incomplete list--

Fixes:

An edge case where a bolus under 0.50U could be transmitted twice, if radio reception follows a pattern of: Barely possible for 30 seconds - complete breakdown for 60 seconds at the right moment of the message sequence, and barely working again for the next 30 seconds. Omnipy will now recognize the failed attempt and recover the pod from crashing if it becomes reachable within 4 minutes.
Fixed bug in UDP beacon service, now AAPS will detect the ip address of omnipy automatically if configured to do so.

New features & improvements

Intermittent BLE disconnections (due to reception or RL battery issues) now will be recovered automatically during message transmission to prevent total communication failures.
Adaptive power amplification during message transmission for faster and more reliable operation when the RL and pod are too close, or are too far.
Better Android APS stability and performance via complete rework of how AAPS communicates with the omnipy API.
Connection and disconnection from omnipy now indicated in the UI via standard AAPS interface style.
"Omnipod/PDM" tab now shows a brief status of connection to omnipy and some information on the active pod.
Added an update script for future versions
omnipy service will now perform a graceful shutdown and wait for the currently running comand to finish.
Reduced file i/o on the SD card to improve stability

Known issues

SetBasalProfile is faking the action as before in v1.0, no actual basal profile changes are sent to the pod.

Links

March 3rd, 2019

Provide feedback