Support for SONOFF Smart Power Meter Switch | POW Elite

[nobodyman1]

PROBLEM DESCRIPTION

Is it possible to use Tasmota on the new SONOFF POW Elite? I found some Pictures here. It´s based on an ESP32 and the power measuring is done with a CSE7759B (same as used in SONOFF POW R2). But what´s about the LCD driver?

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• [x] Read the Contributing Guide and Policy and the Code of Conduct
• [x] Searched the problem in issues
• [x] Searched the problem in discussions
• [x] Searched the problem in the docs
• [x] Searched the problem in the chat
• [ ] Device used (e.g., Sonoff Basic): _____
• [ ] Tasmota binary firmware version number used: _____
  • [ ] Pre-compiled
  • [ ] Self-compiled
• [ ] Flashing tools used: _____
• [ ] Provide the output of command: Backlog Template; Module; GPIO 255:

  TO REPRODUCE

  Steps to reproduce the behavior:

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

[sfromis]

Two points. First the FT232RL is a bad adapter to use for flashing as it does not have sufficient power, especially not for ESP32 Wifi operation. Second, you have to disconnect the adapter, and connect mains power to proceed after the flashing.

What may have been happening while you had mains power connected is unrelated to the above. Your log only demonstrates one single useful thing; that Tasmota is flashed on the device, and able to boot.

[madrose]

Make sure you are flashing the correct version of Tasmota It happened to me once, and it turns out I am flashing the 8266 version of the ESP32. make sure you flash the ESP32 version.

[sfromis]

In this case, the log does show that Tasmota for ESP32 version 12.1.1 was flashed, but other than that, it tells nothing about what happens when having mains power.

[bastians]

Thanks for your answers!

@sfromis I flashed it again without restarting it after flashing through the adapter and instead, I disconnected the adapter and connected the main power. But same result, no wifi. Is there a way to get the logs from the device when it's booting through the main power?

And which adapter would you recommend?

[sfromis]

The Getting-Started page does have a good recommendation, but as I already mentioned, while not very useful, the log you posted did show that you had Tasmota successfully flashed.

But it cannot tell anything about your trouble getting it to connect while on mains, as it shows clear symptoms of your USB/serial adapter not being able to supply power for Tasmota trying to start Wifi. And with an energy monitoring device, it is not safe to connect anything else while powering it with mains power.

[bastians]

Thank you @sfromis! I will try another adapter. But I also think my device is broken because I tried to flash the original firmware, what seemed to be successful but the device is not starting. Thanks again for your help! :)

[PauluzzNL]

I had a lot of issues getting this to work with the display together with the DS18x20 sensor. For whoever is still figuring it out.

• Make sure you use the ESP32 version to flash (tasmota32.bin), not the tasmota.bin - otherwise the device will not come up after flashing and in the serial console will keep restarting.

• Use the following template: https://templates.blakadder.com/sonoff_THR316D.html {"NAME":"Sonoff THR316D","GPIO":[32,0,0,0,225,9280,0,0,0,321,0,576,320,9184,9216,0,0,224,0,9248,0,1,0,3840,0,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":1}

Then in 'configure module' set IO GPIO25 to DS18x20

This lets both relay's work as well as show the temperature on the screen.

[Longlife4ever]

Yep (hestitating)... if you manage to get a stable serial connection.

works like a charm, but need to figure out how to display the values with your new commands.

[arendst]

Suppose you receive the below JSON result (verify with command DspLine9):

    //      {"ENERGY":{"TotalStartTime":"2022-07-05T16:01:39","Total":0.000,"Yesterday":0.000,"Today":0.000,"Power":0.00,"ApparentPower":0.00,"ReactivePower":0.00,"Factor":0.00,"Frequency":50,"Voltage":231.7,"Current":0.000}}
    // index: 1         2                                      3             4                 5             6            7                    8                    9             10             11              12
    //  unit: 0         0                                      4 (kWh)       4 (kWh)           4 (kWh)       4 (W)        0 (VA)               0 (VAr)              0             0              3 (V)           3 (A)

then commands DspLine1 11,3,3,4 and DspLine2 12,3,6,4 should display alternating Volt/Current and TotalEnergy/Power like the POWR3xxD does.

