Of Notes
reMarkable 2 Smart Immich Photo Frame
Table of Contents
Idea
Use a reMarkable 2 as a low-power E-ink smart photo frame, with a Raspberry Pi Zero W fetching images from Immich (see Self Hosting), preprocessing them for E-ink, and displaying them on the reMarkable.
The reMarkable 2 has a 1404x1872 grayscale E-ink display, making it well suited to portrait photographs and static content.
Basic Architecture
Immich Server
|
| API
v
Raspberry Pi Zero W
|
|-- select image
|-- crop to 1404x1872
|-- grayscale
|-- contrast correction
|-- optional dithering
v
reMarkable 2
|
`-- E-ink photo display
The original Raspberry Pi Zero W should be sufficient because the workload is very light and images only need to change occasionally.
Initial Prototype: VNC
The easiest MVP is to treat the reMarkable as a remote display.
Pi Zero W | | TigerVNC | virtual X display: 1404x1872, 16-bit RGB565 v reMarkable 2 | `-- VNSee-QTFB
The Pi could run:
- Raspberry Pi OS Lite
- TigerVNC
- Openbox or another minimal window manager
fehor a tiny custom image viewer- Python / Pillow or ImageMagick for image processing
The image viewer simply displays a file such as:
/frame/current.png
A script periodically replaces this file and refreshes the viewer.
This avoids dealing directly with the reMarkable framebuffer while prototyping.
Immich Integration
Use an Immich API key with minimal read/search permissions.
The Pi could select photos from:
- random assets
- a dedicated photo-frame album
- favorites
- recent uploads
- a particular person
- a particular year
- a weighted mixture of several sources
For example:
50% dedicated frame album 20% favorites 20% older/random photos 10% recently added
A rough update loop:
while True:
asset = immich.get_random_photo()
image = immich.download_preview(asset)
image = crop(image, 1404, 1872)
image = grayscale(image)
image = enhance_contrast(image)
image = dither(image)
image.save("/frame/current.png")
refresh_viewer()
sleep(30 * 60)
E-Ink Image Processing
The preprocessing stage is likely important for making photographs look good.
Possible pipeline:
original image
|
v
smart crop
|
v
grayscale
|
v
local contrast enhancement
|
v
gamma correction
|
v
grayscale quantization
|
v
dithering
Possible rendering modes:
Photo
High-quality grayscale with subtle dithering.
Document
High contrast and little/no dithering.
Sketch
Edge-enhanced rendering.
Newspaper
Ordered dithering / halftone style.
Useful algorithms to test:
- Floyd-Steinberg dithering
- ordered/Bayer dithering
- grayscale quantization
- CLAHE/local contrast enhancement
Metadata Overlay
The rendered image could optionally include understated metadata such as:
Prague · October 1987
Potential metadata:
- location
- date
- year
- album
- people
- short caption
It should remain subtle so that the device still feels like a physical photo rather than a dashboard.
Battery-Powered Version
The entire setup could be battery powered.
A simple version:
10,000-20,000 mAh battery
|
+-----+-----+
| |
Pi Zero W reMarkable 2
The Pi is likely the main continuous power consumer.
If the Pi remains powered and connected to Wi-Fi continuously, runtime would probably be measured in days rather than weeks.
Better Power Architecture
A much better design is to turn the Pi on only when an image needs updating.
battery | v power timer/controller | v Pi Zero W | | boot | join Wi-Fi | query Immich | render image | update reMarkable | shutdown v power cut [wait until next refresh]
The Pi Zero does not have a particularly useful ultra-low-power suspend state, so an external timer/controller could physically cut its power between updates.
If an update takes roughly one minute every 30-60 minutes, the Pi's duty cycle becomes very small.
This could potentially extend runtime from a few days toward many weeks depending on the final power setup.
Ideal Final Design: No VNC
The final version should probably remove VNC entirely.
The key property of E-ink is that the screen can retain its image without being continuously refreshed.
The ideal flow is therefore:
Immich | v Pi Zero W | | select + preprocess photo v send static image | v reMarkable displays image | v reMarkable sleeps Pi powers off | v image remains visible
If the current image can be used as the reMarkable suspend/sleep screen, the device could spend almost all of its time asleep while still displaying the photograph.
Example schedule:
08:00 new photo 10:00 new photo 12:00 new photo 14:00 new photo 16:00 new photo 18:00 new photo 20:00 new photo
Only a handful of brief active periods would be required per day.
Physical Build
Potential final form:
+-----------------------------+
| |
| |
| reMarkable 2 |
| |
| |
| Prague · August 1987 |
+-----------------------------+
|
wooden/magnetic
frame
|
+-----------------------------+
| Pi Zero W battery |
| power timer charger |
+-----------------------------+
The electronics could sit behind the reMarkable inside a shallow frame.
Goals:
- no visible cables during use
- USB charging
- several weeks between charges if possible
- removable reMarkable
- minimal UI
- photographs remain visible while sleeping
Recommended Development Path
Phase 1: Prototype
- Raspberry Pi Zero W
- Raspberry Pi OS Lite
- Immich API
- Pillow/ImageMagick
- TigerVNC
- VNSee on the reMarkable
- update every 15-30 minutes
Phase 2: Improve Rendering
Experiment with:
- crop strategies
- E-ink-specific contrast
- dithering
- metadata overlays
- photo selection policies
Phase 3: Native Static Display
Replace VNC with a small reMarkable-side application or framebuffer integration that accepts a prepared image.
Phase 4: Power Optimization
- use the displayed photo as a suspend/static screen
- suspend the reMarkable between updates
- physically power off the Pi
- use an RTC/timer/power-controller to wake the Pi
Main Design Principle
Do not treat the reMarkable as a continuously running computer monitor.
Instead, exploit the defining property of E-ink:
Refresh the display briefly, then let the entire system sleep while the image remains visible.
That turns the reMarkable + Pi Zero W into a potentially very low-power, battery-operated Immich photo frame.