Tasmota: Support for Shelly 2.5

[JoergTiedemann]

Hi
Is the new Shelly 2.5 supported by Tasmota?
Which firmware version is required in minimum and are there any known open issues with Shelly 2.5 ?
Regards joerg

[arendst]

Not yet. Mine is on the way.

[peterforeman]

Do you have the GPIO pin mapping yet? Then I can fix it temporarily using USER pins.

[arendst]

No, that's the tricky part ;-). If someone knows let him/her make the template as documented here https://github.com/arendst/Sonoff-Tasmota/wiki/Templates

[peterforeman]

Currently I only have GPIO4 = Relay1, GPIO14 = Relay2. Rest I'm trying to figure out...

[curzon01]

Correction:
D2/GPIO4 = Relay1 :white_check_mark:
_D8/GPIO15 = Relay2_

Be warned: :warning:
After I'd tried Switch input for all of the rest of the GPIOs my Shelly2.5 SW1/SW2 pins has steady 230V~ signal also without input. I couldn't revert this status

Edit: Note to my this warning above - I can still measure 230V~ on SW1/SW2 having this connection open but SW1/2 input are working with the template below.

[arendst]

Warning: https://www.facebook.com/groups/ShellyIoTCommunitySupport/permalink/2029876037111750/

Seems to happen on a small amount of production items but it might be usefull to check before power on.

[meingraham]

Was just coming here to add this information. You beat me too it. I added it to the Shelly wiki page.

[arendst]

I just received info from the Shelly support group (Many thanks). The Shelly 2.5 GPIO's should be:

GPIO0 - Led1
GPIO2 - Button1
GPIO4 - Relay1
GPIO5 - Switch1
GPIO13 - Switch2
GPIO15 - Relay2

For correct functionality you may need Switchxn and/or Relayxi. I cannot test this yet as my device is still in the mail.

Energy metering is done by a new chip (ADE7953) connected to I2C on GPIO12/14 and IRQ on GPIO16 not supported by Tasmota yet. I will have to implement this.

Temperature is measured using the Analog input. Again, I have to implement this.

So for now the power control should work. The rest will need my attention...

EDIT: See working template below.

[arendst]

Pls report back if the above template functions as expected.

[Tommi-nrw]

Please be careful handling Shelly 2.5!
Better first open every single Device, cut all pins and check for shortcuts before connecting to power!

See details here:
https://forum.creationx.de/forum/index.php?thread/1753-wichtige-information-zum-shelly-2-5/&postID=22725#post22725

Regards
Tom

[curzon01]

This template works for my 2.5:
{"NAME":"Shelly 2.5","GPIO":[52,255,17,255,21,83,0,0,6,82,5,22,0],"FLAG":1,"BASE":18}

The difference to yours Theo:

• use SwitchXn instead of SwitchX (SwitchX using pull-up does not work here using 230V~ input)
• Switch1 and 2 are exchanged (it confirms the observe from @Tommi-nrw link that Shelly group may have exchanged the SW1/SW2 internal documentation)

[arendst]

Great! I'll post the updated version in the wiki then.

[arendst]

