What a smart plug kWh reading tells you
A smart plug or plug-in energy monitor can show how much energy an appliance used during the period you measured. That measured kWh can be more useful than label wattage when runtime is hard to estimate, the appliance cycles on and off, or the device has standby draw.
The result prices the measured appliance period with the rate you enter. What that rate reflects depends on its source; the reading still describes the measured appliance period, not the full electricity bill.
Check compatibility before measuring
Confirm that the model records energy in kWh; remote switching or an instantaneous W display alone is not a cumulative energy reading. Not all smart plugs include energy monitoring, as TP-Link's smart-plug FAQ illustrates. Check the manual for your exact model and regional version.
Use a plug-in monitor only when its documented load rating, voltage, plug type, and the appliance instructions allow it. Do not use one with equipment or wiring it is not designed to monitor. If that setup is not suitable, use another reliable kWh source instead of forcing a plug-in measurement.
Do not adapt a household plug-in monitor to hardwired equipment or an incompatible dryer or air-conditioner connection. If an appliance requires a direct wall connection, a smart plug or meter is not an exception. For portable electric heaters, follow CPSC's direct-to-wall and no-use-while-sleeping guidance.
Measure one clearly timed period in six steps
- Confirm the monitor is suitable for the appliance, then reset its session reading or write down the cumulative start kWh.
- Connect only the appliance being measured; include a power strip only if both sets of instructions permit it and the combined load is within the monitor's limits.
- Record the start time, appliance mode, and any devices deliberately included on the same strip.
- Run the selected cycle, session, day, or multi-day period without silently changing that boundary.
- Record the end time and end kWh. For a cumulative display, subtract the start reading from the end reading.
- Price that measured difference, then repeat the measurement before scaling if the period was unusual or variable.
Illustrative cumulative-reading example: a monitor starts at 18.420 kWh and ends at 19.105 kWh after one named period. The appliance used 19.105 - 18.420 = 0.685 kWh during that period. At an illustrative rate of 0.205 per kWh, that period costs 0.685 x 0.205 = 0.140425, displayed as 0.14 in the currency used for the rate.
Decide whether the measurement is long enough
Use measured kWh for the period you actually checked. Measure longer before scaling irregular use, especially when the appliance cycles, sits idle, or changes from day to day. Label the period as ordinary, deliberately high-use, or diagnostic before using it as evidence for a longer estimate. Measure only when the estimate depends on an uncertain appliance or setup; stable wattage and runtime can answer a narrower question directly.
Scroll horizontally to see all columns.
| Measured period | Use it for | Be careful before scaling when... | Better next step |
|---|---|---|---|
| One cycle or one short use | That cycle or short use | Use varies from cycle to cycle | Measure more cycles |
| One day | A same-day estimate | Weekday and weekend habits differ | Measure several days |
| Several days | A repeated-use estimate | The period was unusual | Keep the measured dates or context visible |
| Whole setup on one strip | Combined setup cost | You need individual device cost | Measure devices separately only if needed |
| No measured kWh | A fallback estimate | Watts or runtime are uncertain | Use watts only as a fallback |
Before scaling, match the appliance or setup, operating mode, and ordinary-use conditions. Keep the start and end readings and dates with the result, and keep an unusual run as a diagnostic record rather than a normal month.
Third-party activity window: where the boundary starts and stops
Third-party dataset example. The REFIT README maps House 1 Appliance6 to a
dishwasher monitor. Readings above 10 W identify the active cluster, but the published boundary also keeps 298
quiet seconds before it and 298 quiet seconds after it. On December 1, 2014, the selected window runs from 03:56:21 to
04:41:01 UTC, with 397 readings and 396 integrated intervals; it does not mean power stayed continuously above 10 W.
The last above-threshold reading is at 04:35:56 and applies until the next sample at 04:36:03. The 298-second quiet tail starts at that next sample, not at the last active timestamp. Counting from 04:35:56 would wrongly call those seven active seconds quiet.
The calculation includes only House 1 Appliance6. It excludes the whole-home aggregate, other
appliance channels, and unmonitored loads. Practical Calculator Guide did not measure this household or dishwasher;
it selected and integrated a bounded interval from the cited third-party dataset.
Integrating every selected cleaned-source row inside that boundary gives 0.937419 kWh; the highest reading is 2,306 W. At the separate illustrative rate of 0.205 per kWh, that dataset-derived interval costs approximately 0.192171, or about 0.19, using the unrounded integrated kWh. The last reading closes the final interval; no energy is added beyond 04:41:01.
The source instrument is not evidence about a particular consumer smart plug. Its practical lesson is the boundary: include readings on both sides of the selected activity window so the cutoff is visible. If your plug reports cumulative kWh rather than power rows, subtract the start reading from the end reading for the same timed period.
REFIT warns that monitored appliance assignments could change during the study. Its cleaned-data documentation also describes forward-filled gaps and values replaced with zero; this CSV has no row-level imputation marker. Quiet edges therefore do not prove an uninterrupted, complete dishwasher program. This is a selected activity window, not a verified cycle length, a typical dishwasher cycle, or a smart-plug product test. See Methodology for the site's general handling of third-party datasets, cleaning caveats, calculations, and rounding.
Measured use vs wattage estimate
A wattage estimate answers a question about assumed wattage and runtime. A monitor reading answers a question about the period you recorded. Use the measured reading when it is representative of the appliance or setup you want to price; use watts only when those assumptions are easier to defend than a short or unusual reading.
Enter recorded kWh in the kWh to Cost Calculator and choose the period that matches the reading. If you do not have measured kWh and need a watts-based estimate, use the Appliance Electricity Cost Calculator instead.
If the priced appliance period does not explain the amount on a bill, compare the separate bill components in Why Your Electric Bill Is Higher Than the Calculator Estimate.