Tongou TO-Q-SA1 WiFi Smart Energy Meter – Anyone tried flashing it?

Name: Tongou TO-Q-SA1 WiFi Smart Energy Meter – Anyone tried flashing it?
Uploaded: 2025-06-04T07:09:56+0200
Description: Hi everyone, I recently came across a very compact and seemingly well-designed smart energy meter called **Tongou TO-Q-SA1**. It's a WiFi-enabled DIN-rail mounted meter, based on the Tuya platform. What's interesting is that it **doesn't have a relay inside**, which makes it potentially safer...

Question

Hi everyone, I recently came across a very compact and seemingly well-designed smart energy meter called **Tongou TO-Q-SA1**. It's a WiFi-enabled DIN-rail mounted meter, based on the Tuya platform. What's interesting is that it **doesn't have a relay inside**, which makes it potentially safer...

kymlalu · Accepted Answer

I could help with some images. Bigger chip (MCU ) is Wi-Fi module is power measuring chip is

p.kaczmarek2 · Accepted Answer

STC chip and only 4 pads of WB2S soldered? Well, it looks like TuyaMCU. We have a good TuyaMCU support in OBK.

kymlalu · Accepted Answer

Yea, only 4 pins.

p.kaczmarek2 · Accepted Answer

Can you take 2MB flash backup?

kymlalu · Accepted Answer

I hope i did that correctly.
( also edited post with pictures and added link to the power measuring chip for convinience)

{
   "baud":"115200"
}


Sorry, no meaningful pins data found. This device may be TuyaMCU or a custom one with no Tuya config data.
Baud keyword found, this device may be TuyaMCU or BL0942. Baud value is 115200
No module information found.
And the Tuya section starts, as usual, at 2023424

p.kaczmarek2 · Answer

We have flashed similar devices, but not this specific model. We can help you with whole process, but first you need to take one apart and make some photos from the inside. I can help with PCB analysis.

kymlalu · Answer

I'm quite new here, but if I understand it correctly, I can't configure Tasmota MCU because everything goes through that second MCU (STC8). Right?

divadiow · Answer

with TuyaMCU devices it'll not be a case of setting up devices from the dropdown menus in the "Configure Module" page but rather mapping dpIDs in an autoexec script.

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

autoexec examples https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/autoexecExamples.md

there are many TuyaMCU journeys searchable from device list that can be used as a template for how to approach this sort of device https://openbekeniot.github.io/webapp/devicesList.html

to start you off here are the dpIDs for your device.

Log in, to see the code

Note this is not a config to be imported anywhere as-is, but only displayed as json here for readability.

kymlalu · Answer

Thank you for reply.Yesterday I tried to get DpIDs by using TuyaMCU analyzer (as I found tutorial) but it wasn't helpful at all. Mainly keep alive packets and switch from UI. I wasn't able to catch any data related to voltage (I had it connected through variac), which confuses me because in Tuya app I could see how it's changing but no data on serial.Also I tried to find in database but I guess that I used wrong keywords.I try to extract them by that linked tutorial (which I didn't find because I wasn't looking enough), just to learn how to do it (hopefully).

p.kaczmarek2 · Answer

This is VCP:


      "desc_en": "1. Phase A voltage, current and power\n2. Big-endian HEX format, total 8 bytes\n3. Units: voltage 2 bytes (0.1V), current 3 bytes (0.001A), power 3 bytes (0.001kW)\n4. Example: 08 80 00 03 E8 00 27 10 means 217.6V, 1.000A, 10.000kW\n5. Communication: (1) Panel queries on entry, sends 0x08 to meter, meter reports to cloud, panel displays data (WiFi supported). (2) Meter periodically reports: every 15 seconds for WiFi, every hour for NB.",

It seems I need to add a special key for this format, because the one we have, RAW_TAC2121C_VCP, does not match.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

kymlalu · Answer

Tell me if you need any data. I'll try to provide them as far as I will be able ( and I still have it disassembled and wires are hooked ).
But I guess that method through tuya development is more "friendly" ?

p.kaczmarek2 · Answer

I've tried doing that blindly, here is commit:
https://github.com/openshwprojects/OpenBK7231...mmit/59f6d3549f2facf4bc23647952e405d32b9addd5
It should build a release soon, so you can do OTA and try.

