So I wanted to get myself a Kill-a-watt. Being who I am, I wanted information regarding its accuracy, especially at low power draws. I found a comparison with a industry grade equipment (Fluke is about the best out there in handheld electrical meters). It’s not encouraging, so I thought about a more proper meter, but it’s not easy to find an actual power meter that is accurate at low loads, isn’t a hassle to install and doesn’t cost an arm and a leg.
What do you use? Am I overthinking it?
Edit: thanks everyone for chiming in! To clarify a few things:
- I wasn’t (at least initially) looking for a permanent installation on my home server, but rather a good instrument to measure things around the house once I’m done fiddling with the server.
- the comparison with Fluke was just to illustrate what kind of error we can expect from a Kill-a-watt. It would be nice to have a Fluke power meter, but there’s nothing I do at home would even come close to justify it. The kill-a-watt is such an old design and the company behind it seems to focus on cheap trinkets. I was just hoping to find something a bit better than what P3 offers. Wouldn’t mind paying up to $75 for the same features and better accuracy.
- I looked for a multimeter that measured power somehow as I need a better one that can measure capacitance too anyway. Didn’t find it.
You must log in or register to comment.
Tasmota nous sametplugs work great and have a tiny footprint. They integrate nicely in home assistant. They must be calibrated once with a resistive load eg old light bulb.
If there is a problem at low power usage then you can easily solve it by temporary add more power. Lets say add a 40watt lamp or something, later remove it from the calculation.
While it sounds a bit hacky, I think this is an underrated solution. It’s actually quite a clever way to bypass the whole problem. Physics is your enemy here, not economics.
This is kind of like trying to find an electric motor with the highest efficiency and torque at 1 RPM. While it’s not theoretically impossible, it’s not just a matter of price or design, it’s a matter of asking the equipment to do something it’s simply not good at, while you want to do it really well. It can’t, certainly not affordably or without significant compromises in other areas. In the case of a motor, you’d be better off letting the motor spin at its much higher optimal RPM and gear it down, even though there will be a little loss in the geartrain it’s still a much better solution overall and that’s why essentially every low speed motor is designed this way.
In the case of an ammeter, it seems totally reasonable to bring it up to a more ideal operating range by adding a constant artificial load. In fact the high precision/low range multimeters and oscilloscopes are usually internally doing almost exactly the same thing with their probes, just in a somewhat more complex way behind the scenes.
I use Shelly Plus Plug S. Im not sure how accutate it is, but it does decent job for me. I feel like you are looking for something else, but wanted to mention shelly anyway
Are you looking to measure draw for one specific device or across circuits in your whole home. I’ve been considering two systems: IoTaWatt and Lantern Power Monitor. Both are open source and open hardware.
IoTaWatt uses entirely custom hardware for the actual device but serves its own webpage that can be accessed easily at home from any device and if you’re technically savvy can pass to other services. My reservation with it is if at some point in the future the hardware dies, how easy will it be to recreate if the main project goes dormant, even with the hardware open source? What if a chip manufacturer goes out of business or discontinues a part?
In contrast, the Lantern Power Monitor runs on Raspberry Pi with a relatively basic custom board you can solder yourself with minimal skill; I suspect you could even make it work with a breadboard. Recent shortages notwithstanding, Raspberry Pi seems to keep their models pretty available for a long time, so that inspires a little more confidence. On the flip side, the software primarily runs on a mobile app. There is an iPhone app but it doesn’t have as many features as the Android app. But what happens if the project is abandoned and the app is no longer updated to stay compatible with newer phones or operating systems? And the app by default sends the data to an outside server maintained by the main developer. He doesn’t charge for the hosting and it makes it easy to access from anywhere, but some people might have concerns about that. You can also configure it to self-host from the Raspberry Pi but then you need to have the know-how to make it accessible outside your home (if you want). Underneath it also relies on some other open source data analysis components and I assume if you really know what you’re doing you can pass it out to other software.
Of course, in the end I don’t have the budget to do either project right now.
It will be technically a bit more challenging, but I don’t think you need to use the lantern power monitor software with the device. The device seems to be built around two MCP3008 IC’s, which are basic 8 channel analog to digital converters. The values from these can be read and processed (like, sent to home assistant) using a python script on the raspberry. This is the kind of minimal programming effort someone with no experience could do using chatgpt.
Slight nitpick: Brymen handheld meters often have better specs in the handheld market, in particular when you are looking at a fixed price point.
You see a lot of Fluke meters around due to service agreement, as well as government and military contracts.
Don’t get me wrong, meters are fine, but there is no reason to spend that kinda money at home, unless the service manual of your washing machine explicitly states all measurements are to be done by a Fluke meter.
There was a youtube vid, testing multimeters, & there was a specific condition that produced wrong results in all the meters except Fluke, who had engineered to prevent that wrongness.
That was what decided me on trusting Fluke, in the future.
been years, no idea what channel it was on, sorry, but it should be findable for someone with patience, knowing that only the Fluke got it right, of the ones tested.
Do pay attention to the calibration-certificates, though:
Anybody paying for Fluke who ignores that their handhelds have no more than 2.5-digits of actual-accuracy, is foolish/incompetent.
( the cheap ones are sooo much worse… )
