Support for Shelly 2.5 #5592

JoergTiedemann · 2019-04-06T13:23:06Z

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 · 2019-04-06T13:23:59Z

Not yet. Mine is on the way.

peterforeman · 2019-04-06T14:12:53Z

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

arendst · 2019-04-06T14:17:45Z

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 · 2019-04-06T14:26:13Z

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

curzon01 · 2019-04-10T08:37:35Z

Correction:
D2/GPIO4 = Relay1 ✅
D8/GPIO15 = Relay2

Be warned: ⚠️
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 · 2019-04-10T09:56:43Z

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 · 2019-04-10T12:33:42Z

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

arendst · 2019-04-11T09:54:37Z

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 · 2019-04-11T10:28:27Z

Pls report back if the above template functions as expected.

Tommi-nrw · 2019-04-11T11:31:40Z

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 · 2019-04-11T12:03:54Z

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 · 2019-04-11T12:06:28Z

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

arendst · 2019-04-11T15:03:00Z

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 · 2019-04-13T16:27:43Z

First readings are in:

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

joba-1 · 2019-04-13T19:59:47Z

nice progress -- iphone so i typo

Add Shelly 2.5 Energy Monitoring (#5592)

ascillato2 · 2019-04-15T13:35:19Z

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

Thanks 👍

curzon01 · 2019-04-15T14:51:45Z

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 · 2019-04-15T15:14:11Z

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 · 2019-04-15T15:48:31Z

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

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

ArturGabrys · 2019-06-23T15:36:33Z

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 · 2019-06-24T02:09:14Z

@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 · 2019-07-12T18:57:10Z

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 · 2019-07-12T19:05:15Z

@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 · 2019-07-17T21:15:20Z

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 · 2019-07-18T07:07:17Z

See #6036 and use the precompiled dev version.

zkolb · 2019-07-22T07:29:50Z

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 · 2019-08-25T20:48:42Z

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

JeremiahGillis · 2020-02-23T00:09:18Z

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 · 2020-02-23T04:44:18Z

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 · 2020-10-29T12:43:12Z

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 · 2020-11-09T01:04:44Z

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 · 2020-11-09T07:04:59Z

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 · 2020-11-09T10:08:18Z

@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 · 2020-11-19T18:00:12Z

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 · 2020-11-21T11:59:28Z

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 · 2020-11-21T16:40:52Z

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

StarvingDeveloper · 2020-11-22T13:05:38Z

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.

Omega236 · 2021-02-03T08:36:28Z

@michalskrivanek

i have the same problem that i have no Powermeter with a shelly2.5 i flashed over OTA.

is there any solution?

michalskrivanek · 2021-02-03T13:04:04Z

I converted two more and met same issue, but both magically started to work after template changes and 60s+ power off eventually (not on a first try). I would guess it may have something to do with residual charge somewhere or temperature...but I have no idea really and can't reliably reproduce anything.
For reference on 9.2.0 template I use {"NAME":"Shelly 2.5","GPIO":[320,0,32,0,224,193,0,0,640,192,608,225,3456,4736],"FLAG":0,"BASE":18}

Omega236 · 2021-02-03T18:34:42Z

@michalskrivanek
You are right, after a while and without electricity, the energy display worked.

But unfortunately the ENERGY_Total is not split.

arendst · 2021-02-04T17:22:07Z

If you see the same error again where the readings are gone pls try to push the reset button on the device and let me know if this solves the issue.

If so I can make a more neat reset solution.

foobar26 · 2021-07-17T21:22:18Z

Had the same issue, but reverting back to version 7.2.0 and resetting the template fixed the issue for me.
I then went back to 8.5.2 (where I started with the OTA) and energy monitoring was still there. Maybe this helps others to fix their issues as well.

gitmaster2013 · 2022-01-02T11:38:06Z

Had the same problem ShellyFW(everythingWorking)-OTA->tasmota(10.1.0)-tasmota-Upgrade->tasmota-DE(10.1.0)

The first OTA was:
http://dl.dasker.eu/firmware/mg2tasmota-Shelly25
Working config:
{"NAME":"Shelly 2.5","GPIO":[320,0,32,0,224,193,0,0,640,192,608,225,3456,4736],"FLAG":0,"BASE":18}
https://templates.blakadder.com/shelly_25.html

I just had to turn of the CircuitBreaker (for about 30min). After that the page refreshed and the values appeared.

AleXSR700 · 2022-09-09T11:29:34Z

Same here. I had to remove all 2.5 from the grid and then the power monitoring worked.

Hoerli1337 · 2023-01-13T12:01:02Z

I can confirm this.
After flashing with the OTA tool, the Shelly must be without power for >30 minutes.
Only then are the energy values displayed.

AleXSR700 · 2023-01-19T17:31:52Z

I can confirm this.
After flashing with the OTA tool, the Shelly must be without power for >30 minutes.
Only then are the energy values displayed.

For me it was just a few seconds.

ascillato2 added question Type - Asking for Information Currently unsupported device labels Apr 9, 2019

arendst self-assigned this Apr 11, 2019

arendst added enhancement Type - Enhancement that will be worked on and removed question Type - Asking for Information labels Apr 11, 2019

arendst removed the Currently unsupported device label Apr 11, 2019

RavenSystem mentioned this issue Apr 13, 2019

Shelly 2.5 compatibility RavenSystem/esp-homekit-devices#280

Closed

arendst added a commit that referenced this issue Apr 14, 2019

Add Shelly 2.5 Energy Monitoring (#5592)

6adb513

Add Shelly 2.5 Energy Monitoring (#5592)

arendst added the fixed Result - The work on the issue has ended label Apr 14, 2019

arendst removed their assignment Apr 14, 2019

ascillato2 closed this as completed Apr 15, 2019

tonilopezmr mentioned this issue Jul 14, 2019

Support Shelly 2.5 xoseperez/espurna#1827

Merged

AleXSR700 mentioned this issue Sep 9, 2022

Shelly 1PM power monitoring not working after first flash #16472

Closed

9 tasks

Hoerli1337 mentioned this issue Jan 13, 2023

[Site issue] Template wrong - Shelly 2.5 blakadder/templates#1660

Closed

Support for Shelly 2.5 #5592

Support for Shelly 2.5 #5592

Comments

JoergTiedemann commented Apr 6, 2019

arendst commented Apr 6, 2019

peterforeman commented Apr 6, 2019

arendst commented Apr 6, 2019

peterforeman commented Apr 6, 2019 • edited Loading

curzon01 commented Apr 10, 2019 • edited Loading

arendst commented Apr 10, 2019 • edited Loading

meingraham commented Apr 10, 2019

arendst commented Apr 11, 2019 • edited Loading

arendst commented Apr 11, 2019

Tommi-nrw commented Apr 11, 2019

curzon01 commented Apr 11, 2019

arendst commented Apr 11, 2019

arendst commented Apr 11, 2019 • edited Loading

arendst commented Apr 13, 2019

joba-1 commented Apr 13, 2019 via email

ascillato2 commented Apr 15, 2019

curzon01 commented Apr 15, 2019 • edited Loading

arendst commented Apr 15, 2019 • edited Loading

curzon01 commented Apr 15, 2019

ArturGabrys commented Jun 23, 2019

meingraham commented Jun 24, 2019

MaximilanPower commented Jul 12, 2019 • edited Loading

meingraham commented Jul 12, 2019

zkolb commented Jul 17, 2019

arendst commented Jul 18, 2019

zkolb commented Jul 22, 2019

stefanbosch commented Aug 25, 2019

JeremiahGillis commented Feb 23, 2020 • edited Loading

ascillato commented Feb 23, 2020

Support Information

Antexa commented Oct 29, 2020

JeremiahGillis commented Nov 9, 2020 • edited Loading

Antexa commented Nov 9, 2020

kugelkopf123 commented Nov 9, 2020 • edited Loading

michalskrivanek commented Nov 19, 2020

StarvingDeveloper commented Nov 21, 2020

kugelkopf123 commented Nov 21, 2020

StarvingDeveloper commented Nov 22, 2020

Omega236 commented Feb 3, 2021

michalskrivanek commented Feb 3, 2021

Omega236 commented Feb 3, 2021

arendst commented Feb 4, 2021

foobar26 commented Jul 17, 2021 • edited Loading

gitmaster2013 commented Jan 2, 2022

AleXSR700 commented Sep 9, 2022

Hoerli1337 commented Jan 13, 2023

AleXSR700 commented Jan 19, 2023

peterforeman commented Apr 6, 2019 •

edited

Loading

curzon01 commented Apr 10, 2019 •

edited

Loading

arendst commented Apr 10, 2019 •

edited

Loading

arendst commented Apr 11, 2019 •

edited

Loading

arendst commented Apr 11, 2019 •

edited

Loading

curzon01 commented Apr 15, 2019 •

edited

Loading

arendst commented Apr 15, 2019 •

edited

Loading

MaximilanPower commented Jul 12, 2019 •

edited

Loading

JeremiahGillis commented Feb 23, 2020 •

edited

Loading

JeremiahGillis commented Nov 9, 2020 •

edited

Loading

kugelkopf123 commented Nov 9, 2020 •

edited

Loading

foobar26 commented Jul 17, 2021 •

edited

Loading