Shelly Plus Mini devices

[Th0maz]

Hey,
is anybody planing to investigate the new Shelly Plus Mini devices?
I bought a Shelly Plus PM Mini last week and was wondering, if they could be flashed with Tasmota.
Calibration might be a thing with the PM version.
Thanks
Thomas

EDIT by Tasmota crew: Please follow this exactly to convert the device successfully!!

[sfromis]

Now there are autoconf setups for all 3.

[Th0maz]

Seems to be working good 😎👍

[Th0maz]

And I'm not sure if you need to set setoption21 1 to use energy monitoring when power is off (since we have no power/relay here).
I set that during testing, so I don't really know if it's necessary.

[filipq]

Thank you all for your help. All working fine now. After updating to the latest dev release and changing GPIO7 to BL0942 RX 2 everything working as expected.

I did not set setoption21 1.

[Th0maz]

I did not set setoption21 1.

I double-checked with my device.
When setoption21 is set to 0, I don't see any energy monitoring data.

[arendst]

As designed. The shelly plus pm mini needs so21 1 to report anything. Usually a relay is present which is the basis for reporting. I think the best solution is updating auto config for the shelly plus pm mini with so21 1 (@Jason2866 )

[Jason2866]

added so21 1 to Autoconfig for the pmmini

[Jason2866]

Final updated Shelly converter online which supports the new C3 Shelly minis.
The updated Shelly to Tasmota convert process does take care of the new more secured Shelly firmware.
With the new Shelly firmware there was a risk to end in a bricked device with the former version.
This problem is fixed. Currently we have had 100% successful converts in our tests.
Let’s see how long we win the cat and mice game!

[ghostseven]

I am unfortunately stuck on 12.5.0 after flashing the linked http://ota.tasmota.com/tasmota32/shelly/mgos32-to-tasmota32-PlusPMMini.zip I cannot get it to update. Any tips or advice?

If it helps I get Upload Failed

Program flash size is larger than real flash size

When trying to manually upload (not OTA)

I have just tried manually flashing 12.5.0 and that works fine, I just can't go above that.

EDIT: My fault I see I have bricked it, no worries I need to follow the guide more clearly.

[Jason2866]

The Autoconfig routine does delete the Shelly Index.html.gz file and uploads the new bootloader and PartitionWizard.
If uploading is not working (either by Autoconfig or manually) only serial flashing is the way

[ghostseven]

IT LIVES! Honestly thank you for this, absolutely fantastic assistance and apologies for my stupidity. Removing the files that had not been cleaned up and uploading the tapp allowed me to continue the process and all is good.

[ghostseven]

Edit: Works fine! I need to do setoption21 1

Ah I spoke too soon, I think its kind of soft bricked, the power sensing does not work even though the config is right and its on 13.1.0.3

[Jason2866]

Not something that the convert process can be the reason.

[ghostseven]

It was me not doing setoption21 1 as I am a dunce (puts on big hat with D and sits in the corner)!

[xxLexanixx]

I have the same problem with my 1PM Mini
What do I have to change here so that the energy values are displayed?

[Th0maz]

Probably update to a newer version to set GPIO7 properly.
See this comment

[xxLexanixx]

What is the correct firmware?! I don't understand which one I need

[sfromis]

Standard Tasmota build for C3 current version 13.2 should be fine.
Make sure that the template is not just stored, but also enabled.

[falcomenz]

Hi!
I have two Shelly Plus 1PM Minis. The first one got flashed successfully with mgos32-to-tasmota32 (https://github.com/tasmota/mgos32-to-tasmota32), but the second one got stuck, so i want to flash it with the serial connection. I tried flashing all kinds of different tasmota32 versions. tasmota32c3.bin, tasmota32c3-safeboot.bin and tasmota32c3.factory.bin but i always get the following error in the console:

ESP-ROM:esp32c3-api1-20210207
Build:Feb 7 2021
rst:0x10 (RTCWDT_RTC_RST),boot:0xd (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3c0a0020,len:0xf940
load:0x3fc8c600,len:0x6b0
load:0x42000020,len:0x937f8
load:0x3fc8ccb0,len:0x21a8
load:0x40380000,len:0xc514
load:0x50000000,len:0x18
SHA-256 comparison failed:
Calculated: 08fe1a6a30f32ab6a45ccadb3aa9b1cb3cfd91207eb5ed66a3ca4afa5947031d
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x40381d98

What di i need to flash over serial to get my Shelly working again?
Thank you :)

[sfromis]

I'm not seeing any error there. Only an informational message about SHA-256 mismatch, but this is not important as it is not encrypted firmware.

Using the Tasmota web installer is much recommended for flashing, as it automatically selects a workable binary and strategy. You told no details of what you did there. In your case, that should be tasmota32c3.factory.bin at offset 0, with the two others being guaranteed failures. Equally bad to not flash at the correct offset for the type of flashing.

[falcomenz]

letting the web installer do its thing and just selecting Tasmota (english) did the trick. Thank you!