New Shelly Pro Series (i.e. 2/2PM)

[Mark-Muc]

Hello .. is it possible / planed to suppoert these devices??
Shelly Pro Series (i.e. 2/2PM)
In the version "[12.1.1.4] Support for Shelly Plus 2PM using template"
is integrated ..
Thx for any answer!!
Mark

[barbudor]

What answer ?
You already found that it is supported with the given template

[Mark-Muc]

I am asking for Shelly PRO series... like
https://www.shelly-smarthome-shop.de/smarte-relais/pro-line/11153/shelly-pro-2

In version 12.1.1.4 support for Shelly PLUS was built in ... like
https://www.shelly-smarthome-shop.de/smarte-relais/plus-serie/11237/shelly-shelly-plus-2pm?number=Shelly-ShellyPlus2PM

[barbudor]

It needs someone to have its hand on the unit and open it to check what is inside
Can you do it ?
Most likely the Pro is just a Plus in a DIN box

[Mark-Muc]

i ordered one today .. will arrive these days .. I'll try to open it and make some pic's!!
But I don't think so, .. it is complete different layout AND the PRO Series also have LAN (RJ45) & WiFI

[sfromis]

ESPHome already has a setup for Shelly Pro 1 which may have significant similarities even if not the same device, but still including Ethernet support (diagnosed as LAN8720A even if ESPHome does not seem to support this).

The oddity (Shelly likes making things "different" without obvious reason) is that the relay and leds are driven via a SN74HC595B shift register instead of just being hooked directly up to ESP32 pins. Go figure 😉

If the Shelly Pro 2 devices work the same way, the shift register needs setup, but that may not be too bad as Tasmota already has Shift595 support.

[barbudor]

What ?!
Why bothering using an '595 on a ESP32 where you have plenty of pins.
The good news is that we have a driver for the '595 thanks to Faz learning C 🤣

[sfromis]

If I try to invent a reason, the shift register chip may be more robust when it comes to leds drawing power, and maybe even the relay. Pure uninformed speculation of course 🙈

We even have shift register support in Berry too...

[Mark-Muc]

any news on that? I today got the Shelly 2 pro (without power monitoring) .. how to falsh and config ..
Thanks again
Mark

[sfromis]

Flashing and configuration is likely pretty similar to doing it for the Shelly Pro 1, where I linked to what ESPHome has. That gives you something to work with, and then you can submit a Tasmota template when you get it complete for the two-channel model.

[Mark-Muc]

tomorrow i'd like to open the "damed" thing .. didn't find any hint to OPEN it!!
Mark

[sfromis]

Assuming that it is similar to the Shelly Pro 1, you do not need to open it to flash firmware, as the usual connector should be available from the side, with pinout here:
https://www.esphome-devices.com/devices/Shelly-Pro-1#programming-pinout
If the assumed shift register is on the same pins, that setup should get you a long way.

[Mark-Muc]

@sfromis Many thanks for your help ..
I found the connector and have cable .. so it shoud work ..
BUT witch version should I compile? "solo1" as it is on a shelly plus 2??
What to include, to have the shiftregister (SN74HC595B ) available to select or is it in the "standard" edition?
I'll play this week...
Thanks & Regards
Mark

[sfromis]

I just do not know which MCU is in there, esptool.py can tell you something with the flash_id subcommand, but the solo1 build works even if not single core; not the other way around. For normal Tasmota usage, building for dual core really does not give any benefit, anyway.

Shift595 support is included build time setting USE_SHIFT595, and then config the relevant pins as usual.

[Mark-Muc]

OK I will built simply a "solo1" version with USE_SHIFT595..
on the ESPHome link i found:

sn74hc595:
  - id: 'sn74hc595_hub'
    data_pin: GPIO13
    clock_pin: GPIO14
    latch_pin: GPIO4
    sr_count: 1

switch:
  - platform: gpio
    name: "Shelly Pro Relay"
    id: light1
    pin:
      sn74hc595: sn74hc595_hub
      number: 0
      inverted: false

  - platform: gpio
    id: out2
    pin:
      sn74hc595: sn74hc595_hub
      number: 1
      inverted: false

  - platform: gpio
    id: rgb_b
    pin:
      sn74hc595: sn74hc595_hub
      number: 2
      inverted: false

  - platform: gpio
    id: rgb_g
    pin:
      sn74hc595: sn74hc595_hub
      number: 3
      inverted: false

  - platform: gpio
    id: rgb_r
    pin:
      sn74hc595: sn74hc595_hub
      number: 4
      inverted: false

OK i am not so "experiences" but I will try
what i don't know ist how to configure sr_count: 1 in Tasmota
I am sure it comes to thousands of questions ..
I hope I am not too annoying and you help me here further.
Regards
Mark

[sfromis]

I'm not into details of how that config system works, but I'd assume that sr_count means shift register count, which you do not need to set, as the default with Tasmota is already 1. If you need to set it for more than one shift register (not too likely, as each shift register has 8 pins), it would be command Shift595DeviceCount or #define SHIFT595_DEVICE_COUNT.

[arendst]

I ordered a Shelly Pro 2PM. I'll see how to make it work.

[arendst]

Still working on it. It must be possible to get something runng.... Keep faith.

[sfromis]

It would likely be significantly easier to get the Shelly Pro 2 (without PM) working, the one Mark-Muc already has.

