Support for Shelly 3EM

[goodkiller]

Hello

#11909

Seems like Shelly 3EM is not supported yet. Shelly 3EM is 3 phase energy monitor. It's very similar as regular EM and 2.5.

Unfortunately both templates does not work currently well. 3EM is using ADE7880 chip.

Here is some information what I already digged out.

A terminal is connected to ADE7880 > pins 7 & 8
B terminal is connected to ADE7880 > pins 9 & 12
C terminal is connected to ADE7880 > pins 13 & 14
N terminal is connected to ADE7880 > pins 15 & 16

Some library to communicate with ADE7880
https://github.com/NazimBL/ADE7880

ESPhome component
https://github.com/michaelpiron/esphome/blob/dev/esphome/components/ade7880/ade7880.h

Many thanks!

[vtainc]

Any news about support this device? Is it possible or will be possible it the feature? I also have this device and want to go to tasmota firmware.

[plewka]

ADE7880 looks interesting from datasheet view.
"Does not work well"...what does this mean?

[sfromis]

It means that goodkiller just tried templates for very different devices, and found them to not be working for this one.

Getting this device supported is up the usual question of someone with the right combination of hardware, interest, skills and time sits down to do the work, an submit a PR.

[plewka]

Ok, I'm interested in that one, too.
Would be nice to know if the ADE is at least found on I2C bus. It could be useful to follow
the i2c tracks on the PCB...ADE-Pin37/38 to the ESP...

[goodkiller]

Hello. Thanks for showing up interest about this device. Those PCB tracks are so tiny, hard to trace it down. I suggest to get one of this device, how else you can try to dev with it :)

[plewka]

You're right. I'd take a modern multimeter ;-)
I'm fluctuating between a low cost version like that and a version which is matching a solar controller...
Tasmota is preferred of cause.

[goodkiller]

Can you share which one is low cost version of it?

[plewka]

Shelly is anounced ~€100 until tomorrow in their shop.

That's quite cheap with this compact form including the transformers and really easy to handle.
Shelly maybe is not a "premium manufacturer" but I was very happy with them up to now and the
controller does full sampling of faster harmonics.
If you look for compatible and useful meters for Kostal they are at €360+ if I remember correctly.
One or two of these are supported in Tasmota as far as I remember.

[michaelpiron]

Hi @goodkiller ,
Thanks for opening this discussion. I see you referenced my ESPhome code for the ADE7880 (the energy monitoring chip that’s inside the Shelly 3PM), thanks for that.
Please note that this code is not tested yet.
I created the code by modifying the existing ADE7953 (Shelly PM single phase) integration for ESphome, and taking into account the ADE7880 datasheet specifications.

The reason I started to develop this integration is the fact that I have a 3-phase grid connection without neutral (3x230V, 230V between phases). This is not supported by standard Shelly firmware, however the ADE7880 supports it. Basically, a specific register inside the ADE chip has to be set to a specific value. (Datasheet: https://www.analog.com/media/en/technical-documentation/data-sheets/ADE7880.pdf )

Currently I’m still stuck with some issues in setting up the integration. If someone could help me out with that, it would be a win-win: not only my ESPhome integration would be ready then, it would also be a solid base for a Tasmota integration.

The issues I’m still facing:

• Which are the connections between ESP and ADE chip? I have to know which GPIO pins of the ESP are connected to the IRQ’s of the ADE. I can’t see this visually on the PCBs without desoldering the top and bottom PCB, and even then I’m not sure if it can be deduced from the PCB tracks.
• physically: which type of pins/headers do I need to flash the 3EM. The connection header is rather small.
• There are quite some calibration constants to figure out. Anyone who is familiar with this or who could reverse engineer it from the Shelly 3PM firmware binary?

[michaelpiron]

Setting the GPIO linked to the ADE’s IRQ in a correct way is important, as wrong configuration can lead to heating of the device and potential fire hazard! Refering to this related issue: #7991 (comment)

[Axel830]

I took a series of pictures of the PCB an stiched them together. Additionally I measured som connections of the ADE7880:
ADE Pin 29 (/IRQ0) -> ESP8266 Pin 12
ADE Pin 32 (/IRQ1) -> ESP8266 Pin 24
ADE Pin 36 (SCLK/SCL) > ESP Pin 9, via R36 to VDD
ADE Pin 37 (MISO/HSD) > NC
ADE Pin 38 (MOSI/SDA) > ESP Pin 10, via R35 to VDD
ADE Pin 39 (/SS/HSA) > via R46 to VDD

Perhaps this helps.

[michaelpiron]

Fantastic! Thank you @Axel830 ; based on these pin mapping I can continue my effort on an ESPhome integration/component

[sfromis]

I don't have the hardware.

1. You can usually use a multimeter in continuity mode (beeping) to trace what's connected to what.

2. That 6-pin header row looks a lot like what Shelly is using on other devices. It usually works with something like the wires from a solid core Ethernet cable. On Shelly 2.5 (very similar headers) I used the metal parts of a Dupont female header, twisted to push into the small holes. Worked perfectly.

3. Calibration constants should be derivable from the specs (did not read them), and using a known good meter for calibration. The latter is the usual calibration procedure for Tasmota, having the user input the correct value, and let the driver calculate the constants to match.

[sendingstrings]

I've got a 3EM in hand. Handy with a meter. How can I help?

[barbudor]

Identify the circuit / draw the schematic of all connections between the ADE7880 and the ESP

[goodkiller]

Any progress with it? Community, lets pump it up! :)

