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)

[arendst]

Pls provide a photo of your THR316D with sensor connected

[arendst]

Also provide the output of command status 0

[sfromis]

Also the output of Backlog Module; Template; Gpio all to verify that you have the config set correctly.

[anixi]

Outcome Status 0 (took out the internet addresses):

13:02:59.778 CMD: status 0
13:02:59.779 SRC: WebConsole from xxxxxxxx
13:02:59.781 CMD: Grp 0, Cmd 'STATUS', Idx 1, Len 1, Pld 0, Data '0'
13:02:59.788 MQT: stat/tasmota_0FDEC8/STATUS = {"Status":{"Module":0,"DeviceName":"Tasmota","FriendlyName":["Tasmota",""],"Topic":"tasmota_0FDEC8","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0,"StatusRetain":0}}
13:02:59.794 MQT: stat/tasmota_0FDEC8/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota32/tasmota32.bin","RestartReason":"Software reset CPU","Uptime":"0T02:20:19","StartupUTC":"2022-12-12T09:42:40","Sleep":50,"CfgHolder":4617,"BootCount":39,"BCResetTime":"2022-12-11T14:40:16","SaveCount":118}}
13:02:59.799 MQT: stat/tasmota_0FDEC8/STATUS2 = {"StatusFWR":{"Version":"12.2.0.6(tasmota)","BuildDateTime":"2022-12-11T18:58:26","Core":"2_0_5_3","SDK":"v4.4.3","CpuFrequency":160,"Hardware":"ESP32-D0WD-V3 rev.3","CR":"393/699"}}
13:02:59.804 MQT: stat/tasmota_0FDEC8/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":3,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["Molleetjes_Guest",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C80001000680003C5A0A192800000000","00000080","00006000","00004000","00000000"]}}
13:02:59.819 MQT: stat/tasmota_0FDEC8/STATUS4 = {"StatusMEM":{"ProgramSize":1484,"Free":1395,"Heap":134,"StackLowMark":3,"PsrMax":0,"PsrFree":0,"ProgramFlashSize":4096,"FlashSize":4096,"FlashChipId":"16405E","FlashFrequency":40,"FlashMode":"DIO","Features":["00000809","9F9AD7CF","0015A001","B7F7BFCF","05DA9BC0","E0360DC7","400840D2","20200000","D43C482D","000000A1"],"Drivers":"1,2,3,4,5,7,8,9,10,11,12,14,16,17,20,21,24,26,27,29,34,35,38,50,52,59,60,62,63,82,86,87,88","Sensors":"1,2,3,5,6,7,8,9,10,11,12,13,14,15,17,18,19,20,21,22,26,28,31,34,37,39,40,42,43,45,51,52,55,56,58,59,64,66,67,74,85,92,95,98,127"}}
13:02:59.825 MQT: stat/tasmota_0FDEC8/STATUS5 = {"StatusNET":{"Hostname":"tasmota-0FDEC8-7880","IPAddress":"xxxxxxxxx","Gateway":"192.168.178.1","Subnetmask":"255.255.255.0","DNSServer1":"xxxxxx","DNSServer2":"0.0.0.0","Mac":"C4:DE:E2:0F:DE:C8","Ethernet":{"Hostname":"","IPAddress":"0.0.0.0","Gateway":"0.0.0.0","Subnetmask":"0.0.0.0","DNSServer1":"0.0.0.0","DNSServer2":"0.0.0.0","Mac":"00:00:00:00:00:00"},"Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
13:02:59.830 MQT: stat/tasmota_0FDEC8/STATUS6 = {"StatusMQT":{"MqttHost":"xxxxxxx","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_0FDEC8","MqttUser":"DVES_USER","MqttCount":2,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
13:02:59.837 MQT: stat/tasmota_0FDEC8/STATUS7 = {"StatusTIM":{"UTC":"2022-12-12T12:02:59","Local":"2022-12-12T13:02:59","StartDST":"2022-03-27T02:00:00","EndDST":"2022-10-30T03:00:00","Timezone":"+01:00","Sunrise":"08:34","Sunset":"16:52"}}
13:02:59.847 MQT: stat/tasmota_0FDEC8/STATUS10 = {"StatusSNS":{"Time":"2022-12-12T13:02:59"}}
13:02:59.897 MQT: stat/tasmota_0FDEC8/STATUS11 = {"StatusSTS":{"Time":"2022-12-12T13:02:59","Uptime":"0T02:20:19","UptimeSec":8419,"Heap":127,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":20,"MqttCount":2,"Berry":{"HeapUsed":3,"Objects":46},"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Molleetjes_Guest","BSSId":"9A:9A:4A:4C:3D:EE","Channel":7,"Mode":"11n","RSSI":100,"Signal":-50,"LinkCount":1,"Downtime":"0T00:00:03"}}}

[anixi]

backlog module: 13:06:37.690 CMD: Backlog Module 13:06:37.692 SRC: WebConsole from xxxxxxx 13:06:37.694 CMD: Grp 0, Cmd 'BACKLOG', Idx 1, Len 6, Pld -99, Data 'Module' 13:06:37.721 SRC: Backlog 13:06:37.724 CMD: Grp 0, Cmd 'MODULE', Idx 1, Len 0, Pld -99, Data '' 13:06:37.734 MQT: stat/tasmota_0FDEC8/RESULT = {"Module":{"0":"Sonoff THR316D"}}

[anixi]

Template: Grp 0, Cmd 'TEMPLATE', Idx 1, Len 0, Pld -99, Data '' 13:09:31.481 MQT: stat/tasmota_0FDEC8/RESULT = {"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}

[anixi]

Gpio all: rp 0, Cmd 'GPIO', Idx 1, Len 3, Pld 255, Data 'all' 13:14:18.746 MQT: stat/tasmota_0FDEC8/RESULT = {"GPIO0":{"32":"Button1"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"0":"None"},"GPIO4":{"225":"Relay2"},"GPIO5":{"9280":"TM1621 DAT"},"GPIO6":{"0":"None"},"GPIO7":{"0":"None"},"GPIO8":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO11":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"321":"Led_i2"},"GPIO14":{"0":"None"},"GPIO15":{"576":"LedLink_i"},"GPIO16":{"320":"Led_i1"},"GPIO17":{"9184":"TM1621 CS"},"GPIO18":{"9216":"TM1621 WR"},"GPIO19":{"0":"None"},"GPIO20":{"0":"None"},"GPIO21":{"224":"Relay1"},"GPIO22":{"0":"None"},"GPIO23":{"9248":"TM1621 RD"},"GPIO24":{"0":"None"},"GPIO25":{"1312":"DS18x201"},"GPIO26":{"0":"None"},"GPIO27":{"3840":"Output Hi"},"GPIO32":{"0":"None"},"GPIO33":{"0":"None"},"GPIO34":{"0":"None"},"GPIO35":{"0":"None"},"GPIO36":{"0":"None"},"GPIO37":{"0":"None"},"GPIO38":{"0":"None"},"GPIO39":{"0":"None"}}

[anixi]

Pictures to be shared later, thanks so much so far

[sfromis]

What I meant was one command (using Backlog combines multiple commands into one), you did not need splitting it into 3 commands. That's ok anyway.

I can see that your settings are correct with Module 0, the correct template, and with "GPIO25":{"1312":"DS18x201"} the sensor is also configured if it is really a DS18B20 with a cylindrical steel tip. Another sensor probe is the THS01 with a small black plastic case at the end, with slits for air access.

[anixi]

It is a DS18B20 connected via a Sonoff AL560 - Sensor extentionl - 5m and Sonoff AL010 - 2.5mm Audio Jack to RJ9 Adapter

[arendst]

What happens if you remove the 5m extension and connect the DS18B20 directly to the AL010?

[anixi]

as addition if I select another probe at GPIO25, the main screen shows Temperature/humidity but with output null

will remove the extension after office hours

[sfromis]

Verified that If I connect the Sonoff DS18B20 with RJ9 plug to a THR316D set up with the autoconf for that, I'm seeing a temperature in the JSON and on the Tasmota front page, as expected. Using a recent dev build.

[anixi]

I just verified that it does work without the 5m extension ;-( This is very unfortunate as this did work with the old TH16,,,, Would you expect that it would work with the newer DS18B20 with RJ9 and RJ9 extention?

[sfromis]

Don't know, but if not you may have a warranty claim. Maybe adding a pullup resistor would help. One difference to the TH16 is that the ESP8266 driver enables internal pullup, on ESP32 I've always had to add external pullup for DS18B20, but I'd expect (at least hope) that Sonoff already does this on THR16D. It may still help with further pullup, depending on how much is lost in the extension cable.

[anixi]

ok thanks again for all the help. Meanwhile ordered the new DS18B20 (RJ9) and 5 M extension (RJ9). WIll let you know th e outcome!

[anixi]

Just to confirm that the new DS18B20 and the 5M RJ9 extention work togehter, problems gone. THnaks again for help and further explanation!

[chu11u]

ok thanks again for all the help. Meanwhile ordered the new DS18B20 (RJ9) and 5 M extension (RJ9). WIll let you know th e outcome!

Hi @anixi , Where did you ordered the extention from? having similar problem here...

[anixi]

Hi @chu11u, not sure where you live but I ordered it at www.tinytronics.nl,

[chu11u]

Hi @chu11u, not sure where you live but I ordered it at www.tinytronics.nl,

If you can, just send a link to it. ill work my way from there 10x!

[anixi]

https://www.tinytronics.nl/shop/nl/kabels-en-connectoren/kabels-en-adapters/overige/sonoff-rl560-sensor-verlengkabel-5m-voor-th-elite-th-origin

[chu11u]

Thanks. It held all the leads I needed to so I can find and order. I hope it will solve my problem also... Bought 2 standart sensors (with 3.5mm jack) and none works with the THR316...Regards,Naor ElkayamSent from my iPhoneOn Dec 27, 2022, at 12:08 PM, anixi @.***> wrote: https://www.tinytronics.nl/shop/nl/kabels-en-connectoren/kabels-en-adapters/overige/sonoff-rl560-sensor-verlengkabel-5m-voor-th-elite-th-origin

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[chu11u]

@anixi , @arendst , and all of you guys in this post that helps. It worked!! the RL560 sensor really did the work! after I almost gave up! (altho it is shorter than the one came with the device, it was still usable) . I use it to measure the water temperature in my water heater and now I can tell what 's the water temp inside it.

You guys are such a wonderful community! thanks!!!!!

[jfrancais]

Reserecting this thread as I'm still struggling to get the tasmota sonoff thr316d ds18b20. Running 12.3.1 and autoconfigured to "Sonoff THR316D with DS18x20". Comes back with no display and does not report sensor data for the ds18b20. When I had a THS01 it was reporting fine with the proper display. (that sensor is now gone so I no longer have it for testing). I'm on my second ds18b20 as I thought I may have a bad ds18b20 but the new one doesn't work either. Can someone assist troubleshooting here?

[sfromis]

I'm having a Sonoff THR316D with DS18B20 connected and working, also using the auto-configuration "Sonoff THR316D with DS18x20", and experienced no trouble making it work. When booting with the sensor probe plugged in, with Weblog 3 for details, I see this in the console: DSB: Sensors found 1 (or 0 if not having it connected)

Maybe verify that you actually have the configuration in place. Details from the command Backlog Module; Template; Gpio all are a good way of checking.

[jfrancais]

I found this in the log when booted up: 00:00:00.336 DSB: Sensors found 0

This is the output of the Backlog Module; Template; Gpio all 15:02:37.893 MQT: tasmota_BAB7C0/stat/RESULT = {"Module":{"0":"Sonoff THR316D"}} 15:02:38.120 MQT: tasmota_BAB7C0/stat/RESULT = {"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} 15:02:38.375 MQT: tasmota_BAB7C0/stat/RESULT = {"GPIO0":{"32":"Button1"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"0":"None"},"GPIO4":{"225":"Relay2"},"GPIO5":{"9280":"TM1621 DAT"},"GPIO6":{"0":"None"},"GPIO7":{"0":"None"},"GPIO8":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO11":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"321":"Led_i2"},"GPIO14":{"0":"None"},"GPIO15":{"576":"LedLink_i"},"GPIO16":{"320":"Led_i1"},"GPIO17":{"9184":"TM1621 CS"},"GPIO18":{"9216":"TM1621 WR"},"GPIO19":{"0":"None"},"GPIO20":{"0":"None"},"GPIO21":{"224":"Relay1"},"GPIO22":{"0":"None"},"GPIO23":{"9248":"TM1621 RD"},"GPIO24":{"0":"None"},"GPIO25":{"1312":"DS18x201"},"GPIO26":{"0":"None"},"GPIO27":{"3840":"Output Hi"},"GPIO32":{"0":"None"},"GPIO33":{"0":"None"},"GPIO34":{"0":"None"},"GPIO35":{"0":"None"},"GPIO36":{"0":"None"},"GPIO37":{"0":"None"},"GPIO38":{"0":"None"},"GPIO39":{"0":"None"}}

[sfromis]

Your config appears to be ok, but DSB: Sensors found 0 looks like the sensor probe not getting good connection. Could be an issue of dirty contacts, or whatever outside the control of Tasmota.

[jfrancais]

Would the THS01 have a different pinout? It was working fine. I ordered a second DS18B20 sensor to try and have the same problem with it. Funny the THS01 works and the DS18B20 doesn't

[jfrancais]

I can also confirm the voltage pins are outputting proper as measured with a voltmeter

[barbudor]

Is that a probe you made yourself from the parts or purchased as from Sonoff?

Do you have any way to test the probe with a dev board or an Arduino?

[jfrancais]

Both DS18B20 are Sonoff branded RJ9 versions. No modifications made, as is. I highly doubts I got 2 bad sensors. Insure how I would test the sensor it self.

I can confirm the power pins from the THR316D but I'm unsure how I can test the data pins, or even determine which one is the correct pinout for the DS18B20 and THS01

[jfrancais]

OK, I have to apologize, I now have it working as expected. The data pin inside the THR316D somehow was pushed low making poor contact. I used a paperclip to tension the pinouts a bit higher and power cycled and I'm now getting full reporting and proper display. Thanks for the assistance one the debugging, I wouldn't have gotten here with out that.

[spaem66]

Hello, I just bought a Sonoff Pow Elite 16A (POWR316D). I opened the device and the chip onboard is an ESP32 DOWD V3. Saved the origjnal firmware and tried to flash: tasmota32.bin, tasmota32.bluetooth, tasmota32.factory, even tasmota32s3; also tried to flash with several tools, like esptool, tasmota web installer, tasmotizer but no way, the device is able to boot normally just with the original firmware. Of course, all the times I used the usual USB to UART flashing device connected to the Sonoff. The flashing procedure goes on without problems, first it erases the flash and then flashes the new firmware and there are no errors but, when I connect the power, the device doesn't start. I had a look to this thread, seeing that several used the same bin, but exactly which one? I tried the latest, the 12.3.1, the 12.2.0, the 12.0.2 but nothing to do. Any suggestions?

[barbudor]

Yes, read the doc On ESP32, the '.bin.' are for OTA, the '.factory.bin' are for serial flashing Preferably use the Tasmota web installer at https://tasmta.github.io/install that take cares of the details

[spaem66]

Already tried. On web installer I have ESP32, ESP32-S2, S3 and so on and for each one you have a lot of choices. When I start web installer I have to pick one, but exactly which one? I also tried a factory bin via esptool.py but it's the same

[barbudor]

On web installer, you just have to pickup tasmota The installer will identify the right processor by itself

[spaem66]

The web installer identifies it like a "tasmota 32 bluetooth". Resetting is ok, but again, when I connect it to the power (220V), nothing happens.

[barbudor]

Did you configured the Wifi credentials after flashing using the Web installer ? Before going to the complicated stuff, you may just want to try simply "tasmota" (no bluetooth)

[spaem66]

no, because the procedure simply ends

[barbudor]

So your flashing isn't correct Once flashing is complete, the web installer should offer you to setup the wifi credentiels and once that's done, to open the web UI of the device Probably a poor flasher with not enough power

[spaem66]

Don't know really: I flashed more than 12 devices of all types (Sonoff) and I had no problems

[spaem66]

Web installer ended the setup but the only thing I can do after is "download the logs" or "reset" (I did several installations with web installer and it was always the same).

[spaem66]

any other suggestions? Thanks in adv

[sfromis]

Your experience of having had no problems flashing other devices with your USB/serial adapter cannot be conclusive about having enough power, as some devices need more power than others, especially when using ESP32. Not saying "this is the explanation", more to clarify things, and still a potential risk factor.

Still, it is hard to "see" what exact steps you do, as the Tasmota Web Installer just cannot identify it like a "tasmota 32 bluetooth". When using this installer, you should make no selection at all before clicking "connect", letting it default to "Tasmota (english)" and "All".

[spaem66]

Thanks a lot, just did as you described, also cleared browser cache (in any case ..) and the Tasmota web installer selected the defaults but nothing changed after. Is there any "recommended" USB to serial unit to be used? I bought one from Amazon because of the many references; it is based on CH340G and supports 3.3 or 5V devices (in this case, I'm using 3.3V)

[sfromis]

Yes, docs mention a recommended adapter..... https://tasmota.github.io/docs/Getting-Started/#needed-hardware

You should always use 3.3V, unless (in unusual cases) having specific knowledge about 5V being needed instead. Using 5V with a device designed for 3.3V may cause hardware damage.

[spaem66]

I confirm: 3.3V and the adapter has a voltage regulator of the type just described above. The device also supports 5V but it is (obviously) not this case.

[sfromis]

You specifically said "in this case, I'm using 5V". Just having done that once may have fried something.

[spaem66]

Sorry, it was a mistake: 3.3V

[spaem66]

Anyway, the docs say that when using Tasmota Web Installer, after installation you can configure wifi connection settings through the GUI, but I never did that after flashing. Just connected to the tasmota internal net coming up after installation in order to complete all the needed settings.