Do you know how to use it? What is your autoexec.bat now?

Still, I didn't test that. If you provide me a sample capture with packed of dpID 6, I may be able to verify that.

kymlalu · Answer

I'm not that far, I'm affraid. And still tuya original FW ( as you wrote in that tutorial - it is better for indentifying most DpIDs ).
Also I had read a lot of things here. There are some things that I yet don't understand.
I guess that for what you asking I will have to flash OBK FW , right?

I'm struggling with basics ( I guess) because something isn't obvious at first look or it is confusing for me. And I don't want bother here with questions that I can answer by reading informations here.

Spoiler:

Also things are scattered kinda everywhere.
I'm not complaining in any way, just sharing how I see it as a novice here . I'm more HW guy, I have to do to some SW work here and there so I can comprehend some things ( and sometimes to do some light code ), also my english is pretty bad so all those things are factor in mine understanding in all this.
Again no complains from my, I'm aware that lot of this work is done in your free time and shared freely. But this will be better in some "feedback" threat.

p.kaczmarek2 · Answer

I see, don't worry, we can help you step by step. But first:
TuyaMCU flashing, setup and configuration guide - configure dpIDs for Home Assistant
https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/autoexecExamples.md
And if you have already connected TuyaMCU analyzer in a safe way (take care - device may not be isolated from mains, so if you connect it to your PC, you may cause a short, explosion and fire), please take some packets capture for later reference.

Then proceed along tutorial. If you have any specific questions, then feel free to ask. Also if something is not clear on tutorial - just give us a specific question and we will help.

kymlalu · Answer

There is some capture. Didn't have much time today to play with it.
Device with original FW, powered from socket (through variac, I also discovered that it works if you supply it with 26V DC - connected to wires that supposed to go on 230V).
Device was booted up and I went through most clickable things in UI (see. screenshots) in that order.
Captured HEX


55AA00060008720200040000001CA155AA0006000568040001007755AA00000000FF55AA0006000568040001017855AA00060008730200040000010E9555AA00060008730200040000010E9555AA00060008730200040000010D9455AA0006000566040001007555AA0006000566040001017655AA00060008740200040000006BF255AA0006000567040001007655AA0006000567040001017755AA0006000877020004000004831155AA0006000569040001007855AA0006000569040001017955AA000600087602000400000244CF55AA000600087602000400000243CE55AA00000000FF55AA000600056B040001007A55AA00060008780200040000000A9555AA00060008780200040000000A9555AA0006000565040001007455AA0006000565040001017555AA000600050B010001011855AA000600050B010001001755AA00000000FF55AA000600050C010001011955AA000600080E020004000003E80C55AA00000000FF55AA000600050B010001011855AA00000000FF55AA00000000FF55AA00000000FF55AA000600050B010001001755AA0006000522010001012F55AA00000000FF55AA00000000FF

I guess it didn't catch any measurements - I switched on 100W bulb as load. And I also changed voltage few times (from roughly 230V to 150V and back) - saw that in app but not in console (or maybe I'm doing something wrong) .

kymlalu · Answer

more i read, more i am lost and confused.

Anyway, i flashed it and there could be that DpID 6 ? ( only powered up, no current flowing through )

EDIT: I did some config ( use some examples and changed it to RAW_V2C3P3 ) and it seems that reading is almost correct. It is possible to do some "calibration" to have it more precise (voltage is off by 1V and current is off by 2mA )?

Autoexec.bat


// Start TuyaMCu driver
startDriver TuyaMCU
// set TuyaMCU baud rate
tuyaMcu_setBaudRate 115200
// set TuyaMCU default wifi state 0x04, which means "paired",
// because some TuyaMCU MCUs will not report all data
// unless they think they are connected to cloud
tuyaMcu_defWiFiState 4
// Measurements - Dpid 6 "phase_a" - channel RAW_V2C3P3
// TAC2121C VoltageCurrentPower Packet
// This will automatically set voltage, power and current
linkTuyaMCUOutputToChannel 6 RAW_V2C3P3
setChannelType 0 Voltage_div10
setChannelLabel 0 "Voltage"
setChannelType 1 Current_div1000
setChannelLabel 1 "Current"
setChannelType 2 Power
setChannelLabel 2 "Power"

