add smart plugs

[Mariusthvdb]

did some initial experimenting with my smart plugs and found the following interesting differences:

type ON OFF

Greenwave GWPN1 1.1 0.3

Fibaro FGWP102 0.8 0.3

Everspring AN158 0.5 0

Qubino Smart Plug 16A 0.5 0.3

Philips Smart plug 0.8 0

All numbers were measured on a Fibaro FGW102, which reported the power readings immediately. (even saw a couple of small initial spikes when inserting, or turning on, I guess depending on the led rings on some of these plugs)

the above could be considered power consumption in a normalized state

[nepozs]

Zero watt in standby mode is really impossible it just looks like Fibaro FGW102 is unable to measure power <0.3W.

[Mariusthvdb]

I've set it to include its own power and it uses 0.5 when off, and 0.9 even when on without further load!

At least, that's what the device reports in Z-WaveJs device config

[nepozs]

I understand, but this is only traditional math without using complex numbers and imaginary part, so it could be used only for strictly resistive load (not the case of any smart plug).
In reality their power factor is variable and much smaller than one.

I've measured some other smart-plugs (I have nice power meter but only manual):

manufacturer	model	power draw on	power draw standby	comments
WiFi hardware:
unknown	Oukitel P2	~0.85W	~0.55W	*
unknown	Blitzwolf BW-SHP6 version 15A	~0.8W	~0.4W	*
Shenzhen Hysiry Technology	Blitzwolf BW-SHP6 version 10A	~0.85W	~0.5W	*
Alterco Robotics	Shelly Plug S	0.82W	0.52W	measured with both LED settings off
Alterco Robotics	Shelly Plug S	0.82W	0.52W	measured with both LED settings on (surprisingly both measurements were identical)
TP-link	HS110	2.56W	1.77W	**
Zigbee hardware:
Signify (Philips)	Hue smart plug LOM002	0.91W	0.23W	normal situation
Signify (Philips)	Hue smart plug LOM002	0.92W	0.25W	when LED lights (only about 0,5 min. after state change)
Osram	Lightify Plug 01	1.04W	0.44W
Z-Wave hardware:
Fibaro	FGWP-102	****	****
Shenzhen NEO Electronic	NAS-WR01Z	~0.6W	~0.3W	***

*- "~" means unstable power draw, fluctuating between distant values
**- TP-link HS110 (and also HS100) is old construction based on completely different chipset (as I remember taken from WiFi router, so it connects very high-speed compared to others, but it has unnecessary high power draw)
***- measured years ago, so I don't remember how (but surely used power meter wasn't really accurate)
****- not measured yet

BTW I also have Z-Wave Fibaro FGWP-102 (probably, because I don't remember exact model and I can't verify model now, but it is "french" version - IEC "E" socket) but I believe it is one of most reliable smart sockets (in meaning of lifespan), so I use it in my remote location where I can be only once/twice per year (so it is a reason, why I can't promise any deadline when I will measure its power draw).

[CloCkWeRX]

#1006 started

[CloCkWeRX]

@bramstroker what would be the next step to get a few of these into an appropriate model.json?

There's a few of these that are more or less just waiting on a bit of guidance; ie:
#964 (comment)

While none of it would necessarily work out of the box, if the measurements are in roughly the right format; any extra code for auto detection has basically sample data to look at.

[bramstroker]

See this issue where there were extra options added to provide both standby_power and standby_power_on. #779

Also device_type needs to be set. Currently we have light and smart_switch as allowed options, but we can specify more in https://github.com/bramstroker/homeassistant-powercalc/blob/master/custom_components/powercalc/data/model_schema.json

Also I think it makes no sense to just add a power/energy sensor for only the standby power, so the user also needs to specify the power of the end-device.
We have an option in model.json to specify it cannot be automatically added without the user configurating it.
requires_additional_configuration.
Currently only a warning will be shown when this a smart switch is detected and not configured by the user "Model found in database, but needs additional manual configuration to be loaded". Maybe we can extend upon that in the future and also do something in the config flow, but that would be a topic on its own.

Also I should maybe have a look into sub dividing the supported_models.md for several device-types somehow, but I think it's no must when we only have a few non-light devices yet.

Hope this helps to get this started.

[thomaskonrad]

@nepozs, which exact power meter did you use for your measurements? I'm looking for one that can handle very small power values.

[nepozs]

@thomaskonrad
only for small power values (>0.1W manual measurement): Zhirui-tec PR10-D ("french" socket)
https://lygte-info.dk/review/Power%20Zhurui%20Power%20Recorder%20PR10%20UK.html
it has resolution 0.01W
and accuracy based on declared 0.5FS should not be worse than 0.10W (for values under 10W)
and… it is not a mistake - resolution for low values is often really better than accuracy
(but in reality using additional multimeters I've estimated accuracy as 0.005W-0.015W depending on power factor)
measure under 0.1W is not possible directly, but could be done by temporal estimation

edit: I've read now (linked above) review of pretty same model PR10-C (main and probably only difference is "german" socket) and the conclusions are the same there (but Henrik K. Jensen from lygte-info.dk has really better multimeter as comparative).

for other (>0.4W) automatic measurements Shelly Plug S.

---

If you need professional tool (but this one is really expensive and beyond my financial possibilities)
https://www.tme.eu/en/details/gm-m249a/portable-digital-multimeters/gossen-metrawatt/metrahit-energy/

edit2: haha he has used this one as comparative

[thomaskonrad]

Thanks for this detailed answer! It's really not easy to accurately measure low power values.