[arendst]

Ah I forgot. Ok will make that work first.

[TimelessNL]

Please forgive me for being a little off topic, but the dual ADE7953 could probably be because the 2PM can switch 2 separate phases and even AC combined with DC? This would also mean that e.g. voltage of the 2 ADE7953's can differ?

shelly_product_catalog.pdf

[arendst]

Alas, latest Shelly Pro 2PM V1 does not support 12V and in the new guide it is also not recommended to connect two phases.

See https://www.shelly.cloud/knowledge-base/devices/shelly-pro-2pm/ and read this

⚠CAUTION! Use one and the same phase for both load circuits and the Device power supply circuit.

Voltage is measured between Ix and the single N so connecting different phases will probably blow the earth leakage circuit breaker.

[arendst]

As a Proof Of Concept (POC) you can use tasmota32.bin and this template:

{"NAME":"Shelly Pro 2 (POC)","GPIO":[1,1,1,1,8320,1,0,0,1,8384,8288,1,1,0,5600,0,0,0,0,5568,0,0,0,0,0,0,0,0,1,1,1,32,1,1,160,161],"FLAG":0,"BASE":1}

and configure the 74HC595 in the GUI like this:

With that configuration you can switch the relays with the first and second button in the GUI. Ethernet works and Switch input should also work.

For a more final solution I'll have to write a driver to better support the GUI.

Adding both ADE7953 for the PM version is a different task but I think it can be done.

EDIT: I will default add the 74HC595 driver in tasmota32.bin now.

[Mark-Muc]

ohha .. this was very quick .. I just come home und will test tomorrow ...
Many Many THX for your excellent work!!

Mark

[barbudor]

This is already a bad design idea to use a '595 to drive only 2 relays as it is using more GPIO
Should they be stupid enough to skip bits in addition ?
If this is the thing, Shift595DeviceCount +<n>, <mask> which would require an additional uint32 to manage masking of bits not in use

@arendst Could you please kindly confirm that it is outputs 1 and 2 that are actually used by the Shelly 2 Pro ?

[sfromis]

Skipping bits would not be "stupidity", just convenience when routing traces on the PCB. I suppose that arguments for complicating the design using a shift register at all might be up to electrical characteristics, like when it can provide level shifting, and being a "buffer" for the more sensitive MCU chip, but whatever - they did it, and it is not that uncommon for Shelly to elaborate on hardware designs in "surprising" ways.

[barbudor]

So let's specify it
If we imagine a configuration with 2x '595 with only 6 pins in-use:

As today, relays are numbered from the 1st bit shifted-in which is also the one that will go the further through the registers chain.

So would the following command make sense ?
Shift595DeviceCount +10111001010000
Which would mean a count of relays of actual 6 (number of bits set to one) on positions 1, 3, 4, 5, 8, 10 for a total of 14 ser?clock ticks

For the Shelly, assuming relays on outputs Q0 and Q1, it would be Shift595DeviceCount +11

Does this syntax makes sense ?

[arendst]

The shift register is needed as gpio extender. All other gpios are used for ethernet, serial, spi, switch inputs. They better had used an esp32s3. Anyway, the extender is used for two relays (port 0 and 1) and three leds for wifi status (ports 2,3,4 if set to one all leds are off).

I'll write a small driver for the shelly to handle the 595 as used here.

In addition I need to update the ade7953 to support spi on TWO devices showing as two channels in the energy driver. Working on it already.

[barbudor]

ok, so a bit outside of a generic '595 driver

[arendst]

Latest dev release supports Shelly Pro 1/2 "out of the box" in binary tasmota32.bin using one of the below templates:

 * {"NAME":"Shelly Pro 1","GPIO":[0,0,0,0,768,0,0,0,672,704,736,0,0,0,5600,6214,0,0,0,5568,0,0,0,0,0,0,0,0,0,0,0,32,0,0,160,0],"FLAG":0,"BASE":1}
 * {"NAME":"Shelly Pro 2","GPIO":[0,0,0,0,768,0,0,0,672,704,736,0,0,0,5600,6214,0,0,0,5568,0,0,0,0,0,0,0,0,0,0,0,32,0,0,160,161],"FLAG":0,"BASE":1}

Support for Shelly Pro 1PM/2PM takes a bit longer...

[arendst]

If it crashes to it's defaults it means it detects a prolonged button press and just resets after 40 seconds as designed. Change button to button_i or button_n to inverse it's function.

I don't see the reason to use buttons as switches can do the job as well or even better using the correct switchmode, which btw only work for switches and not for buttons. Setting switchmode to 4 on a button is useless.

[Mark-Muc]

in my eys al momentary switch is a button.. or I am wrong?
Mark

[arendst]

You're right but a button does not support switchmodes. A switch configured correctly as a button using switchmode becomes a button.

There is a lot to say about tasmota button or switch gpios. Plus search docs. Suffice for to say keep the Shelly pro inputs configured as switch and change it's action using switchmode.

[Mark-Muc]

so .. did some testing of the device .. and I had to admit, I have been completely wrong in my thinking!!
https://tasmota.github.io/docs/Buttons-and-Switches/#switchmode
helped me now a lot .. simply switchmode 4 does the trick i whan't to have .. GPIO's defined as switch!!
So I habe to reconfigure all my devices... because the funktionality is different what I thout ..
then it doesn't make not much sense to def. a GPIO as button!!
Thx @arendst u brought a LOT of light in my "darkness".
Regards
Mark-Muc