Works as just verified with my PZEM016 ;-)

[Longlife4ever]

Works as just verified with my PZEM016 ;-)

you are brilliant. Works great. And the °C unit can be displayed as well?

[arendst]

Yes as long as there is a temperature in the JSON message. You now know the drill.

[titou4307]

Hello I'm a newbee of the Tasmota SonOff ... I have a SonOff Elite flashed with tasmota and with a sensor THS01 (temp humidity sensor...) All seem OK but my question is :

Is it possible to put more than one THS01 like another SonOff ? (I think TH Origin where it is possible to connect DS18B20 ..I have one with 3 sensor DS18B20)

[NiklausS]

i have the same issue as bastians further up. I've tried with two different adapters and with lower speed.

@bastians did you find a solution for this?

Thanks in advance Nik

00:00:00.003-212/50 HDW: ESP32-D0WD-V3 00:00:00.080-210/49 UFS: FlashFS mounted with 308 kB free 00:00:00.146 CFG: Loaded from File, Count 2 00:00:00.162 QPC: Count 3 00:00:00.315 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.350 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.512 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DOUT, clock div:2 load:0x3fff0030,len:184 load:0x40078000,len:12616 load:0x40080400,len:2916 entry 0x400805c4

00:00:00.003-212/50 HDW: ESP32-D0WD-V3 00:00:00.080-210/49 UFS: FlashFS mounted with 308 kB free 00:00:00.146 CFG: Loaded from File, Count 2 00:00:00.162 QPC: Count 4 00:00:00.315 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.350 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.512 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DOUT, clock div:2 load:0x3fff0030,len:184 load:0x40078000,len:12616 load:0x40080400,len:2916 entry 0x400805c4

[malo6008]

Hi, I bought two POWR316D and I flashed them accordingly the bangertech.de website (Template applied). Both devices works and i can see all values per browser and values seems to be ok. The only thing i didn't get working is the display. In the meantime I've upgraded to the dev release 12.1.1.2. Now I'm able to execute the DspLine-commands (accordingly somewhere in this thread), but still I don't get any values on the display. Probably I've overseen an important action but cannot figure out which one. Can someone help me further? The output of the console is attached.

Many thanks in advance.

