A snap for Ubuntu Core intended to run on a Raspberry Pi as an internet-connected digital picture frame.
A Raspberry Pi with a screen that loops over a local directory with pictures and periodically refreshes these from a Backblaze B2 bucket. New pictures in the bucket will, after a while, automatically show up on the picture frame. New pictures can be added via a public webpage.
We can no longer visit my grandmother - something to do with a worldwide pandemic - and she has no interest in learning how to use a tablet for video calls. She has one of these digital picture frames with the same 20 photos for years now. If only we would remember to refresh the pictures from time to time! Oh, wait, what if the family could send pictures to the device directly? A quick photo from the grandchildren at school? A picture of her newborn great-grandchild in the hospital?
A little webpage where family and friends can upload images to a Backblaze B2 bucket on one side, a Raspberry Pi with a screen on the other. The Raspberry refreshes the pictures multiple times per day.
A bit geeky but not too much: no soldering or programming required. You’ll need a Raspberry Pi, tested with a 3 model B, but any will do, with a screen. This should cost you around €90.
Install Ubuntu Core on the Raspberry Pi. Ubuntu Core is a self-updating read-only (almost) OS. We could use any Linux for this project, but Ubuntu Core and the applications (called snaps) will automatically update. This helps to keep maintenance low. Configure the wifi or connect the Pi via ethernet.
Create a Backblaze B2 bucket and add some (family) pictures. Create a new App Key pair with read and write access to the bucket while you are at it.
You’ll also need to configure custom CORS headers on the bucket to allow for file uploads. This needs to be done via the B2 command line tool. Replace the NNNN with the Backblaze subdomain for your bucket (check the friendly URL on any file in the bucket or use the downloadUrl from b2 get-account-info).
$ b2 update-bucket --corsRules '[
{
"corsRuleName": "uploadsFromOmaBOX",
"allowedOrigins": ["<https://NNNN.backblazeb2.com>"],
"allowedHeaders": ["*"],
"allowedOperations": ["b2_upload_file"],
"exposeHeaders": ["authorization", "x-bz-file-name", "x-bz-content-sha1"],
"maxAgeSeconds": 3600
}]' <bucket-name> allPublicNext, install the mir-kiosk snap on the Raspberry Pi to run graphical applications. The omaBOX snap is next, it adds an image viewer and some scripts to tie the whole thing together. Configure the B2 bucket and App Key pair.
$ snap install mir-kiosk
$ snap install omabox
$ snap set omabox b2-application-key-id=123abc b2-application-key=abc123 b2-bucket=abcWait for up to an hour for the Pi to sync and show the photos on the screen. An index.html file will appear in the bucket as well, this can be used by friends and family to quickly add new photos.
Each picture will be shown for 10 seconds, this can be changed via the omaBOX configuration settings on the Raspberry Pi. Pictures will be removed after 30 days, this can be configured as well.
$ snap set omabox imv-duration=30 # defaults to 10 sec
$ snap set omabox remove-after-days=10 # defaults to 30 daysThe omaBOX can optionally dim the screen after sunset. Connect the display-control plug to give the omaBOX the necessary permissions to dim the screen. For now, it uses UTC and a location in central Europe to detect sunrise and sunset, this still needs to be improved.
$ snap connect omabox:display-controlOptional. My omaBox connects to the internet via a 4G USB stick. Sometimes Ubuntu connects to the wifi before the stick has finished booting. As a workaround, the network interface can be restarted daily. For this, the omaBOX needs network setup control. It’s a hack, and you probably don’t need this.
$ snap connect omabox:network-setup-control
This section explains the inner workings of the omaBOX snap and is not needed to get your omaBOX up and running.
The omaBOX snap has 4 main components, all run locally on the Raspberry Pi.
The imv image viewer for the heavy lifting of showing the pixels on the screen.
A Python script that syncs the images from the bucket to the Pi via the B2 SDK library. It runs hourly but this can all be tweaked in the snapcraft.yaml.
An upload script to refresh the B2 authorization key and upload URL in the index.html and upload it to the bucket, also via the B2 SDK. The index.html is a simple website so friends and family don’t need access to B2 bucket. Since the B2 authorization key is only valid for 24 hours the upload needs to run daily. The index.html also resizes the pictures before uploading, it’s faster and I noticed imv has issues with larger images.
The index.html is a single HTML page for easier installation. The upload/src folder is for development. Inline the JavaScript, CSS, and logo with inliner to the upload/dist folder before building a new snap.
inliner --nocompress upload/src/index.html > upload/dist/index.htmlThe brightness script uses a hard-coded (for now) latitude and longitude to detect if it’s daytime. If so, it increases the brightness of the screen to 90 (maximum is 255). After sunset, it drops the brightness to 20. Since snaps are confined, and this script needs access to a system file you need to manually grant permissions by connecting the display-control plug (see above).
-
Why is the screen upside down?
Depending on your hardware the screen might be upside down. We can rotate the screen in the Ubuntu Core or mir-kiosk config.
-
How do I change the network settings?
You can change the network settings via the
console-confcommand. -
Why does it show a number after the index.html file in my Backblaze bucket?
The script reuploads the index.html file over and over with a new authorization key and upload URL. Backblaze will keep old versions around for one day before deleting them, even with the lifecycle settings set to only keep the last version.
The snap itself, imv, and B2 SDK library are all MIT licensed. The omaBOX was forked from the picviewer-kiosk snap. The logo is from unDraw.