[Mark-Muc]

never the less i get it to work Switchtype: button by define the GPIO as: Button_in
here are now the templates for the Shelly PRO 2 (NOT PM!!)

Switchtype: switch
{"NAME":"Shelly Pro 2 (switch)","GPIO":[0,0,0,0,768,0,0,0,672,704,736,0,0,0,5600,6214,0,0,0,5568,0,0,0,0,0,0,0,0,0,0,0,32,4736,4737,160,161],"FLAG":0,"BASE":1}

Switchtype: button
{"NAME":"Shelly Pro 2 (button)","GPIO":[0,0,0,0,768,0,0,0,672,704,736,0,0,0,5600,6214,0,0,0,5568,0,0,0,0,0,0,0,0,0,0,0,34,4736,4737,128,129],"FLAG":0,"BASE":1}

Regards
Mark-Muc

[arendst]

Progress!!!!

[Noschvie]

And the Tasmota web installer should automatically detect ESP32, and flash tasmota32.factory.bin (which is the preferable option for initial flashing only).

The web installer detected the ESP32 with tasmota32solo.bin

Updated to http://ota.tasmota.com/tasmota32/tasmota32.bin, use the template from above and the device is "up and running"
Thanks!

The voltage seems to be broken (no consumer connected)

[arendst]

No. Normal behavior. Just enable So21 1

[Noschvie]

L1 : The voltage shows "2" but should be "0" if no line is connected.
L2 : If the line is connected the value is 235 V and ok.

[JoeBue1]

@arendst on my WebUI to Shelly Pro 2PM I get only one energy value for today, yesterday and total for both circuits (L1,L2). It looks like noschvie's screenshots.
in your Screenshot there are individual energy values for each circuit.
I tried firmware 12.2.0 and 12.3.1 with no change on this behavior.
Additionally I tried the template posted her and the one from repository.
How do I get the the individual values to my WebUI and to the mqtt output?

[arendst]

Scan the documentation looking for command SetOption129 1

[Jason2866]

@Mark-Muc Please do not use a flashing tool made for a other project. It uses a different partition scheme which is problematic for Tasmota since the filesystem partition is too small.
If you dont want or you cant use the Web Tasmota Installer (which is just great imho) you can use Tasmota Esp Flasher or the always good to use esptool.py

[sfromis]

You can use the Partition Wizard to upgrade to new partition layout. However, if you do not worry about losing existing config details, it may be easier to do a wired flashing using the .factory image, which gets you the new and improved partition layout for much larger binary.

[Jason2866]

OTA update can not change the partition scheme. You can load the Berry TAPP (Tasmota APP), Partition Manager https://github.com/arendst/Tasmota/raw/development/tasmota/berry/modules/Partition_Manager.tapp to do a partition resize or Partition Wizard https://github.com/arendst/Tasmota/raw/development/tasmota/berry/modules/Partition_Wizard.tapp to convert to the Tasmota safeboot partition scheme. The later is stamdard for Tasmota.

[Mark-Muc]

Thx sfromis and Jason2866 for your help .. I run Partition_Wizard.tapp reboot and run it on a Shelly Plus 2PM PCB v0.1.9
it worked SUPER ... many many thx for your hints -- looks like this now:

hope this should be. like it should!
In future I will use the "right" way to flash it!!
Regards
Mark_Muc
one little thing: can I remove the 444 KB Partition Partition fs ??

[sfromis]

You can resize the file system partition, but you should not aim to remove it, as it is used by Tasmota. With ESP32, you also gain a lot of possibilities with Berry language scripting where program code is stored in the file system. You can even store files on the device too. Anyway, you are likely not even near your app0 partition becoming a bottleneck. With safeboot, OTA upgrades do not need any extra space in the app0 partition, as Tasmota reboots to the safeboot partition, and then replaces the app0 partition content.

Default partition layout when flashing .factory does have the fs partition a bit smaller at 320 KB, and the app0 partion correspondingly larger at 2880 KB.

[Mark-Muc]

OK Thanks .. just wonder if it is neaded @ all .. try to adjust close to 320 KB .. just for testing!!
Mark-Muc
I leaf it as it is .. didn't work because internal error .. last part. habe no system .. something like that .. as sfromis admited .. no need because enough space free!!

[PetterVikenes]

If anyone's interested.
Couldn't find any tear down pictures of Shelly3Pro
Seems Like Debug/program Port is located on Front Buttons PCB.
If true complete tear down is required to access Header. Can't see any other obvious port candidates
I'm moving so lab is in boxes but I'l try to probe it with whats at hand.

[DerT94]

Now the tricky part.

I would assume that, as with the other Shellys, 230V must not be applied when flashing.

I would try the following.
(Please correct me if I have made a mistake)

1. Connect GND to GND
2. Bridge GPIO0 to GND
3. 3.3V to 3.3v
4. RXD to TXD
5. TXD to RXD

Start ESPTOOL and try to read the Chip.

[sfromis]

Right. Beware that not all USB/Serial adapters can deliver sufficient power for flashing.

[DerT94]

I tried, but without success
The LEDs on the board come on but I can't get a connection to the ESP
I have also tried to read the information from a NodeMCU with ESP32-WROOM-32 for verification.
It worked with that. (Of course I also connected it to GPIO)
This means that my FTDI adapter is working