casiopeia80 · Answer

>>21570955 Hi! Is your module working properly?

I'm configuring it like this:

setChannelType 0 Voltage_div10
setChannelLabel 0 Voltage
setChannelType 1 Current_div1000
setChannelLabel 1 Current
setChannelType 2 Power
setChannelLabel 2 Power
In the startup command list, I add:

startDriver TuyaMCU
tuyaMcu_setBaudRate 115200
tuyaMcu_defWiFiState 4
linkTuyaMCUOutputToChannel 6 RAW_V2C3P3
Everything starts working — I get voltage, current, and power readings.

But after about 25 minutes, the data stops coming. I only see zero values.
Either the MCU is waiting for something from the Tuya cloud, or I just got a faulty unit and it's a hardware issue

p.kaczmarek2 · Answer

When it goes silent,can you try running tuyaMcu_sendQueryState command?

When it goes silent, what is in the web app log, are TuyaMCU heartbeats received?

Do you have TuyaMCU queue flag enabled?

I think I can add calibration to RAW_V2C3P3, I'll add it and let you know. So, we need three adjustable offsets - for Voltage, Current and Power?

casiopeia80 · Answer

Code: text Expand Select all Copy to clipboardtuyaMcu_sendQueryState' Result] OK Info:TuyaMCU:Received: 55 AA 03 03 00 00 05  Info:TuyaMCU:ProcessIncoming[v=3]: cmd 3 (WiFiState) len 7 Info:TuyaMCU:Received: 55 AA 03 07 00 08 01 02 00 04 00 00 00 AF C7  Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15 Info:TuyaMCU:ParseState: id 1 type 2-val len 4 Info:TuyaMCU:ParseState: int32 175 Info:TuyaMCU:Received: 55 AA 03 07 00 05 0B 01 00 01 00 1B  Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12 Info:TuyaMCU:ParseState: id 11 type 1-bool len 1 Info:TuyaMCU:ParseState: byte 0 Info:TuyaMCU:Received: 55 AA 03 07 00 05 65 04 00 01 00 78  Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12 Info:TuyaMCU:ParseState: id 101 type 4-enum len 1 Info:TuyaMCU:ParseState: byte 0 Info:TuyaMCU:Received: 55 AA 03 07 00 05 66 04 00 01 01 7A  Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12 Info:TuyaMCU:ParseState: id 102 type 4-enum len 1 Info:TuyaMCU:ParseState: byte 1 Info:TuyaMCU:Received: 55 AA 03 07 00 05 67 04 00 01 01 7B  Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12 Info:TuyaMCU:ParseState: id 103 type 4-enum len 1 Info:TuyaMCU:ParseState: byte 1 Yes, I have this flag set. I checked three times. The same amount of time always passes (about half an hour), and the MCU stops giving current and voltage values.

p.kaczmarek2 · Answer

So it sends more data after tuyaMcu_sendQueryState , but did it resend dpID 6? Voltage, current, etc?

casiopeia80 · Answer

>>21576526 Yes, after issuing tuyaMcu_sendQueryState, the MCU does send multiple dpIDs, but unfortunately dpID 6 (RAW_V2C3P3 — voltage, current, power) is not among them. Here's what I received in the log after sending the command:
Info:TuyaMCU:Received: 55 AA 03 07 00 08 01 02 00 04 00 00 00 AF C7
Info:TuyaMCU:ParseState: id 1 type 2-val len 4 -> int32 175

Spoiler:

