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)

[mariusrugan]

hi @idea-thinker,

you need to use tasmota32, nothing else, also erase flash always, i also used the web installer, and also observed on serial console when powered at 3.3V the permanent "reboot". I have hook it up to 220V after, WITHOUT serial connection. Wifi AP from Tasmota came up and i was able to configure wifi.

I have 2 devices, the 20A model, both behaved the same.

I didn't experience the web flasher wifi configuration as with other devices - sonoff basic for example.

[sfromis]

Using the base tasmota32 means just selecting Tasmota in your language, without looking for anything ESP32, as the web installer will detect chip architecture, and select the appropriate binary. Thus do not go for bluetooth/lvgl/whatever else. The rudimentary wifi config is selecting which AP you connect to, which you can do by connecting to the AP broadcast by Tasmota.

[ejohb]

hi @idea-thinker,

you need to use tasmota32, nothing else, also erase flash always, i also used the web installer, and also observed on serial console when powered at 3.3V the permanent "reboot". I have hook it up to 220V after, WITHOUT serial connection. Wifi AP from Tasmota came up and i was able to configure wifi.

I have 2 devices, the 20A model, both behaved the same.

I didn't experience the web flasher wifi configuration as with other devices - sonoff basic for example.

I've flashed 5 x 16a and 2 x 20a recently and observed the same behaviour on all of them. You need to power by AC for it to start working as expect. I will also reemphasize the other thing you say: I believe you must not power by both serial and AC at the same time or it will kill you and everyone around.

[idea-thinker]

I have gotten my THR316D connected. It was my problem of not connecting the device to AC power after programming It. When connected to my USB to Serial the WIFI would not come up. It is now on my network and I can connect to it but it does not display the Temperature or Humidity. It only displays the ESP32 Temperature. Any guidance would be helpful.

I used the web installer to install the Tasmota software. I used the Tasmota (English) option and allowed the installer to detect the processor type.

