v1.5.0 Beta Release

Omnipy v1.5 Beta

Featuring small fixes and huge improvements

Omnipy v1.4.3

Download the image file omnipy.1.4.3.zip, unzip it and write it to an sd-card for your raspberry pi.

Note: The image is a full-install only and as such will erase information on your current and previous pods. Do not install the image until you are ready to activate a new pod - or if you don't know how to resume an active pod from the command line.

See release notes for details.

Use the latest AndroidAPS for omnipy v1.4.3 build 3 with this release.

For further information on setup, refer to the Setup & Configuration section on the wiki.

Omnipy v1.4.2

Download the image file omnipy.1.4.2.zip below, unzip it and write it to an sd-card for your raspberry pi.
If you're having problems extracting the image file, download the slightly larger omnipy.1.4.2-deflate.zip file instead.

Note: The image is a full-install only and as such will erase information on your current and previous pods. Do not install the image until you are ready to activate a new pod.

If you want to upgrade and keep all your settings, you have to do it manually with ssh. Connect to your pi and execute the following commands:

cd ~/omnipy
./scripts/pi-update.sh

See release notes for details

Use the latest AndroidAPS client v1.4.1 with this release.

For further information on setup, refer to the Setup & Configuration section on the wiki.

v1.4.1

The image for this release is not yet build, you can however perform the upgrade using ssh with the following commands:

cd ~/omnipy
./scripts/pi-update.sh

See release notes for details

Don't forget to build the corresponding AndroidAPS client

For further information on setup, refer to the Setup & Configuration section on the wiki.

Omnipy v1.4

This release contains the following items:

• omnipy1.4.0.zip: Zipped binary image file for the sd card to be run on raspberry pi.
• omnipy1.4.0-AAPS2.3.0.apk: Android APS v2.3.0 for omnipy v1.4 application, to be installed on the android device. (File removed per request of Milos Kozak, owner of the original AAPS repository which omnipy-AAPS forks from)

See release notes for details

For further information on setup, refer to the Setup & Configuration section on the wiki.

v1.3 - preliminary release alpha 06

Removed fw update procedure
Raspberry pi will be discoverable as long as there are no paired devices
Pairing process does not require a PIN anymore
Now works on huawei p20pro and galaxy s9 - hopefully all other newer androids.

Following empty files can be placed in boot for various recovery:

/boot/omnipy-btreset
/boot/omnipy-pwreset

v1.3 - preliminary release alpha 05

Fixed build issues with image as described in v1.3.4: No manual rebooting necessary, file system resizing and firmware update will be executed upon two automated reboots on the first run. Bluetooth setup will launch in approximately 4 minutes.

Fixed duplicate method names in restapi, which would have crashed the application if the methods were used (unused currently)

v1.3 - preliminary release alpha 04

Note: something went wrong during imaging process, this image has therefore quite the limited space. I'd suggest using raspi-config to "extend fs" after everything is set up

Release primarily for testing the new installation image:

Upon starting the image should in order:

• resize itself (standard raspbian behaviour)
• update rpi firmware (required for newly installed components)
• It should reboot - but it doesn't due to error note above, you have to manually reboot it. This means give it 3 to 4 minutes for first boot, then scan and look for the "omnipy" bluetooth device. DO NOT CONNECT to it, instead REBOOT and then you can connect.

this takes around 5 minutes on the pi-zero with a relatively fast sd card. after reboot it will start up omnipy services. As long as there is no bluetooth device associated, the image will start in bluetooth discoverable mode and wait for a pairing request from an android device.

On your android, turn on bluetooth tethering and look for the bluetooth device "omnipy" and pair with it using the PIN: 3434

After pairing, the raspberry pi ("omnipy" bluetooth device) will connect to your android for bluetooth tethering.

The omnipy service has the default password: "piesnotalie" (without quotes)
The default password on the raspberry pi image for the "pi" user is "omnipy" (without quotes)
You can ssh to it directly from your android (find out the IP in android aps by selecting search automatically) or you can put the wpa_supplicant.conf file into the /boot partition manually to have it connect to your wifi.

you can also have your bluetooth configuration reset by putting an empty file in the boot partition with the name "omnipy-btsetup"

to have the raspberry pi password and omnipy password reset to defaults (see above) put the following empty file into the boot partition: "omnipy-pwreset"

to force a firmware upgrade: "omnipy-fwupdate"

Note: AAPS release not there yet, but you can grab the latest from omnipod_dev branch

v1.3 - preliminary release alpha 03

Known issues:
Basal profile cannot be updated, when a temp basal is active (aaps tries to do it all the time, better disable loop, cancel temp basal, let it run and then continue loop)

No AAPS user interface for activating a new pod: use the ./omni.py command as follows

./omni.py archive or ./omni.py deactivate (to get rid of the existing pod)
./omni.py activate 120 (activate a pod with pod time set to UTC + 2h, i.e. GMT+2h)
./omni.py start 1 (set a fixed rate basal of 1u/hr for whole day, start the injection process) (you can change basal rate later in aaps)

v1.3 - preliminary release alpha 02

fixes python 3.5 compatibility errors