[barbudor]

Would you give me a unit ?
No plans to spend 120€ on it just to please the community for now 😂

[boehla]

I would give you one, if you want to do it.

[barbudor]

I don't have much time now but would be happy to help in March.

[AndreKR]

I have ordered one with the intention of dumping the I2C communication, but it's on backorder and won't arrive until next month.

[degreal]

Shelly is advertising this product that it can detect leaks and energy theft using optional neutral clamp but failed to deliver. I'm starting to think Tasmota is the answer, Shelly has not responded to this issue since July.

[barbudor]

I'm not sure that Tasmota would be the solution either.
Tasmota model would be to mesure the power on each phase.
I'm not sure how to detect a leak/theft unless all your equipment is mono phase and distributed on the 3 phase and using neutral. In that case the sum of powers on 3 phase should be equal to the power on neutral, wouldn't it?
A 3 phase equipment such as a motor would be connected to the 3 phases but not to neutral. Would it be considered a theft?

[AndreKR]

I got my device and did a little bit of research.

Obligatory safety warning: Do not try to repeat this without the necessary equipment. There are voltages inside the Shelly that can kill you. I powered the Shelly off an isolation tranformer, ran the USB through a USB isolator and put the whole setup into an IKEA SAMLA box before plugging it in.

Note that I had the current transformer flipped, so everything is reported as negative. Oopsie, sorry for that.

First some more photos of the PCB.

Overview front and back:

The core part magnified:
The backside is mirrored and aligned, so you can flip between them to follow the traces through vias. It seems to be a 4-layer board though. On the back side photo I took the RTC battery out so we can see what's underneath.

Pinouts for reference:

Datasheets: ADE7880, PCF85363A

I took three captures, one while having the ESP externally powered by 3.3V (the power rails of ESP and ADE are not directly connected, but it seemed to answer anyway), one with an incandescent light bulb (242 V, 0.11 A, PF 100, 27.9 W) and one with a CFL lamp I had lying around (242 V, 0.09 A, PF 52, 11.5 W).

Here are the original captures, they can be opened with Saleae Logic 2:
captures.zip

In general the communication looks like this:

1: After powerup the ESP will first talk to the PCF85363A RTC (7-bit I2C address 0x51) that is also on board. Ignoring this here.
2: Following a low-pulse on IRQ1 (possibly triggered by that) it will talk to the ADE7880 (I2C addr 0x38).
3-7: After that there's a pulse on IRQ0 once every second that seems to trigger some communication. The first two conversations (3 and 4) are different, all of the rest look very similar to each other.

As described in the datasheet on page 76 the ADN follows a register read/write pattern for all(?) I2C communication, so I have interpreted the I2C communication in terms of register reads/writes like this:

rel_time addr dir   reg    data
    7.092 0x38 read  0xE503 0x01A08000
    7.093 0x38 read  0xEA01 0x35
    7.093 0x38 read  0xE9FE 0xE503
...

i2c.txt

Those only show the communication with the ADN and you should be able to easily identify the conversations from the relative timestamps in the first column.

The datasheet (p. 79) describes a burst mode to read multiple registers. I believe in my file those would simply show up as a long read, but the longest read I observed was 4 bytes, so it doesn't seem to use the burst mode. (Of course those 4-byte reads might be multiple 1-byte or 2-byte registers, I didn't check the register lengths.)

[arendst]

Just ordered one and will try to write a driver based on yuor findings.

[arendst]

Based on the above information I wrote the driver for the Shelly 3EM (ade7880). It is default disabled (USE_ADE7880) so you'll need to compile it first.

I haven't tested it as I do not have the hardware yet so if someone is willing to, be my guest and report back.

Remember to make a firmware copy first before installing tasmota.

[arendst]

Latest PR results in this:

Still need to do calibration and GUI change like Sonoff SPM:

[goodkiller]

Did you published a branch with this example?

[arendst]

As always in development

[arendst]

Did some research and for now it's very important to make a 4M firmware dump BEFORE you install tasmota with ADE7880 support.

The Shelly 3EM firmware dump contains calibration parameters in a JSON file called calib.dat.

{
  "state": 0,
  "rms": {
    "current_a": 3166385,
    "current_b": 3125691,
    "current_c": 3131983,
    "current_n": -1474892307,
    "current_s": 1756557,
    "voltage_a": -767262,
    "voltage_b": -763439,
    "voltage_c": -749854
  },
  "angles": {
    "angle0": 180,
    "angle1": 176,
    "angle2": 176
  },
  "powers": {
    "totactive": {
      "a": -1345820,
      "b": -1347328,
      "c": -1351979
    },
    "apparent": {
      "a": 214966,
      "b": 214961,
      "c": 214949
    }
  },
 "energies": {
    "totactive": {
      "a": 8752,
      "b": 8751,
      "c": 8751
    },
    "apparent": {
      "a": 40496,
      "b": 40513,
      "c": 40524
    }
  }
}