I used the template below: {"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}

I have the temperature sensor (ths01) plugged into the THR316D. After I copied the template to the device I did check the box to activate it.

Thanks; idea-thinker

[arendst]

https://github.com/arendst/Tasmota/discussions/16304#discussioncomment-3457133

[idea-thinker]

arendst; That fixed my issue. Thanks so much for your help.

I also want to thank all those who responded to my questions about getting my THR316D up and running.

Thanks; idea-thinker

[pluk77]

@Nuffic / @idea-thinker , do you know if one could add two DS18B20 sensors to the THR316D (instead of 1 temp and 1 humidity) and what the RJ11 pin layout if one would use an off the shelf DS18B20 sensor (not one bought from sonoff)

Seeing there are two lines on the LCD, it would be nice if one could use two temp sensors to show the temp in my hot water cylinder and at the solar collector.

[idea-thinker]

Marcel; I think you can only have one sensor on the RJ-11 Jack.

Thanks; ide-thinker

On Thu, Aug 25, 2022 at 8:41 AM Marcel Berteler @.***> wrote:

@Nuffic https://github.com/Nuffic / @idea-thinker https://github.com/idea-thinker , do you know if one could add two DS18B20 sensors to the THR316D (instead of 1 temp and 1 humidity) and what the RJ11 pin layout if one would use an off the shelf DS18B20 sensor (not one bought from sonoff)

Seeing there are two lines on the LCD, it would be nice if one could use two temp sensors to show the temp in my hot water cylinder and at the solar collector.

— Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/15856#issuecomment-1227277684, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIRRRVU5WOTJOSEDTD67AG3V25ZW7ANCNFSM5ZVP735A . You are receiving this because you were mentioned.Message ID: @.***>

[pluk77]

@idea-thinker I now read that it should be possible in theory to connect multiple sensors to the ESP8266, but I have not received my unit yet so can not confirm if it will work: https://tasmota.github.io/docs/DS18x20/

[pluk77]

As expected, GPIO26 would be the second wire on the RJ11 connector if they had populated R16 and R25. Currently the output is floating and cannot be used.

Pity. Would have been a great opportunity to support I2C. So without a hack it's a single wire interface for either DS18x20 or DHT derivatives.

@arendst Can you share the pin layout of the RJ11 so one can connect an off the shelf DS18B20?

[gr10001]

i have 2 DS18B20 connected on the rj11 on THR316D on GPIO25 and it works w/o any problems, but i think i only get the latest one to show on the display. It would be great to get them alternating or be able to influence what is being shown

[arendst]

It would be great to get them alternating or be able to influence what is being shown

How do you plan to distinguish between the shown temperatures. The LCD hardware has limited capabilities. Any input is welcome.

[arendst]

@pluk77

Yellow = Gnd Green = NC Red = GPIO25 data Black = GPIO27 providing 3V3

[barbudor]

I don't know what level of control is available on the Lcd but supporting it with the Display commands would give some flexibility. Basic mapping of letters on 7-segment is possible so with rules and timer it should be possible to alternate displaying labels as "t1" before the 1st temperature, "t2" before the next.

[arendst]

Hardly possible. See here what elements are available on the crippled LCD: https://github.com/arendst/Tasmota/issues/15856#issuecomment-1173848181

[sfromis]

Since DS18B20 is temperature-only, the bottom display row could have the sensor number, instead of the unavailable %RH. Or maybe ignore that the bottom row is supposed to be RH, and have both temperatures on the two rows, when only 2. Or are there limitations to what you can do outside of what elements are available?

[arendst]

Other than limited elements there are no limitations.

I guess there needs to be some kind of display driver so users can do their thing. What is the current display driver philosophy?

[sfromis]

From my perspective, it would be nice to have it working in Berry, the digits, decimal point and indicators to the right could be reasonably simple to deal with. In principle, maybe also element-level control for people wanting to be "creative"....

[arendst]

Thought so. Then I leave it to a Berry magician to provide the driver.

[arendst]

@gr10001 as a workaround to show alternating (or more) DS18B20 sensors you can execute command GlobalTemp2 2 to select the second DS18B20 to be shown on the diplay. To see the first DS18B20 just execute GlobalTemp2 1 and after some seconds the first will be shown. Equal for any additional DS18B20 in the string.

A rule could do this automatically.

[arendst]

I'll add some code to use the lower part to for a second sensor. When more are attached I'll add it's index number on the second line (as suggested by sfromis)

Nice exercise.....

[gr10001]

@arendst thanks for the suggestion with GlobalTemp2. I'll add it to my Berry script

[pluk77]

i have 2 DS18B20 connected on the rj11 on THR316D on GPIO25 and it works w/o any problems, but i think i only get the latest one to show on the display. It would be great to get them alternating or be able to influence what is being shown

Did you have to add an external pull-up resistor?

[gr10001]

no pull up resistor. I actually have 2 THR316D and they are bot running on similar setup (2 DS18B20, no pull up)

[sfromis]

I'd more or less guess that the Sonoff device already has a pullup on the board.

[Longlife4ever]

I have a THR320D flashed with Tasmota 12.1.1. Relays working fine but the temp/humidity sensor is not working. The THR320D came with a Sensor with marking AM2301 on the case but inside is a 8R08A1 and a HTU21. Is it possible to get it working? looks to me like the 8R08A1 is for translating "onewire" to I2C. The board has another header with I2C. This is connected directly to the HTU21. Unfortunately, the THR320D only has one GPIO running on the RJ connector.

EDIT: Got it working

Select the SI7021 at GPIO 25

[barbudor]

This should be what you are looking for https://tasmota.github.io/docs/AM2301/

[Longlife4ever]

what a waste of resources or just to confuse others. Dont know why they did not use all 4 pins of the rj11 connector and made it possible to use I2C. Intead they used a nother MCU to use I2C on 1wire.

[barbudor]

This is inherited from old Sonoff TH where the connector was a jack with only 3 connectors It may be also that this single wire protocol is more resilient on long lines than I2C that is designed for short on-board connections

[Longlife4ever]

But there is a 4Pin rj11 and a 4Pin 2,5mm "Klinke" connector. Just a small trace from a GPIO to the pin with the green wire on the PCB. You could still have used the 1wire, but the possibility for additional sensors and peripherals would be possible. However :D

But is the GPIO27 realy for powering the Sensor with 3,3V? Is there a way to get real 3,3V to this unused Pin? Then GPIO27 and GPIO25 could made it possible to use I2C at the rj11 connector.

Because of the use of external sensors and connectors with touchable metal, there must be a galvanic isolation isn't it? Frontside of the PCB: Frontside in detail:

Backside of the PCB: Back in detail

[barbudor]

On device without power measurment, the ESP is normally isolated from AC. This is why you can safely connect an external sensor wihtout isolation. Just the same ase using a mini-D1/Node MCU with a USB wall adapter.

If Sonoff decided to use a GPIO to power the sensor, they probably faced the problem with low quality sensors that need to be reset from time to time. Something that you can do on tasmota is you configure the pin as a Relay and use a rule.

You are free to take you own responsibility to hack the device to connect a direct 3V3 and use both GPIO for I2C sensors (don't forget that I2C is not meant for long connections). If you do it properly this is safe.

But don't hack the POW Elite as all power measurment device are not isolated from AC and NO connection should be done to the outside.

[sfromis]

The unused RJ11 pin is connected to the test point "RX1" nearby, just verified that on my device. Seems that "something" is going on there; not checked further details...

[Longlife4ever]

@pluk77

Yellow = Gnd Green = NC Red = GPIO25 data Black = GPIO27 providing 3V3

This Pinout is wrong!

Assuming the rj11 on the picture is physically oriented correctly an you plug it into the THR320D the pin assignment is as follows: Yellow = 3V3 GPIO27 providing 3V3 Green = GPIO25 Red = GPIO26 (NC) Black = GND

there is nothing fancy to do to get another GPIO unlocked. I'll tell you how to do it tomorrow. Need to edit some pictures to show you how.

EDIT: The Connector is a RJ10 typ like on older telephone handset. The RJ11 is to big.

[sfromis]

Short version, change the template for the pin you want to change. Directly there, or to "User" if you want to have it on "Configure Module".

[pluk77]

@Longlife4ever Thank you. I have send a PR for the docs to be updated.

[Longlife4ever]

@Longlife4ever Thank you. I have send a PR for the docs to be updated. you're welcome

[Longlife4ever]

I think the second GPIO on the rj10 connector is working. Need a seperate rj10 connector to prove it.

Long story short, the only thing that is missing are two resistors. But if you're happy with a simlpe GPIO whitch is directly connected to the ESP32 a littl soldering tin dot is everything thats between you and a second GPIO at the RJ10.

EDIT: So here is how I managed to get the second GPIO working on SonOff THR320D. So it's possile to use I2C and other seriel connections on this DIN rail mount device. The Template should be changed like sfromis said.

The following Template ist only for the modded Version of SonOff THR320D!

{"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,1,3840,0,0,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":1}

Second GPIO on SonOff THR320D.pdf

[arendst]

As my hands and eyes are just not good enough for handling SMD I managed to short R16 and come up with this:

Even the display succesfully shows my connected HTU21 temp and humidity.

So now it's time I invent user display update functionality....

[Longlife4ever]

So now it's time I invent user display update functionality....

That would be awesome.

Is it possible, that the Display of the THR320D and POWR20D are the same? The Units of the THR320D [°C and %RH] are on top row. The Units of the POWR20D [V;A; W;kWh]are in middle row and bottom row. It would be nice to have control over the units as well.

THR320D

POWR20D

[arendst]

Yes. both displays are the same and are currently supported by the same driver.

I won't plan full user control (leaving that up to someone wanting to write a display driver for the crippled 2 x 4 x 7-segemnt display lacking decimals points in all except the character before last). In my opinion the only task of the display is showing values from attached sensors only. So if a SCD30 is connected it provides teleperiod data like:

{"Time":"2022-09-07T16:19:19","SCD30":{"CarbonDioxide":566,"eCO2":597,"Temperature":30.0,"Humidity":44.7,"DewPoint":16.6},"TempUnit":"C"}

So I plan to add a command for a user to select which value he/she wants to see on the top line and which value on the bottom line. As with the global temp/hum/pressure the users needs to provide the index of the value like in the above case CarbonDioxide is 1, eCO2 is 2 etc. he wants to see.

[Longlife4ever]

So it would be possible to connect a PZEM-004 for example and display the values with the right units on the LCD?

[arendst]

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

[Longlife4ever]

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

challenge accepted 👍

[madrose]

I just tried to flash the latest tasmota on 2 different POWR316D units and got the same errors and no mater what I try i keep getting to the same point over and over.

Connecting.... Detecting chip type... Unsupported detection protocol, switching and trying again... Connecting... Detecting chip type... ESP32 Connecting...

Chip Info:

• Chip Family: ESP32
• Chip Model: ESP32-D0WD-V3 (revision 3)
• Number of Cores: 2
• Max CPU Frequency: 240MHz
• Has Bluetooth: YES
• Has Embedded Flash: NO
• Has Factory-Calibrated ADC: YES
• MAC Address: C4:DE:E2:0F:F5:2C Uploading stub... Running stub... Stub running... Changing baud rate to 460800 Changed.
• Flash Size: 4MB
• Flash Mode: dout
• Flash Frequency: 40MHz

Writing at 0x0016d204... (100 %)Wrote 1448704 bytes (1011944 compressed) at 0x00010000 in 24.1 seconds (effective 480.2 kbit/s)... Hash of data verified.

Leaving... Hard Resetting... Hard resetting via RTS pin... Done! Flashing is complete!

After flashing trying to reset and check:

Using 'COM10' as serial port. Showing logs: [21:46:37] [21:46:37]00:00:00.003 HDW: ESP32-D0WD-V3 [21:46:37]00:00:00.042 UFS: FlashFS mounted with 48 kB free [21:46:37]00:00:00.086 CFG: Loaded from File, Count 2 [21:46:37]00:00:00.101 QPC: Count 2 [21:46:38]00:00:00.203 BRY: Berry initialized, RAM used=3735 bytes [21:46:38]00:00:00.229 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) [21:46:38]00:00:00.489 WIF: WifiManager active for 3 minutes [21:46:38]ets Jul 29 2019 12:21:46 [21:46:38] [21:46:38]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) [21:46:38]configsip: 0, SPIWP:0xee [21:46:38]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 [21:46:38]mode:DOUT, clock div:2 [21:46:38]load:0x3fff0018,len:4 [21:46:38]load:0x3fff001c,len:1044 [21:46:38]load:0x40078000,len:8896 [21:46:38]load:0x40080400,len:5828 [21:46:38]entry 0x400806ac [21:46:39] [21:46:39]00:00:00.003 HDW: ESP32-D0WD-V3 [21:46:39]00:00:00.042 UFS: FlashFS mounted with 48 kB free [21:46:39]00:00:00.086 CFG: Loaded from File, Count 2 [21:46:39]00:00:00.101 QPC: Count 3 [21:46:39]00:00:00.203 BRY: Berry initialized, RAM used=3735 bytes [21:46:39]00:00:00.229 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) [21:46:39]00:00:00.489 WIF: WifiManager active for 3 minutes [21:46:39]ets Jul 29 2019 12:21:46 [21:46:39] [21:46:39]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) [21:46:39]configsip: 0, SPIWP:0xee [21:46:39]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 [21:46:39]mode:DOUT, clock div:2 [21:46:39]load:0x3fff0018,len:4 [21:46:39]load:0x3fff001c,len:1044 [21:46:39]load:0x40078000,len:8896 [21:46:39]load:0x40080400,len:5828 [21:46:39]entry 0x400806ac [21:46:40]