tuyaMcu_sendQueryState' Result] OK
Info:TuyaMCU:Received: 55 AA 03 03 00 00 05
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 3 (WiFiState) len 7
Info:TuyaMCU:Received: 55 AA 03 07 00 08 01 02 00 04 00 00 00 AF C7
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 1 type 2-val len 4
Info:TuyaMCU:ParseState: int32 175
Info:TuyaMCU:Received: 55 AA 03 07 00 05 0B 01 00 01 00 1B
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 11 type 1-bool len 1
Info:TuyaMCU:ParseState: byte 0
Info:TuyaMCU:Received: 55 AA 03 07 00 05 65 04 00 01 00 78
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 101 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 0
Info:TuyaMCU:Received: 55 AA 03 07 00 05 66 04 00 01 01 7A
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 102 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 07 00 05 67 04 00 01 01 7B
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 103 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 07 00 05 68 04 00 01 01 7C
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 104 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 07 00 05 69 04 00 01 00 7C
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 105 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 0
Info:TuyaMCU:Received: 55 AA 03 07 00 05 6B 04 00 01 01 7F
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 107 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 07 00 05 6E 04 00 01 00 81
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 110 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 0
Info:TuyaMCU:Received: 55 AA 03 07 00 08 72 02 00 04 00 00 00 32 BB
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 114 type 2-val len 4
Info:TuyaMCU:ParseState: int32 50
Info:TuyaMCU:Received: 55 AA 03 07 00 08 73 02 00 04 00 00 01 18 A3
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 115 type 2-val len 4
Info:TuyaMCU:ParseState: int32 280
Info:TuyaMCU:Received: 55 AA 03 07 00 08 74 02 00 04 00 00 00 64 EF
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 116 type 2-val len 4
Info:TuyaMCU:ParseState: int32 100
Info:TuyaMCU:Received: 55 AA 03 07 00 08 76 02 00 04 00 00 03 20 B0
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 118 type 2-val len 4
Info:TuyaMCU:ParseState: int32 800
Info:TuyaMCU:Received: 55 AA 03 07 00 08 77 02 00 04 00 00 07 D0 65
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 119 type 2-val len 4
Info:TuyaMCU:ParseState: int32 2000
Info:TuyaMCU:Received: 55 AA 03 07 00 08 78 02 00 04 00 00 00 0A 99
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 120 type 2-val len 4
Info:TuyaMCU:ParseState: int32 10
Info:TuyaMCU:Received: 55 AA 03 07 00 08 7D 02 00 04 00 00 00 AF 43
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 125 type 2-val len 4
Info:TuyaMCU:ParseState: int32 175
Info:TuyaMCU:Received: 55 AA 03 07 00 08 83 02 00 04 00 00 02 3A D6
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 131 type 2-val len 4
Info:TuyaMCU:ParseState: int32 570
Info:TuyaMCU:Received: 55 AA 03 07 00 08 20 02 00 04 00 00 13 8E D8
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 32 type 2-val len 4
Info:TuyaMCU:ParseState: int32 5006
Info:TuyaMCU:Received: 55 AA 03 07 00 08 32 02 00 04 00 00 00 46 8F
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 50 type 2-val len 4
Info:TuyaMCU:ParseState: int32 70
Info:TuyaMCU:Received: 55 AA 03 00 00 01 01 04
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 0 (Hearbeat) len 8
Info:TuyaMCU:Received: 55 AA 03 00 00 01 01 04
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 0 (Hearbeat) len 8
Info:TuyaMCU:Received: 55 AA 03 00 00 01 01 04
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 0 (Hearbeat) len 8
Info:TuyaMCU:Received: 55 AA 03 00 00 01 01 04
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 0 (Hearbeat) len 8
Info:TuyaMCU:Received: 55 AA 03 00 00 01 01 04
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 0 (Hearbeat) len 8
Info:TuyaMCU:Received: 55 AA 03 07 00 08 01 02 00 04 00 00 00 B0 C8
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 1 type 2-val len 4
Info:TuyaMCU:ParseState: int32 176
Info:TuyaMCU:Received: 55 AA 03 07 00 08 7D 02 00 04 00 00 00 B0 44
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 125 type 2-val len 4
Info:TuyaMCU:ParseState: int32 176
Info:TuyaMCU:Received: 55 AA 03 07 00 08 0D 02 00 04 00 00 00 00 24
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 13 type 2-val len 4
Info:TuyaMCU:ParseState: int32 0
Info:TuyaMCU:Received: 55 AA 03 00 00 01 01 04
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 0 (Hearbeat) len 8
Info:TuyaMCU:Received: 55 AA 03 00 00 01 01 04
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 0 (Hearbeat) len 8

As you can see, dpID 6 is completely missing, and only other IDs like 1, 11, and 101–103 are returned. This confirms that the MCU is alive and responding, but simply stops sending measurement data after ~30 minutes, even when explicitly queried.

