How to repurpose an old Kindle into a permanent Home Assistant smart home dashboard

At a glance:

• Uses a jailbroken Kindle (specifically Paperwhite models) to create an always-on E Ink smart home display.
• Requires a WebSocket proxy running in a Docker container to bridge Kindle's old WebKit standards with Home Assistant.
• Offers superior visibility in sunlight and better readability compared to standard LCD smart displays.

The problem with modern smart displays

Most modern smart home interfaces rely on LCD technology, which presents significant usability issues in a residential setting. LCD screens are often difficult to read from across a room due to glare and limited contrast, frequently forcing users to rely on voice commands rather than visual interaction. For many enthusiasts, this makes the current crop of consumer smart displays feel inadequate for a truly integrated home.

Furthermore, many commercial displays from giants like Google or Amazon are locked into their respective ecosystems. This creates a barrier for users running local-first setups like Home Assistant, which offers granular control over diverse hardware and custom sensors. There is a growing demand for an always-on, high-visibility display that doesn't require a smartphone app to monitor home status.

Why E Ink is the superior choice

Electronic Ink (E Ink) offers distinct advantages over traditional liquid crystal displays, particularly regarding legibility and power efficiency. Unlike LCDs, E Ink screens remain perfectly viewable even in direct, bright sunlight, making them ideal for wall-mounted displays in sunlit rooms. As long as the icons and fonts are scaled appropriately, they provide a high-contrast experience that is much easier on the eyes for long-term monitoring.

While the technology is highly effective, it hasn't seen widespread adoption in the smart display market. This is largely due to the cost of E Ink panels; Amazon is able to subsidize these screens through the Kindle ecosystem via advertising and book sales, but there is little commercial incentive for companies like Amazon or Google to build E Ink-based Echo Shows or Nest Hubs. This leaves a gap in the market that DIY enthusiasts can fill by upcycling older hardware.

Technical requirements for the Kindle dashboard

Transforming a Kindle into a functional dashboard is not a plug-and-play process. Because Kindle hardware is optimized strictly for e-reading, the internal WebKit standards are often too outdated to communicate with modern web interfaces. To overcome this, users must first jailbreak their device to allow for custom software installations, such as the KUAL extension or Tailscale for remote connectivity.

The implementation relies heavily on the Kindle SmartHome Dashboard project. For those using a Paperwhite, the process involves setting up a WebSocket proxy to translate the Kindle's aging API into a format that Home Assistant can interpret. This proxy is best deployed as a Docker container on a local server or mini PC running the Home Assistant instance.

To successfully configure the proxy, users must edit a config.json file with the following parameters:

• homeassistant.wsUrl: The URL of your Home Assistant instance (e.g., http://[IP]:8123).
• homeassistant.accessToken: A long-lived access token generated via Home Assistant (Profile → Security).
• kindle-display.accessToken: A custom string used for authentication between the Kindle and the proxy.

Deployment and configuration steps

Once the proxy is running in a Docker environment, the final step involves installing the dashboard extension on the Kindle itself. This requires modifying a JavaScript configuration file within the KUAL extension folder to match the user's specific environment. Key variables to adjust include the proxy_ip, the access_token, and geographic coordinates (lat and lon) to ensure weather data displays accurately.

Users should also tailor the following settings within the JavaScript file:

• DISPLAY_CALENDARS: A list of calendar entities to display (e.g., ['calendar.studium', 'calendar.geburtstage']).
• AUTO_NIGHT_MODE: A boolean to toggle night settings.
• SCREEN_BRIGHTNESS_DEFAULT and SCREEN_BRIGHTNESS_NIGHT: Numerical values for light levels.
• Language and scaling: Adjusting the code from German to English and upscaling the UI to fit specific generations, such as the 7th gen Paperwhite.

By utilizing modern AI tools like Claude to assist with code adjustments and entity mapping, even users with moderate technical skills can successfully bridge the gap between legacy e-reader hardware and modern smart home automation.