PowerSave is recommended for most devices. I would only avoid using PowerSave on BL0937 power metering devices and on IR devices. Otherwise PowerSave should be on, this will reduce current usage. Otherwise low quality power supplies of Tuya products may fail.
Just back to it now... the LED in the unit is showing solid red. Yes, I have opened it and the chip is CBS2. I think during the cloudcutter something failed and it's not completed.
Have been trying to get this working but hitting the following error, seems it connects, starts doing something, then re-connects and cannot do anything after that. Any ideas?
Quote:
[?] Select your custom firmware file for BK7231T chip: ESPHome-Kickstart-v23.08.29_bk7231t_app.ota.ug.bin
► ESPHome-Kickstart-v23.08.29_bk7231t_app.ota.ug.bin
OpenBeken-v1.17.262_bk7231t.ug.bin
================================================================================
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.
================================================================================
Wiping NetworkManager configs
Scanning for open Tuya SmartLife AP
........
Found access point name: "GRID-23A4", trying to connect...
Device 'wlan0' successfully activated with 'redacted'.
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/jpw2un7yZBw6.deviceconfig
Saved device config in /work/configured-devices/jpw2un7yZBw6.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.
================================================================================
Wiping NetworkManager configs
Scanning for open Tuya SmartLife AP
...
Found access point name: "GRID-23A4", trying to connect...
Error: Connection activation failed: (53) The Wi-Fi network could not be found.
Wiping NetworkManager configs
Found access point name: "GRID-23A4", trying to connect...
Device 'wlan0' successfully activated with 'redacted'.
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/jpw2un7yZBw6.deviceconfig
Saved device config in /work/configured-devices/jpw2un7yZBw6.deviceconfig
is device still with Tuya? Do you have that deviceconfig file? Can you share it?
is device still with Tuya? Do you have that deviceconfig file? Can you share it?
Yep, I had two, bricked one, and returned to the shop and got a new one. So I have two again, one not in the app and one that is still in the Smart Life app. How do I grab device config files there?
Hey guys, I bought one of these plugs from Bunnings and I managed to flash it with ESPHome. All good - thanks to this topic. I was just wondering what is the ESPHome equivalent of this `PowerSave` which has been mentioned above? Thanks.
The discussion revolves around the Arlec Grid Connect PC191HA Series 2 plug-in socket, focusing on issues related to flashing the device with custom firmware using CloudCutter and OpenBeken. Users report varying experiences with different chipsets (BK7231N and BK7231T) found in the devices, with some successfully flashing the devices while others encounter difficulties. Key topics include the importance of enabling PowerSave mode to prevent overheating, configuring energy statistics, and troubleshooting GPIO settings for LED control. Users share configurations, firmware versions, and experiences with device performance, including issues with relay control and power reporting. The conversation highlights the variability in hardware between batches and the need for careful configuration to ensure proper functionality. Summary generated by the language model.