[BK7231N/CB2S] MOES Smart USB Wall Outlet with USBC charger WK-US2-TC (5V/2.1A)

WK-US2-TC is a dual MOES smart socket that features also an USB output (5V/2.1A) with both Type-C and Type-A socket. Product ASIN is B0BV9HRPMN, manufacturer is WENZHOU NOVA NEW ENERGY CO.,LTD. This MOES smart socket can easily run OpenBeken, and can be also flashed both via UART and by Tuya-cloudcutter (via WiFi).

Device information has been submitted by our user. Here are some screenshot from device seller's page:





Product specification:


Here's OpenBeken template, as exported by BK7231 Easy Flasher (our tool can detect Tuya config and automatically configure OBK):

Here's OBK json:

And here's pin description:

Quote:

- Relay (channel 1) on P26
- Relay (channel 2) on P8
- Relay (channel 3) on P6
- Relay (channel 4) on P7
- WiFi LED on P10
- Button (channel 1) on P11
- Button (channel 2) on P24

Sadly enough it doesn't look like this device supports fast charging, but I would be happy to be proven wrong.

Hi,
ordered this exact same device hoping I could flash it via Cloudcutter.
The device template for WK-US2-TC is based on firmware 1.1.8.
however checking my firmware with the Smartlife app gives 1.1.17.
I have tried both the provided option (1.1.8) and using " By firmware version and name" (with 1.1.17) but was unsuccessful : "The profile you selected did not result in a successful exploit", see log below.

What would you recommend as next steps / troubleshooting?

Thank you!

'''
Building cloudcutter docker image
[+] Building 0.3s (13/13) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 462B 0.0s
=> [internal] load metadata for docker.io/library/python:3.9.18-slim-bullseye 0.3s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 3.02kB 0.0s
=> [base 1/2] FROM docker.io/library/python:3.9.18-slim-bullseye@sha256:9ac27d4ecadc3ef02f980a8e2b37c7e8cdbf24039c5eddd9f98aff00d23b9e03 0.0s
=> CACHED [base 2/2] RUN apt-get -qq update && apt-get install -qy --no-install-recommends git hostapd rfkill dnsmasq build-essential libssl-dev iproute2 mosquitto 0.0s
=> CACHED [python-deps 1/4] RUN pip install --upgrade pipenv 0.0s
=> CACHED [python-deps 2/4] COPY src/Pipfile /src/ 0.0s
=> CACHED [python-deps 3/4] COPY src/Pipfile.lock /src/ 0.0s
=> CACHED [python-deps 4/4] RUN cd /src && PIPENV_VENV_IN_PROJECT=1 pipenv install --deploy 0.0s
=> CACHED [cloudcutter 1/2] COPY src /src 0.0s
=> CACHED [cloudcutter 2/2] WORKDIR /src 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:7fb627b4c3ea335dc27c1bcbd6da031012f5721fc20ff1740848e82532896d02 0.0s
=> => naming to docker.io/library/cloudcutter 0.0s
Successfully built docker image
Loading options, please wait...
[?] How do you want to choose the device?: By firmware version and name
By manufacturer/device name
► By firmware version and name
From device-profiles (i.e. custom profile)

[?] Select the firmware version and name: 1.1.17 - BK7231N / oem_bk7231n_temp_hum_sensor
1.1.0 - BK7231T / oem_bk7231s_rnd_switch
1.1.1 - BK7231N / oem_bk7231n_ffc_remote_ctrl_ty
1.1.1 - BK7231T / HYS_03_018_bk7231t_a4y9plclmzpct6ol
1.1.1 - BK7231T / oem_bk7231s_light_ty_oldDp
1.1.11 - BK7231N / oem_bk7231n_temp_hum_sensor
1.1.14 - BK7231T / oem_bk7231s_switch1_zero_kjd
► 1.1.17 - BK7231N / oem_bk7231n_temp_hum_sensor
1.1.2 - BK7231N / oem_bk7231n_control_switch
1.1.2 - BK7231N / oem_bk7231n_dimmer_kjd
1.1.2 - BK7231N / tuya_demo_heater
1.1.2 - BK7231T / oem_bk7231s_control_switch
1.1.2 - BK7231T / oem_bk7231s_dltj_2switch_alerc
1.1.2 - BK7231T / oem_bk7231s_hailai_1_plug

[?] Select the brand of your device: Tuya Generic
► Tuya Generic

[?] Select the article number of your device: Temperature and Humidity Sensor v1.1.17
► Temperature and Humidity Sensor v1.1.17


Performing safety checks to make sure all required ports are available
Checking UDP port 53... Occupied by systemd-resolve with PID 20308.
Port 53 is needed to resolve DNS queries
Do you wish to terminate systemd-resolve? [y/N] y
Attempting to stop systemd-resolved.service
Checking UDP port 67... Available.
Checking TCP port 80... Available.
Checking TCP port 443... Available.
Checking TCP port 1883... Available.
Checking TCP port 8886... Available.
Safety checks complete.

Selected Device Slug: tuya-generic-temperature-and-humidity-sensor-v1.1.17
Selected Profile: oem-bk7231n-temp-hum-sensor-1.1.17-sdk-2.3.1-40.00

================================================================================
Place your device in AP (slow blink) mode. This can usually be accomplished by either:
Power cycling off/on - 3 times and wait for the device to fast-blink, then repeat 3 more times. Some devices need 4 or 5 times on each side of the pause
Long press the power/reset button on the device until it starts fast-blinking, then releasing, and then holding the power/reset button again until the device starts slow-blinking.
See https://support.tuya.com/en/help/_detail/K9hut3w10nby8 for more information.
================================================================================

Scanning for open Tuya SmartLife AP

Found access point name: "SmartLife-6DC2", trying to connect...
Device 'wlp4s0' successfully activated with 'b1de12a4-c20d-4ac8-a511-7ab869c5b933'.
Connected to access point.
Waiting 1 sec to allow device to set itself up...
Running initial exploit toolchain...
Exploit run, saved device config too!
output=/work/configured-devices/HymYmaXLnmJE.deviceconfig
Saved device config in /work/configured-devices/HymYmaXLnmJE.deviceconfig

================================================================================
Power cycle and place your device in AP (slow blink) mode again. This can usually be accomplished by either:
Power cycling off/on - 3 times and wait for the device to fast-blink, then repeat 3 more times. Some devices need 4 or 5 times on each side of the pause
Long press the power/reset button on the device until it starts fast-blinking, then releasing, and then holding the power/reset button again until the device starts slow-blinking.
See https://support.tuya.com/en/help/_detail/K9hut3w10nby8 for more information.
================================================================================

Scanning for open Tuya SmartLife AP

Found access point name: "SmartLife-6DC2", trying to connect...
Device 'wlp4s0' successfully activated with 'b1de12a4-c20d-4ac8-a511-7ab869c5b933'.
Connected to access point.
================================================================================
[!] The profile you selected did not result in a successful exploit.
================================================================================
'''

Fixed by flashing via USB2UART/soldering:

https://www.elektroda.com/rtvforum/topic4057805.html

tested on WK-US2-TC and KS-604S

Flashing by UART is always reliable. Please refer to our video tutorials for more information:
https://www.youtube.com/playlist?list=PLzbXEc2ebpH0CZDbczAXT94BuSGrd_GoM