I had a Kindle Paperwhite doing duty as a Home Assistant (an open-source home automation platform that talks to lights, switches, thermostats, and other smart devices) dashboard for a few months. It worked. I sold the Kindle, bought a 12th Generation Paperwhite to replace it, and tried to set up the same project. Nothing worked. The jailbreak I had relied on no longer applied. The community-built apps had moved on. The firmware had shifted underneath me.
A few weeks ago I went back to it with the new Véra jailbreak. I have a Home Assistant dashboard running on my desk again. It is more fragile than the first one, it does not do everything I wanted, and it took me a full weekend to get working. This is the honest report of what landed and what did not.
The starting point: an e-ink Home Assistant view
The core idea is solid. A Kindle sitting on a phone stand on my desk, showing my smart home state, lights and Apple TVs and PS5 status all visible at a glance. E-ink does not drain battery like an LCD, and the front light means I can glance at it in a dark room without the harsh glow a phone throws off. I do not have to unlock my phone to check if I left the bedroom light on.
Bottleneck is the Kindle browser. It is slow, locked to a specific WebKit version, and any tool that wants modern browser features has to find a way around it. The Kindle SmartHome Dashboard project handles this by routing through a WebSocket proxy (a small relay that translates between the Kindle’s old browser and a modern Home Assistant frontend). It works, but it works on specific Kindle hardware and firmware. That is the part that broke when I moved to a newer Kindle.
The community around jailbroken Kindles is active, but it is also small enough that a single firmware update can wipe out the projects people built. KOReader (an alternative ebook reader app for Kindle) and KUAL (a launcher for Kindle extensions) had been my tools on the older Kindle. On the 12th Gen Paperwhite, neither worked out of the box.
What the new jailbreak actually enabled
Véra is the newer jailbreak for recent Paperwhite models. It landed on my 12th Gen without too much fuss. With it installed, I could put KOReader back on the device. That was the foundation. Without KOReader, I had no way to keep the screen from sleeping every five minutes, and that broke every browser-based dashboard I tried.
The KUAL extensions I had relied on previously were not all functional under the new jailbreak. KUAL Next picks up where the old KUAL left off, but it is a work in progress. Some extensions work. Some do not. I did not find a stable path to a “real” Kindle Home Assistant app. What I found instead was a working browser.
That is the gap to understand going in. The “Kindle as a smart home dashboard” project is, today, mostly “Kindle browser pointed at Home Assistant.” It is not a native app. The trade is real and it shapes everything else.
The interaction problem I kept hitting
The original Kindle SmartHome Dashboard project shows the state of devices. Lights on or off. Apple TVs and PS5s idle or in use. It does not let me tap a button to change anything. For the new build, I expected more. Other builds in the community do offer real control, with webhook taps that fire back to Home Assistant to toggle a device.
My setup did not get there.
The Web App Framework (WAF, a runtime on jailbroken Kindles that lets small apps run on the device) technically supports touch input. The older firmwares rendered WAF apps well. The newer firmware runs the Kindle UI through a different, more modern app layer, and WAF apps do not actually display even when they launch. I confirmed this the slow way, by launching Mesquite (a WAF project) and watching the window not appear. It is a known issue with recent firmware.
The result is that my Kindle dashboard is read-only. I can see what my home is doing. I cannot change it from the Kindle. For a status display, that is fine. For a real control surface, it is not.
If you are starting from scratch, assume you are building a status display. Plan the dashboard for “what is the state of my house right now,” not “let me tap to fix it.” That is the more accurate mental model for what 2026-era jailbroken Kindles can actually do.
The browser approach that worked
Eventually I stopped trying to make a real app work and pointed the Kindle browser at Home Assistant’s own web frontend. It is the same browser the WebSocket proxy was trying to route around. Going direct was simpler.
It works. The dashboard loads. The state shows up. E-ink handles the layout reasonably well, with some caveats I will get to. The Vera jailbreak plus KOReader plus the option to disable the screensaver is the minimum recipe.
What surprised me: I do not miss the control that much. For the things I check on the Kindle (light state, media playback state, weather, room temperature), I do not need to change them from the Kindle. I check, and if I want to change something, I open the Home Assistant app on my phone. The Kindle has become a glanceable status surface, which is what I wanted it to be in the first place.
The rough edges
Ghosting is the first thing anyone with an e-ink device will notice. Near-constant refreshes leave traces on screen, especially on tiles with a lot of text and icons. The weather widget is the worst offender. I do a manual full-screen refresh once or twice a day to clear it.
State changes are not instant. There is a noticeable lag, around half a second, between something happening in Home Assistant and the Kindle reflecting the new state. For “is the light on” queries, that is fine. For “I just toggled something and I want immediate confirmation,” that lag is real.
Browser-based PDF tools and similar heavy interactive pages on the Kindle are slow to scroll and render. That is not a Home Assistant issue. That is the device. Plan accordingly.
The biggest caveat is firmware updates. An automatic Kindle update can undo the entire setup. The jailbreak will need to be redone. KOReader and the KUAL extensions may need to be reinstalled. Any community project that relied on a specific older firmware may not work after an update. Avoid updating your Kindle’s firmware unless you have a reason, and accept that you are signing up to maintain this setup against Kindle’s automatic update cycle.
Trade-offs
An old Kindle as a Home Assistant dashboard is not free in time. My first attempt took a full weekend. The newer attempt took another weekend plus a few evenings. Each was mostly troubleshooting fragile community projects against shifting firmware.
Maintenance is the real cost. Firmware updates will undo work. You will reinstall things. You will tweak configs. You will accept that “Kindle” projects age out faster than “iPad” projects because the jailbreak community is small and the platform is not actively maintained by Amazon for these purposes.
The migration took me a full weekend the second time around. Most of that was waiting for community guides to load, figuring out which extensions still worked, and trial-and-error on Mesquite. If you are starting fresh on a Kindle you already have jailbroken, expect a long Saturday.
The actual reading-time cost is low. The Kindle still reads fine. The smart home dashboard sits on a stand and does not interfere with reading.
If your old Kindle is in a drawer and you want a glanceable status display for your smart home, this is worth trying. If you need touch control, or if you cannot tolerate firmware-update fragility, look at a cheap Android tablet instead. The e-ink battery and front light are the real wins. If those do not matter to you, a tablet will be easier.
What I would tell past me
Four things, if I could send a message back:
- Assume read-only, not control. Plan the dashboard for state. Add tap-to-toggle later if you find a build that works on your firmware. Do not let the lack of control stop you from getting a status display running.
- Disable automatic Kindle updates on day one. This is non-negotiable. A single automatic update can wipe out the entire setup. Disable updates, then disable them again after any firmware-related Kindle activity.
- Pick the community build that matches your exact Kindle model and firmware version. Do not assume the project page applies to your hardware. Read the issues. Find someone who has reported success on the same model and firmware you have. Save yourself a Saturday.
- Keep an escape hatch in Home Assistant itself. The Kindle is a complement, not a primary control surface. Make sure your automations and important devices work through the Home Assistant app and through physical controls. The Kindle is the nice-to-have display, not the load-bearing one.