Any Ideas?

[sfromis]

Probably better to open a separate thread for the Shelly 3 pro, instead of it being buried in the middle of an old thread for a different device.

[DerT94]

Done
#20230

[Jason2866]

Another way to backup/flash the device would be directly programming the Flash IC since it is good to reach.
A CH341 flasher with a IC clamp can be used for.

[ChrisHolter]

Hi,
I flashed my Shelly 2 Pro with the latest Tasmota (12.3.1) which claims official support for the device and used the template from blakadder but for whatever reason I can't switch any of the relais but I'm just seeing the temperatures. Do I miss anything in my setup?

[Noschvie]

Have you activated the template ?

[ChrisHolter]

Yes, I activated the template, I'll go for the latest dev-version and see if that brings any change...

[Jason2866]

@ChrisHolter Use latest development version. There are changes and bug fixes done.

[ChrisHolter]

Flashing the latest dev binaries from the nightly fixed it, no need to set any switches. Thx a lot!

[Mark-Muc]

Hi there .. just to mention / ask:
Did u use the compiler switches:

#define USE_SPI
#define USE_SHELLY_PRO

when you built the version?
otherwise it won't work @ all!!
Just my 2ct worth!
Mark

[sfromis]

By now, those two #define are already included in the precompiled tasmota32.bin. Still, better use latest development build instead of release, to have all fixes.

[ChrisHolter]

I've used the release version from the pre-build binaries, but I'll try it with the development binaries to see if anything changes...

[Noschvie]

@ChrisHolter : which hardware version do you have ?
https://kb.shelly.cloud/knowledge-base/shelly-pro-2pm-v1

[ChrisHolter]

Hi @Noschvie I've got the v0 version as mine has still the 12v support. Is that a problem?

[Noschvie]

have the "newer" one v1 (without 12v support) up and running with Tasmota 12.2

[ChrisHolter]

It seems like the old version is also working using the latest nightly build

[TimelessNL]

I've used mgos32-to-tasmota32 to get my Shelly Pro 1 (v1) flashed with Tasmota, had to do it twice as the instructions mentioned.
So if anyone can update the state to [✅tested] that would be much appreciated.

