Evidence summary
This guide is based on current U.S. government, standards-owner, utility-data, manufacturer product, support, privacy, lifecycle, and recall sources initially assembled on July 26, 2026 and reviewed on October 16, 2026. It compares monitoring architectures, not brands: utility account data, utility-meter integrations, panel-level aggregate monitoring, selected-circuit monitoring, and plug-level measurement. No monitor was purchased, installed, calibrated, or hands-on tested for this guide. Manufacturer accuracy, data, savings, security, and support statements remain attributed claims rather than independent findings.
The market is in transition. Sense permanently stopped selling its consumer panel monitor by the end of 2025 while continuing support for installed units, and Schneider Electric marks the exact Wiser Energy Monitor reference WISEREM as discontinued as of June 2, 2026. Those products are therefore treated as legacy or transition evidence, not current default purchase routes. Amounts below are manufacturer-page observations reviewed on October 16, 2026, not live prices, checkout totals, installed totals, or lifecycle costs.
Quick answer
Choose the smallest monitoring layer that can answer the question. Start with the utility portal or Green Button data when monthly or interval trends are enough. Use a local plug-in meter for one accessible 120-volt plug load when you want a bounded measurement without an app or cloud account. Consider a utility-meter integration only after the exact utility, meter, address, enrollment, Wi-Fi, and data route are confirmed. Consider panel-level or selected-circuit hardware only when you truly need seconds-level whole-home or hardwired-load visibility, have permission, and have a qualified installation route for the exact panel.
No architecture is universally best. A renter may get more useful evidence from a utility download plus one temporary plug measurement than from a permanent panel device. A homeowner with several hardwired loads may need selected-circuit coverage. A billing dispute belongs with the utility bill, settlement meter, and approved metering process—not a consumer monitor.
Start with the decision, not the device
“How much electricity does my home use?” can mean several different questions. A monthly bill trend, a fifteen-minute load pattern, a seconds-level whole-home trace, a selected circuit, and one refrigerator are not interchangeable measurement problems. Before comparing hardware, write down the decision, the required time resolution, the loads that must be included, the acceptable account or cloud dependency, the retention and export need, and the permission boundary.
Scroll horizontally to see all columns.
| Buyer question | Likely first route | What it can establish | Important limit |
|---|---|---|---|
| Is total household use changing month to month? | Utility portal, bill history, or Green Button download | Account-level totals and available interval patterns | May not provide seconds-level or device-level data |
| How much does one accessible plug load use? | Local plug-in meter | Energy for the connected compatible load during the measured period | Does not cover hardwired, most 240 V, or shared-circuit loads |
| When does whole-home demand rise? | Utility-meter integration or aggregate mains monitor | Whole-home time pattern at the available interval | Aggregate data does not guarantee exact appliance identity |
| Which selected hardwired circuits use energy? | Selected-circuit monitor | Direct attribution for instrumented circuits | Uninstrumented and shared circuits remain unresolved |
| Do I need billing-grade evidence? | Utility bill, utility meter, or an approved metering route | The governing billing record and applicable review process | Consumer-monitor accuracy claims do not create billing authority |
| Will a permanent monitor change a decision? | No purchase or temporary measurement may be enough | A bounded answer without permanent complexity | Do not buy a dashboard without a defined action |
Takeaway: Resolution is a scope decision. Higher-frequency data is not automatically more useful, and more sensors do not automatically create better appliance attribution.
Method and update obligations
The routing method is deterministic, non-scoring, and fail-closed. It starts with safety/recall, billing-grade need, measurement question, housing access, utility eligibility, plug-load access, account/cloud acceptance, export need, time resolution, panel compatibility, qualified installation, and circuit count. It can return utility data, meter-linked, local plug, connected plug, aggregate mains, selected-circuit, hybrid, hold, incompatible, professional review, no purchase, or stop outcomes. It never chooses a brand or authorizes installation, billing treatment, or purchase. The version 2 software validation used 30 migrated synthetic fixtures, 16 invalid-input checks, 800 randomized property checks, 1,184 boundary combinations and 17 regressions. Repairs enforce unknown safety/recall, exact plug-load compatibility, connected meter account/local-data acceptance and export-fit gates. This article provides no interactive router, and those software checks are not physical installation, calibration, safety, eligibility or product-performance evidence.
Recheck the evidence when a utility changes Green Button or meter-integration support; a monitor is launched, retired, recalled, or changes price; an app, cloud, account, export, retention, privacy, or support route changes; panel or meter safety guidance changes; or related safety, comparison, integration, or apartment-audit guidance changes. Product, privacy, and safety triggers override a routine review calendar.
Architecture map: utility, meter-linked, panel, circuit, and plug
Scroll horizontally to see all columns.
| Architecture | Measurement boundary | Home installation | Typical resolution | Best-fit question | Stop or hold condition |
|---|---|---|---|---|---|
| Utility account data | Billing account or utility interval data | None | Monthly to interval, utility-dependent | Long-term trend and bill context | Required interval or fields are unavailable |
| Utility-meter integration | Compatible smart meter or home-area network | Usually no panel device, but enrollment and network setup apply | Potentially near-real-time, implementation-dependent | Whole-home visibility without panel-installed consumer hardware | Utility, meter, address, enrollment, or Wi-Fi is ineligible |
| Aggregate mains monitor | Whole-home service mains | Panel access; qualified-professional route for this guide | Seconds-level for current examples | Whole-home timing and aggregate load changes | Permission, panel fit, recall, or professional route is unresolved |
| Selected-circuit monitor | Instrumented branch circuits plus mains where supported | Panel access; qualified-professional route for this guide | Seconds-level for current examples | Direct selected-circuit attribution | Needed circuits cannot be safely or completely instrumented |
| Local plug-in meter | One compatible 120 V plug load | None beyond normal plug-in use | Local cumulative and live values | One appliance or device | Load is hardwired, 240 V, inaccessible, or beyond meter limits |
| Connected monitoring plug | One compatible controlled plug load | None beyond normal plug-in use | Vendor/app-dependent | One load with remote history or scheduling | Load-control safety, account, network, or retention route fails |
Use utility data first when it already answers the question
The U.S. Department of Energy’s Green Button overview distinguishes Download My Data from Connect My Data. Download My Data gives the customer a file from the utility. Connect My Data supports authorized transfer to a third party. Depending on the utility implementation, data may be available at fifteen-minute, hourly, daily, or monthly intervals. That range is why Green Button should not be described as universally real-time.
The Green Button utility directory is a discovery tool, not proof that a household is eligible or that every listed implementation has the same certification, fields, interval, or authorization process. Check the exact utility account, service territory, available date range, interval, units, time zone, export format, and whether the data is estimated or actual.
Scroll horizontally to see all columns.
| Check | Record | Pass condition | Unknown treatment |
|---|---|---|---|
| Account access | Exact utility and authorized account | Customer can lawfully access the data | Hold |
| Interval | Monthly, daily, hourly, or sub-hourly | Matches the decision | Do not call it real-time |
| Coverage | Service point, meter, date range | Includes the loads and period being analyzed | Hold or narrow the question |
| Units and timestamps | kWh, demand if present, time zone, daylight-saving treatment | Can be interpreted without silent conversion | Do not calculate |
| Transfer route | Manual download or authorized third party | Consent and revocation are understood | Use manual download or no transfer |
| Retention | Available historical period | Long enough for the buyer question | Export and preserve only as authorized |
Utility data can be the no-purchase answer for a renter who needs a seasonal trend or a before-and-after comparison. It is not a universal substitute for seconds-level events, direct circuit attribution, or a temporary measurement of one appliance.
Meter-linked routes are eligibility products, not universal smart-meter accessories
A smart meter does not automatically mean that a retail device can read it. The exact utility, meter technology, service address, enrollment process, network path, and account authorization must align. Emporia’s current Utility Connect support page lists a bounded group of U.S. utilities and describes a home-area-network registration route. The company’s direct product page displayed USD 39.99 when reviewed on October 16, 2026 and explicitly directs buyers to verify compatibility before purchase.
Sense also supports a utility-enabled smart-meter route for participating utilities and eligible addresses. Its eligibility guidance makes the utility invitation, exact meter, Wi-Fi, and current solar limitations part of the decision. This is separate from the older panel-installed Sense monitor, which is no longer sold to consumers.
Scroll horizontally to see all columns.
| Question | Why it matters | Safe treatment |
|---|---|---|
| Is the exact utility supported now? | Support can be territory- and program-specific | Use the current official eligibility route |
| Is the exact meter eligible? | Not every smart meter exposes the required interface | Confirm meter and account before purchase |
| Does the household have the required network? | Wi-Fi or another local path may be required | Hold when setup requirements are unknown |
| What data leaves the utility or home? | Account, authorization, app, cloud, and sharing may apply | Review consent, revocation, retention, and export |
| What happens when service ends? | The hardware may depend on a utility or vendor route | Record support horizon as known, unknown, or retired |
Panel-level aggregate monitoring answers timing, not guaranteed appliance identity
A mains monitor measures aggregate household current at the service level. That can reveal when the total load changes, support demand-pattern review, and provide a higher-frequency whole-home trace than many utility portals. It does not directly label every appliance. Software may infer patterns, but inference remains different from physically measuring a selected circuit or one plug load.
Emporia’s current Vue monitor page listed a mains-only configuration at USD 99.99 in its FAQ when reviewed on October 16, 2026. Emporia publishes a plus-or-minus two percent accuracy claim and describes one-second monitoring on its product page. Its current help page describes app updates within a few seconds. These are manufacturer statements, not independent calibration, latency or billing-grade findings.
Sense illustrates the limitation of software attribution. Its device-identification guidance explains that devices can remain unnamed and that household verification is required. Whole-home inference can be useful, but it cannot be treated as guaranteed identification of every load.
Selected-circuit monitoring trades installation scope for direct attribution
Selected-circuit sensors can directly associate data with instrumented branch circuits. That is more defensible than software guessing for a clearly separated circuit, but it does not automatically identify devices that share the circuit, and it says nothing about uninstrumented circuits. Circuit count, sensor fit, conductor arrangement, panel space, service configuration, and the exact loads of interest all matter.
Emporia displayed eight-sensor and sixteen-sensor Vue configurations at USD 149.99 and USD 199.99 when reviewed on October 16, 2026. The company states that one Vue can monitor up to sixteen individual circuits and that multiple units can be combined in the app. Those statements do not prove that a particular panel can accept the sensors, that every important circuit can be covered, or that several units create a simple or supportable installation.
Scroll horizontally to see all columns.
| Preflight item | Required record | Failure outcome |
|---|---|---|
| Permission | Owner, property, and applicable professional route | Keep existing setup or use utility/plug measurement |
| Exact panel identity | Manufacturer, catalog/model, date code where relevant | Hold; do not assume compatibility |
| Recall status | Current CPSC and manufacturer remedy records | Stop monitor planning until exact remedy route is complete |
| Service and conductor arrangement | Qualified assessment under the product manual | Professional review required |
| Sensor and space fit | Exact product/panel compatibility | Incompatible or narrower architecture |
| Needed circuit coverage | Named circuits and required resolution | Hybrid route or hold rather than false completeness |
| Installation and rollback | Qualified installation, documentation, and safe removal route | Use non-panel alternative |
Safety boundary: this guide provides no instructions for opening a panel, identifying conductors, placing current transformers, connecting breakers, measuring voltage, or working near service conductors. CPSC has recalled specific Schneider QO load centers and specific Siemens SolarReady meter combos for overheating or fire hazards. Those recalls do not apply to every panel, but they show why exact identity and remedy status are stop conditions—not footnotes.
Plug-level measurement stays within one compatible load
A local plug-in meter can answer a narrow question without panel access, vendor account, or cloud service. The P3 Kill A Watt EZ P4460 is documented for 115 VAC operation, 125 V maximum, 15 A maximum, and 1,875 VA maximum. P3 publishes a 0.2 percent accuracy claim. The company’s direct store displayed USD 34.99 and marked the item sold out when reviewed on October 16, 2026. That does not establish availability at other sellers. The claim remains manufacturer-provided and is not directly comparable with Vue’s claim because the architectures, boundaries, reference conditions, and methods differ.
A plug-in meter measures only the compatible connected load during the chosen period. It cannot directly measure a hardwired water heater, central air-conditioning circuit, electric range, most 240 V loads, or a shared circuit. A short test can also miss cycling, standby, seasonal, defrost, or behavior effects. Match the measurement duration to the decision.
A connected energy-monitoring smart plug can add remote history and automation, but it also adds app, account, network, update, retention, and load-control dependencies. Emporia displayed a four-pack at USD 34.99 when reviewed on October 16, 2026. The electrical and load-control decision remains separate: Emporia’s current product page warns against power-sensitive equipment such as refrigerators/freezers, medical or pet equipment and equipment affected by an outage. Use the exact model and load restrictions; monitoring does not make an unsuitable controlled load safe.
Scroll horizontally to see all columns.
| Route | Data location | Account/network | Best fit | Primary limitation |
|---|---|---|---|---|
| Local plug-in meter | Local display | None | Temporary or repeated measurement of one compatible load | Manual recording and no hardwired coverage |
| Connected monitoring plug | App/vendor route | Usually required | One compatible load with remote history | Control safety, retention, support, and cloud dependence |
| Utility interval data | Utility portal/download | Utility account | Whole-home trend without new hardware | No direct one-load attribution |
Data ownership, retention, and export are part of the product
NIST IR 8425 provides a useful consumer-IoT product-system frame: the device may depend on an app, cloud, account, updates, and support services. For a monitor, those dependencies can determine whether historical data remains available, whether local operation is possible, and what happens if the vendor changes the service.
Emporia’s cloud-architecture help page describes cloud access over 2.4 GHz Wi-Fi and no local API. The Vue 3 product page also lists Ethernet. Do not turn the help page’s Wi-Fi wording into an exclusive networking requirement for every Vue configuration; an active internet/cloud service remains part of the documented route. Its current storage documentation states that one-second data is retained for three hours, one-minute data for seven days, fifteen-minute data for one year through CSV export, and hourly/daily aggregates for the device lifetime. Sense’s current download guidance describes hour- or day-level CSV export through the Sense Home app for supported accounts. Confirm the current account, device and export limits before relying on that workflow. These are different retention and export contracts, not a universal “has export” feature.
Scroll horizontally to see all columns.
| Route | Account dependency | Local-only? | Export/retention question | Update risk |
|---|---|---|---|---|
| Utility portal or Green Button | Utility account | Downloaded file can be stored locally | Interval, history, file fields, consent | Utility implementation can change |
| Utility-meter integration | Utility plus vendor account may apply | No assumption | Current app/export and enrollment state | Utility and vendor support both matter |
| Emporia Vue | Vendor app/account | No; current support describes a cloud/internet dependency | Resolution-specific retention and CSV workflow | Vendor-controlled service and support |
| Legacy Sense panel monitor | Vendor account | No independent local-only route established here | Hour/day CSV export for supported accounts; confirm current app route | Hardware sales retired; support horizon must be monitored |
| P3 P4460 | None | Yes, local display | Manual transcription | Minimal software dependency |
| Connected smart plug | Vendor/platform-dependent | Do not assume | Exact retention and export per model | App, firmware, account, platform, support |
Do not rank manufacturer accuracy figures across architectures
Emporia’s plus-or-minus two percent claim and P3’s 0.2 percent claim look comparable when stripped from context. They are not enough for a ranking. A defensible comparison would require the same reference instrument, sample handling, load range, waveform, power factor, interval, installation conditions, calibration treatment, and uncertainty analysis. This guide has none of that direct evidence.
Accuracy is also not the only resolution question. A precise one-load meter does not answer whole-home demand. A whole-home monitor can be useful even when it cannot name every appliance. A circuit sensor can directly attribute a branch but not individual devices sharing that branch. A utility record can govern billing while still being too coarse for short cycling.
Dated product and market snapshot
The following examples document current or transitional routes. They are not a shortlist, recommendation, complete market census, or proof of independent performance.
Scroll horizontally to see all columns.
| Example | Architecture | Manufacturer-page observation reviewed October 16, 2026 | What the source supports | What remains unknown |
|---|---|---|---|---|
| Emporia Vue 3 mains-only | Aggregate mains | USD 99.99; manufacturer FAQ | Current configuration, declared sampling/accuracy, cloud route | Exact panel fit, installed cost, independent accuracy, long-term support |
| Emporia Vue 3 with 8 sensors | Mains plus selected circuits | USD 149.99 | Current eight-sensor configuration | Which circuits fit and whether coverage is sufficient |
| Emporia Vue 3 with 16 sensors | Mains plus selected circuits | USD 199.99 | Current sixteen-sensor configuration | Panel space, installation, multi-unit complexity |
| Emporia Utility Connect | Utility-meter integration | USD 39.99 | Current product and compatibility-check route | Exact utility, meter, address, enrollment and support duration |
| P3 Kill A Watt EZ P4460 | Local plug meter | USD 34.99; direct store marked sold out | Exact electrical limits and local-display route | Independent accuracy and long-duration workflow fit |
| Emporia monitoring plugs, four-pack | Connected plug measurement | USD 34.99 | Current product and device-level monitoring route | Exact load-control fit, retention and support horizon |
| Sense Home Energy Monitor | Legacy panel aggregate/inference | Consumer sales ended by December 31, 2025 | Existing-unit support and transition state | Future support duration; no current direct-purchase route |
| Schneider WISEREM | Legacy panel monitor | Discontinued June 2, 2026 | Exact end-of-commercialization status | Stock, support, app continuity and replacement route |
Tax, shipping, accessories, professional installation, panel work, subscription, future service costs, and checkout availability are excluded. A current direct price is not a complete ownership cost.
Market transition: separate legacy support from a new purchase
Sense’s support notice says the company permanently stopped selling its consumer Home Energy Monitor by December 31, 2025 or when inventory was exhausted, while continuing support for installed monitors. That creates two different decisions: an existing owner may still need support and export guidance; a new buyer should not treat old installation pages as evidence of current retail availability.
Schneider Electric’s exact WISEREM lifecycle page records end of commercialization on June 2, 2026 with no replacement for that reference. A category page, cached retailer result, or remaining stock display does not reverse an exact lifecycle notice. Legacy hardware may still matter to owners, but it should not be presented as a current long-term default.
Renter, permission, recall, and professional-review boundaries
Panel access changes the risk and permission profile. A renter should not infer permission from physical access, a removable sensor, or a product marketed as do-it-yourself. For this guide, work inside service equipment stays with a qualified electrical professional and the property decision owner. Emporia’s support page discusses DIY installation, while Sense’s installation guidance uses a licensed-electrician boundary. That difference does not relax this guide’s qualified route or establish one rule for every jurisdiction. This guide does not interpret any lease, electrical code, permit, insurance policy, or utility contract.
Scroll horizontally to see all columns.
| Condition | Guide outcome | Next safe route |
|---|---|---|
| Permission denied | No panel monitor | Utility data, temporary plug meter, or no purchase |
| Panel identity unknown | Hold | Qualified identification before product selection |
| Applicable unresolved recall | Stop | Complete exact manufacturer/CPSC remedy route |
| Panel fit or service arrangement unknown | Professional review required | Use a non-panel route meanwhile |
| Qualified installation unavailable | No panel architecture | Utility, meter-linked if eligible, or plug measurement |
| Billing dispute | Consumer monitor not controlling | Utility bill/meter and approved review process |
| Medical, emergency, or safety-critical decision | Outside scope | Use the applicable qualified/authority route |
A fail-closed buyer workflow
Scroll horizontally to see all columns.
| Step | Question | Pass action | Fail or unknown action |
|---|---|---|---|
| 1 | What decision will the data change? | Write the question and threshold | No purchase |
| 2 | What loads and time resolution are required? | Choose a measurement boundary | Hold rather than buy broadly |
| 3 | Does utility data already answer it? | Use portal/download and document intervals | Continue to another layer |
| 4 | Is one accessible plug load enough? | Use a compatible local meter or safely bounded connected plug | Continue |
| 5 | Is the exact smart meter eligible for an integration? | Confirm utility, meter, address, account and network | Do not buy a meter accessory |
| 6 | Is panel-level coverage truly needed? | Document permission, panel identity, recall, fit and qualified route | Use non-panel alternative |
| 7 | Is aggregate timing enough? | Consider mains monitoring | Define selected circuits |
| 8 | Can required circuits be directly instrumented? | Consider selected-circuit route | Use hybrid measurement or hold |
| 9 | Are cloud, account, retention, export and support acceptable? | Record exact service dependencies | Choose local/download route or no purchase |
| 10 | Are all central facts current? | Proceed only to documented product verification | Hold and recheck |
When a hybrid route is better
One layer does not have to answer every question. A bounded renter workflow may combine utility interval trends with temporary measurement of one ordinary compatible cord-and-plug load. Compatibility includes the exact load and meter manuals, ratings, outlet condition and operating environment; a wattage calculation alone does not authorize an intermediate device on a major appliance or critical load. A small-home owner may use selected-circuit data for HVAC and water heating, a plug meter for a difficult shared circuit, and the utility bill as the billing reference. Each layer should keep its own time boundary, units, uncertainty, and retention limits.
Do not add layers merely to make a dashboard more detailed. More devices create more accounts, support obligations, exports, update triggers, and failure modes. When a single temporary measurement or existing portal already changes the decision, no purchase is a successful outcome.
What this guide could not establish
- No independent matched accuracy, calibration, latency, recovery, radio-range, reliability, or long-term support test was available for the current examples.
- No architecture-level privacy or security winner was established.
- No consumer monitor was shown to be billing-grade or suitable for overriding a utility record.
- No product was shown to identify every appliance or every shared-circuit device.
- No household energy-saving percentage, payback period, installed cost, or lifecycle-cost advantage was established.
- No universal rule establishes when a landlord, electrician, permit, insurer, or utility must approve an installation; those questions remain exact-situation matters.
Bottom line
Use the lowest-complexity architecture that can answer a defined question. Utility data is often the first and least invasive layer. A local plug meter can answer a bounded question about one ordinary compatible load. Meter-linked products require exact utility and meter eligibility. Panel aggregate and selected-circuit monitors require permission, panel-specific compatibility, recall clearance, a qualified route, and acceptance of the product’s account, cloud, retention, export, and support dependencies. Keep the existing setup when the data will not change a decision, and treat every unknown central fact as a reason to hold—not as permission to proceed.
Related reading
Use the Home Energy Monitor Installation Safety and Permission Checklist before any hardware project. It separates property decisions, exact equipment, recalls, listing and qualified responsibilities without authorizing installation.
After choosing the monitoring architecture, read Sense vs Emporia Home Energy Monitors for the existing-owner, current-hardware and utility-meter comparison. Exact eligibility, data, privacy and service limits remain separate; the comparison does not approve installation or establish a winner.
Before relying on an export or integration, use Home Energy Data, App, and Smart-Home Integrations Compared to check the exact data route, account access, intervals and documented limits. A documented route does not establish exact compatibility, privacy, reliability or savings.
Method and sources
The source pages below support the dated manufacturer observations and routing boundaries. They do not prove independent accuracy, household eligibility, compatibility, privacy, certification, installation or savings. Manufacturer claims and availability can change; check the exact product and service before acting.
- NIST IR 8425
- U.S. Department of Energy Green Button overview
- Green Button Standard
- Green Button Directory for utilities
- Emporia Vue energy monitor overview
- Emporia Vue 3 16-sensor product page
- Emporia Vue installation route
- Emporia Vue cloud architecture
- Emporia measurement data storage
- Emporia Utility Connect supported utilities
- Emporia Vue Utility Connect product page
- Emporia energy-monitoring smart plug
- P3 Kill A Watt EZ P4460
- P3 Kill A Watt EZ direct store page
- Sense support after consumer-monitor retirement
- Sense smart-meter eligibility
- Sense data export
- Sense device identification limitations
- Sense data security and privacy support page
- Sense legacy panel installation boundary
- Schneider/Wiser Energy Monitor status
- CPSC Schneider QO load-center recall
- CPSC Siemens SolarReady meter-combo recall
What changed
October 16, 2026 — Refreshed the dated manufacturer price, availability, export and retirement observations. Separated manufacturer monitoring and app-update statements. Repaired the software decision rules so unknown safety/recall, exact plug-load compatibility, connected meter account/cloud acceptance and export-fit constraints fail closed. These are source and software updates; no physical product or installation test was performed.