[mariusrugan]

@madrose disconnect serial and plug to AC; issue has been addressed above in the thread.

[madrose]

@mariusrugan that work. It was a very long thread and did not reach that.

thanks for your help

[mariusrugan]

maybe @arendst can comment if there is a wiki of devices i can offer to transcribe issues that i had - so we stop spamming the github issue :) i know for sonoff basic there was such thing somewhere ...

[sfromis]

If you mean to add tips for people flashing Tasmota onto a device, the device page in the Templates repository has room for such, and there is an edit button on the pages.

[arendst]

Latest dev release adds two new commands:

DspSpeed 2..127 = Display rotation speed in seconds if more than one value is requested DspLine<1|2> <index>,<unit>,<index>,<unit>,... = Display specific JSON value and rotate between them unit 0 = None 1 = Temperature (Line 1 only) 2 = %RH (Line 2 only) 3 = Both V (Line 1 only) / A (Line 2 only) 4 = Both kWh (Line 1 only) / W (Line 2 only) DspLine1 0 and DspLine2 0 = Default of temperature/humidity

  index:  1        2                   3          4                  5               6
Example: "SCD30":{"CarbonDioxide":746,"eCO2":727,"Temperature":30.6,"Humidity":43.6,"DewPoint":16.8}

DspLine1 4,1,3,0 = Temperature and eCO2 DspLine2 2,0,5,2 = CarbonDioxide and humidity