After activating the template the device came to life, but the temperature reading seems off.
(I can hardly believe that it's that cold 🥶):

The Shelly 2.5 uses an ANALOG_NTC_BRIDGE_RESISTANCE as mentioned in xsns_02_analog.ino is that also the case for the Shelly Pro series?

EDIT:
Ah never mind, I forgot to execute AdcParam1 2,10000,10000,3350 🤦.
Now it's at 47.2°C (that even seem a bit high 🤔)

[Jason2866]

@TimelessNL Thanks, changed as confirmed working.

[sfromis]

which seems a bit hot at idle

Instead of seeming, better check if it is a realistic indication of actual temperature in there.
You may have hoped for it to be cooler, but that's not how the world works.
I'd certainly not be surprised if it is how the device works, but of course that's purely speculation.

[TimelessNL]

but that's not how the world works.

Eeh sure 😅, odd thing to say but fine.
In the meanwhile the issue is resolved, after some refitting it's at 27,4°C which is 4°C above ambient.
The reason why I'm bringing this up is because according to the simplified schematics the NTC is placed close to the relay which is on separate PCB:

So at idle with no current flowing this PCB should not get high above ambient.

[sfromis]

Assumptions of "should" is another variations of "seems", instead of measuring reality.

[TimelessNL]

I prefer to stay on-topic, the issue has been resolved and that is all that matters 👍

[bkoulouris]

Hi, I used firmware "http://ota.tasmota.com/tasmota32/shelly/mgos32-to-tasmota32-Pro2.zip" from "https://github.com/tasmota/mgos32-to-tasmota32" to flash a Shelly Pro 2 succesfully. Please note that the link in the main page gets tasmota version 12.4.0, however in the releases page 12.5.0 is available.

[bonjour81]

Hi ! can you share how you flashed with mgos ?
I cannot find pro 2 em (or any shelly pro) on mongoose (to install mongoose first)

[sfromis]

https://github.com/tasmota/mgos32-to-tasmota32/ has 7 Shelly Pro devices, but indeed no one named "Pro2EM". I do not see such a device on the site with Shelly products either. 2PM and 3EM exists, but not 2EM.

[bonjour81]

Hi, I don't talk about mgos32-to-tasmota, but initial flash from stock shelly firmware to mgos, as stated in prerequisite of the link you shared:
Your Shelly device must have Mongoose OS firmware version 0.12.0 or higher installed.

I assume (but may be wrong) that this shall be flashed 1st : https://github.com/mongoose-os-apps/shelly-homekit

regarding 2em => my mistake, I meant shelly pro 2pm.

[Jason2866]

Let the device Boot in Shelly firmware and use the OTA firmware update, if not already the min. needed revision is installed.

[bonjour81]

arf, problem solved !!
stock firmware was too old to offer OTA from an url and I forgot my firewall blocks by default any connexion from IoTs to internet..after opening firewall, I was able to update to last shelly firmware and then I was able to flash mgos32-to-tasmota.
thanks !

[marcinkowalczyk]

Hi,
Last week I've got Pro 2PM and I can't get it to work. As long as I change template it goes to boot-loop. Anybody had same issue? Tried with latest build too:

00:00:00.051-218/51 UFS: FlashFS mounted with 4400 kB free
00:00:00.070 CFG: Loaded from File, Count 2
00:00:00.080 QPC: Count 4
00:00:00.513 BRY: Berry initialized, RAM used=4560 bytes
00:00:00.562 CFG: Energy loaded from file
00:00:00.570 Project tasmota - Tasmota Version 12.5.0.3(tasmota32)-2_0_9(2023-05-22T10:54:32)
00:00:00.940 WIF: WifiManager active for 3 minutes

00:00:00.002-219/51 HDW: ESP32-D0WDQ6 
00:00:00.050-218/51 UFS: FlashFS mounted with 4400 kB free
00:00:00.069 CFG: Loaded from File, Count 2
00:00:00.080 QPC: Count 5
00:00:00.512 BRY: Berry initialized, RAM used=4560 bytes
00:00:00.562 CFG: Energy loaded from file
00:00:00.570 Project tasmota - Tasmota Version 12.5.0.3(tasmota32)-2_0_9(2023-05-22T10:54:32)
00:00:00.940 WIF: WifiManager active for 3 minutes

[sfromis]

That's not a boot loop, it seems to be working perfectly for the normal onboarding, where it is waiting for you to connect to the Wifi AP. You can alternatively config Wifi details via serial console, if you prefer.

Note that there is a high risk of Wifi not working properly unless replacing the setup for flashing by mains power.

[marcinkowalczyk]

Hi,
Thanks for reply but Like I wrote above - after template is applied I can't login anymore. No AP is exposed nor device connects to wifi. This is a reason why I connected over UART to see what's going on there.

[sfromis]

Well, it clearly is waiting for onboarding, meaning that it has been "factory reset". Try configuring Wifi details via commands.....

[marcinkowalczyk]

Hi,

I'm catching on a console and it's in a boot-loop in my opinion. Status shows uptime 1sec when executed couple of times

00:00:00.003-219/51 HDW: ESP32-DSTATUS 00WDQ6 
00:00:00.029-218/51 UFS: FlashFS mounted with 4404 kB free
00:00:00.034-218/51 TFS: File '.settings' not found
00:00:00.059 CFG: Use defaults
00:00:00.199 QPC: Reset

00:00:00.607 BRY: Berry initialized, RAM used=4560 bytes
00:00:00.646 CFG: Energy loaded from file
00:00:00.658 Project tasmota - Tasmota Version 12.5.0.3(tasmota32)-2_0_9(2023-05-22T10:54:32)
00:00:00.873 CMD: STATUS 0
00:00:00.878 RSL: STATUS = {"Status":{"Module":1,"DeviceName":"Tasmota","FriendlyName":["Tasmota"],"Topic":"tasmota_8DA880","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}}
00:00:00.913 RSL: STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota32/release/tasmota32.bin","RestartReason":"Vbat power on reset","Uptime":"0T00:00:01","StartupUTC":"","Sleep":50,"CfgHolder":4617,"BootCount":0,"BCResetTime":"1970-01-01T00:00:00","SaveCount":2}}
00:00:00.947 RSL: STATUS2 = {"StatusFWR":{"Version":"12.5.0.3(tasmota32)","BuildDateTime":"2023-05-22T10:54:32","Core":"2_0_9","SDK":"4.4.4.20230310","CpuFrequency":160,"Hardware":"ESP32-D0WDQ6 rev.1","CR":"390/699"}}
00:00:00.960 RSL: STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]}}
00:00:00.994 RSL: STATUS4 = {"StatusMEM":{"ProgramSize":1526,"Free":1353,"Heap":208,"StackLowMark":4,"PsrMax":0,"PsrFree":0,"ProgramFlashSize":8192,"FlashSize":8192,"FlashChipId":"17701C","FlashFrequency":40,"FlashMode":"DIO","Features":["00000809","9F9AD7CF","0015A001","B7F7BFCF","05DA9BC0","E0360DC7","480840D2","20200000","D4BC482D","000A80B1"],"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,66,67,68,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,31,34,37,39,40,42,43,45,51,52,55,56,58,59,64,66,67,74,85,92,95,98,103,105,127","I2CDriver":"7,8,9,10,11,12,13,14,15,17,18,20,24,29,31,36,41,42,44,46,48,58,62,65,69,76,77"}}
00:00:00.050 RSL: STATUS5 = {"StatusNET":{"Hostname":"tasmota-8DA880-2176","IPAddress":"0.0.0.0","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer1":"0.0.0.0","DNSServer2":"0.0.0.0","Mac":"EC:62:60:8D:A8:80","IP6Global":"","IP6Local":"","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","IP6Global":"","IP6Local":""},"Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":16.0}}
00:00:00.094 RSL: STATUS6 = {"StatusMQT":{"MqttHost":"","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_8DA880","MqttUser":"DVES_USER","MqttCount":0,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
00:00:00.119 RSL: STATUS7 = {"StatusTIM":{"UTC":"1970-01-01T00:00:00","Local":"1970-01-01T00:00:00","StartDST":"1970-01-01T00:00:00","EndDST":"1970-01-01T00:00:00","Timezone":"+00:00","Sunrise":"14:37","Sunset":"04:20"}}
00:00:00.136 RSL: STATUS10 = {"StatusSNS":{"Time":"1970-01-01T00:00:00"}}
00:00:00.143 RSL: STATUS11 = {"StatusSTS":{"Time":"1970-01-01T00:00:00","Uptime":"0T00:00:01","UptimeSec":1,"Heap":206,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":0,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":38}}}
STATUS 000:00:01.046 WIF: WifiManager active for 3 minutes

00:00:00.003-219/51 HDW: ESP32-D0WDQ6 
00:00:00.046-218/51 UFS: FlashFS mounted with 4400 kB free
00:00:00.065 CFG: Loaded from File, Count 2
00:00:00.075 QPC: Count 1

00:00:00.502 BRY: Berry initialized, RAM used=4560 bytes
00:00:00.550 CFG: Energy loaded from file
00:00:00.558 Project tasmota - Tasmota Version 12.5.0.3(tasmota32)-2_0_9(2023-05-22T10:54:32)
00:00:00.664 CMD: 
00:00:00.926 WIF: WifiManager active for 3 minutes

00:00:00.002-219/51 HDW: ESP32-D0WDQ6 
00:00:00.045-218/51 UFS: FlashFS mounted with 4400 kB free
00:00:00.065 CFG: Loaded from File, Count 2
00:00:00.075 QPC: Count 2
00:00:00.502 BRY: Berry initialized, RAM used=4560 bytes
00:00:00.550 CFG: Energy loaded from file
00:00:00.557 Project tasmota - Tasmota Version 12.5.0.3(tasmota32)-2_0_9(2023-05-22T10:54:32)
00:00:00.919 WIF: WifiManager active for 3 minutes

00:00:00.002-219/51 HDW: ESP32-D0WDQ6 
00:00:00.045-218/51 UFS: FlashFS mounted with 4400 kB free
00:00:00.065 CFG: Loaded from File, Count 2
00:00:00.075 QPC: Count 3
STATUS 000:00:00.502 BRY: Berry initialized, RAM used=4560 bytes
00:00:00.550 CFG: Energy loaded from file
00:00:00.558 Project tasmota - Tasmota Version 12.5.0.3(tasmota
32)-2_0_9(2023-05-22T10:54:32)
00:00:00.666 CMD: STATUS 0
00:00:00.670 RSL: STATUS = {"Status":{"Module":1,"DeviceName":"Tasmota","FriendlyName":["Tasmota"],"Topic":"tasmota_8DA880","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}}
00:00:00.704 RSL: STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota32/release/tasmota32.bin","RestartReason":"Vbat power on reset","Uptime":"0T00:00:01","StartupUTC":"","Sleep":50,"CfgHolder":4617,"BootCount":0,"BCResetTime":"1970-01-01T00:00:00","SaveCount":2}}
00:00:00.738 RSL: STATUS2 = {"StatusFWR":{"Version":"12.5.0.3(tasmota32)","BuildDateTime":"2023-05-22T10:54:32","Core":"2_0_9","SDK":"4.4.4.20230310","CpuFrequency":160,"Hardware":"ESP32-D0WDQ6 rev.1","CR":"390/699"}}
00:00:00.751 RSL: STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C80001000600003C5A0A192800000000","00000080","00006000","00004000","00000000"]}}
00:00:00.784 RSL: STATUS4 = {"StatusMEM":{"ProgramSize":1526,"Free":1353,"Heap":208,"StackLowMark":5,"PsrMax":0,"PsrFree":0,"ProgramFlashSize":8192,"FlashSize":8192,"FlashChipId":"17701C","FlashFrequency":40,"FlashMode":"DIO","Features":["00000809","9F9AD7CF","0015A001","B7F7BFCF","05DA9BC0","E0360DC7","480840D2","20200000","D4BC482D","000A80B1"],"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,66,67,68,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,31,34,37,39,40,42,43,45,51,52,55,56,58,59,64,66,67,74,85,92,95,98,103,105,127","I2CDriver":"7,8,9,10,11,12,13,14,15,17,18,20,24,29,31,36,41,42,44,46,48,58,62,65,69,76,77"}}
00:00:00.840 RSL: STATUS5 = {"StatusNET":{"Hostname":"tasmota-8DA880-2176","IPAddress":"0.0.0.0","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer1":"0.0.0.0","DNSServer2":"0.0.0.0","Mac":"EC:62:60:8D:A8:80","IP6Global":"","IP6Local":"","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","IP6Global":"","IP6Local":""},"Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":16.0}}
00:00:00.885 RSL: STATUS6 = {"StatusMQT":{"MqttHost":"","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_8DA880","MqttUser":"DVES_USER","MqttCount":0,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
00:00:00.909 RSL: STATUS7 = {"StatusTIM":{"UTC":"1970-01-01T00:00:00","Local":"1970-01-01T00:00:00","StartDST":"1970-01-01T00:00:00","EndDST":"1970-01-01T00:00:00","Timezone":"+00:00","Sunrise":"14:37","Sunset":"04:20"}}
00:00:00.926 RSL: STATUS10 = {"StatusSNS":{"Time":"1970-01-01T00:00:00"}}
00:00:00.932 RSL: STATUS11 = {"StatusSTS":{"Time":"1970-01-01T00:00:00","Uptime":"0T00:00:01","UptimeSec":1,"Heap":206,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":0,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":38}}}
00:00:01.082 WIF: WifiManager active for 3 minutes

[barbudor]

Looks like you haven't configured your Wifi settings yet

[marcinkowalczyk]

I did.
This happens when I click activate of Pro2 PM config.
Plus it should go into AP mode and this does not happen.

[marcinkowalczyk]

I went with older releases - seems with 12.2.0 works OK (boots, ADC temp is shown) but as long I go 12.3.1 or above wifi does not work. On module it self It says it's V1 but maybe design has changed recenty? Not sure how to open it without breaking plastics to compare PCB

[Jason2866]

Since it is booting and it "just" fails to connect to wifi, i think it is a compatibility problem between the used closed source espressif wifi libs used. The have changed between the used cores. Tasmota v12.2.0 uses an older Arduino core with older wifi espressif libs.
Which brand is your router / access point?

[marcinkowalczyk]

I'm using Ubiquiti Unifi devices.
Strange thing is, that users reported above it works for them with 12.3.1 -> #16733 (comment)

Another odd thing it that Shelly can connect to wifi and will work as long as template for 2PM is not activated.

I mange to open module and PCB is marked ~07.2022 so noting new.

[Jason2866]

Don't think it is a general issue. Ubiquiti Unifi had some "unlucky" firmware releases.
Try if the Shelly device connects to an other AP or mobile Hotspot.

[arendst]

Just upgraded my Shelly Pro 2PM from v12.3.0.3 to v12.5.0.3 without problems:

00:00:00.002 HDW: ESP32-D0WDQ6 
00:00:00.038 UFS: FlashFS mounted with 4400 kB free
00:00:00.062 CFG: Loaded from File, Count 286
00:00:00.203 CFG: Saved, Count 287, Bytes 4096
00:00:00.211 QPC: Count 1
00:00:00.215 SPI: Hardware using GPIO14(CLK), GPIO13(MOSI) and GPIO12(MISO)
00:00:00.217 CFG: CR 489/699, Busy 0
00:00:00.217 CFG: CR 489/699, Busy 0
00:00:00.223 TFS: File 'mcp23x.dat' not found
00:00:00.223 MCP: Invalid template
00:00:00.227 ROT: Mode 1
00:00:00.350 CFG: No '*.autoconf' file found
00:00:00.357 BRY: Berry initialized, RAM used=4203 bytes
00:00:00.370 BRY: No 'preinit.be'
00:00:00.409 CFG: Energy loaded from file
00:00:00.512 SPI: ADE7953 found
00:00:00.517 TFS: File 'calib.dat' not found
00:00:00.518 NRG: Init driver 7
00:00:00.519 SRC: Restart
00:00:00.526 Project tasmota - ShellyPro2PM1 Version 12.5.0.3(theo)-2_0_9(2023-05-29T14:27:36)
00:00:00.526 ETH: No ETH MDC and/or ETH MDIO GPIO defined
00:00:00.528 HDW: Shelly Pro 2PM initialized
00:00:00.623 BRY: No 'autoexec.be'
00:00:00.903 WIF: Attempting connection...
00:00:01.147 WIF: Connecting to AP1 indebuurt_IoT Channel 11 BSSId 18:E8:29:CA:17:C1 in mode 11n as shellypro2pm1...
00:00:01.929 WIF: IPv4 192.168.2.163, mask 255.255.255.0, gateway 192.168.2.254
00:00:02.219 WIF: Connected
00:00:02.477 HTP: Web server active on shellypro2pm1 with IP address 192.168.2.163
00:00:02.789 WIF: DNS resolved 'ntpserver1' (192.168.2.27) in 20 ms
00:00:02.805 RTC: UTC 2023-05-29T12:50:22, DST 2023-03-26T02:00:00, STD 2023-10-29T03:00:00
14:50:22.001 RTC: Synced by NTP
14:50:22.426 MQT: Attempting connection...
14:50:22.433 WIF: DNS resolved 'mqttbroker' (192.168.2.24) in 5 ms
14:50:22.463 MQT: Connected
14:50:22.468 MQT: tele/shellypro2pm1/LWT = Online (retained)
14:50:22.471 MQT: cmnd/shellypro2pm1/POWER = 
14:50:22.473 MQT: Subscribe to cmnd/shellypro2pm1/#
14:50:22.477 MQT: Subscribe to cmnd/tasmotas/#
14:50:22.480 MQT: Subscribe to cmnd/DVES_8BB07C_fb/#
14:50:22.491 MQT: tele/shellypro2pm1/INFO1 = {"Info1":{"Module":"Shelly Pro 2PM","Version":"12.5.0.3(theo)","FallbackTopic":"cmnd/DVES_8BB07C_fb/","GroupTopic":"cmnd/tasmotas/"}}
14:50:22.498 MQT: tele/shellypro2pm1/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"shellypro2pm1","IPAddress":"192.168.2.163","IP6Global":"","IP6Local":"fe80::ee62:60ff:fe8b:b07c"}}
14:50:22.507 MQT: tele/shellypro2pm1/INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":109}}
14:50:22.510 MQT: stat/shellypro2pm1/RESULT = {"POWER1":"ON"}
14:50:22.512 MQT: stat/shellypro2pm1/POWER1 = ON
14:50:22.514 MQT: stat/shellypro2pm1/RESULT = {"POWER2":"OFF"}
14:50:22.516 MQT: stat/shellypro2pm1/POWER2 = OFF
14:50:22.522 TFS: File 'autoexec.bat' not found
14:50:22.993 WIF: IPv6 Local fe80::ee62:60ff:fe8b:b07c
14:50:25.790 QPC: Reset
14:50:26.788 MQT: tele/shellypro2pm1/STATE = {"Time":"2023-05-29T14:50:26","Uptime":"0T00:00:08","UptimeSec":8,"Heap":164,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":22,"MqttCount":1,"Berry":{"HeapUsed":3,"Objects":42},"POWER1":"ON","POWER2":"OFF","Wifi":{"AP":1,"SSId":"indebuurt_IoT","BSSId":"18:E8:29:CA:17:C1","Channel":11,"Mode":"11n","RSSI":100,"Signal":-27,"LinkCount":1,"Downtime":"0T00:00:03"}}
14:50:26.805 MQT: tele/shellypro2pm1/SENSOR = {"Time":"2023-05-29T14:50:26","Switch1":"OFF","Switch2":"OFF","ANALOG":{"Temperature1":37.1,"Temperature2":32.3},"ENERGY":{"TotalStartTime":"1970-01-01T00:00:00","Total":[0.000,0.000],"Yesterday":[0.000,0.000],"Today":[0.000,0.000],"Period":[0.00,0.00],"Power":[0.00,0.00],"ApparentPower":[0.00,0.00],"ReactivePower":[0.00,0.00],"Factor":[0.00,0.00],"Frequency":[49.98,49.98],"Voltage":[247.59,248.39],"Current":[0.000,0.000]},"TempUnit":"C"}
14:50:26.994 WIF: IPv6 Global fd79:962c:bf13:49d0:ee62:60ff:fe8b:b07c
14:50:27.777 APP: Boot Count 109
14:50:28.060 CFG: Saved, Count 288, Bytes 4096
14:51:24.083 CMD: template
14:51:24.085 SRC: WebConsole from 192.168.2.1
14:51:24.086 CMD: Grp 0, Cmd 'TEMPLATE', Idx 1, Len 0, Pld -99, Data ''
14:51:24.096 MQT: stat/shellypro2pm1/RESULT = {"NAME":"Shelly Pro 2PM","GPIO":[9568,1,9472,1,768,0,0,0,672,704,736,9569,0,0,0,6214,0,0,0,0,0,0,0,0,0,0,0,0,3460,0,0,32,4736,4737,160,161],"FLAG":0,"BASE":1}

Make sure to do your test while connected to AC power; just a serial connection won't work as not enough power. REMOVE SERIAL WIRES WHEN CONNECTED TO AC.

[arendst]

Using Ubiquiti UAP-AC_Pro v6.2.49

[marcinkowalczyk]

I don't think it's Ubi issue - as if I'm not using PRO2PM template it works like a charm Tasmota 12.3.1 : "Uptime":"0T03:35:08"

As soon I apply template it's a game over. Relay clicks and I can't get there anymore

Wifi led chages color blue->green->blue

[arendst]

Compare your template with mine shown above last line.

[marcinkowalczyk]

Hi,

I did tests starting hotspot on old andorid phone

With your config (works verrry slow ~15...30sec to switch between pages). For test I used template for PRO2 (wihout PM) and works extremly fast. I did small mistake and lost orginal shelly firmware so I can't go back ;-)

[marcinkowalczyk]

Got it - if no mains connected to I1 of I2 than module is not usable due to extremly high latency.

[TimelessNL]

I've noticed that the relay of the Shelly Pro 1 briefly pulses during power on sometimes. Looking at how the SN74HC595 is wired all the LEDs are inverted but the relay is not. This basically means that the relay will be ON and LEDs OFF when OE is low and nothing is written to the SN74HC595 yet, correct?

If I read the code comments:

OE is connected to Gnd with 470 ohm resistor R62 AND a capacitor C81 to 3V3
- this inhibits output of signals (also relay state) during power on for a few seconds

The OE pin will be high until the capacitor is depleted and that's what inducing a delay on the output during poweron?
But if the state is not yet written to the SN74HC595 the relay will become active after the OE is pulled low?

[antoniochetti]

Hi, I used firmware "http://ota.tasmota.com/tasmota32/shelly/mgos32-to-tasmota32-Pro2.zip" from "https://github.com/tasmota/mgos32-to-tasmota32" to flash a Shelly Pro 2 succesfully.

Everything seems to work, but in the knx page I can't find the option to control the two relays. How can I do?

[Noschvie]

Did you a test with the latest development version too?

[Noschvie]

There seems to be a problem with the ESP32 KNX variant / 12.5.0: receiving KNX messages seems to be broken, send KNX messages works fine, tested with a Shelly plus 1.
Using a "Athom LB017W" running the tasmota-knx.bin.gz / 12.5.0 works fine for sending and receiving KNX messages.

[Noschvie]

Latest development version solves this for the "Shelly plus 1", have no Shelly Pro for tests.

[Jason2866]

Mhh, seems the used lwip code (IDF) changed in Tasmota Core 2.0.10 is the reason. Nothing else has been changed in KNX part since release 12.5.0.

[derpeter]

Today i added an Pro2 (no PM) to our tasmota zoo. I used the template from blakadder. For some reason the temperature readings are way of (currently arrount 0 C while it should be around 25). Any hint what i may have missed. (running tasmota 13 now, 12.5 was the same)