Config? - Atorch GR2P-W/S/L Smart DIN Rail Meter (BK7231N) (CB2S) (CH573F) (BL0942)

Hello Everybody!

My mailbox received some DIN Rail Energy monitors from Aliexpress:
- Atorch GR2P-W/S/L





The buttons, menus, and display appearance are strikingly similar to the Atorch S1-B/W/T/H.
I also got the S1, which I was able to flash and configure with the help of the discussion at https://www.elektroda.com/rtvforum/topic4003739.html . Thanks a lot to the contributors there!

The GR2P is easy to open with two screws on the bottom.
Inside, there is a stack of the display on top of the PCB with a block of black foam in between.


A CB2S is mounted through the PCB from below. The foam sticks to both, the display and the board.
To get to the component side of the board, one has to peel off the foam block. The adhesive is somewhat strong, some residues of foam stuck to the components.

On the board, there are the following ICs:
- CHF573F (RISC-V MCU)
- BL0942 (Metering IC)
- PN8015 (Power Management)

I didn't try to flash the CB2S in place. It came out easily with the help of desoldering braid and gravity.
After flashing and soldering it back into the device, the wifi node and the openbeken web app came up as expected.

Now I am stuck. I tried the configuration for similar devices, including:
- Atorch S1 (https://www.elektroda.com/rtvforum/topic4003739.html). This one has a CB3S.
- Tuya LSPA9 (https://www.elektroda.com/rtvforum/topic3887748.html).
- quite a few other energy meters

None of these worked. I didn't get any measurements.

Any ideas how to proceed?

It's a very nice device, we can make this work together.
First of all, have you seen the TuyaMCU generic guide?
https://www.elektroda.com/rtvforum/topic4038151.html
This should give you a basic overview of the process.

Since this device is already flashed, you can with guessing baud rate and requesting dpIDs with tuyaMcu_sendQueryState command.

Thanks for the hint! I dumped the backup image on extractor in the flash tool, and it said 
{
"baud":"9600"
}
Probably I could have guessed that as well.   

autoexec.bat wrote:

startDriver TuyaMCU
startDriver NTP
ntp_setServer 172.25.1.1
ntp_timeZoneOfs +01:00
tuyaMcu_setBaudRate 9600
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

I get measurements in both web app and to the mqtt server (no load connected). Perfect!

9600 is a default baud, it should work without any specific settings.

Is everything working as expected? I can see your config is missing the setting of default WiFi state 0x04. By default, it's set only when MQTT is connected.

I realize that I posted the wrong autoexec. It was the last from the S1 instead of the GR2P.
I corrected that above: Baud rate is 9600 and 'mqtt_broadcastInterval 5' is not there. Sorry for the confusion!

You are right that it works with the default baud rate without tuyaMcu_setBaudRate. It was just there because I copied from the S1.

I don't know why the main page shows two toggle buttons. I'm using the device without any switch.

But yes, everything that is there seems to work!

I didn't know about the WiFi state 0x04, but I think that showing the MQTT state is the best for my use case.

Maybe you still have "Toggle" channel types set? Check in the web app.

Hello, @bbb34 !

Searching for the thread I started some time ago on the same device, I've found that you had started this one before...

Just writing this to tell you that, in case you haven't already come over it, you can find there more information about this device's DpIDs and configuration