The parameters in this file currently need to be added in to file xnrg_23_ade7880.ino. See below:

#define ADE7880_AIGAIN_INIT     3166385      // rms, current_a
#define ADE7880_BIGAIN_INIT     3125691      // rms, current_b
#define ADE7880_CIGAIN_INIT     3131983      // rms, current_c
#define ADE7880_NIGAIN_INIT     1756557      // rms, current_s !!
#define ADE7880_AVGAIN_INIT     -767262      // rms, voltage_a
#define ADE7880_BVGAIN_INIT     -763439      // rms, voltage_b
#define ADE7880_CVGAIN_INIT     -749854      // rms, voltage_c
#define ADE7880_APHCAL_INIT     180          // angles, angle0
#define ADE7880_BPHCAL_INIT     176          // angles, angle1
#define ADE7880_CPHCAL_INIT     176          // angles, angle2
#define ADE7880_APGAIN_INIT     -1345820     // powers, totactive, a
#define ADE7880_BPGAIN_INIT     -1347328     // powers, totactive, b
#define ADE7880_CPGAIN_INIT     -1351979     // powers, totactive, c

Once done the possibly negative power values turn to the correct values like

As I mounted all three current sensors on the same power line one can see I have an issue with L3 constantly showing wrong values.

I plan to release this driver on a 4M tasmota image allowing to use our filesystem to strore the calib.dat file.

[arendst]

NB. latest template is

{"NAME":"Shelly 3EM","GPIO":[1,1,288,1,32,8065,0,0,640,8064,608,224,8096,0],"FLAG":0,"BASE":18}

using the former link led also for relay state.

[rossi75]

.> {"NAME":"Shelly 3EM","GPIO":[1,1,288,1,32,8065,0,0,640,8064,608,224,8096,0],"FLAG":0,"BASE":18}

using the former link led also for relay state.

I have a question regarding the second LED, is it possible to adress it? Then it would make sense to use one LED for the relay, the other one for WiFi link (and mqtt processing).

[charly181274]

Das würde mich auch sehr interessieren wie man die zweite LED benutzen kann.

[rossi75]

Das würde mich auch sehr interessieren wie man die zweite LED benutzen kann.

I tested all gpios. But none of them lit the red led.

I assume that this led will be set and unset via the new ade7880 chip...

[rossi75]

Das würde mich auch sehr interessieren wie man die zweite LED benutzen kann.

The 3em pro version has also a led connected via the ade Chip. So i assume that without any special feature request, the red led won't lit any further with tasmota Firmware

[michaelpiron]

Great progress, thank you @arendst . With my limited, rusty coding skills this would have taken me ages... ;-)

Would it be possible to support different wiring configurations?

Standard setting

With the current/standard register settings, the ADE7880 is capable of measuring three single-phase loads or a 4-wire wye load:

Possibility to measure 3-wire delta load

I would like to use the Shelly 3EM in configurations with a 3-wire delta load (some homes have a 3-wire connection without neutral, a delta configuration). This can be enabled by setting a specific register of the ADE7880:
According to datasheet ADE7880 page 45:

Pg 50:

Looking into the AN-639 Application note:

[pieterdt]

Are you sure?

[michaelpiron]

I believe you should look at the references to the right of the “Attenuation network” blocks. The left side is the outside of the Shelly

[pieterdt]

Yes @michaelpiron , but those voltage of A and C are measured against B, due to lack of N, hence I think L2 should be connected to both B and N. Otherwise, with B unconnected, those voltage will not measure anything meaningful.

[michaelpiron]

My interpretation is that in 3phase3wire mode, the chip will measure two voltages:

• voltage between Vcp and Vn. This would be the voltage between our wires L3 and L2.
• voltage between Vap and Vn. this would be the voltage between our wires L1 and L2.

that’s why I don’t think a connection to terminal B is needed.
I would connect:

• wire L1 to terminal Va on the Shelly
• Wire L2 to terminal Vn
• Wire L3 to terminal Vc

however, I don’t think it does any harm to bridge L2 wire to terminal Vn and Vc. It’s just not necessary

[Mousketeer]

@michaelpiron @pieterdt I'm very much lost on how to connect the wiring in 3-wire delta (no neutral) mode. I've compiled a tasmota 13 with these changes (hopefully).

The config you suggested (L1-Va, L2-Vn, L3-Vc) appears to have reasonable values, except that the voltage on L2 is shown as 0V - this is not unexpected, as that sensor is disconnected, but has the effect of all the amps producing zero watts ;-).

Bridging L2-Vn-Vb together has the effect of the L2 grid frequency going wonky (96 to 198Hz, in a 50Hz country..). The voltage is also still 0.

Bridging L1-Va-Vb together gives plausible values for voltage, frequency and current, but the L2 active power (and power factor) goes negative. These negative values are subtracted from the total. This is with the clamp in the correct orientation and no power generation going on. (I guess I could invert the clamp??)

(I can't remember if I tried a L3-Vc-Vb config, I'll try again if need be).

