Hi, I am using the “E1001” and have deleted it from my account. I am planning to pair it with another account at “sensecraft.seeed.cc/hmi,” but the PIN is not showing up, even after updating the firmware in factory reset mode. The user interface is stuck on the default page, even after connecting to Wi-Fi.
Thanks in advance.
Hi there,
and Welcome Back…
so, Yes, there are documented troubleshooting steps to resolve this. When a reTerminal E1001 is deleted from a SenseCraft account, the device itself doesn’t automatically know it has been unlinked. It remains trapped in its old state, which prevents it from generating a new pairing PIN even if you flash the firmware.
To fix this and force the device to generate a new pairing code, try the following sequence:
If the user interface is stuck on the default home page, it is likely still trying to use old handshake data. You need to wipe the network configuration to trigger a clean boot cycle.
Instead of relying on the web dashboard right away, go through the local AP setup to ensure a clean binding code is generated:
reTerminal E1001-{MAC Address} (no password required).192.168.4.1.If standard factory flashing via the SenseCraft HMI flasher keeps resulting in a frozen screen, the background pairing flags may be corrupted in the ESP32-S3’s non-volatile storage (NVS).
You can clear the internal memory completely by navigating to the TRMNL Web Flasher, plugging the device into your PC via USB-C, and executing a Full Flash (Erase All) using their public firmware. Once completely wiped, you can cleanly switch it back to the official SenseCraft HMI firmware via the SenseCraft device utility page, which will guarantee the device boots up completely empty and generates a fresh setup code.
HTH
GL 
PJ 
Hi @PJ_Glasso , Thanks for the response. I tried all of these, even erased the flash with espweb too, and flashed back to HMI firmware, but still no pairing PIN is shown.
Hi there,
No worries, the last one is what should work. Something else maybe’s afoot?
What mobile device you using , may I know ?
Is it doa looking or are there any signs of it alive after the last factory flashing ?
I will look into it further.
Hang in there.
GL PJ
After the reset, it’s properly connected to the internet, and I also checked the local page on the computer, so it’s not about the mobile.
I can see the reflashing is successful
@PJ_Glasso You appear to be the guru on this issue, do you have any suggestions for me?
I am also having this same problem, but with a reTerminal E1002. I have flashed the firmware to TRMNL, Arduino, and ESPHome, each time with a “full” erase and re-flash via (I can’t include links in my posts, so here is an approxomation of the URL)
seeed-projectsgithubio/OSHW-reTerminal-Series-E-D/
After the firmware has flashed, I then go to:
sensecraftseeedcc/hmi/tools/firmware
…to complete the firmware erase and re-flash so I can use my e1002 with Sensecraft Seeedash. The problem is that after the re-flash, once I connect my device to WiFi, it is registered to another user’s account. As soon as it joins the WiFi, then it downloads the other users current/last project and displays it. At no point, once I have connected the e1002 to WiFi, do I get a pairing PIN code.
Is there any way to remove my device from another user’s account?
FYI: Why? My e1002 was purchased from Amazon as a returned device. Yes, I can return it to Amazon identifying it as defective, but I figure there must be a way around this issue. I don’t want to see this e1002 go to e-waste just because it was paired to another user’s account.
Hi there,
SO , it appears its the cloud issue and not being unbound…
The binding between the reTerminal (E1001 / E1002) and a Seeedash/SenseCraft account lives in the cloud on Seeed’s backend servers, not in local ESP32 flash memory:
When the reTerminal boots official firmware and connects to Wi-Fi, it reports its unique hardware identifier (factory MAC address / Chip ID) to Seeed’s SenseCraft backend.
If that hardware ID is still registered to the previous owner’s account in Seeed’s database, the server automatically associates it and pushes down the previous owner’s dashboard project.
A local flash erase (esptool.py erase_flash) wipes the local NVS, Wi-Fi credentials, and code, but as soon as you re-flash the official firmware and reconnect to the internet, the backend instantly recognizes the MAC address again.
Official SenseCraft / Seeedash unbinding: The user needs to contact Seeed Studio support or forum staff (@Seeed_John / technical support) with the device’s MAC address and Serial Number / Proof of Purchase. Seeed support must manually unbind or release the hardware ID from their backend database.
Alternative open-source route (Bypass SenseCraft): If they don’t want to wait for Seeed backend support, they can use standalone third-party firmwares that do not touch Seeed’s cloud (e.g., custom ESPHome, TRMNL, or Home Assistant e-paper dashboards pointing to a local Home Assistant instance or independent server).
Send pictures of the unit as well. 
HTH
GL PJ
Thank you, that makes sense and what I figured the problem was, but I didn’t know who/how to fix it.
I’m new to this forum, so I’ll have to figure out if there is a PM system so I don’t post my MAC/serial no/proof of purchase for everyone to see.
Thanks again!
I was able to fix it by contacting the Seeed team (Thanks for Meililly) and remove the already paired account.
So what happened is, I used this device for a e-ink workshop and on of the participants is paired with this device as part of the workshop and did experiment, and at the end I asked everyone to un-pair and all confirmed they did, but unfortunately they didn’t done that even I asked to check again and there is no way to find that.
So after many day and multiple tries, with seeed team, was able to fix it be removing that account.
Hi there,
Glad you got it sorted out… I hope the info was helpful
and thanks for letting us know it was resolved.
GL PJ
I have a similar sort of issue.
I performed several resets. flashes sam e resullt The Flash propcedure works persfecvtly no error messages.
reTerminal E1001
Firmware E1001_1.1.5
Serial port selected.
Start flashing…
Using initial baud rate: 921600
esptool.js
Serial port WebSerial VendorID 0x1a86 ProductID 0x7523
ESP32-S3
Chip Revision: 0
Chip is ESP32-S3 (QFN56) (revision v0.2)
Features: Wi-Fi,BLE,Embedded PSRAM 8MB (AP_3v3)
Crystal is 40MHz
MAC: ac:27:6e:a6:b2:d0
Uploading stub…
Running stub…
Stub running…
Flash ID: 1940ef
Detected chip: ESP32-S3 (QFN56) (revision v0.2)
Using configuration for firmware_type: hmi, board: reterminal_e1001
Starting flash process…
delete part of the logging data to save space
I: [app_power] release owner=download owner_ref=0 total_ref=0 owner_mask=0x8x
I: [app_sensecraft] IOT report sent.
System loops I: [app_sensecraft] IOT report sent. message and screen says the same
Thanks, Ronald