<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>A Connected Frame on Reeveel</title><link>https://blog.getreeveel.com/tags/a-connected-frame/</link><description>Recent content in A Connected Frame on Reeveel</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 28 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.getreeveel.com/tags/a-connected-frame/index.xml" rel="self" type="application/rss+xml"/><item><title>A connected frame: from firmware to app.</title><link>https://blog.getreeveel.com/blog/posts/unframed-2-a-connected-frame/</link><pubDate>Fri, 28 Aug 2026 00:00:00 +0000</pubDate><guid>https://blog.getreeveel.com/blog/posts/unframed-2-a-connected-frame/</guid><description>&lt;h2 id="where-it-started-python-a-raspberry-pi-and-a-power-cable"&gt;Where it started: Python, a Raspberry Pi and a power cable&lt;/h2&gt;&#10;&lt;p&gt;Before the ESP work began, I had been experimenting with the most straightforward path: a &lt;a href="https://www.raspberrypi.com/"&gt;Raspberry Pi&lt;/a&gt;, some Python scripts, images pushed to the e-ink screen over WiFi. It worked, technically. But you had to keep the Pi plugged in at all times, it was the size of a brick, and calling it &amp;lsquo;wireless&amp;rsquo; was generous.&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="https://blog.getreeveel.com/images/posts/unframed-02/raspberry-setup_hu_92b5e4ae4f5f6187.webp" srcset="https://blog.getreeveel.com/images/posts/unframed-02/raspberry-setup_hu_92b5e4ae4f5f6187.webp 640w" sizes="(min-width: 760px) 700px, 100vw" width="640" height="1138" alt="Raspberry Pi setup, the very first working prototype" decoding="async" data-zoom-src="https://blog.getreeveel.com/images/posts/unframed-02/raspberry-setup_hu_92b5e4ae4f5f6187.webp" loading="lazy"&gt;&lt;/p&gt;</description></item></channel></rss>