Lastly, I tried L1-Va, L2-Vb, L3-Vn with external 3.3V DC power supply. Frequency & current appear correct. But the voltage is shown as 138V, thus the power calculations are way off. The power factor is currently also showing weirdly low values, but potentially this is just my specific load. I'll go around the house with a resistive load later to test.

So all in all no correct configuration thus far.
I see two more options:

1. Use the suggested L1-Va, L2-Vn, L3-Vc, but somehow guesstimate the voltage - the phase shift is constant and the voltage doesn't differ much between phases.
2. Perhaps somehow use ground (the literal earth connection, so this is not the neutral as I don't have one) as a reference to the configuration with the external 3.3V source? This surely violates some safety codes, but as long as there is no current...

But I wouldn't know where to start... Any help welcome :-)

[goodkiller]

Well.... thats funny now. I installed my 3EM to electricity enclosure and did proper installation. After trying to install custom firmware, device resets itself. This happens after applying template ({"NAME":"Shelly 3EM","GPIO":[1,1,288,1,32,8065,0,0,640,8064,608,224,8096,0],"FLAG":0,"BASE":18}):

00:00:00.001 HDW: ESP8266EX
00:00:00.050 CFG: Loaded from flash at F8, Count 12
00:00:00.055 QPC: Count 1
00:00:00.057 CFG: CR 340/699, Busy 0
00:00:00.062 ROT: Mode 1
00:00:00.071 SRC: Restart
00:00:00.073 Project tasmota - Shelly 3EM Version 11.0.0.3(QW-3EM-TEST)-2_7_4_9(2022-03-09T13:24:15)
00:00:00.226 WIF: Checking connection...
00:00:00.227 WIF: Attempting connection...
00:00:00.563 WIF: Connecting to AP1 IoT Channel 6 BSSId 32:23:03:E0:D9:98 in mode 11n as tasmota-D68BD5-3029...
00:00:02.426 APP: Button1 multi-press 1
00:00:02.427 WIF: Checking connection...
00:00:02.428 WIF: Attempting connection...
00:00:03.427 WIF: Checking connection...
00:00:03.428 WIF: Connected
00:00:03.680 HTP: Web server active on tasmota-D68BD5-3029 with IP address 192.168.1.193
00:00:04.432 WIF: Sending Gratuitous ARP
00:00:04.433 NTP: Sync time...
00:00:04.481 RTC: UTC 2022-03-09T11:29:18, DST 2022-03-27T02:00:00, STD 2022-10-30T03:00:00
12:29:18.001 RTC: Synced by NTP
12:29:18.206 RSL: INFO1 = {"Info1":{"Module":"Shelly 3EM","Version":"11.0.0.3(QW-3EM-TEST)","FallbackTopic":"cmnd/DVES_D68BD5_fb/","GroupTopic":"cmnd/tasmotas/"}}
12:29:18.211 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-D68BD5-3029","IPAddress":"192.168.1.193"}}
12:29:18.222 RSL: INFO3 = {"Info3":{"RestartReason":"Software/System restart","BootCount":5}}
12:29:18.230 RSL: RESULT = {"POWER":"ON"}
12:29:18.233 RSL: POWER = ON
12:29:20.441 QPC: Reset
12:29:22.409 APP: Boot Count 5
12:29:22.670 HTP: Main Menu
12:29:23.267 CFG: Saved to flash at F7, Count 13, Bytes 4096
12:29:23.382 RSL: STATE = {"Time":"2022-03-09T12:29:23","Uptime":"0T00:00:11","UptimeSec":11,"Heap":28,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":30,"MqttCount":0,"POWER":"ON","Wifi":{"AP":1,"SSId":"IoT","BSSId":"32:23:03:E0:D9:98","Channel":6,"Mode":"11n","RSSI":76,"Signal":-62,"LinkCount":1,"Downtime":"0T00:00:05"}}
12:29:35.348 HTP: Main Menu
12:29:36.894 HTP: Configuration
12:29:37.454 WIF: Checking connection...
12:29:37.826 HTP: Configure Module
12:29:39.032 HTP: Configuration
12:29:39.132 HTP: Configuration
12:29:56.815 HTP: Configure Other
12:29:57.425 WIF: Checking connection...
12:29:58.861 RSL: RESULT = {"Reset":"Reset and Restarting"}
12:29:59.206 CFG: Use defaults

What makes it odd is that before installation (using only one phase) works well...

[arendst]

I think the I of IO needs to be connected.

[arendst]

Any phase will do

[goodkiller]

I don't. I is Line input for contactor control. It's isolated. 3EM gets it's power from V(A/B/C).

[arendst]

You're right.

What is the output of command i2cdriver?

[goodkiller]

19:08:41.657 CMD: i2cscan
19:08:41.676 RSL: RESULT = {"I2CScan":"Device(s) found at 0x38 0x51"}

[arendst]

Something different. As Tasmota currently cannot calibrate the device it's important to start the Shelly firmware at least once.

Then add the device to your network and access webpage http:///calib.dat. Store the information in a safe place as it is needed again when Tasmota is installed.

[AndreKR]

https://shelly.cloud/knowledge-base/devices/shelly-3em/#tab_624733fb153bf

[kopfkraft]

thanks for the info!!! will give it a try!

[AndreKR]

@kopfkraft As usual please disconnect mains power before connecting anything to the programming port.

Also remember to download calib.dat from the original Shelly firmware before you flash Tasmota.

[pieterdt]

@sfromis , which one would be gnd? the one on the side of the sensors or the side of the line connections?

[pieterdt]

nvm found it by googling for pinout

[meidlinga]

I flashed a build with these flags enabled via OTA, applied the template, the calibration data as Rule and enabled Option 21. (many times :))
It startet to work only, after I went to Configure module and saved it once.

I am not sure why, but wanted to leave this here for people struggling at the same point.

[goodkiller]

How did you get calibration data. Any instructions?

[barbudor]

As written above:

Also remember to download calib.dat from the original Shelly firmware before you flash Tasmota.

[meidlinga]

@goodkiller This part is also described here: https://templates.blakadder.com/shelly_3EM.html

[ArturZurawski]

Do I have to anything else than what's described in https://templates.blakadder.com/shelly_3EM.html ?
Run SetOption21 1 in console.
Flashed with http://ota.tasmota.com/tasmota/tasmota.bin
Can't see any readings :(

[muebau]

Well I am not sure if I understand it correctly. I used the Shelly 3EM with the original firmware for the last ~6 month and got positive values every second.
Now with Tasmota (with calib.dat) I get negative values without changing the clamps. I guess this means the clamps are installed 'correctly' (according to the original firmware).

As I need the data for a scientific project I thought to go back to the original firmware as I was not able to set the update interval to 'every second' like it was before with the original firmware (TelePeriod 10).

I have a normal setup (no solar). I will check the direction of the clamps (even if it was fine with the original firmware).

[AleXSR700]

I will look up the tool to revert to Shelly's stock and post it either tonight after work or this weekend.

What I could imagine is, that Shelly changed the logic and that is why for some devices the clamp needs to be installed according to instructions and for some the opposite direction. And tasmota always uses the same logic.

But that is pure speculation and why I reocmmended to flip them and then attach a know device to ensure that the measurements themselves are accurate afterwards.

P.S.: Kind of a stupid question, but when you copied the values to the compilation options and to the rule, you checked that the numeric signs of your original calb.dat and the template are the same, right? Really just covering all bases here :D

[muebau]

Thank you lot. Yes I checked everything a few time as I also expected me for this mistake ;-). I think I will check with the original firmware and than with Tasmota again to make sure I don't miss some stupid mistake.

In the end I need to figure out how to get a full picture (power, power factor, voltage ...) every second as it was with the original firmware. If I am lucky I get the harmonics working to.

[AleXSR700]

As I said, I would try the clamps first because tasmota does give you a lot of options on how to handle your data.
You could even filter what you publish via MQTT and probably even publish as quickly as you like (basically real-time) using rules.

You may also be able to get real-time data with something like SetOption108. But I cannot test myself right now, so maybe that is not the one.

If you decide to stick with Tasmota, the discord channel also offers excellent expert support. :)

[AleXSR700]

https://github.com/yaourdt/tasmota-to-mgos

[saulous]

Hello together,
i have a Problem with the Tasmota Flashed Shelly 3EM.

I have Flashed the Shelly 3EM with this Instruction : "https://www.congenio.de/infos/shelly3em.html"
I don't have self compiled the Tasmota Firmware. On this website the Firmware can be downloaded.
(At first Minimal Firmware, then tasmota.bin.gz 14.0.0 )

Both Firmware Upgrades i have installed at the Shelly.
Tasmota has been startet up.

Actually i can switch the relais in the shelly. But no Measurement will be shown. (see Picture)

i2cscan in the console :

01:36:13.351 CMD: i2cscan
01:36:13.376 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x39 0x51"}
01:36:22.278 CMD: i2cscan
01:36:22.305 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x39 0x51"}
01:36:23.154 CMD: i2cscan
01:36:23.179 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:23.717 CMD: i2cscan
01:36:23.744 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x39 0x51"}
01:36:24.282 CMD: i2cscan
01:36:24.307 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:24.782 CMD: i2cscan
01:36:24.806 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:25.183 CMD: i2cscan
01:36:25.208 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:25.691 CMD: i2cscan
01:36:25.716 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x39 0x51"}
01:36:26.621 CMD: i2cscan
01:36:26.645 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:27.027 CMD: i2cscan
01:36:27.053 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:27.450 CMD: i2cscan
01:36:27.474 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:27.851 CMD: i2cscan
01:36:27.877 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:28.251 CMD: i2cscan
01:36:28.276 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:28.704 CMD: i2cscan
01:36:28.730 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:29.053 CMD: i2cscan
01:36:29.078 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x39 0x51"}
01:36:29.498 CMD: i2cscan
01:36:29.523 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:29.906 CMD: i2cscan
01:36:29.931 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x39 0x51"}
01:36:30.321 CMD: i2cscan
01:36:30.347 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x39 0x51"}
01:36:30.779 CMD: i2cscan
01:36:30.805 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x39 0x51"}
01:36:31.132 CMD: i2cscan
01:36:31.158 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:31.534 CMD: i2cscan
01:36:31.560 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x51"}
01:36:32.789 CMD: i2cscan
01:36:32.814 MQT: stat/tasmota_755DC5/RESULT = {"I2CScan":"Device(s) found at 0x39 0x51"}

The ADE Chip will be found for a short time. Is this normal ?

i2cdriver in the console :

09:58:50.830 CMD: i2cdriver
09:58:50.842 MQT: stat/tasmota_755DC5/RESULT = {"I2CDriver":"7,65"}

rule0 in the console :

01:39:20.309 CMD: rule0
01:39:20.320 MQT: stat/tasmota_755DC5/RESULT = {"Rule1":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}
01:39:20.324 MQT: stat/tasmota_755DC5/RESULT = {"Rule2":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}
01:39:20.330 MQT: stat/tasmota_755DC5/RESULT = {"Rule3":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":300,"Free":211,"Rules":"on file#calib.dat do {"rms":{"current_a":3166385,"current_b":3125691,"current_c":3131983,"current_s":1756557,"voltage_a":-767262,"voltage_b":-763439,"voltage_c":-749854},"angles":{"angle0":180,"angle1":176,"angle2":176},"powers":{"totactive": {"a":-1345820,"b":-1347328,"c":-1351979}},"freq":0} endon"}}

Can anyone help me with this Problems ?

[JayBraker]

Which exact tasmota.bin.gz 14.0 did you install - where did you download that?
I had to compile the firmware myself (13.5) because the default build, available as a Github Release, did not include the necessary drivers (see #13515 (comment)) I am unsure what the config for Github releases is and why back then the driver was not configured
But from your observations I anticipate that the default build still doesn't include USE_ADE7880

So head over to tasmocompiler and build a custom firmware image:)
That should do the trick

[JayBraker]

I am unsure what the config for Github releases is and why back then the driver was not configured But from your observations I anticipate that the default build still doesn't include USE_ADE7880

Had another look, USE_ADE7880 is still not part of the provided builds. You need to compile yourself to use Shelly 3EM properly
(Build configurations: https://github.com/arendst/Tasmota/blob/6673fb906bdc755eddbfc71d85e3eb9b9d11cd91/BUILDS.md)

So you can simply follow the steps I described right in the previous Thread: #13515 (reply in thread)

[saulous]

Hello, thank you for your Help. I have compiled and uploaded the Firmware in the 3EM. The result is the same like before :(
The Tasmota Version now is 14.1.0.

[rossi75]

Can you try uploading the firmware via serial? Be aware to not upload it via serial If 230v connected in any way

[madduck]

This thread seems to be the only resource for the 3EM, so I hope it's okay that I turn here with a question… two actually.

I had a spare 3EM and so decided to do a total house measurement. It's wired up right behind the "official" utility meter. I saved and restored calib.dat, of course. But the meter's readings are off. See the following graph, which shows the "official" meter in red, and the 3EM in blue over a period of a few days with measurements at random points in time. They shouldn't diverge this much in just a week:

My first question is: Is there a way to calibrate the meter in its current position, using the data from the official meter?

Second, when I try to use EnergyTotal[123] …kwh… to set the total energy measurement to match that of the main meter, that's not idempotent. If I run EnergyTotal[123] to get the current readings, and then I set the total to those readings, something else seems to get written. A new call to EnergyTotal[123] will produce a different number. Similarly, it's impossible for me to actually make the meter display e.g. 88,456 kWh, the current house reading, because if I enter this, or a third for each phase, then I get a much smaller total.

Can someone shed some light on this, or maybe refer me to a better forum (I have already posted this on Discord, but nobody replied…)? Thank you!

[rossi75]

To your second issue....

I have in mind that there was sth with a max value, 65535.....? Hence it either goes into negative or will just count upwards.
Can you share the logs as soon as you enter a new value...?

To which tasmota firmware did you compile?

To your first question, If the value is about 10% less than the official one, i simply would try to multiply the values given from the dat with 1.10.
Maybe only one Phase is affected, then you need to figure out this one phase

[madduck]

I have in mind that there was sth with a max value, 65535.....? Hence it either goes into negative or will just count upwards. Can you share the logs as soon as you enter a new value...?

Sure:

10:32:56.464 CMD: Backlog EnergyTotal; EnergyTotal1 101193087; EnergyTotal2 101187399; EnergyTotal3 101117501
10:32:56.489 MQT: stat/tas-house/RESULT = {"EnergyTotal":{"Total":[101193.109,101187.914,101117.602],"Yesterday":[6.035,5.596,1.882],"Today":[1.697,1.826,0.800],"ExportActive":[0.000,0.000,0.000]}}
10:32:56.720 MQT: stat/tas-house/RESULT = {"EnergyTotal":{"Total":[101194.805,101187.914,101117.602],"Yesterday":[6.035,5.596,1.882],"Today":[1.697,1.826,0.800],"ExportActive":[0.000,0.000,0.000]}}
10:32:56.961 MQT: stat/tas-house/RESULT = {"EnergyTotal":{"Total":[101194.805,101189.742,101117.602],"Yesterday":[6.035,5.596,1.882],"Today":[1.697,1.826,0.800],"ExportActive":[0.000,0.000,0.000]}}
10:32:57.214 MQT: stat/tas-house/RESULT = {"EnergyTotal":{"Total":[101194.805,101189.742,101118.398],"Yesterday":[6.035,5.596,1.882],"Today":[1.697,1.826,0.800],"ExportActive":[0.000,0.000,0.000]}}

So it turns out that the values aren't completely off anymore, since I figured out that EnergyTotal reports kWh, but actually wants Wh when setting. That is arguably a bug.

To which tasmota firmware did you compile?

I've compiled this for 12.5.0.

To your first question, If the value is about 10% less than the official one, i simply would try to multiply the values given from the dat with 1.10. Maybe only one Phase is affected, then you need to figure out this one phase

There are 22 different values in the DAT file. I wouldn't know which ones to modify. And wasn't that the entire point of saving the calib.dat file? Or was the device not properly calibrated when new?

[jeroenst]

Is it with tasmota also possible to use the 3em not as 3 phase measure device but as 3 seperate circuits in a single phase installation?

In which case kwh is calculated separately per ct coil? In the last few pictures I saw the kwh is summed.

I want to use one coil for grid measurement, one coil for ess and one coil for backup power.

According to shelly documentation, this functionality is included in the original shelly firmware, but I prefer Tasmota.

[sfromis]

Not using the device, but the drawings on the Shelly page about the device does include one example with one phase connected to all 3 inputs, and then the clamps on each of 3 outputs.
https://kb.shelly.cloud/knowledge-base/shelly-3em

Tasmota does have SetOption129 for "enable split total energy results", which sounds like something you'd be interested in.

[jeroenst]

Thank you! Actually, wiring diagram 2 on the Shelly page is about 1 phase and 3 loads.

Setoption129 sounds good.

[jeroenst]

Is it also possible to monitor the N connection ADE7880 > pins 15 & 16 as a separate measurement?

[jeroenst]

I flashed the 3em with 14.3.0 and defined USE_ADE7880 on building with tasmocompiler. I also did rule3 with the calibration data but still I have no readings. I also applied the template and selected the template in the settings. What am I doing wrong?

[sfromis]

Maybe check if you actually have the driver included, as I mentioned earlier in this thread:

If the driver is included, output from the command I2CDriver should include index 65 for ADE7880. And the command I2CScan should list address 0x38. Of course, then you should also see the ADE7880_IRQ pins in the config dropdown.

[arendst]

Using this template:

{"NAME":"Shelly 3EM","GPIO":[1,1,288,1,32,8065,0,0,640,8064,608,224,8096,0],"FLAG":0,"BASE":18}

My Shelly 3EM shows:

[jeroenst]

I applied this template, but i2cscan fails:

12:34:16.849 CMD: i2cdriver
12:34:16.854 RSL: RESULT = {"I2CDriver":"65"}
12:34:21.607 CMD: i2cscan
12:34:21.627 RSL: RESULT = {"I2CScan":"No devices found"}

[jeroenst]

A powercycle fixed it all. Thank you for support!

[jeroenst]

Is it possible to set the amps to 0? They have an offset of 13mA.

[jeroenst]

I also found a small bug, active power disappears and show again. I thought it was only hidden when 0 but it is sometimes also show when it is 0.

[sfromis]

Your images suggest that "Active Power" is specifically not 0, when it shows as "-0" rounded to zero decimals. Using WattRes, you can get decimals. Likewise, VoltRes and FreqRes are there, if/when you want to look for details.

[jeroenst]

It is about active power total, in picture1 it is not shown, in picture2, a second later it show up again.

[arendst]

Active Power Total only shows up if both positive and negative phases are detected. Or in your case no loads which is a special case anyway.

[jeroenst]

It was only for a moment on my test bench. Now it is mounted into the fusebox where there is always energy flowing it will not happen.

[jeroenst]

I found another little issue. As I have solar panels, my current is flowing backwards, but the current shown in Tasmota is still shown as a positive value and should be a negative value. Watt is indeed negative, which is right.

[jeroenst]

I understand, but also at Victron which is a big manufacturer of on grid and off grid inverters they use negative current values at the ac side. So a negative ac current isn't a strange thing to display.

[tl-photography]

It is actually not correct in a alternating voltage system, where also the current is actually alternating and only the angle between it indicates the power flow.

Victron is simplifying here to get a more compact visualisation.

https://en.wikipedia.org/wiki/Power_factor

[jeroenst]

And I also think this simplification is easier to understand for many people.

[Jason2866]

Wrong keeps wrong. Anyways theoretical discussion. Theo answered already.

[jeroenst]

I think we have to agree we disagree. But no problem as I can convert it in Nodered easily and watt is more important to me than current. So again I want to thank the Tasmota team for all the work and support they do and have done. Thank you.

[jeroenst]

I also have a 0 reading once in a while, is this a know issue?

16:44:52.602 RSL: SENSOR = {"Time":"2024-11-30T16:44:52","ENERGY":{"TotalStartTime":"2024-11-30T13:18:05","Total":[0.012,1.144,-0.001],"Yesterday":[0.000,0.000,0.000],"Today":[0.012,1.144,-0.001],"TodaySumImport":1.582,"TodaySumExport":0.427,"ExportActive":[0.000,0.000,0.000],"Power":[0,0,0],"ApparentPower":[0,0,0],"ReactivePower":[0,0,0],"Factor":[0.00,0.00,0.00],"Frequency":[0,0,0],"Voltage":[0,0,0],"Current":[0.000,0.000,0.000],"CurrentNeutral":0.011}}
16:44:55.594 RSL: SENSOR = {"Time":"2024-11-30T16:44:55","ENERGY":{"TotalStartTime":"2024-11-30T13:18:05","Total":[0.012,1.144,-0.001],"Yesterday":[0.000,0.000,0.000],"Today":[0.012,1.144,-0.001],"TodaySumImport":1.582,"TodaySumExport":0.427,"ExportActive":[0.733,0.000,0.001],"Power":[331,318,0],"ApparentPower":[454,427,3],"ReactivePower":[311,285,3],"Factor":[0.73,0.74,0.09],"Frequency":[50,50,50],"Voltage":[242,242,242],"Current":[1.888,1.777,0.014],"CurrentNeutral":0.011}}

[jeroenst]

For anyone that isn't able to compile tasmota for Shelly3EM here is a prebuild binary tasmota 14.4.0 shelly3em tls.bin.gz

These lines where added in user_config_override.h:
#define USE_ADE7880
#define USE_MQTT_TLS

[jeroenst]

Probably you first need to flash the tasmota factory .bin and after that flash it with the gz file via the tasmota menu.

[sfromis]

There are no .factory binaries when it is ESP8266 instead of ESP32. Initial wired flashing cannot be a .gz binary, but tasmota.bin should do, before upgrading.

[jeroenst]

You're right, factory is only for esp32

[Nazarbayevv]

Yes, but I used mgostotasmota

Can you give link for shelly 3em, please? I found for lot of models, but no 3em.

[jeroenst]

I think I used http://dl.dasker.eu/firmware/mg2tasmota-Shelly3EM.zip

[Nazarbayevv]

Hello,

Can I use Tariff for off-peak configuration with shelly 3em? If yes, does it works for each phase or summary for all phases?

[sfromis]

No devices are by themselves writing to flash all the time. Whatever firmware you use (including Tasmota) can decide when to update flash. To avoid wearing down flash, Tasmota is not doing it all the time, only when settings are saved for other reasons, or at midnight. It would be possible to make a small automation to save more frequently.

I'm not doing that, but basing my energy monitoring data on the payloads published via MQTT. This facilitates things like plotting data without a drop, even if the Tasmota total might have reverted a few hours in case of me inadvertently having caused a "very local" outage.

[Nazarbayevv]

Thank you. So "Energy Today" at 00:00 will be move to "Energy Yesterday", "Energy Total" will be updated and it all will be writing to flash, isn't it?

[sfromis]

Yeah, the running "Energy Total" is not kept anywhere, it is a sum of "Energy Today" and what "Energy Total" was updated to at midnight.

[Nazarbayevv]

And I hope latest question:) After power off and restart device I will lose "Energy Today", but I keep "Energy Yesterday" and "Energy Total" the day before, isn't it?

[sfromis]

Yes, only energy numbers since last save will be lost if you do the bad thing of cutting input power without first doing a save.

[Nazarbayevv]

Hello. Strange situation

I configured Off-Peak tariff, but it calculation is wrong:

08:05:31.893 MQT: stat/Shelly_3EM/RESULT = {"Tariff":{"Off-Peak":{"STD":"23:00","DST":"23:00"},"Standard":{"STD":"07:00","DST":"07:00"},"Weekend":"OFF","Forced":"1"}}

My time is 8:10. It should set value to tariff 2, but it still set value to tariff 1:

08:10:23.268 MQT: tele/Shelly_3EM/SENSOR = {"Time":"2025-01-20T08:10:23","ENERGY":{"TotalStartTime":"2025-01-19T00:04:06","Total":33.509,"TotalTariff":[33.508,0.000],"Yesterday":2.279,"Today":31.231,"TodaySumImport":31.230,"TodaySumExport":0.000,"ExportActive":[0.000,0.226,0.194],"ExportTariff":[0.420,0.000],"Period":[75,28,44],"Power":[5270,1706,2671],"ApparentPower":[5303,3356,5141],"ReactivePower":[593,2890,4392],"Factor":[0.99,0.51,0.52],"Frequency":[50,50,50],"Voltage":[223,216,217],"Current":[23.801,15.543,23.725],"CurrentNeutral":0.012}}

[Nazarbayevv]

I recompiled firmware by myself and "Forced" parameter changed to "0" and now it works correctly

[mmmmm009]

Hi,

I wonder If it's also possible to get THD (total harmonic distortion) from ADE7880 (the chip itself supports this parameter)?

[muebau]

It should be possible as I wrote in #13515 (comment) .

If the setup section for the ADE7880 would be extended to initialize the needed registers all would be set to trigger the harmonics calculation regularly. A simple 'script' command with a parameter could be provided to trigger the calculation.