00:00:00.002 HDW: ESP32-D0WD-V3 00:00:00.038 UFS: FlashFS mounted with 304 kB free 00:00:00.083 CFG: Loaded from File, Count 45 00:00:00.098 QPC: Count 1 00:00:00.230 BRY: Berry initialized, RAM used=3935 bytes 00:00:00.255 Project tasmota - Tasmota Version 12.1.1.2(tasmota)-2_0_5(2022-09-19T20:20:52) 00:00:00.304 CFG: XDRV87 loaded from file 00:00:00.305 DSP: TM1621 00:00:00.953 WIF: Connecting to AP1 FRITZ!Box 7590 OL Channel 1 BSSId 2C:3A:FD:B1:68:2D in mode 11n as tasmota-A65F28-7976... 00:00:02.693 WIF: Connected 00:00:03.183 HTP: Web server active on tasmota-A65F28-7976 with IP address 192.168.188.55 14:38:14.156 RSL: INFO1 = {"Info1":{"Module":"Sonoff POWR316D","Version":"12.1.1.2(tasmota)","FallbackTopic":"cmnd/DVES_A65F28_fb/","GroupTopic":"cmnd/tasmotas/"}} 14:38:14.172 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-A65F28-7976","IPAddress":"192.168.188.55"}} 14:38:14.177 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":9}} 14:38:14.191 RSL: RESULT = {"POWER":"ON"} 14:38:14.194 RSL: POWER = ON 14:38:16.897 QPC: Reset 14:38:18.942 RSL: STATE = {"Time":"2022-09-20T14:38:18","Uptime":"0T00:00:10","UptimeSec":10,"Heap":150,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":39,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":44},"POWER":"ON","Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 OL","BSSId":"2C:3A:FD:B1:68:2D","Channel":1,"Mode":"11n","RSSI":100,"Signal":-44,"LinkCount":1,"Downtime":"0T00:00:04"}} 14:38:18.989 RSL: SENSOR = {"Time":"2022-09-20T14:38:18","ENERGY":{"TotalStartTime":"2022-09-20T10:20:40","Total":0.002,"Yesterday":0.000,"Today":0.002,"Period":0,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":239,"Current":0.000}} 14:38:27.838 CMD: DspLine1 14:38:27.848 RSL: RESULT = {"DspLine1":"0,0"} 14:38:34.628 CMD: DspLine9 14:38:34.646 RSL: RESULT = {"ENERGY":{"TotalStartTime":"2022-09-20T10:20:40","Total":0.002,"Yesterday":0.000,"Today":0.002,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":238,"Current":0.000}} 14:38:47.259 CMD: DspLine1 11,3,3,4 14:38:47.270 RSL: RESULT = {"DspLine1":"11,3,3,4"} 14:39:11.353 CMD: DspLine2 12,3,6,4 14:39:11.366 RSL: RESULT = {"DspLine2":"12,3,6,4"} 14:40:01.215 CMD: display 14:40:01.226 RSL: RESULT = {"Command":"Unknown"} 14:40:07.402 CMD: dspline 14:40:07.412 RSL: RESULT = {"DspLine1":"11,3,3,4"} 14:40:22.552 CMD: TelePeriod 14:40:22.558 RSL: RESULT = {"TelePeriod":300} 14:40:22.884 RSL: STATE = {"Time":"2022-09-20T14:40:22","Uptime":"0T00:02:14","UptimeSec":134,"Heap":144,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":24,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":40},"POWER":"ON","Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 OL","BSSId":"2C:3A:FD:B1:68:2D","Channel":1,"Mode":"11n","RSSI":98,"Signal":-51,"LinkCount":1,"Downtime":"0T00:00:04"}} 14:40:22.930 RSL: SENSOR = {"Time":"2022-09-20T14:40:22","ENERGY":{"TotalStartTime":"2022-09-20T10:20:40","Total":0.002,"Yesterday":0.000,"Today":0.002,"Period":0,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":237,"Current":0.000}} 14:45:22.882 RSL: STATE = {"Time":"2022-09-20T14:45:22","Uptime":"0T00:07:14","UptimeSec":434,"Heap":145,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":40},"POWER":"ON","Wifi":{"AP":1,"SSId":"FRITZ!Box 7590 OL","BSSId":"2C:3A:FD:B1:68:2D","Channel":1,"Mode":"11n","RSSI":100,"Signal":-41,"LinkCount":1,"Downtime":"0T00:00:04"}} 14:45:22.928 RSL: SENSOR = {"Time":"2022-09-20T14:45:22","ENERGY":{"TotalStartTime":"2022-09-20T10:20:40","Total":0.002,"Yesterday":0.000,"Today":0.002,"Period":0,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":231,"Current":0.000}}

[sfromis]

If you took it apart for flashing, one risk factor is that the connection from the display to the PCB can be highly susceptible to a bit of dust. I have Tasmota 12.1.1.2 running on POWR316D with the display showing data; did nothing to enable the display, outside of the general setup and flashing the template.

[bastians]

i have the same issue as bastians further up. I've tried with two different adapters and with lower speed.

@bastians did you find a solution for this?

Thanks in advance Nik

00:00:00.003-212/50 HDW: ESP32-D0WD-V3 00:00:00.080-210/49 UFS: FlashFS mounted with 308 kB free 00:00:00.146 CFG: Loaded from File, Count 2 00:00:00.162 QPC: Count 3 00:00:00.315 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.350 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.512 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DOUT, clock div:2 load:0x3fff0030,len:184 load:0x40078000,len:12616 load:0x40080400,len:2916 entry 0x400805c4

00:00:00.003-212/50 HDW: ESP32-D0WD-V3 00:00:00.080-210/49 UFS: FlashFS mounted with 308 kB free 00:00:00.146 CFG: Loaded from File, Count 2 00:00:00.162 QPC: Count 4 00:00:00.315 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.350 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.512 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DOUT, clock div:2 load:0x3fff0030,len:184 load:0x40078000,len:12616 load:0x40080400,len:2916 entry 0x400805c4

@NiklausS Unfortunately, I didn't find a solution with this device, it seemed to be broken (or I broke it). I also tried it with the recommended adapter but no success. I was able to set the Wifi through the webbased flasher, but the display did not work then. Therefore I bought a new device and there everything worked fine.

[NiklausS]

ts'me again,

somehow after some tries this fw worked... :-)

(esptool.venv) nik@yoga-15IIL05:~/Projects/esptool.venv/esp_bins$ esptool.py -b 921600 -p /dev/ttyUSB0 write_flash -e -fm dio 0x0 ~/Downloads/tasmota32-bluetooth.factory.bin

but with: ./components/esp_littlefs/src/littlefs/lfs.c:1229:error: Corrupted dir pair at {0x0, 0x1}

rst:0x1 (POWERON_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DOUT, clock div:2 load:0x3fff0030,len:184 load:0x40078000,len:12616 load:0x40080400,len:2916 entry 0x400805c4

00:00:00.003 HDW: ESP32-D0WD-V3 ./components/esp_littlefs/src/littlefs/lfs.c:1229:error: Corrupted dir pair at {0x0, 0x1} 00:00:00.172 UFS: FlashFS mounted with 312 kB free 00:00:00.178 CFG: Use defaults 00:00:00.328 QPC: Reset 00:00:00.405 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.432 Project tasmota - Tasmota Version 12.1.1(bluetooth)-2_0_4_1(2022-08-25T11:34:24) 00:00:00.434 iBeacon register for advert callbacks 00:00:00.436 MI32Option0: 1 00:00:00.447 MI32Option1: 0 00:00:00.449 MI32Option2: 0 00:00:00.450 MI32Option4: 1 00:00:00.451 MI32Option5: 0 00:00:00.452 MI32Option6: 0 00:00:00.454 M32: init: request callbacks 00:00:00.764 WIF: WifiManager active for 3 minutes 00:00:01.285 HTP: Web server active on tasmota-B9F444-5188 with IP address 192.168.4.1

however, i could install this and configure the sonoff.

@sformis - great idea. i had indeed taken apart the device to have a closer look. I'm searching for a free pin for with ad functionality for a CT. I was hard thinking which pin was causing the reboot - after fixing the screws things went much smoother. Thanks for this.

but i had only success with the latest developer software -

Program Version | 12.1.1.2(tasmota) 2022-09-20T18:37:43

now things are working - but i am not sure if the next OTA upgrade will work. The others did not always.

hope this helps Nik

[malo6008]

@sfromis : thanks for the tip!!! I've took it apart again and cleaned both sides of the contacts with an ear swab and isopropyl alcohol: and... it works now! based on DspLine9: 14:02:38.647 RSL: RESULT = {"ENERGY":{"TotalStartTime":"2022-09-20T10:20:40","Total":0.004,"Yesterday":0.000,"Today":0.004,"Power":6,"ApparentPower":21,"ReactivePower":20,"Factor":0.30,"Voltage":242,"Current":0.085}} I've set: DspLine1 10,3,5,4 // Voltage (V) & Today's Power consumption (kWh) DspLine2 11,3,6,4 // Current (A) & Actual Power Consumption (W)

[Seeelefant]

When will this be integrated in the standard tasmota version?

[arendst]

Mid October

[brageeb]

Mid October

12.2.0 has been released and definitely works on POWR320D. Firmware flashed via https://tasmota.github.io/install/ (options: tasmota & ESP32). Tasmotizer won't work since it's not compatible with ESP32 chip. After connecting the device to your network SSID, the configuration provided in by webpage https://templates.blakadder.com/sonoff_POWR320D.html (ref. to code reported at the end of this post) must be pasted into device's web UI, Configuration / Configure Other and activated afterwards.

{"NAME":"Sonoff POWR320D","GPIO":[32,0,9313,0,9312,576,0,0,0,0,9280,0,3104,0,320,0,0,0,0,0,0,9184,9248,9216,0,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":1}

[sfromis]

The Tasmotizer tool (if that's what you meant) does not try to support ESP32 at all. What exact binary you tried with can also be important.

Anyway, the recommended procedure would just be to do OTA upgrade to the new binary, not "cold flash" via wired.

[sfromis]

It was about which exact binary, there are many files for Tasmota 12.2.0 binaries. For wired flashing of ESP32 devices, it should generally be tasmota32.factory.bin, for OTA upgrade, it should be tasmota32.bin. Or another variant, if applicable. What's recommended for wired flashing is the Tasmota Web Installer. https://tasmota.github.io/install/

[barbudor]

Just Tasmota It will automatically select tasmota32

[sfromis]

Beware that if you download yourself, there is a non-minor risk that you do not download it as a strictly binary file, that's one of the pitfalls you avoid with the web installer, and letting it take care of automatic architecture selection and working download.

[arendst]

Did you activate the correct template? If not, nothing will be shown or happening.

[sfromis]

What's recommended is to input the template via the web UI, Configuration / Configure Other (remember to activate too). See the how-to link to the left on the template repository site.

[arendst]

@brageeb

12.2.0 has been released and tried to tasmotize it (via rev. 1.2) on POWR320D.

what hardware did you buy? Is it a THR320D or a POWR320D? They are totally different.

I will better wait for the next release of Tasmota firmware hoping that THR320D will be listed among alle the rest of pre-configured devices.

Won't happen. Use button Auto-configuration which is version independant from the configuration menu and select new auto-configuration - Sonoff POWR320D

[sfromis]

If your device is indeed THR320D with a temperature probe, that one would often be SI7021 (rectangular plastic, flat top/bottom) instead of DS18B20 (round steel tube).

[titou4307]

Hello I have join this discussion : If the device is POW320D so it needeed to chose button Auto-configuration which is version independant from the configuration menu and select new auto-configuration - Sonoff POWR320D (hardware can give Temp, humidity, power, etc....other parameters..) If the device is THR320D it no needeed to do this because the hardware only give temp + humidity ????

Thanks

[sfromis]

The POWR320D has no temp/hum sensor, and full setup is available as auto config. Sensors are only for energy monitoring.

The THR320D has a port for a sensor, but as there are two different ones sold for the device, this detail is not included in the auto configuration setup (still recommended). You need to configure gpio 25 for your sensor. Of course, no energy monitoring too.

[sfromis]

Maybe have 3 different autoconfig setups for THR320D, with either of the two "standard" sensors, or without....?

[arendst]

Let me chk if auto-config is able to do that.....

[arendst]

Works! A perfect way to flood the auto-config drop down list with all kinds of sensors.... I'll add two.

[rmoosa]

Is there any way to write custom output to the display using rules?

[arendst]

Yes and especially no.

The current implementation supports users to select any value from the teleperiod output. That's it. I see no advantage to support any other functionality. The hardware is crippeled as it has only one decimal point at a fixed location. Some units are tied together.

[rmoosa]

Yes and especially no.

The current implementation supports users to select any value from the teleperiod output. That's it. I see no advantage to support any other functionality. The hardware is crippeled as it has only one decimal point at a fixed location. Some units are tied together.

I have gpio25 configured as a switch. I want to write the state of the switch out to the display. 0 or 1 is fine. But the output in the teleperiod data is alpha and not numeric and hence doesn't write to the display. Any thoughts on how to resolve this. Sample data: SENSOR = {"Time":"2022-10-30T12:36:47","Switch1":"ON"}

[arendst]

In that case try to change "ON" to "1" and "OFF" to "0" using command StateText and see if it works.

[rmoosa]

In that case try to change "ON" to "1" and "OFF" to "0" using command StateText and see if it works.

Thanks. I tried that, but is still doesn't work. Think it is cause the field is still a text field, even though it has a numeric value. This is evident in the fact that the value is quoted in the sensor json payload.

[sfromis]

You could create a small Berry driver to have numeric values in the SENSOR payload.

[sfromis]

Not sure exactly how the DspLine works for picking from the JSON, but maybe something like this:

class MySwitch
  def json_append()
    var idx = 0
    var res = ''
    import string
    for sw : tasmota.get_switches()
      idx += 1
      res += string.format('%s"Switch%i":%i', (idx == 1 ? '' : ','), idx, sw ? 1 : 0)
    end
    if res != ""
      tasmota.response_append(',"NumSwitch":{' + res + '}')
    end
  end
end
tasmota.add_driver(MySwitch())

Resulted in this: /SENSOR = {"Time":"2022-10-31T00:50:15.108+01:00","Switch1":"ON","Switch2":"ON","NumSwitch":{"Switch1":0,"Switch2":0}}

Of course, you may have to tweak what on vs off means for numbers....

[rmoosa]

Thank you; this worked perfectly.

[blacknell]

I definitely saw it somewhere in this repo's issues, but can't find it.

Need to add another user GPIO to POWR320D to I can have I2C. Someone (possibly @arendst) linked a PDF that showed how to hack the board with a couple of approaches (0R resistor I think). Would be grate if this could be reposted.

[arendst]

Seasrch for the THR320D or THR316D as what you ask is NOT SUPPORTED on POWR320D (too hazaedous as Gnd is connected to AC)

[MatthewRorke]

I have a Sonoff POWR320D I configured the wiring as per the small booklet that comes with the device and I am running the latest release of Tasmota32.bin

It is currently sitting in my Distribution Box receiving power from a 20A breaker. My multimeter shows that the voltage going in from the breaker is at 220-230v and the voltage going out from the POW320D is 220-230V. However, all other values are 0.00

My hotwater heater is being powered and is definitely running.

But this is the data I have available:

[arendst]

Provide result of command template. Provide some weblog 4 logging. Expect something like

17:08:53.805 CMD: weblog 4
17:08:53.808 SRC: WebConsole from 192.168.2.1
17:08:53.811 CMD: Grp 0, Cmd 'WEBLOG', Idx 1, Len 1, Pld 4, Data '4'
17:08:53.821 MQT: stat/powr320d3/RESULT = {"WebLog":4}
17:08:53.859 DMP: 55 5A 02 D6 90 00 03 58 00 3C FF 04 D9 8E 4D 6C 50 11 0F DF 61 0F B4 95
17:08:53.886 DMP: 55 5A 02 D6 90 00 03 58 00 3C FF 04 D7 4E 4D 6C 50 11 0F DF 61 0F B4 53
17:08:53.986 DMP: 55 5A 02 D6 90 00 03 58 00 3C FF 04 D7 4E 4D 6C 50 11 0F DF 61 0F B4 53
17:08:54.086 DMP: 55 5A 02 D6 90 00 03 58 00 3C FF 04 D7 4E 4D 6C 50 11 0F DF 61 0F B5 54
17:08:54.186 DMP: 55 5A 02 D6 90 00 03 58 00 3C FF 04 D7 4E 4D 6C 50 11 0F DF 61 0F B5 54
17:08:54.286 DMP: 55 5A 02 D6 90 00 03 58 00 3C FF 04 D7 4E 4D 6C 50 11 0F DF 61 0F B5 54

[MatthewRorke]

@arendst Thanks for replying. Let me know if you need any further logs.

Provide result of command template.

17:12:13.873 MQT: stat/GEYSER_SMART_SWITCH/RESULT = {"NAME":"Sonoff POWR320D","GPIO":[32,0,9313,0,9312,576,0,0,0,0,9280,0,3104,0,320,0,0,0,0,0,0,9184,9248,9216,0,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":1}

Provide some weblog 4 logging.

17:12:40.595 MQT: stat/GEYSER_SMART_SWITCH/RESULT = {"WebLog":4}
17:12:40.630 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 27 23 FF 61 00 62 E0
17:12:40.751 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 28 BE 63 61 00 62 E0
17:12:40.851 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 2A 57 C8 61 00 62 E0
17:12:40.952 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 2B F1 2D 61 00 62 E0
17:12:41.052 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 2D 8A 92 61 00 62 E0
17:12:41.152 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 2F 23 F7 61 00 62 E0
17:12:41.252 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 30 BC 5D 61 00 62 E0
17:12:41.352 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 32 56 C1 61 00 62 E0
17:12:42.121 CFG: Saved, Count 57, Bytes 4096
17:12:42.137 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 33 F0 26 61 00 62 E0
17:12:42.187 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 35 89 8B 61 00 62 E0
17:12:42.237 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 37 22 F0 61 00 62 E0
17:12:42.287 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 38 BB 56 61 00 62 E0
17:12:42.337 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 3A 55 BA 61 00 62 E0
17:12:42.388 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 3B EE 20 61 00 62 E0
17:12:42.437 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 3D 87 85 61 00 62 E0
17:12:42.488 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 06 3E 11 4E 08 90 3F 21 E9 61 00 62 8F
17:12:42.537 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 06 3E 11 4E 08 90 40 BB 4E 61 00 62 8F
17:12:42.588 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 06 3E 11 4E 08 90 42 54 B3 61 00 62 8F
17:12:42.637 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 06 3E 11 4E 08 90 43 EE 18 61 00 62 8F
17:12:42.687 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 06 3E 11 4E 08 90 45 87 7D 61 00 62 8F
17:12:42.737 DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 06 3E 11 4E 08 90 47 20 E2 61 00 62 8F```

[arendst]

DMP: F2 5A 02 DF 28 00 03 3D 00 3D C2 07 3D 62 4E 08 90 27 23 FF 61 00 62 E0

Byte one: F2 = Power cycle exceeds range - takes too long - No load

Re-verify cabling. For some reason the energy monitoring chip doesn't see any load.

[titou4307]

I definitely saw it somewhere in this repo's issues, but can't find it.

Need to add another user GPIO to POWR320D to I can have I2C. Someone (possibly @arendst) linked a PDF that showed how to hack the board with a couple of approaches (0R resistor I think). Would be grate if this could be reposted.

Seasrch for the THR320D or THR316D as what you ask is NOT SUPPORTED on POWR320D (too hazaedous as Gnd is connected to AC)

Hello It is possible to add a second (2ème) sensor temp humidity on THR320D ??

[ag3nt-sn4k3]

Hello all, unfortunately I have problems with my POW Elite (THR320D).

I can switch it on/off but it does not show me any consumption data on the display or on the web interface.

Furthermore, the LEDs on the device are all off unless I turn on, then the power ON LED lights up. Das Gerät hat nur ein Relay, wieso gibt es zwei Buttons zum schalten?

Tasmota version: 12.2.0 Template: {"NAME":"Sonoff THR320D","GPIO":[32,0,0,0,226,9280,0,0,0,321,0,576,320,9184,9216,9312,0,0,9313,9248,0,1,0,3840,0,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":1} from https://templates.blakadder.com/sonoff_THR320D.html

LOG: 00:00:00.003 HDW: ESP32-D0WD-V3 00:00:00.061 UFS: FlashFS mounted with 304 kB free 00:00:00.114 CFG: Loaded from File, Count 16 00:00:00.130 QPC: Count 1 00:00:00.302 BRY: Berry initialized, RAM used=4041 bytes 00:00:00.369 Project tasmota - Tasmota Version 12.2.0(tasmota)-2_0_5(2022-10-17T08:39:59) 00:00:00.449 CFG: XDRV87 loaded from file 00:00:00.450 DSP: TM1621 00:00:01.211 WIF: Connecting to AP1 Sisteron Channel 1 BSSId E0:63:DA:CA:B0:EE in mode 11n as tasmota-A68B34-2868... 00:00:03.297 WIF: Connected 00:00:03.511 HTP: Web server active on tasmota-A68B34-2868 with IP address 10.1.11.150 18:21:56.487 RSL: INFO1 = {"Info1":{"Module":"Sonoff THR320D","Version":"12.2.0(tasmota)","FallbackTopic":"cmnd/DVES_A68B34_fb/","GroupTopic":"cmnd/tasmotas/"}} 18:21:56.502 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-A68B34-2868","IPAddress":"10.1.11.150"}} 18:21:56.506 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":7}} 18:22:00.939 RSL: STATE = {"Time":"2022-11-04T18:22:00","Uptime":"0T00:00:09","UptimeSec":9,"Heap":150,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":58,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":44},"POWER1":"OFF","POWER2":"ON","Wifi":