<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>ESPHome — ELECROW - FORUM</title>
        <link>https://forum.elecrow.com/index.php?p=/</link>
        <pubDate>Wed, 10 Jun 2026 22:29:07 +0000</pubDate>
        <language>en</language>
            <description>ESPHome — ELECROW - FORUM</description>
    <atom:link href="https://forum.elecrow.com/index.php?p=/discussions/tagged/esphome/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>ESP32-S3 display reboots into old firmware after successful flash</title>
        <link>https://forum.elecrow.com/index.php?p=/discussion/28475/esp32-s3-display-reboots-into-old-firmware-after-successful-flash</link>
        <pubDate>Sat, 09 May 2026 08:00:12 +0000</pubDate>
        <category>TFT-LCD &amp; Touch Screen</category>
        <dc:creator>Tomas</dc:creator>
        <guid isPermaLink="false">28475@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>I can flash firmware over serial (COM3) and the panel goes black during flashing, so the write process seems to start correctly.<br />
However, after reboot, the display comes back with the previous/old UI instead of the new minimal test UI.</p>

<p>What I have already tested:</p>

<ul>
<li>Only one*  display is connected (COM3).</li>
<li>Serial flashing completes without obvious cable disconnect issues.</li>
<li>I tested a very small minimal firmware/config to rule out application complexity.</li>
<li>The issue is still that after restart, old behavior/layout appears.</li>
<li>Could you please advise:</li>
</ul>

<p>Is there any known boot fallback/rollback behavior on this display + ESP32-S3 combination?<br />
1. Are there required power/reset/boot pin sequences after flashing?<br />
2. Are there known constraints for RGB timing/pins that could cause app boot failure and fallback?<br />
3. Is there a recommended “factory clean flash” procedure for this board?<br />
4. Should I use any specific partition table or flash settings for stable boot with this panel?<br />
5. If useful, I can share full logs and my exact ESPHome display pin mapping.</p>

<p>Thanks in advance.</p>
]]>
        </description>
    </item>
    <item>
        <title>DIE07300S : CrowPanel ESP32 4.2” E-paper HMI Display - Elecrow Wiki</title>
        <link>https://forum.elecrow.com/index.php?p=/discussion/1152/die07300s-crowpanel-esp32-4-2-e-paper-hmi-display-elecrow-wiki</link>
        <pubDate>Thu, 20 Mar 2025 04:16:47 +0000</pubDate>
        <category>Elecrow HMI Display</category>
        <dc:creator>nerdingOut</dc:creator>
        <guid isPermaLink="false">1152@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>I recently purchased the CrowPanel ESP32 4.2-inch E-Paper Display, which uses the SSD1683 driver IC. I’m trying to integrate it with ESPHome but have been running into issues.</p>

<p>What I’ve Tried So Far:<br />
    •   Used the waveshare_epaper component in ESPHome, which supports SSD1680 (a similar driver).<br />
    •   Tried different models (4.20in-bv2, 4.20in-bv2-bwr) in ESPHome.<br />
    •   Adjusted reset durations and power cycled the display.<br />
    •   Verified SPI pin connections match the CrowPanel documentation.<br />
    •   Checked logs—ESPHome recognizes the display, but operations are very slow (Component display took a long time for an operation (157ms)) and no image updates.</p>

<p>Questions:<br />
    1.  Has anyone successfully integrated this CrowPanel SSD1683 e-paper display with ESPHome?<br />
    2.  If so, which settings or custom drivers did you use?<br />
    3.  Would a custom ESPHome driver be needed for SSD1683, or is there an alternative workaround?<br />
    4.  Has anyone tried controlling this panel with the GxEPD2 Arduino library instead?</p>

<p>Any guidance, YAML examples, or alternative approaches would be greatly appreciated. Thanks in advance!</p>
]]>
        </description>
    </item>
   </channel>
</rss>
