How to Reset Tuya Socket with ECR6600 Chip to AP Mode Using Power Button?

loveolgavanya wrote:

{
"vendor": "Tuya",
"bDetailed": "0",
"name": "Full Device Name Here",
"model": "enter short model name here",
"chip": "ECR6600",
"board": "TODO",
"flags": "1107297280",
"keywo...

Initial assessment of your device data (topic 4149825)

- The JSON you posted is an OpenBeken-style template (roles such as Btn;1, Rel;1, WifiLED;0 and BL0937 pins). That strongly indicates the device is (or will be) running OpenBeken, not stock Tuya firmware.
- Mapped I/O:
- P24 = Btn;1 → main physical button
- P25 = Rel;1 → relay
- P22 = WifiLED;0 → Wi‑Fi status LED
- P14/P15/P20 = BL0937 metering lines

Because of this, the most robust way to “hold the power button for 10 seconds to start a new AP” is to bind a long‑press event from that button to a command that starts the on‑device Wi‑Fi AP.

References (for what follows):
- How OpenBeken button events and event handlers work (OnClick/OnDblClick/OnHold/OnHoldStart, pin-number addressing) and setting timing with SetButtonTimes. (github-wiki-see.page)
- OpenBeken behaviour when no Wi‑Fi is configured (starts its own AP at 192.168.4.1). (github-wiki-see.page)
- Typical OpenBeken AP SSID seen after flashing (contains “OpenBeken”). (reddit.com)
- For devices that are still on stock Tuya firmware: the official Tuya reset and AP/EZ mode LED patterns. (smartapp.tuya.com)


Direct answer

If you are on OpenBeken:
- Add a long‑press (10 s) action on P24 that starts the device’s Wi‑Fi AP:
- Set the hold threshold to 10 s and bind the event to AP start, for example:
- `SetButtonTimes 100 3 3`
- `addEventHandler OnHoldStart 24 startAP`
- After this, holding the main button for ~10 seconds will start a fresh AP. The Wi‑Fi LED on P22 will begin blinking to indicate AP is active, and you will see an SSID that typically includes “OpenBeken”. Connect and browse to 192.168.4.1 to (re)configure Wi‑Fi. (elektroda.com)

If you are on stock Tuya firmware:
- Power the device, then long‑press the main/reset button for ~5 seconds until the LED flashes rapidly (EZ mode); long‑press again for ~5 seconds until the LED flashes slowly (≈ once every 3 s) to switch to AP mode. In AP mode the device exposes its own Wi‑Fi network for pairing. (smartapp.tuya.com)


Detailed problem analysis

- Why use OnHoldStart and SetButtonTimes in OpenBeken:
- OpenBeken exposes button events by pin number (P24 in your template). Supported events include OnClick, OnDblClick, OnHold, and OnHoldStart. OnHold may repeat while held; OnHoldStart fires once at the beginning of the long press—ideal for “do this once after 10 s.” (elektroda.com)
- The first parameter of SetButtonTimes is the long‑press threshold in 100 ms ticks. Setting it to 100 gives 10.0 s. The remaining parameters control repeat/interval timings (defaults commonly used are 3 and 3). Multiple examples in OpenBeken articles show this pattern. (elektroda.com)
- Starting an AP on OpenBeken:
- OpenBeken automatically brings up its own AP if no STA credentials are stored or connection fails, served at 192.168.4.1. The console command startAP triggers the same AP startup without clearing Wi‑Fi settings. This is the cleanest way to implement a “recovery AP” long press. (github-wiki-see.page)
- Visual feedback:
- With P22 assigned to WifiLED, OpenBeken drives that LED to reflect Wi‑Fi state (blinking during AP/config). This lets you confirm the 10 s press did invoke AP start. (github-wiki-see.page)
- Stock Tuya behaviour is different:
- Tuya devices generally expect a 5 s long‑press to reset into pairing (EZ) mode; repeating the long press toggles to AP mode (slow blink). That’s why some manuals say “5–10 seconds”—but the authoritative pattern is “5 s, then 5 s again to toggle.” (smartapp.tuya.com)


Current information and trends

- On OpenBeken, scripting button behaviour via event handlers is now the standard way to add local recovery functions (AP start, safe‑mode, etc.), documented across multiple recent community guides. This avoids cloud or mobile app dependencies entirely. (github-wiki-see.page)
- For Tuya‑stock devices, Tuya still documents EZ vs AP indication with fast vs slow blink and 5 s toggles as of October 2025. (smartapp.tuya.com)


Supporting explanations and details

- Suggested OpenBeken minimal script for your template (place in LittleFS autoexec.bat or send once from Console so it persists):
- `startDriver Button`
- `SetButtonTimes 100 3 3` (10 s hold)
- Optional: short‑press toggles relay → `addEventHandler OnClick 24 POWER toggle`
- Long‑press recovery AP → `addEventHandler OnHoldStart 24 startAP`
This mirrors examples published by OpenBeken contributors (events by pin number; POWER toggle command on click). (github-wiki-see.page)
- If you prefer “hold to clear Wi‑Fi” (so AP comes up at next boot), bind a long‑press to forgetting Wi‑Fi followed by restart. That’s less user‑friendly for quick recovery, which is why starting AP directly is preferable. (github-wiki-see.page)
- LED behaviour: once AP is active, P22 WifiLED should blink. If not, re‑check the role assignment for P22 and ensure no other script forces the LED. (github-wiki-see.page)


Practical guidelines

- Implementation steps (OpenBeken):
- Web UI → Console: paste the four lines above; or Web UI → LittleFS → edit autoexec.bat and add them; then reboot.
- Test: press and hold the main button for ~10 s. Watch the Wi‑Fi LED start blinking, then look for a new SSID containing “OpenBeken” and browse to 192.168.4.1. (github-wiki-see.page)
- Implementation steps (stock Tuya):
- Hold 5 s to EZ (fast flash), hold another 5 s to AP (slow flash). Connect to the device AP and complete setup in the Tuya/Smart Life app. (smartapp.tuya.com)
- Troubleshooting:
- Nothing happens after 10 s: confirm SetButtonTimes is applied; verify your event uses the physical pin number 24 (not the role name); prefer OnHoldStart to avoid repeated triggers. (elektroda.com)
- Still no AP visible: power‑cycle and retry; if you intentionally cleared Wi‑Fi, OBK will fall back to AP on boot at 192.168.4.1. (github-wiki-see.page)


Ethical and legal aspects

- Ensure you only modify devices you own and comply with local RF regulations when operating temporary APs.


Suggestions for further research

- OpenBeken commands/events and examples (Elektroda threads and wiki mirrors). (github-wiki-see.page)
- OBK first‑run/AP fallback behaviour and recovery IP details. (github-wiki-see.page)
- Tuya’s official reset documentation (for stock firmware units). (smartapp.tuya.com)


Brief summary

- On OpenBeken, bind P24 long‑press (10 s) to startAP using SetButtonTimes (100 = 10 s) + addEventHandler OnHoldStart.
- On stock Tuya firmware, use the 5 s press to enter EZ and a second 5 s press to switch to AP, indicated by slow LED blinking per Tuya’s guide.


Questions for you

- Can you confirm whether the device currently runs OpenBeken or stock Tuya firmware?
- When you press and hold the button today, what exact LED pattern do you see (fast vs slow blink, or none)?
- Do you want the long press to start AP immediately (without clearing credentials), or do you prefer “factory network reset” behaviour?

loveolgavanya wrote:

{
"vendor": "Tuya",
"bDetailed": "0",
"name": "Full Device Name Here",
"model": "enter short model name here",
"chip": "ECR6600",
"board": "TODO",
"flags": "1107297280",
"keywo...

Initial assessment of available information
- Vendor: Tuya; SoC: ECR6600 (stock Tuya firmware, latest as per your note).
- Single front button is exposed in your profile as Btn;1 on pin 24 (main/power button).
- Wi‑Fi status LED is on pin 22 (WifiLED).
- You want to force the device to forget Wi‑Fi and start a fresh configuration AP by holding the power button.

This is consistent with standard Tuya behavior: a long press places the device into network configuration, first EZ mode (fast blink), then AP mode (slow blink). On many builds you can reach AP mode with one continuous hold; on others you toggle modes with a second long press.

Direct answer to the question
To reset Wi‑Fi and start a new access point using the main power button:
1. Power the device and wait ~20–30 seconds until it’s fully booted.
2. Press and hold the main button continuously for about 10–12 seconds.
- Around 5 seconds: the Wi‑Fi LED should switch to fast blinking (EZ mode). Keep holding.
- Around 10 seconds total: the LED should change to slow blinking (~1 flash every 2–3 s), which indicates AP mode.
3. Release the button when you see the slow‑blink pattern. The device is now broadcasting its own Wi‑Fi AP.
4. On your phone, connect to the device’s AP (commonly named SmartLife‑XXXX, TuyaSmart‑XXXX, or a brand‑specific SSID).
5. In the Tuya/Smart Life app, choose Add device → AP mode (or “Add manually” → “AP mode”) and provide your 2.4 GHz Wi‑Fi credentials.

If you only get fast blinking after 10 seconds, release, then press and hold again for ~5 seconds to switch from EZ to AP mode.

Detailed problem analysis
- Button and LED roles:
- Btn;1 on pin 24 is an active button input. Short press usually toggles the relay (Rel;1 on pin 25). Long press invokes the firmware’s network-reset handler.
- WifiLED on pin 22 will indicate mode transitions:
- Fast blink (~2–3 Hz): EZ mode (pairing via broadcast).
- Slow blink (~0.3–0.5 Hz): AP mode (device creates its own hotspot).
- Timing nuances you may see across Tuya builds:
- 5 s long press: clear Wi‑Fi and enter EZ mode (fast blink).
- 10 s continuous hold (or a second 5 s long press while in fast blink): switch to AP mode (slow blink).
- Some OEMs map AP directly to a single ~10 s hold; others require two steps. Your “10 seconds” request aligns with both behaviors—just watch the LED pattern to confirm AP mode.
- What gets reset:
- This procedure clears network credentials and re-enters provisioning. It does not erase energy‑measurement calibration (BL0937 front end) or other factory parameters.
- ECR6600 specifics:
- ECR6600 is a Tuya platform SoC. From the end‑user perspective the reset/pairing behavior matches other Tuya Wi‑Fi devices; the LED patterns are the reliable indicator, not the chip name.

Practical guidelines
- Use 2.4 GHz Wi‑Fi only; disable band steering or temporarily split SSIDs if your router merges 2.4/5 GHz.
- On the phone:
- Accept “No Internet” prompts after joining the device AP.
- Disable mobile data/auto‑switch to mobile temporarily to avoid the OS hopping off the AP.
- Keep the load disconnected (lamp/heater off) while you do long presses to avoid nuisance switching of the relay during the hold.

Troubleshooting
- LED won’t change when holding:
- Ensure the device is fully booted first, then press and hold firmly for a continuous 10–12 s.
- Try the two‑step method: 5 s hold to fast blink, release; then another 5 s hold to slow blink (AP).
- No AP visible after slow blink:
- Wait 10–20 seconds; some devices take a moment to start the hotspot.
- Scan again; SSID names vary by OEM (SmartLife‑XXXX, TuyaSmart‑XXXX, brand‑XXXX).
- Alternative trigger if the button method fails:
- Power‑cycle method: turn the device off/on 3–5 times with ~2 s intervals; many Tuya firmwares enter pairing after repeated power cycles.
- Still not entering AP/EZ mode:
- Check for a secondary pinhole reset (some enclosures hide one).
- Confirm the button itself is sound (short press should still toggle the relay click).
- Remove the device from the Tuya/Smart Life app first, then retry the long press.

Possible notes
- Some OEM skins invert LED logic (on=LOW). Ignore absolute on/off level—use the blink rate to determine mode.
- If your router enforces WPA3‑only, enable WPA2 or WPA2/WPA3 mixed mode for Tuya devices.

Suggestions for further verification
- After you believe you’re in AP mode, confirm by:
- Observing slow LED blink on the device.
- Seeing a new SSID from the device on your phone.
- The app explicitly being in “AP mode” flow during pairing.

Brief summary
- Hold the main button for ~10–12 s from normal operation until the LED changes from fast to slow blinking, then release. Slow blinking means AP mode. Join the device’s SSID and complete provisioning in the Tuya/Smart Life app.

Questions for you
- When you hold the button, what exact LED patterns do you see (none → fast → slow, or only fast)?
- Do you see any new SSID appear after the slow blink starts?
- What is the physical product type/model (plug, inline switch, wall switch)? A photo of the front and PCB (if accessible) can help confirm if there’s a secondary reset input.