Updated template with analog temperature readings (if compiled with //#define USE_ADC_VCC and using latest development release (2c6df2b) or up).

{"NAME":"Shelly 2.5","GPIO":[52,255,17,255,21,83,0,0,6,82,5,22,0],"FLAG":2,"BASE":18}

[arendst]

First readings are in:

Still a lot to do like separating the outputs and calibration.

[joba-1]

nice progress

iphone so i typo

[ascillato2]

Closing this issue as the support for shelly 2.5 has been added.

Thanks :+1:

[curzon01]

It might be I make a principle failure but can't get power monitor to work on my Shellys 2.5.
I did also flash erase and re-flash to start from scratch but always got the VEML6070 UV sensor instead of power monitor:

Status 0:

stat/sonoff/STATUS = {"Status":{"Module":0,"FriendlyName":["Sonoff","Sonoff2"],"Topic":"sonoff","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],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0}}
stat/sonoff/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://thehackbox.org/tasmota/sonoff-sensors.bin","RestartReason":"Software/System restart","Uptime":"0T00:00:37","StartupUTC":"2019-04-15T14:40:47","Sleep":50,"CfgHolder":4617,"BootCount":3,"SaveCount":13,"SaveAddress":"FA000"}}
stat/sonoff/STATUS2 = {"StatusFWR":{"Version":"6.5.0.8(2163df5-sensors)","BuildDateTime":"2019-04-15T11:06:27","Boot":31,"Core":"2_4_2","SDK":"2.2.1(cfd48f3)"}}
stat/sonoff/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["dev.prsolution.eu","<*_*>"],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","280500000100000000000000000000000000","00000000"]}}
stat/sonoff/STATUS4 = {"StatusMEM":{"ProgramSize":562,"Free":440,"Heap":16,"ProgramFlashSize":1024,"FlashSize":2048,"FlashChipId":"1540EF","FlashMode":3,"Features":["00000809","0FDEE394","0007A3A4","B7FFBFCC","00DABBC0"]}}
stat/sonoff/STATUS5 = {"StatusNET":{"Hostname":"sonoff-6422","IPAddress":"172.18.10.151","Gateway":"172.18.10.4","Subnetmask":"255.255.255.0","DNSServer":"172.18.10.4","Mac":"DC:4F:22:5D:B9:16","Webserver":2,"WifiConfig":4}}
stat/sonoff/STATUS6 = {"StatusMQT":{"MqttHost":"mqtt.local.prsolution.eu","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_5DB916","MqttUser":"tasmota","MqttCount":1,"MAX_PACKET_SIZE":1000,"KEEPALIVE":15}}
stat/sonoff/STATUS7 = {"StatusTIM":{"UTC":"Mon Apr 15 14:41:25 2019","Local":"Mon Apr 15 15:41:25 2019","StartDST":"Sun Mar 31 02:00:00 2019","EndDST":"Sun Oct 27 03:00:00 2019","Timezone":"+01:00","Sunrise":"05:59","Sunset":"19:41"}}
stat/sonoff/STATUS10 = {"StatusSNS":{"Time":"2019-04-15T15:41:25","Switch1":"OFF","Switch2":"OFF","ANALOG":{"Temperature":51.0},"VEML6070":{"UvLevel":65535,"UvIndex":99.00,"UvIndexText":"OoR","UvPower":2.475},"TempUnit":"C"}}
stat/sonoff/STATUS11 = {"StatusSTS":{"Time":"2019-04-15T15:41:25","Uptime":"0T00:00:38","SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"dev.prsolution.eu","BSSId":"5C:49:79:A2:34:FB","Channel":13,"RSSI":82,"LinkCount":1,"Downtime":"0T00:00:04"}}}

Template

stat/sonoff/RESULT = {"NAME":"Shelly 2.5","GPIO":[52,255,17,255,21,83,0,0,6,82,5,22,0],"FLAG":2,"BASE":18}

i2cscan

MQT: stat/sonoff/RESULT = {"I2CScan":"Device(s) found at 0x38"}

[arendst]

Oh boy, someone connected a sensor to an energy monitoring device....

The VEML has the same I2C address as the ADE7953.

As the VEML is most probably initialised before the ADE7953, which needs a delay of 100mS at power up, it took over energy monitoring.

Remove the sensor or change it's I2C address.

[curzon01]

I tried to remove remove the none existing device, I couldn't. :grinning:

Theo, it's an original Shelly 2.5 without any modification...

[arendst]

Ah. I see. You did not connect a VEML but the code detects the VEML too even if it is not connected.

Short term solution, remove the VEML from the compile options.
Long term solution, either the VEML code owner finds a way to actively search for the device or I have to come up with some kind of address reservation system; once detected do not allow other to take over (this should work for the ADE7953 as it is a driver which is searched first before the sensor).

To be continued....

[arendst]

Should be fixed in latest update just released.

[curzon01]

I still didn't got it work also not with last commit and also not VEML disabled so I dig a little into the code.

The reason is simply the previous communicated template might be wrong. GPIO16 must be defined as ADE7953 IRQ and setting this energy monitor works.

But the comment in code confused me (ade7953 driver)

void Ade7953DrvInit(void)
...
if (i2c_flg && (pin[GPIO_ADE7953_IRQ] < 99)) {  // Irq on GPIO16 is not supported...

My template now is:

{"NAME":"Shelly 2.5","GPIO":[52,255,17,255,21,83,0,0,6,82,5,22,156],"FLAG":2,"BASE":18}

(new is ...,156],"FLA... instead of ...,0],"FLA...)

@arendst - can you pls confirm?

[arendst]

@curzon I've updated th wiki some days ago with the correct template. Pls chk

[curzon01]

Unfortunatley the given template does not work - reason is the GIPO16 setting (=0):

GPIO16 must be setup as ADE7953 IRQ (156) to get it started

[arendst]

So sorry. You're right. Forgot to update (again).

Yes gpio16 should be 156.

Hope that works for you too.

[BafHS]

Good morning,
thx a lot, its working fine, i use 6.5.0.9.
i do every step from Shelly 2.5 now one Calibration ... you write

execute the commands

but where? Can you give me a tipp
Sorry, who can read is clearly in the advantage. i found my answer Command

[Yarikx]

Hi.
Does anyone experience random device reboots after switching some of the relays?
I can easily reproduce by quickly switching one relay from web.
I don't have non-tasmotized shelly 2.5 to check if it happens on original firmware =(

[arzaman]

hi
Does last binary official release 6.5.0 works with shelly 2.5 or need to compile a more recent development version?
thks
Davide

[curzon01]

6.5.0 might be usable for IO-GPIOS (relay, switches) but without energy monitor.

For fully Shelly 2.5 support use the latest developer version (minimum v6.5.0.8 branch 5e810f1f)

You don't need to compile by yourself, download the latest compiled developer binary as described here.
If you get WiFi issues with this binary, try the core 2.3.0 developer compile

[arzaman]

cristal clear thanks, I will try to flash the developer binary on my shelly 2.5 and report any issue in case !

[lobocobra]

When will the shelly be added to master?
6.5.0.16 wifi connection is unstable and I want to use my 20+ shelly 2.5 in a productive environnment.
Same issues with 6.5.0.16. Reset 5 brought no improvement.

[ArturGabrys]

When will the shelly be added to master?
6.5.0.16 wifi connection is unstable and I want to use my 20+ shelly 2.5 in a productive environnment.
Same issues with 6.5.0.16. Reset 5 brought no improvement.

I would really appreciate this, one of main reasons for buying Shelly devices for me was ability to run Tasmota on it. Any approximate time? Thank you.

[meingraham]

@lobocobra Wi-Fi instability is usually associated with the core you are using. Even when the latest stable development branch becomes the next master, this will not address your Wi-Fi connectivity issues.

If you haven't tried 2.5.2, give that a try. Otherwise, 2.3.0 tends to be foolproof.

[MaximilanPower]

Hello everyone,
is there a reason, why the shelly 2.5 is not selectable under Module Type or did I just not found the commit?
Best regard Max

[meingraham]

@MaximilanPower,

Going forward, Tasmota modules will be solely for unique capability requiring special coding. The 2.5 makes use of existing components configurations to specify its template. The Template feature was added in order to support the explosion in the number of ESP devices on the market.

[zkolb]

Hello everyone,
I've just installed two shelly 2.5 devices with release 6.6.0. After 10-15 minutes they reach 73C and turn off both relays (the threshold set by SetOption42 is ignored). I've replaced the lightbulbs with LED ones, lowering the power consumption to 14W, that extended the ON time to15-20 minutes. At this point I've turned off temperature sensing (flag 2 -> 0), but I'm not happy with this solution. Can we calibrate the temperature reading? Is there a way to change the 73C threshold? Does anyone else experience this issue?
Best regards, Zoltan

[arendst]

See #6036 and use the precompiled dev version.

[zkolb]

Thanks!
The dev version works fine. The temperature does not even go above 72C. I was runnng it for several hours and it never turned off the relays due to overtemp.

[stefanbosch]

Great fix, dev version did the trick for the temp threshold! 👍

[JeremiahGillis]

Can anyone confirm Shelly 2.5 still fully works with Tasmota 8.1.0? My energy measurements are not working or showing up.

I just flashed it and this is what my interface looks like:

I followed this guide https://tasmota.github.io/docs/#/devices/Shelly-2.5 and used template:

{"NAME":"Shelly 2.5","GPIO":[56,0,17,0,21,83,0,0,6,82,5,22,156],"FLAG":2,"BASE":18}

My serial logging is off

01:03:43 CMD: Group 0, Index 1, Command "STATUS", Data "0"
01:03:43 RSL: stat/tasmota/STATUS = {"Status":{"Module":0,"FriendlyName":["Tasmota","Tasmota2"],"Topic":"tasmota","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":0,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0}}
01:03:43 RSL: stat/tasmota/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"tasmotas","OtaUrl":"http://thehackbox.org/tasmota/release/tasmota.bin","RestartReason":"External System","Uptime":"0T00:17:28","StartupUTC":"2020-02-22T23:46:15","Sleep":50,"CfgHolder":4617,"BootCount":14,"SaveCount":44,"SaveAddress":"F8000"}}
01:03:43 RSL: stat/tasmota/STATUS2 = {"StatusFWR":{"Version":"8.1.0(tasmota)","BuildDateTime":"2019-12-25T12:33:25","Boot":31,"Core":"2_6_1","SDK":"2.2.2-dev(38a443e)","Hardware":"ESP8266EX","CR":"329/699"}}
01:03:43 RSL: stat/tasmota/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":4,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["Butchery IoT",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["0020880A","0105C8000100060000005A00000000000000","00000000","00000000"]}}
01:03:43 RSL: stat/tasmota/STATUS4 = {"StatusMEM":{"ProgramSize":566,"Free":436,"Heap":27,"ProgramFlashSize":2048,"FlashSize":2048,"FlashChipId":"1540EF","FlashMode":3,"Features":["00000809","8FDAE397","043683A0","22B617CD","01001BC0","00007881"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,29","Sensors":"1,2,3,4,5,6,7,8,9,10,14,15,17,18,20,22,26,34"}}
01:03:43 RSL: stat/tasmota/STATUS5 = {"StatusNET":{"Hostname":"tasmota-6366","IPAddress":"192.168.3.112","Gateway":"192.168.3.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.3.1","Mac":"80:7D:3A:74:58:DE","Webserver":2,"WifiConfig":4}}
01:03:43 RSL: stat/tasmota/STATUS6 = {"StatusMQT":{"MqttHost":"","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_7458DE","MqttUser":"DVES_USER","MqttCount":0,"MAX_PACKET_SIZE":1000,"KEEPALIVE":30}}
01:03:43 RSL: stat/tasmota/STATUS7 = {"StatusTIM":{"UTC":"Sun Feb 23 00:03:43 2020","Local":"Sun Feb 23 01:03:43 2020","StartDST":"Sun Mar 29 02:00:00 2020","EndDST":"Sun Oct 25 03:00:00 2020","Timezone":"+01:00","Sunrise":"07:44","Sunset":"18:22"}}
01:03:43 RSL: stat/tasmota/STATUS10 = {"StatusSNS":{"Time":"2020-02-23T01:03:43","Switch1":"OFF","Switch2":"OFF","ANALOG":{"Temperature":43.1},"TempUnit":"C"}}
01:03:43 RSL: stat/tasmota/STATUS11 = {"StatusSTS":{"Time":"2020-02-23T01:03:43","Uptime":"0T00:17:28","UptimeSec":1048,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Butchery IoT","BSSId":"7A:8A:20:0F:93:DB","Channel":5,"RSSI":82,"Signal":-59,"LinkCount":1,"Downtime":"0T00:00:07"}}}

01:05:33 CMD: Group 0, Index 1, Command "STATUS", Data "8"
01:05:33 RSL: stat/tasmota/STATUS8 = {"StatusSNS":{"Time":"2020-02-23T01:05:33","Switch1":"OFF","Switch2":"OFF","ANALOG":{"Temperature":44.5},"TempUnit":"C"}}
01:05:35 CMD: status 9
01:05:35 SRC: WebConsole from 192.168.1.105
01:05:35 CMD: Group 0, Index 1, Command "STATUS", Data "9"
01:05:35 RSL: stat/tasmota/STATUS = {"Status":{"Module":0,"FriendlyName":["Tasmota","Tasmota2"],"Topic":"tasmota","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":0,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0}}

What could be wrong?

I would expect the energy parameters to show up even if the hardware isn't working correctly.

I have more Shelly 2.5's that I could try. I just did a Shelly 1PM which showed energy measurements correctly. I just don't know if this is a hardware or software issue. This specific Shelly 2.5 was never used with the stock firmware.

[ascillato]

My Shelly 2.5 is fully working with latest Tasmota.

If you are self compiling remember to define I2C. Please use the precompiled bins.

Please, address this to the Tasmota Support Chat. The chat is a better and more dynamic channel for helping you. Github issues are meant for Tasmota Software Bug Reporting.

Please check the Contributing Guideline and Policy and the Support Guide.

Thanks.

---

Support Information

See Wiki for more information.
See FAQ for common questions/answers and links if none of your question is in the list
See Chat for more user experience.
See Community for forum.
See Code of Conduct

[Antexa]

Can anyone confirm Shelly 2.5 still fully works with Tasmota 8.1.0? My energy measurements are not working or showing up.

I just flashed it and this is what my interface looks like:

I followed this guide https://tasmota.github.io/docs/#/devices/Shelly-2.5 and used template:

{"NAME":"Shelly 2.5","GPIO":[56,0,17,0,21,83,0,0,6,82,5,22,156],"FLAG":2,"BASE":18}

My serial logging is off

01:03:43 CMD: Group 0, Index 1, Command "STATUS", Data "0"
01:03:43 RSL: stat/tasmota/STATUS = {"Status":{"Module":0,"FriendlyName":["Tasmota","Tasmota2"],"Topic":"tasmota","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":0,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0}}
01:03:43 RSL: stat/tasmota/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"tasmotas","OtaUrl":"http://thehackbox.org/tasmota/release/tasmota.bin","RestartReason":"External System","Uptime":"0T00:17:28","StartupUTC":"2020-02-22T23:46:15","Sleep":50,"CfgHolder":4617,"BootCount":14,"SaveCount":44,"SaveAddress":"F8000"}}
01:03:43 RSL: stat/tasmota/STATUS2 = {"StatusFWR":{"Version":"8.1.0(tasmota)","BuildDateTime":"2019-12-25T12:33:25","Boot":31,"Core":"2_6_1","SDK":"2.2.2-dev(38a443e)","Hardware":"ESP8266EX","CR":"329/699"}}
01:03:43 RSL: stat/tasmota/STATUS3 = {"StatusLOG":{"SerialLog":0,"WebLog":4,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["Butchery IoT",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["0020880A","0105C8000100060000005A00000000000000","00000000","00000000"]}}
01:03:43 RSL: stat/tasmota/STATUS4 = {"StatusMEM":{"ProgramSize":566,"Free":436,"Heap":27,"ProgramFlashSize":2048,"FlashSize":2048,"FlashChipId":"1540EF","FlashMode":3,"Features":["00000809","8FDAE397","043683A0","22B617CD","01001BC0","00007881"],"Drivers":"1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,29","Sensors":"1,2,3,4,5,6,7,8,9,10,14,15,17,18,20,22,26,34"}}
01:03:43 RSL: stat/tasmota/STATUS5 = {"StatusNET":{"Hostname":"tasmota-6366","IPAddress":"192.168.3.112","Gateway":"192.168.3.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.3.1","Mac":"80:7D:3A:74:58:DE","Webserver":2,"WifiConfig":4}}
01:03:43 RSL: stat/tasmota/STATUS6 = {"StatusMQT":{"MqttHost":"","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_7458DE","MqttUser":"DVES_USER","MqttCount":0,"MAX_PACKET_SIZE":1000,"KEEPALIVE":30}}
01:03:43 RSL: stat/tasmota/STATUS7 = {"StatusTIM":{"UTC":"Sun Feb 23 00:03:43 2020","Local":"Sun Feb 23 01:03:43 2020","StartDST":"Sun Mar 29 02:00:00 2020","EndDST":"Sun Oct 25 03:00:00 2020","Timezone":"+01:00","Sunrise":"07:44","Sunset":"18:22"}}
01:03:43 RSL: stat/tasmota/STATUS10 = {"StatusSNS":{"Time":"2020-02-23T01:03:43","Switch1":"OFF","Switch2":"OFF","ANALOG":{"Temperature":43.1},"TempUnit":"C"}}
01:03:43 RSL: stat/tasmota/STATUS11 = {"StatusSTS":{"Time":"2020-02-23T01:03:43","Uptime":"0T00:17:28","UptimeSec":1048,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Butchery IoT","BSSId":"7A:8A:20:0F:93:DB","Channel":5,"RSSI":82,"Signal":-59,"LinkCount":1,"Downtime":"0T00:00:07"}}}

01:05:33 CMD: Group 0, Index 1, Command "STATUS", Data "8"
01:05:33 RSL: stat/tasmota/STATUS8 = {"StatusSNS":{"Time":"2020-02-23T01:05:33","Switch1":"OFF","Switch2":"OFF","ANALOG":{"Temperature":44.5},"TempUnit":"C"}}
01:05:35 CMD: status 9
01:05:35 SRC: WebConsole from 192.168.1.105
01:05:35 CMD: Group 0, Index 1, Command "STATUS", Data "9"
01:05:35 RSL: stat/tasmota/STATUS = {"Status":{"Module":0,"FriendlyName":["Tasmota","Tasmota2"],"Topic":"tasmota","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":0,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0}}

What could be wrong?

I would expect the energy parameters to show up even if the hardware isn't working correctly.

I have more Shelly 2.5's that I could try. I just did a Shelly 1PM which showed energy measurements correctly. I just don't know if this is a hardware or software issue. This specific Shelly 2.5 was never used with the stock firmware.

@JeremiahGillis Did you manage to get it works ?

[JeremiahGillis]

Can anyone confirm Shelly 2.5 still fully works with Tasmota 8.1.0? My energy measurements are not working or showing up.

@Antexa Sorry for the delay. Yes, I was able to get mine work on a different Shelly 2.5. I flashed Tasmota 8.1.0 on another Shelly 2.5 and it functioned correctly.

My problem was a hardware issue. I flashed the device in question back to stock firmware. The energy measurements did not work. So, the energy measurements only seem to show up if the energy IC is detected over I2C. Not intuitive when you have faulty hardware.

[Antexa]

Hey @JeremiahGillis, I also revert back to stock firmware 👎
I think this issue happen some time, I saw it on Discord channel, this might be helpfull for another people.

[kugelkopf123]

@Antexa I can't see any problems when using a Shelly2.5 and Tasmota. I have installed 8 of them in my house and they all run wonderfully. For months.
Since version 9 the bug with the high temperature caused by the ADE IC has also been solved. just install the latest version. Take the template from the official site: https://templates.blakadder.com/shelly_25.html Enter the Template, Choose module 0 as Device and everything is fine.
If you like, you can also find links to further information on calibration.
If they are used as shutter control, just search for "Blinds and Shutters" in the Tasmota Docs.

[michalskrivanek]

FWIW I'm seeing similar issues. I flashed 3 Shellies via OTA with https://github.com/yaourdt/mgos-to-tasmota, all of them to Tasmota 8.5 , first worked like a charm, the other two do not have power monitoring. They all did work with stock firmware.
Tried downgrading to Tasmota 8.2 and re-set template (as a desperate try per #9692, I do have both loads connected) - didn't help. Reset power couple times, sometimes i2cscan returned errors (error 4 on 0x39), sometimes no device detected. It did come up eventually on the third shelly (while I was at Tasmota 8.2, with 60s+ power off)...but I still don't see any meaningful pattern - the first shelly always works, the second one doesn't, the third one is currently working. Soft restarts with restart 1 or reset 5 doesn't seem to make any difference.
I have all of them in wall and difficult to power cycle so I didn't do that many tests, but it's definitely fishy...

[StarvingDeveloper]

I have similar issue - flashed over air with mg2x and upgraded to v9. So had hard time convert to new template format. Then spent some time till made monitoring showup, but for me only 1 line and I cant make both line show power monitoring whatever I do.
So we all should unite and find out it's faulty shelly devices or tasmota firmware got many undocumented settings which make our devices act weird.

[kugelkopf123]

Dont get it...
why not simply flash via cable. No problem. Works like a charm.

[StarvingDeveloper]

Dont get it...
why not simply flash via cable. No problem. Works like a charm.

Not everyone want spend life diging deep in this shit, buying programers, dig trought wiki for days and such. Some bought shelly to use it and forget it got instaled. Then see such thing as tasmota exist and posible flash over air, so why dont try? Especialy this first time when I see diference flashing over air and via cable. Problem somewhere else, and even if I would buy programer nd flash firmware via cable problems would stay since people have 3 shelly devices and all 3 act diferent.