Tuya ATORCH S1-B/W/T/H Smart Socket Energy Monitor (BK7231N) (C3BS) (CH573F) (BL0942)

Question

Hi everyone, I just received my new ATORCH Smart Socket Energy Monitor from AliExpress ( The UI does look like almost similar to the ATORCH AT4P ( I took it apart and the inside looks like this The smart chip is a C3BS (BK7231N), the main logic chip is a CH573F, and the metering chip is a BL0942...

p.kaczmarek2 · Answer

Hello, can you post the current autoexec.bat so we can work from there?

maximesharp · Answer

Like I said in my original post, I've reused the autoexec.bat from the AT4P, so here it is :

startDriver TuyaMCU
startDriver tmSensor
startDriver NTP
tuyaMcu_setBaudRate 115200
setChannelType 1 toggle
setChannelType 2 Voltage_div10
setChannelType 3 Power
setChannelType 4 Current_div1000
setChannelType 5 Frequency_div100
setChannelType 6 ReadOnly
setChannelType 7 Temperature
setChannelType 8 ReadOnly
setChannelType 9 ReadOnly
//ch 1 (dpid 1) power relay control
linkTuyaMCUOutputToChannel 1 bool 1
//ch 2(dpid 20) voltage
linkTuyaMCUOutputToChannel  20 1 2
//ch 3(dpid 19) power watts
linkTuyaMCUOutputToChannel 19 1 3
//ch 4 (dpid 18)current Amps
linkTuyaMCUOutputToChannel 18 1 4
//ch 5 (dpid 133) frequency 
linkTuyaMCUOutputToChannel 133 1 5
//ch 6 (dpid 102) energy cost used
linkTuyaMCUOutputToChannel 102 1 6
// ch 7 (dpid 135) temp
linkTuyaMCUOutputToChannel 135 1 7
//ch 8 (dpid 134) power factor 
linkTuyaMCUOutputToChannel 134 raw 8
//ch 9 (dpid 123) energy consumed
linkTuyaMCUOutputToChannel 123 1 9

p.kaczmarek2 · Answer

tmSensor is most likely not needed, who put that here? Please link to original post, I will edit that as well.

If voltage is ten times too high, change:


Voltage_div10

to


Voltage_div100

maximesharp · Answer

startDriver tmSensor was present on this post: already tried to change setChannelType 2 Voltage_div10 to setChannelType 2 Voltage_div100 but it doesn't work and when I try to apply it manually, it gave me this error: Code: text Expand Select all Copy to clipboardFAILED! Invalid command setChannelType 2 Voltage_div100

p.kaczmarek2 · Answer

Ah, I see, we don't have Voltage_div100 yet! I will add this for you tomorrow in the morning.

tecnolobo · Answer

>>20743620You can try using one dummy channel to receive the values and one RepeatingEvent every second or one ChangeHandler to transfer the values to the correct channel.I can't test it because I don't have any device like yours.I use a similar solution to be able to store one counter values without ruining the flash memory. So I only transfer to channel 1 (with option -1, saving to the flash in case of change in configure startup) every 120 seconds.

p.kaczmarek2 · Answer

I have added now Voltage_div100 to the firmware, it should be live within 15 minutes or so. @tecnolobo I will publish an interesting article of using flash save in a moment, but in general, you also keep in mind that we have a system that reduces a number of flash erases (we write data to the same flash page many times and erase it once when needed), so the flash situation is not as bad as it seems

maximesharp · Answer

I've upgraded OpenBeken to version 1.17.251 but I don't think the Voltage_div100 was merged in this build.

Also, I've got some news:

On Channel 1, the toggle button doesn't act on the relay when pressed, but the state of the button does change when I toggle the relay on the device itself.

On Channel 3, the power (watts) is also reading 10x too high with Power_div10, and Power_div100 doesn't exist.

On Channel 6, I can't find any field for energy cost, if in the future such a field exists, it should be EnergyCost_div1000 for this device.

On Channel 8, The PowerFactor is reading 10x too low with PowerFactor_div1000, and PowerFactor_div100 doesn't exist.

Here my current autoexec.bat file :

startDriver TuyaMCU
startDriver NTP
tuyaMcu_setBaudRate 115200
setChannelType 1 toggle
setChannelType 2 Voltage_div10
setChannelType 3 Power_div10
setChannelType 4 Current_div1000
setChannelType 5 Frequency_div100
setChannelType 6 ReadOnly
setChannelType 7 Temperature
setChannelType 8 PowerFactor_div1000
setChannelType 9 EnergyTotal_kWh_div1000
//ch 1 (dpid 1) power relay control
linkTuyaMCUOutputToChannel 1 bool 1
//ch 2(dpid 20) voltage
linkTuyaMCUOutputToChannel  20 1 2
//ch 3(dpid 19) power watts
linkTuyaMCUOutputToChannel 19 1 3
//ch 4 (dpid 18)current Amps
linkTuyaMCUOutputToChannel 18 1 4
//ch 5 (dpid (133) frequency 
linkTuyaMCUOutputToChannel 133 1 5
//ch 6 (dpid  102) energy cost used
linkTuyaMCUOutputToChannel 102 1 6
// ch 7 (dpid 135) temp
linkTuyaMCUOutputToChannel 135 1 7
//ch 8 (dpid  134) power factor 
linkTuyaMCUOutputToChannel 134 raw 8
//ch 9 (dpid  123) energy consumed
linkTuyaMCUOutputToChannel 123 1 9

And here the autoexec.bat file that should perfectly fit this device once all the features listed above will be implemented:

startDriver TuyaMCU
startDriver NTP
tuyaMcu_setBaudRate 115200
setChannelType 1 toggle
setChannelType 2 Voltage_div100
setChannelType 3 Power_div100
setChannelType 4 Current_div1000
setChannelType 5 Frequency_div100
setChannelType 6 EnergyCost_div1000
setChannelType 7 Temperature
setChannelType 8 PowerFactor_div100
setChannelType 9 EnergyTotal_kWh_div1000
//ch 1 (dpid 1) power relay control
linkTuyaMCUOutputToChannel 1 bool 1
//ch 2(dpid 20) voltage
linkTuyaMCUOutputToChannel  20 1 2
//ch 3(dpid 19) power watts
linkTuyaMCUOutputToChannel 19 1 3
//ch 4 (dpid 18)current Amps
linkTuyaMCUOutputToChannel 18 1 4
//ch 5 (dpid (133) frequency 
linkTuyaMCUOutputToChannel 133 1 5
//ch 6 (dpid  102) energy cost used
linkTuyaMCUOutputToChannel 102 1 6
// ch 7 (dpid 135) temp
linkTuyaMCUOutputToChannel 135 1 7
//ch 8 (dpid  134) power factor 
linkTuyaMCUOutputToChannel 134 raw 8
//ch 9 (dpid  123) energy consumed
linkTuyaMCUOutputToChannel 123 1 9

p.kaczmarek2 · Answer

I must have forgotten to push. I've added Voltage_div100 and I will add remaining types tomorrow.

maximesharp · Answer

Thanks a lot for your work. I've flashed version 1.17.252, it does fix the issue on the device itself but the HASS template is still broken

p.kaczmarek2 · Answer

I think that you just need to redo the HASS discovery so the new change is send correctly to HA. Please try and confirm

maximesharp · Answer

I've already tried it, but it does not send the correct configuration payload.

p.kaczmarek2 · Answer

Sorry, I must have confused number of dec places with dec offset, I will push a fix now.\

maximesharp · Answer

It's working fine now, yesterday I tried to edit the HASS Payload part but I wasn't able to find which one of the two values was the dec offset or dec places (and Visual Studio wasn't giving me the hint).

I've modified the fw to display the value correctly on HASS, so if it can help you, here's the code:

case ChType_Power_div100: 
{
	dev_info = hass_init_sensor_device_info(POWER_SENSOR, i, 2, 2);
	MQTT_QueuePublish(topic, dev_info->channel, hass_build_discovery_json(dev_info), OBK_PUBLISH_FLAG_RETAIN);
	hass_free_device_info(dev_info);
	discoveryQueued = true;
}
break;
case ChType_PowerFactor_div100:
{
	dev_info = hass_init_sensor_device_info(POWERFACTOR_SENSOR, i, 4, 2);
	MQTT_QueuePublish(topic, dev_info->channel, hass_build_discovery_json(dev_info), OBK_PUBLISH_FLAG_RETAIN);
	hass_free_device_info(dev_info);
	discoveryQueued = true;
}
break;
case ChType_EnergyTotal_Cost_div1000: 
{
	dev_info = hass_init_sensor_device_info(ENERGYCOST_SENSOR, i, 3, 3);
	MQTT_QueuePublish(topic, dev_info->channel, hass_build_discovery_json(dev_info), OBK_PUBLISH_FLAG_RETAIN);
	hass_free_device_info(dev_info);
	discoveryQueued = true;
}
break;

Note: I've renamed EnergyCost_div1000 to EnergyTotal_Cost_div1000, just to follow the naming convention.

maximesharp · Answer

Hello,Big thanks for your work.Just seen that Power_div100 has been added yesterday with OpenBK 1.17.406 (and PowerFactor_div100 back in December 16).I've updated my device to the latest release, everything works fine.Still missing a channel type for energy total cost, but using EnergyTotal_kWh_div1000 will work for now.Also, is there a setting for NTP daylight saving?Here's my current working autoexec.bat for the device:Code: text Expand Select all Copy to clipboardstartDriver TuyaMCU startDriver NTP ntp_setServer 216.239.35.0 ntp_timeZoneOfs +01:00 tuyaMcu_setBaudRate 115200 setChannelType 1 toggle setChannelType 2 Voltage_div100 setChannelType 3 Power_div100 setChannelType 4 Current_div1000 setChannelType 5 Frequency_div100 setChannelType 6 EnergyTotal_kWh_div1000 setChannelType 7 Temperature setChannelType 8 PowerFactor_div100 setChannelType 9 EnergyTotal_kWh_div1000 //ch 1 (dpid 1) power relay control linkTuyaMCUOutputToChannel 1 bool 1 //ch 2(dpid 20) voltage linkTuyaMCUOutputToChannel 20 1 2 //ch 3(dpid 19) power watts linkTuyaMCUOutputToChannel 19 1 3 //ch 4 (dpid 18)current Amps linkTuyaMCUOutputToChannel 18 1 4 //ch 5 (dpid (133) frequency  linkTuyaMCUOutputToChannel 133 1 5 //ch 6 (dpid 102) energy cost used linkTuyaMCUOutputToChannel 102 1 6 // ch 7 (dpid 135) temp linkTuyaMCUOutputToChannel 135 1 7 //ch 8 (dpid 134) power factor  linkTuyaMCUOutputToChannel 134 raw 8 //ch 9 (dpid 123) energy consumed linkTuyaMCUOutputToChannel 123 1 9

Ggaljoen · Answer

Thank you for this device integration, I love IT. Took my time to figure out the rest of the dpId meaning; main goal was to switch on/off, managed to get this done with dpId 131 enum(4) 0 = ON, 1 = off, 2 = auto dpId 1 is more like a STATUS display (wake function I wrongly thought)

p.kaczmarek2 · Answer

For enum, I usually recommend to select the proper channel type, and if that's not present, you can always use "TextBox". Alternatively, you can write your own little page with REST interface and host it in LittleFS:
OpenBeken as a mini HTTP hosting - writing pages in Javascript, Tasmota REST

maximesharp · Answer

dpid 1 is marked as power relay control but it should be called power relay indicator (0=off/1=on) since it doesn't control the relay and only shows if the relay is on or off.I didn't notice this before since I use this device as a power monitor (and not as a smart switch).Here is a working autoexec.bat that fixes this error and adds the correct dpid to control the relay:Code: text Expand Select all Copy to clipboardstartDriver TuyaMCU startDriver NTP ntp_setServer 216.239.35.0 ntp_timeZoneOfs +01:00 tuyaMcu_setBaudRate 115200 setChannelType 0 Toggle_Inv setChannelType 1 ReadOnly setChannelType 2 Voltage_div100 setChannelType 3 Power_div100 setChannelType 4 Current_div1000 setChannelType 5 Frequency_div100 setChannelType 6 EnergyTotal_kWh_div1000 setChannelType 7 Temperature setChannelType 8 PowerFactor_div100 setChannelType 9 EnergyTotal_kWh_div1000 linkTuyaMCUOutputToChannel 131 enum 0 linkTuyaMCUOutputToChannel 1 bool 1 linkTuyaMCUOutputToChannel 20 1 2 linkTuyaMCUOutputToChannel 19 1 3 linkTuyaMCUOutputToChannel 18 1 4 linkTuyaMCUOutputToChannel 133 1 5 linkTuyaMCUOutputToChannel 102 1 6 linkTuyaMCUOutputToChannel 135 1 7 linkTuyaMCUOutputToChannel 134 raw 8 linkTuyaMCUOutputToChannel 123 1 9

Ggaljoen · Answer

That was a fast reply.How do I manage to have a selection between 0 / 1 / 2 for the 131 Enum? Can you point me to an example?Goal is to have this changeable in Home Assistant (over MQTT).

p.kaczmarek2 · Answer

@maximesharp isn't there already a channel type for that? If not, I can add one, it seems like a very common requirement

@Ggaljoen you can even just set TextField channel type and then manually script your Home Assistant in YAML to have a nice gui and everything. Are you planning to control this device mainly from Home Assistant or from OBK Web Panel?

maximesharp · Answer

I'm just using the Toggle_Inv channel since 0 = ON, 1 = off, 2 = auto, by sending 0 or 1 we can close or open the relay.I don't know what Auto should do, but I've tried with the OffDimBright (send 0, 1 or 2), 0 and 1 does switch the relay but 2 doesn't do anything.For HA, you may need to delete the device and use the Start Home Assistant Discovery button on the webui of the device, but it does work. They're a few that send the required 0,1,2 like OffDimBright' or LowMidHigh, but nothing for OnOffAuto. As I wrote, Auto (2) didn't do anything here.

Ggaljoen · Answer

Auto mode only works in specific modes like Timing_CountDown, for example.Code: text Expand Select all Copy to clipboard118 Enum(4) Device Interface 0 - 7, Security Protect, Electricity price, Smart Power Off /B, Timing CutOff/On/Cycle/CountDownThis device has many more capabilities than just reporting numbers of usage. Not sure how, but I am more in favor of Home Assist over the OBK interface (other users' protection on exposed control/usage).The option for 0/1/2 will work fine; the textual meaning can be added otherwise.

maximesharp · Answer

Well, while waiting for the OnOffAuto channel type to be implemented, you can set channel 0 type to LowMidHigh or OffDimBright and it should work as expected (but with the wrong option name)

Ggaljoen · Answer

For those who fear removing the CB3S module, a small suggestion: you don't need to desolder the WiFi module.
Instead, I used a USB to serial that is capable of powering the 3V3 line with enough current (to start up the unit completely), and then you can program the CB3S without removing it.
Just be sure NOT to plug it into a wall socket at the same time while programming.

hwti · Answer

For me, even with a dedicated 3.3V supply, it didn't work with a CH343P USB-serial (firmware backup was always interrupted), but it worked with a CP2102 one.Maybe it also needs the ability to drive the UART pin with enough current to avoid issues with the MCU trying to send data to the CB3S module.I added the tuyaMcu_defWiFiState 4 to bypass the Tuya pairing screen, else I had to press the + key on each boot.The device shows the energy values with 0.01Wh resolution, but only 1Wh is reported.I suppose the only way to get the full resolution would be to modify the CH573F firmware (not sure if possible).

p.kaczmarek2 · Answer

What was the resolution shown in Tuya app?

divadiow · Answer

by coincidence my S1 arrived last week. I've only just opened it up. cool device. initially quite impressed. Added after 9 [minutes]: also, the app shows a CPU temperature. Is this something that could be added to OBK for all Beken devices, like the LN temp?

p.kaczmarek2 · Answer

The autoexec.bat posted earlier also contains 0.01W resolution setup; Code: text Expand Select all Copy to clipboard setChannelType 3 Power_div100 So, @hwti , can you elaborate what do you mean here? Are you saying that the values from the screen display are not sent to OBK?

maximesharp · Answer

I can't relate to what he said about both the power resolution and the additional line to bypass the pairing screen.

Using the latest firmware (1.17.450) and my latest autoexec.bat, I don't have any issue with the power resolution and the pairing screen disappears once the device is connected to the Wi-Fi network.

(Note that channel 6 is set on kWh but should be in currency)

Added after 5 [minutes]:

divadiow wrote:
also, the app shows a CPU temperature. Is this something that could be added to OBK for all Beken devices, like the LN temp?

As you can see in my post above, on this device, the CPU temp is sent on dpid 135 from tuyamcu and set on channel 7 on OBK

Tuya ATORCH S1-B/W/T/H Smart Socket Energy Monitor (BK7231N) (C3BS) (CH573F) (BL0942)

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Post #30

Topic summary