Both commands work on POWR3xxD and THR3xxD

[bastians]

Hi together, I am new here and in the Tasmota area. I am trying to flash a TH320D with Tasmota. Latest, I used the web client for it and it seemed to be successful, but when I plug the device to the 230V power, the Tasmota wifi doesn't show up. I connected the device again with the FTDI adapter to check the logs and this is what it look like:

00:00:00.492 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (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 00:00:00.049 UFS: FlashFS mounted with 312 kB free 00:00:00.064 CFG: Use defaults 00:00:00.297 QPC: Reset 00:00:00.425 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.463 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.906 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (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.002-212/50 HDW: ESP32-D0WD-V3 00:00:00.069-210/49 UFS: FlashFS mounted with 308 kB free 00:00:00.134 CFG: Loaded from File, Count 2 00:00:00.150 QPC: Count 1 00:00:00.289 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.322 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.523 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (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 00:00:00.069 UFS: FlashFS mounted with 308 kB free 00:00:00.134 CFG: Loaded from File, Count 2 00:00:00.149 QPC: Count 2 00:00:00.288 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.321 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.522 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (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 00:00:00.069 UFS: FlashFS mounted with 308 kB free 00:00:00.134 CFG: Loaded from File, Count 2 00:00:00.149 QPC: Count 3 00:00:00.288 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.321 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.522 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (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 00:00:00.069 UFS: FlashFS mounted with 308 kB free 00:00:00.134 CFG: Loaded from File, Count 2 00:00:00.149 QPC: Count 4 00:00:00.288 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.321 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.522 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (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 00:00:00.069 UFS: FlashFS mounted with 308 kB free 00:00:00.134 CFG: Loaded from File, Count 2 00:00:00.149 QPC: Count 5 00:00:00.288 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.321 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.522 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (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 00:00:00.069 UFS: FlashFS mounted with 308 kB free 00:00:00.134 CFG: Loaded from File, Count 2 00:00:00.149 QPC: Count 6 00:00:00.288 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.321 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.522 WIF: WifiManager active for 3 minutes ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (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.070-210/49 UFS: FlashFS mounted with 308 kB free 00:00:00.134 CFG: Loaded from File, Count 2 ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x13 (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.002 HDW: ESP32-D0WD-V3 00:00:00.067 UFS: FlashFS mounted with 312 kB free 00:00:00.077 CFG: Loaded from NVS, Count 2 00:00:00.081 FRC: Some settings have been reset (2) 00:00:00.201 BRY: Berry initialized, RAM used=3735 bytes 00:00:00.234 Project tasmota - Tasmota Version 12.1.1(tasmota)-2_0_4_1(2022-08-25T11:34:17) 00:00:00.506 WIF: WifiManager active for 3 minutes ...

I cropped it as it seems that the same log part is repeating. Is this a boot loop? The display of the device also shows nothing when I plug it.

I am using a FT232RL USB to serial adapter for flashing. I am using for jumpers to connect RX to TX TX to RX VDC to 3V3 GND to GND

Before the web client, I also used esphomeflasher for flashing. That also seemed to be successful but same issue here.

Any ideas what could be the problem? Is my device broken?