ay129-35MR

ay129-35MR / esphome-display-screenshot

Public

ESPHome component to capture ESP32 display screenshots over HTTP. Remote UI inspection for TFT/OLED development.

13
2
100% credibility
Found Feb 18, 2026 at 13 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
C++
AI Summary

A custom ESPHome component that enables remote screenshots of ESP32 displays via HTTP for easier development and monitoring.

How It Works

1
💡 Discover a handy helper

While building a smart gadget with a tiny screen, you learn about a simple way to view that screen from your computer without walking over every time.

2
📝 Add screenshot sharing

You add a short note to your device's setup instructions to enable sharing pictures of the screen.

3
🔄 Update your gadget

You refresh your gadget with the new instructions, and it restarts ready to share.

4
🌐 Open the web view

From any browser, go to your gadget's web address followed by /screenshot, and instantly see a perfect picture of what's on the screen.

5
📱 Switch screens or get info

Add ?page=number to see different screens on your gadget, or visit /info to learn about available views.

6
💾 Save or share the picture

Right-click to save the image, or use a quick download to grab it for checking or sharing.

🎉 Remote viewing magic

Now you can check, debug, and perfect your gadget's display from anywhere, making building fun and easy.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 13 to 13 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is esphome-display-screenshot?

This C++ ESPHome component lets ESP32 devices with PSRAM capture live screenshots of their TFT or OLED displays over HTTP, adding `/screenshot` and `/screenshot/info` endpoints to the built-in web server. Hit the URL in a browser or curl a BMP image of the framebuffer--perfect for remote UI inspection without walking to your hardware. It handles single screens, native ESPHome pages, or global-based page switching via `?page=N`, plus JSON metadata for dimensions and page lists.

Why is it gaining traction?

ESPHome display dev often hits pains like "esphome component display took a long time for an operation" or "esphome component.update" timeouts during iteration; this grabs pixel-perfect shots remotely, closing the loop for AI agents like Claude that curl screenshots to verify layouts. Unlike basic ESPHome github components, it enables visual regression tests, Home Assistant webhook integrations, and ngrok-exposed remote monitoring--no more squinting at tiny screens or photographing enclosures. Developers grab it from esphome github components for instant feedback in esphome github io esp web tools workflows.

Who should use this?

ESPHome hardware hackers building rotary-encoder UIs on ESP32-S3 with ST7789V or ILI9341 displays, tired of compile-flash-trek cycles. Home Assistant tinkerers debugging wall-mounted controllers or kiosk screens remotely. Teams scripting esphome components github auto-docs or visual diffs to catch "esphome component display is marked failed" issues before deploy.

Verdict

Grab it if you're deep in ESPHome display projects--solid docs and quick YAML setup make it a dev accelerator despite 12 stars and 1.0% credibility score signaling early maturity. Monitor esphome github issues for edge cases like PSRAM alloc fails, but it's battle-tested on real TFT knobs.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.