You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Full SSH output, running on RP3B. Looks it is working fine but I realize I did put the wrong password.
Device will go into blinking state but no APP.
Anyone nows how to get it back online?
@raspberrypi:~/tuya-cloudcutter $ sudo ./tuya-cloudcutter.sh -s '✅#404' 'WrongPassword'
Building cloudcutter docker image
[+] Building 1.5s (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 1.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [base 1/2] FROM docker.io/library/python:3.9.18-slim-bullseye@sha256:9ac27d4eca 0.0s
=> [internal] load build context 0.1s
=> => transferring context: 3.02kB 0.0s
=> CACHED [base 2/2] RUN apt-get -qq update && apt-get install -qy --no-install-re 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 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:65a921bbc8f5c37ff1e6c7bd00b4989b02aba91c9243dc783a143c8 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 manufacturer/device name
► By manufacturer/device name
By firmware version and name
From device-profiles (i.e. custom profile)
[?] Select the brand of your device: LSC
Kanlux
Klarstein
Kobi
Kuled
LEDLUMEN
LEDVANCE
► LSC
Lampsero
Laser
Lenovo
Lepro
Lexi
LightingInside
[?] Select the article number of your device: 3204432 Moodlight RGBW Bulb
3005457 Smart Outdoor LED Light Strip
3006767 970820 Tunable White Downlight 360Lumen
3007213 970787 Ceiling Light
3007257 970729 Extra Warm White Ambiance Smart Filament E27 350Lumen
3008407 LED Light Strip 1.0.14
3008407 LED Light Strip 1.0.18
3009188 Outdoor Spotlights
3200719 Outdoor Flood Light
3202086 XXL LED Strip v1.0.18
3202087 Plug with Energy Monitoring v1.3.5
► 3204432 Moodlight RGBW Bulb
8435606703567 WOOX Smart Bulb Full Colour and White E14 470Lumen
Smart Outdoor Wall Light
[?] Select the firmware version and name: 2.0.0 - BK7231N / oem_bk7231n_atmosphere_light_t
y► 2.0.0 - BK7231N / oem_bk7231n_atmosphere_light_ty
► 2.0.0 - BK7231N / oem_bk7231n_atmosphere_light_ty
Performing safety checks to make sure all required ports are available
Checking UDP port 53... Available.
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: lsc-3204432-moodlight-rgbw-bulb
Selected Profile: oem-bk7231n-atmosphere-light-ty-2.0.0-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 t imes. 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 releas ing, 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-CD09", trying to connect...
Device 'wlan0' successfully activated with 'f7ce1f44-e61f-4178-b850-b8ea33e605dc'.
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/tuoljLtFGoBE.deviceconfig
Saved device config in /work/configured-devices/tuoljLtFGoBE.deviceconfig
================================================================================
Power cycle and place your device in AP (slow blink) mode again. This can usually be acco mplished by either:
Power cycling off/on - 3 times and wait for the device to fast-blink, then repeat 3 more t imes. 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 releas ing, 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-CD09", trying to connect...
Error: Connection activation failed: 802.1X supplicant took too long to authenticate.
...
Found access point name: "A-CD09", trying to connect...
Device 'wlan0' successfully activated with 'ff35d7b1-9cd7-4897-bc2b-2c2285e3ab93'.
Connected to access point.
Configured device to connect to 'cloudcutterflash'
Device is connecting to 'cloudcutterflash' access point. Passphrase for the AP is 'abcdabc d' (without ')
Cutting device off from cloud...
================================================================================
Wait for up to 10-120 seconds for the device to connect to 'cloudcutterflash'. This script will then show the activation requests sent by the device, and tell you whether local act ivation was successful.
================================================================================
Using WLAN adapter: wlan0
Configuration file: /dev/stdin
Using interface wlan0 with hwaddr b8:27:eb:4d:6b:25 and ssid "cloudcutterflash"
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED
Using PSK v1 - Received PSK ID version 01
Processing endpoint /v2/url_config
Processing endpoint tuya.device.active
Processing endpoint tuya.device.dynamic.config.get
Device should be successfully onboarded on WiFi AP! Please allow up to 2 minutes for the device to connect to your specified network.
Device MAC address: b8:06:0d:11:cd:09
Device Id: 1S3cFboM44lsuiVwxJu1
Local Key: 0zEavdkTyawm4w6b
@raspberrypi:~/tuya-cloudcutter $ ls
Once it is cut, it will never connect to the Tuya SmartLife app again. If you used the wrong password, just cut it again using the correct one, you can cut it any number of times until you flash 3rd party firmware, which is final.
Full SSH output, running on RP3B. Looks it is working fine but I realize I did put the wrong password.
Device will go into blinking state but no APP.
Anyone nows how to get it back online?
Logs: deviceconfig:
`
The text was updated successfully, but these errors were encountered: