Beiträge von stfns

Confirmed working with Shelly 1:

https://www.aliexpress.com/item/400050552….283d4c4dEHWOpE

Tested with model: AC110-240V

Model AC85-AC265V NOT tested.

Confirmed working with the Shelly 1: Renkforce 4016139070186

It's produced and sold by Conrad: https://www.conrad.nl/p/renkforce-40…it-ip20-1425528

Only downside is it's size. You need 5cm+ in-wall space when combined with the Shelly 1.

I did some testing today, it is not the cables near the clamp, I made sure they were completely free. I switched some clamps, also with another 3EM, but no matter what phase 2 always gives me 0.15a and phase 3 0.37a.

I also tried with my other 3EM, it gave the exact same readings, while all the time my Testo says 0.0a.

I will contact support.

Zitat von archi

I have performed a check with my EM devices.

If the clamp has cable nearby. At the time it passes current by the cable, the clamp starts showing a small measure.

That could be my issue, there are lots of cables with current around it. I will see if I can adjust that. Thnx!

Zitat von Seven of Nine

Are you sure the clamps are connected to their "paired" connectors?
They are calibrated to the specific connector so Clamp A has to be connected to A, B to B and C to C..

Der Inhalt kann nicht angezeigt werden, da Sie keine Berechtigung haben, diesen Inhalt zu sehen.

Yes I doubled checked everything. Redid the wiring, still incorrect readings. I only have this issue with 1 Shelly 3EM, the other is working as expected. Only difference is, is that the other one is monitoring a 3 phase device.

Nobody?

Hello,

I have an issue with 1 of my Shelly 3EM's. It is set up to monitor 3x 1 phase according the "1 phase wiring up to 3 different circuits" as stated in the manual.

When there is no load (0W) on the phase I still see a current of 0.15A and 0.37A. I measured it with a separate clamp meter (Testo 770-3) and that displays the correct 0A.

When there is a load both the Shelly and my Testo display the same value.

Is this a bug? Others have witnessed the same behavior?

Firmware 20201124-092854/v1.9.0@57ac4ad8 but also the same on 20210122-155800/v1.10.0-rc1@00eeaa9b.