This strongly suggests that the MCU is intentionally suppressing dpID 6, probably due to missing Tuya cloud handshake or timeout. I don’t believe this is a hardware fault — it seems more like Tuya MCU firmware behavior.

Let me know if you want me to try anything else.

Added after 34 [minutes]:

Add some photos of the device

p.kaczmarek2 · Answer

Try what this guy used. he has equivalent of send query state with some extra commands

casiopeia80 · Answer

I’ve noticed another thing. As I mentioned earlier, the transmission of voltage and current values stops after about 30 minutes of operation. After that, the MCU seems to “sleep” exactly for one hour. Then it sends voltage, current, and power values once, and goes back to sleep again.

Added after 29 [minutes]:

p.kaczmarek2 wrote:
Try what this guy used.
https://www.elektroda.com/rtvforum/topic3959907.html#20465272
he has equivalent of "send query state" with some extra commands

I didn't understand anything from that link ((
Isn't it possible to just connect the BL0942 directly to the BK7231N and throw the 8H3K64S2 chip to hell?))
I know how to solder.

p.kaczmarek2 · Answer

I just meant that you can try the same thing as @xury , add this to autoexec.bat and check again for few hours:


addRepeatingEvent 10 -1 backlog uartSendHex 55AA000300010407; uartSendHex 55AA0008000007;uartSendHex 55AA00000000FF

I just want to know. If it fails, we'll try to connect BL0942 directly to WiFi module.

casiopeia80 · Answer

I added the following commands to the startup set: startDriver TuyaMCU tuyaMcu_setBaudRate 115200 tuyaMcu_defWiFiState 4 linkTuyaMCUOutputToChannel 6 RAW_V2C3P3 addRepeatingEvent 10 -1 backlog uartSendHex 55AA000300010407; uartSendHex 55AA0008000007; uartSendHex 55AA00000000FF Then I power-cycled the module so that the MCU would start sending data every five seconds again, instead of once per hour like it does now. I’ll report back the results after half an hour. By the way, the idea of removing the 8H3K64S2 chip still lingers in my mind. Because if I do that, won’t I get proper readings not only for current and voltage but also for the cumulative energy meter data?

p.kaczmarek2 · Answer

You can connect BL0942 directly to WiFi module via UART (RX1/TX1), make sure to put BL0942 in UART mode, check datasheet. OpenBeken has BL0942 driver, it will calculate some data like total energy usage, today energy, etc. This may work for you, however, you will need to calibrate BL0942 first by connecting a known load, like 60W bulb, to the device, measuring it with a third party, reliable meter and then use commands PowerSet, VoltageSEt, CurrentSet to set expected measurements. You can also do the same in the obk web App, tools section

casiopeia80 · Answer

Well, half an hour has passed, and the device stopped sending readings again.

The commands addRepeatingEvent 10 -1 backlog uartSendHex 55AA000300010407; uartSendHex 55AA0008000007; uartSendHex 55AA00000000FF didn’t change anything.
If you have any other suggestions, please let me know. I'll try to implement them. It's a pity — I really liked the device for its ease of installation and compactness.

p.kaczmarek2 · Answer

There is one reliable method that can help us. You would need to be able to capture traffic between WiFi module with Tuya firmware and the MCU in a safe manner, without exploding your PC. You would need a galvanic signal isolation for that. It could be done with adum1201 . Then we would compare what Tuya firmware sends versus things send by OBK. We have a TuyaMCU Analyzer tool for that. https://github.com/openshwprojects/TuyaMCUAnalyzer

Added after 46 [seconds]:

To be sure - it does not stop with Tuya firmware?

casiopeia80 · Answer

So, why is galvanic isolation needed? I can just use an old laptop and connect to UART1 through a USB-UART adapter. I’ll only supply 3.3V to power the chips. Yes, voltage and current readings will be zero, but the device will still be sending zeros. I’ll see it through MQTT in Grafana. I think it’s worth trying. As for the Tuya firmware, I only tested it for a few minutes, so that part still remains in question.

Tongou TO-Q-SA1 WiFi Smart Energy Meter – Anyone tried flashing it?

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