Treat a local energy archive as a separate component
An API route is useful only if the receiving system handles its measurements correctly. Before choosing this plug for local records, write a small data contract: device identity, field name, unit, timestamp, sampling behavior, counter-reset behavior and destination storage.
For an illustrative cumulative-energy series, a counter rising from 12,400 Wh to 12,650 Wh represents 250 Wh, or 0.25 kWh. If it later reads 20 Wh after a reset, subtracting it from 12,650 Wh would create a false negative. Mark the reset boundary and use the documented field semantics; do not silently clip an unexplained negative value to zero.
Check the current Shelly device API documentation for the selected mode and firmware. The example explains counter accounting, not a claim about unverified reset behavior. Preserve missing intervals and avoid assuming that local access includes a complete permanent archive.
Choose Shelly for a data path you can maintain. If that recordkeeping is unwanted, an app-oriented plug may fit better even when Shelly exposes more interfaces.
Quick verdict
Shelly Plug US Gen4 is the energy-monitoring plug for a buyer who wants choices after installation. It can meter one connected load, expose an on-device web interface and RPC API, run local schedules and scripts, and join supported ecosystems through Matter or a Zigbee configuration. That is a deeper local toolkit than most app-first consumer plugs offer.
Depth creates decisions, not automatic simplicity. Wi-Fi, Zigbee, Matter, Shelly Cloud, MQTT, webhooks, and scripts are not one interchangeable setup. More importantly, the current 15A/1,800W headline applies to a 120V resistive load. It does not prove compatibility with motors, compressors, heaters, EV charging, medical equipment, or anything whose unexpected shutdown or restart has serious consequences.
Search Amazon for Shelly Plug US Gen4 S4PL-00116US, then confirm the listing and received label show that exact North American model.
Decision matrix
| Monitoring job | Fit | What decides it |
|---|---|---|
| Meter and schedule a low-consequence indoor resistive load | Strong | Local data and automation can share one outlet |
| Feed local readings into a maintained home platform | Strong | Built-in WebUI, RPC, MQTT, webhooks, and scripting provide routes |
| Use Apple Home, Google Home, Alexa, or another Matter controller | Potentially strong | Controller support decides which energy fields and history appear |
| Operate as a Zigbee plug and router | Conditional | Zigbee is a selected mode, not an extra simultaneous copy of every integration |
| Need Thread | Wrong product assumption | Current official specs and Matter certificate do not list Thread |
| Switch a motor, compressor, heater, or EV charger | Stop and verify | Resistive rating does not establish startup or continuous-load suitability |
| Need whole-home or circuit totals | Wrong category | One plug sees only the connected appliance |
| Need safety-certified load shedding | Weak | Smart protections do not replace correct wiring, breakers, or purpose-built controls |
The right purchase starts with a named load and a chosen data path. Buying it because it “supports everything” is likely to create a more complicated system than the household needs.
Exact model and electrical identity
Shelly identifies the current North American device as Shelly Plug US Gen4, model S4PL-00116US. The current white and black variants use EANs 3800238072094 and 3800238072100 respectively. The body measures 38 × 64 × 51 mm, or 1.50 × 2.52 × 2.01 inches, and weighs 64 g.
It accepts NEMA 1-15 and 5-15 plugs and connects to a NEMA 5-15 receptacle. The published supply is 120V at 60Hz. Maximum switching current is 15A and maximum output is 1,800W for resistive load only. Shelly also lists device consumption below 1.5W, an operating range of −5°F to 105°F, and indoor pollution-degree and altitude limits.
Those specifications are not a generic “anything with a US plug” promise. A marketplace page that omits the model, regional socket, Gen4 identity, or power-metering feature is not enough. Confirm S4PL-00116US on the listing and received label.
What local capability actually means
Shelly’s technical documentation exposes a built-in web interface and local RPC components for the switch, power meter, illuminance sensor, networking, timers, schedules, scripts, and integrations. The current specification lists up to 20 schedules, 20 webhooks with multiple URLs, as many as 10 script instances, MQTT, UDP, outbound WebSocket, encryption, and key-value storage.
That can support a vendor-cloud-light setup: read current power on the LAN, run a schedule on the device, or forward measurements into a maintained local system. It does not mean every historical chart exists locally in a beginner-friendly form. The household still has to choose storage, retention, backups, authentication, updates, and remote-access design.
Shelly’s current data statement says the plug can generate output state, power, voltage, current, energy, internal temperature, protection configuration, logs, network status, schedules, firmware information, and other JSON data. It distinguishes device access through the WebUI/RPC API from Shelly Smart Control and remote APIs. That is unusually concrete evidence for buyers who care about data portability.
“Local capable” is not the same as “private by default.” Adding the device to Shelly Cloud or several third-party platforms creates external data paths. Review each chosen service, use strong credentials, keep firmware current, and remove obsolete integrations.
Matter, Wi-Fi, Bluetooth, and Zigbee are separate choices
The Connectivity Standards Alliance record certifies the device for Matter specification 1.3 and lists Wi-Fi and Bluetooth as its Matter transport interfaces. Shelly’s current radio specification includes 2.4GHz Wi-Fi 6, Bluetooth LE, and Zigbee. It does not list a Thread radio.
This matters because some coverage and retailer text can blur “Matter” and “Thread.” Matter can run over Wi-Fi; a Matter logo does not prove Thread. A Thread-border-router purchase is therefore not the basis for choosing this plug.
Shelly documents Zigbee as an available device mode. Switching protocol modes may change which Shelly components or features remain available; its API documentation, for example, notes that BTHome components are not available in Zigbee mode. Decide the intended controller first and verify the exact current firmware path before commissioning several units.
Controller feature exposure varies. The Matter certificate establishes protocol compatibility, but it does not promise that Apple Home or another controller will show Shelly’s complete energy history, configuration, or automation interface. Verify the chosen controller’s current capabilities when platform-side history matters.
Energy data: useful questions and limits
The plug can answer narrow, actionable questions:
- How much power is this office setup drawing now?
- How many kWh did a supported appliance use over a comparable week?
- Did a conservative schedule reduce an identified standby period?
- Did the load pattern change after a setting or maintenance action?
The color LED can provide at-a-glance load indication, while the WebUI, app, or an integration provides numeric data. The built-in light sensor reports three illumination bands (bright, twilight, and dark), which can be used as an automation input where its orientation and room lighting make that meaningful.
Do not use the plug as a revenue-grade meter or to settle a utility bill. Sampling, retention, tariff structure, controller support, and clock handling all affect what a dashboard can prove. Treat measurements as trend and before/after evidence unless the exact metrology requirement is documented.
Load worksheet: resistive is the key word
Before connecting an appliance, record this:
| Check | Evidence | Pass condition |
|---|---|---|
| Region and voltage | Plug and appliance rating labels | Both are intended for North American 120V/60Hz use |
| Load type | Appliance maker documentation | Compatible resistive load or explicitly supported switching use |
| Running and startup current | Nameplate/manual, not guesswork | Within all device, receptacle, circuit, and continuous-load limits |
| Restart behavior | Appliance instructions | An unexpected off/on state cannot create harm |
| Environment | Outlet location | Indoor, dry, within published temperature/humidity limits |
| Failure consequence | Household risk review | Loss or restoration of power is low consequence |
| Physical condition | Plug, receptacle, cord | No looseness, heat damage, arcing, discoloration, or cable damage |
A resistive ceiling does not validate compressors, pumps, motors, transformers, chargers, or high-inrush electronics. It also does not override appliance warnings about extension devices, smart plugs, unattended operation, or dedicated circuits. Do not use a consumer smart plug as an EV-charging control, medical-power control, fire-safety control, or substitute for a qualified electrical assessment.
The device advertises overtemperature, overvoltage, overcurrent, and overpower safeguards. These are backups within the product, not permission to connect a mismatched load. The branch breaker, receptacle, conductors, appliance protection, and operating instructions still govern the installation.
Setup and failure-state plan
Commission the plug without a load connected, as the safety guide instructs. Update firmware, choose one protocol path, set account and local credentials, and confirm the desired power-on state. Test switching and data reporting with a harmless low-load lamp before moving to the intended supported appliance.
Then test ordinary failures deliberately: internet unavailable, controller offline, router restarted, and power restored. Record which schedules remain local, which dashboards disappear, and whether the outlet returns on or off. Never run that test on a load whose interruption or restart matters.
If the plug becomes hot, smells unusual, buzzes, shows damage, disconnects repeatedly, reports implausible power, or trips protection under a supposedly compatible load, stop using it. Do not raise a protection threshold merely to suppress a warning without identifying the electrical cause.
Shelly Plug US Gen4 versus nearby monitors
| Option | Better when | Main trade-off |
|---|---|---|
| Shelly Plug US Gen4 | Local APIs, scripts, protocol choice, and one-load metering matter | More configuration decisions; resistive-load boundary |
| Tapo P110M | Mainstream app workflow and Matter-over-Wi-Fi simplicity matter | Rich energy history may remain app-centered |
| SONOFF S31 | Low-cost stock eWeLink monitoring meets the requirement | Verify the energy-monitoring variant and stock service features; do not assume modified firmware |
| Basic plug-in meter | Temporary measurement is needed without remote switching | No schedules, remote control, or continuous export by default |
The Tapo P110M review is the closest mainstream alternative. Our Shelly versus Tapo decision matrix compares the exact US models by local data route, app history and load boundary. The local-versus-cloud monitoring comparison helps choose who should operate the data path. If the goal is still unclear, the starter smart-plug bundle guide explains why one or two defined loads beat an undirected multipack.
Who should buy it
Buy Shelly Plug US Gen4 when one compatible, low-consequence indoor load needs both energy data and control, and the household has a concrete reason to use local WebUI/RPC access, scripts, MQTT, Matter, or Zigbee. It fits a technically maintained system that values exit routes beyond a single cloud dashboard.
Start with one plug. Establish a baseline, create one conservative rule, and verify the result before expanding. Protocol flexibility has value only when the chosen path is documented and maintained.
Who should skip it
Skip it when the buyer wants a single app with no architecture decisions, needs whole-home or circuit data, or cannot verify the exact load. Skip it for outdoors, 240V equipment, EV charging, hardwired appliances, essential equipment, and loads whose unexpected state creates safety or property risk.
Choose a passive plug-in meter when measurement is useful but remote switching adds risk. Choose a qualified-installed circuit monitor when the target is hardwired or spans several circuits.
Research method and limits
This is a documentary review of Shelly’s current U.S. specification, API documentation, safety guide, data statement, and Matter certification record, checked September 19, 2026. We did not conduct hands-on electrical or metrology testing. Product figures remain manufacturer specifications; confirm the received model, current firmware, controller support, and appliance compatibility before use.
Sources
Final verdict
Shelly Plug US Gen4 is unusually flexible for one outlet. Its local WebUI and RPC access, power data, scripts, schedules, MQTT, Matter, Wi-Fi, and Zigbee option give a maintained home system room to evolve.
The disciplined purchase is narrower than the feature list: one verified 120V indoor resistive load, one chosen protocol, one data path, and one low-consequence automation. If those are not defined, a simpler plug or passive meter is the better tool.
Frequently asked questions
Does Shelly Plug US Gen4 monitor energy?
Yes. Shelly documents instantaneous power plus voltage, current, and accumulated energy data. The built-in web interface and RPC API provide local access, while the Shelly app can provide cloud-backed views.
Does Shelly Plug US Gen4 use Thread?
No Thread radio is listed in Shelly’s current specifications. The Connectivity Standards Alliance certification lists Matter transport over Wi-Fi and Bluetooth. Zigbee is a separate selectable protocol mode.
Can it run a 1,800-watt appliance?
The published 1,800W maximum is explicitly for a resistive load at 120V, with a 15A switching-current ceiling. Appliance type, startup current, continuous-load rules, plug condition, and manufacturer instructions still control suitability.
Does it work without the cloud?
It has a built-in web interface, local RPC API, schedules, scripts, and other local integration options. The exact dashboard, remote access, history, and third-party functions depend on the configuration you choose.