Shelly devices

[michalk-k]

I'm currently measuring the following devices:

• Shelly 1
• Shelly 1PM
• Shelly 2.5
• Shelly Dimmer (v 1)
• Shelly i3
• Shelly 3EM
• Shelly EM
• Shelly Duo GU10
• Shelly Pro 3EM

Removed Shelly UNI and Shelly RGBW2 from the list since both are DC-powered only.

[bramstroker]

I just got the Shelly Pro 3EM delivered btw, so also measured it using Zhurui PR10, before installing it.
Measured 90% of the time 1.04W, jumping to 1.05 every now and then.
Curious what figures you get.

[bramstroker]

I will also check with mini PM gen3 tomorrow, got that device yesterday as well.
Did you only connect C clamp or also A and B?

[michalk-k]

Yeah, all 3 clamps are connected.

This is interesting; consumption depends on enabled interfaces (200 samples / sleep 0.5 sec).

eth+wifi_ap+wifi_clnt+bt: 1.379W
eth+wifi_clnt+bt: 1.3395W
eth+bt: 0.979W
eth: 0.930W
eth+wifi_clnt: 1.3175W
wifi_clnt: 1.0225W

What are we going to do with this?

Let alone, that it's expected that consumption will depend on scripts running too.

[bramstroker]

We could just provide 7 sub profiles where the user can choose from.
https://docs.powercalc.nl/library/sub-profiles/
I'm planning to connect via Eth only, so that profile will be applicable for me.
What do you mean with scripts?

[michalk-k]

All gen2 and gen3 devices can run JavaScript scripts inside. It is taxing on the device's CPU as any computing. Hence higher consumption.
While higher consumption is obvious, I have no idea how much.
For example, scripting is needed on gen2 to make BLE gateway from them. In gen3 the BLE gateway is built-in and may be turned on/off.
Also, have no data on how many people are using scripting.
There are more use-cases for sure

Ahh and I expect TLS will increase consumption for sure :)
Covering all possibilities is almost impossible. We are doing the best approximation. But let's not overdo that.

[bramstroker]

Yes, I would say the best we can do is provide some profiles for the common use cases.
I highly doubt people will bother with custom javascript besides the built in BLE proxy. When you have HA at your hands to do anything you want with the device regarding automations.

[michalk-k]

I think we need another device_type. it would work like power_meter but it's not. It doesn't measure anything. Also it has no relays. It's just a controller. I'm thinking about Shelly i3 and i4. Those have only inputs performing some actions based on them (sending events, switching scenes etc). What might be more challenging is, that it must not have any associated entities. It might generate events only.

For such cases would be comfortable to select a device instead. A tricky is, that device cannot exist without entities, lol.

[bramstroker]

I have added this device_type last week which is a perfect fit imo: https://docs.powercalc.nl/library/device-types/generic-iot/

[michalk-k]

Hahaha. you are so foreseeing

[michalk-k]

BTW Is there any benefit of using power_meter since we can use generic_iot ? Especially in context of devices like Shelly 3EM / Pro 3EM ?

[bramstroker]

No, but it's easier to find in the library to have it categorized.
No functional benefit besides that.