Setup and ownership

Plan the setup, schedules and handoff for a smart plug

Start with the app and network you will actually keep

Before pairing a smart plug, confirm that its regional version supports the app and ecosystem you intend to use. Check the required Wi-Fi band, account sign-in, Bluetooth setup step and any Matter controller. If the product uses 2.4 GHz Wi-Fi, make sure your phone can reach that network during commissioning. Do not assume a device joins a 5 GHz-only network because a phone supports 5 GHz.

Choose the order for a multi-platform setup

For Matter devices, follow the exact manufacturer's instructions for first setup and adding another controller. The setup code may have a limited commissioning window or need to be regenerated by the first ecosystem. Keep the quick-start guide and code where household members can find them; do not publish or photograph a security code publicly.

Test the routine before it matters

Set a harmless schedule or short timer and verify that it behaves as expected while you are nearby. Check what happens after Wi-Fi or internet service is interrupted, but do not use a smart plug as the only protection for a critical appliance, medical device or safety system. A scheduled shutoff can be useful for a light; it may be inappropriate for equipment that must remain powered.

Think about shared control and handoff

Homes change hands: a roommate moves, the router is replaced, or a hub is reset. Know how the manufacturer handles shared users and how to remove the plug from a former account before factory reset or disposal. Write down the model and hardware version, keep the manual, and avoid storing account passwords in a product note.

Check behavior, not just compatibility

Once paired, verify the physical button, app state and any automations with the connected appliance in a safe condition. A feature list cannot prove the reliability of your local network or the suitability of the appliance. For the P125M, the manufacturer documents Tapo schedules, countdown and Away Mode, plus Matter setup; its third-party controller requirement and internet-loss wording are described in the model review.

Do not assume that a platform label identifies one protocol. The Tapo P125 sources describe Apple HomeKit, while the P125M is a separate Matter-enabled model. The P125 HomeKit setup card says an Apple home hub helps with remote access, sharing and automations; check the exact model review and your intended Home app use before choosing a hub or plug.

The Kasa EP25P2 V2.6 and earlier EP25P4 routes also document HomeKit, but their energy view is in Kasa Smart rather than Apple's Home app. EP10 uses the Kasa app and named voice routes, but its checked materials do not establish HomeKit or Matter. Compare the exact edition and the relevant EP25P2, EP25P4 and EP10 assessments before planning the household's app sequence.

For an outdoor plug, finish these network choices before mounting it. EP40A uses a HomeKit setup code alongside Kasa Wi-Fi, while EP40M uses Matter commissioning and a controller/network route; TP-Link documents both multi-platform support and differences between the vendor and third-party apps. EP40M's exact product page lists per-outlet schedules and a countdown timer, but the source set does not guarantee identical schedules in Apple Home, Alexa, Google Home or SmartThings. EP40's profile stays reference-only because the catalog route leaves the hardware version unresolved. Review the EP40A HomeKit setup notes and EP40M Matter routine details before choosing.

The Tapo P400M and P430M are also outdoor Matter products but have different loads. P400M is a dual-socket on/off plug with Tapo schedules, timer and Away Mode; P430M is a lighting-only dimmer with Tapo schedules, auto-off and energy reporting. TP-Link's Matter feature table shows app-by-app differences, and the SmartThings Energy FAQ says dimmer devices are not currently supported there. Keep the Tapo app for the P430M's confirmed energy view, and verify the precise controller/platform route before mounting either device.

Finder answer: weekly schedules

Thirty-nine current profiles document a weekly schedule, including the one-plug MSS110 US/JP route, MSS110HK US/CA and the MSS425FHK US strip through Meross-app routines; MSS315 US remains unconfirmed for weekly recurrence. The black Shelly Gen4 package routes schedule through Shelly’s own app/device plan, while Wave Plug LR’s SmartThings schedule evidence is specific to Z-Wave mesh and the Wave Edge driver. Compare MSS110 US/JP, MSS110HK and MSS425FHK, then show the same-condition weekly-schedule result. Their routine controls are not assumed to appear in Apple Home or voice apps.

Weekly scheduling is documented for thirty-nine current eligible profiles, including TP25, HS300 and KP115 as well as TP15 V1 in three package sizes, all six Shelly Plug US Gen4 package profiles and the Meross MSS425F US/JP, original MSS620 US and unsuffixed MSS630 US routes. Wave Plug LR also enters through its documented SmartThings mesh route, not Long Range star mode. Pack count does not multiply scheduling capabilities, and a routine in the maker app does not guarantee identical controls in every third-party app. Their recurring schedule examples are from Meross; the base MSS110 US/JP also documents weekday/weekend routines in Meross rather than schedule-editor parity in third-party apps.

P400M, TP25 and P430M add outdoor Tapo schedules for different loads: two separately controlled sockets under shared ratings versus one compatible-light dimmer. HS300 schedules its six AC outlets separately, while its USB ports remain always on; KP115 schedules one indoor outlet. P110M and P115 packages also list schedules alongside P105, P110, P125, P125M, P135 KIT, P306 and P316M; exact pack size does not change per-device capacity. P306's three switched outlets work individually, while the P316M strip's six outlets share its total rating. Choose the app and check whether the schedule supports your required days, state and network conditions. Compare P105, P110, P110M two-pack, P110M four-pack, P115 two-pack, P115 four-pack, P135 KIT dimmer, P306 extender, P316M strip, P400M, TP25, HS300 V1, KP115 V1, P430M, KP125MP4, EP10 and P125M; show models with a documented weekly schedule.

The weekly-schedule result has thirty-nine current profiles, including MSS425F US/JP, original MSS620 US and unsuffixed MSS630 US. The separately reviewed Wave Plug LR enters through its SmartThings-compatible mesh/Edge-driver arrangement, not the Long Range star path. Their exact pages document on/off schedules and Meross routine guidance supplies recurring examples; this does not establish the same schedule editor in Apple Home, Alexa, Google Home or SmartThings. Compare the MSS425F US/JP, original MSS620 US and MSS630 US reviews, then open the same-condition weekly-schedule finder.

Thirty-nine current profiles document weekly schedules, including the black Shelly Plug US Gen4 packages through Shelly routines and Wave Plug LR through the SmartThings mesh arrangement; neither establishes schedule controls in every other listed ecosystem. Compare black single, black 2-pack, black 4-pack, Wave Plug LR. Compare the single, 2-pack and 4-pack assessments and open the same-condition weekly-schedule finder.

TP15 pack configurations are separate assessment entries; the ratings and functions stated here are per plug, not multiplied by package count. See the evidence for the TP15 V1 one-pack, two-pack and three-pack.

Finder answer: countdown or auto-off timer

Forty-one current profiles document a countdown or auto-off timer, including the separate one-plug MSS110 US/JP, MSS110HK and MSS425FHK through the Meross app; their controls are not assumed to appear in Apple Home or voice apps. The white and black Shelly Gen4 device/app route has an integrated one-hour countdown; timer parity in third-party apps remains unestablished. Compare MSS110 US/JP, MSS110HK and MSS425FHK, then show the same-condition timer result.

Countdown or Auto-Off timers are documented for forty-one current profiles, including the Meross MSS110 US/JP one-plug route, MSS115, MSS110HK, MSS425FHK, original MSS620 US, unsuffixed MSS630 US, MSS620BHK and MPD100HK plus TP25, HS300, KP115, all three TP15 V1 pack routes and the white/black Shelly Gen4 package profiles. Shelly’s product page documents a one-hour device/app countdown; do not transfer that control to third-party apps without model-specific evidence. Distinguish one-time shutoff from a weekly routine, and confirm the app that controls it.

These five Meross models document timers through separate Meross-app sources or plans, not necessarily in Apple Home, Matter, Alexa, Google Home or SmartThings. MSS115's third-party Matter plan has local control but the timer is not established there; MPD100HK's auto-off applies to a lamp dimmer, not a general appliance. TP25, P400M and KP115 have Tapo/Kasa timer paths; HS300's V1 guide covers its timer; P430M auto-off is also documented in its maker app. A timer is not a fail-safe for equipment that must stay on. P110M, P115, P105/P110, P135 KIT, P306 and P316M list distinct maker-app timer routes. See MSS115, MSS110HK, MSS425FHK, MSS620BHK, MPD100HK, P105, P110, P110M two-pack, P110M four-pack, P115 two-pack, P115 four-pack, P135 KIT, P306, P316M, P400M, TP25, HS300 V1, KP115 V1, P430M, KP125MP4, EP25P2 and P125; filter for documented countdown timers.

The countdown result has forty-one current profiles. Shelly documents an integrated one-hour countdown for both black and white Gen4 plug configurations through its device/app route; identical timer controls in Apple Home or other third-party platforms are not established. Compare black single, black 2-pack, black 4-pack, white single, white 2-pack, white 4-pack. Compare the MSS425F US/JP, MSS620 US and MSS630 US assessments, then open the same-condition countdown-timer result.

Finder answer: Away Mode

Away Mode is documented for twenty-two current profiles, including TP25, HS300, KP115, all three TP15 V1 pack routes and Tapo P400M; P430M does not have a confirmed Away Mode in its checked model sources.

Away Mode depends on exact model and controlling app. The checked evidence supports it for Kasa EP10, EP25P2, HS300, KP115, KP125MP4 and Tapo P105, P110, P110M, P115, P125, P125M, P135 KIT, P400M and TP25. It is not documented for P306, P316M, P430M or EP40M; missing evidence is not evidence that no other model could support it. Compare P400M, TP25, HS300 V1, KP115 V1, P105, P110, P110M two-pack, P110M four-pack, P115 two-pack, P115 four-pack, P135 KIT, KP125MP4, EP10 and P125; show current Away Mode candidates.

Finder answer: local control after internet loss

Twenty-two current profiles document local access after an internet outage following configuration, including Meross MSS115 through a local Matter controller and all six Shelly Gen4 package routes via their embedded web interface, along with TP15 V1, P400M/P430M, P110 V1, P110M/P115, P316M and P125/P125M. This is after setup on a working home LAN, not cloud-free onboarding or Wi-Fi-independent operation.

Meross's MSS115 Matter claim is about configured device access on a functioning LAN during an internet outage; it does not establish Meross-app local control. TP-Link scopes its P110/P110M/P115/P316M statements to configured Tapo access; P400M/P430M rely on their documented local-network arrangements, not every third-party controller. HS300/KP115 routine persistence is not the same as manual LAN access, and MPD100HK's saved schedules running offline do not prove that its app remains locally reachable. None of these cases covers a failed router, first setup or remote access from away. Review the MSS115 Matter path, P110, P110M two-pack, P110M four-pack, P115 two-pack, P115 four-pack, P316M, P400M, P430M, P125 and P125M; filter for the documented local-control case.

Meross's MSS115 Matter claim is about configured device access on a functioning LAN during an internet outage; it does not establish Meross-app local control. Shelly documents its embedded web interface on the same LAN, but that local route still depends on the working router/Wi-Fi. TP-Link scopes its P110/P110M/P115/P316M statements to configured Tapo access; P400M/P430M rely on their documented local-network arrangements, not every third-party controller. HS300/KP115 routine persistence is not the same as manual LAN access, and MPD100HK's saved schedules running offline do not prove that its app remains locally reachable. None of these cases covers a failed router, first setup or remote access from away. Review the MSS115 Matter path, Shelly Gen4 single, 2-pack, 4-pack, P110, P110M two-pack, P110M four-pack, P115 two-pack, P115 four-pack, P316M, P400M, P430M, P125 and P125M; filter for the documented local-control case.

Twenty-two current profiles document configured local access after internet loss, including all three black Shelly Gen4 packages through the embedded web interface on a working home LAN; this does not cover router failure, initial setup or the Wave LR hub route. Compare black single, black 2-pack, black 4-pack, Wave Plug LR’s unknown offline behavior. Compare the single, 2-pack and 4-pack assessments and use the same-condition local-control finder.

Nineteen current configurations document energy reporting, including black Shelly Gen4 packages in Shelly’s app/device path and Wave Plug LR through its compatible gateway; the Wave SmartThings energy integration is documented for mesh mode, not LR star. Compare the black single, black 2-pack, black 4-pack and Wave Plug LR; the same-condition finder link below retains just the energy-monitoring requirement.

Finder answer: energy-use monitoring

Nineteen current configurations document energy reporting, including MSS315 US with live and historical readings in the Meross app and the Shelly Gen4 white single, 2-pack and 4-pack; MSS110HK explicitly has no energy monitor. Compare the MSS315 assessment, Shelly Gen4 single, 2-pack and 4-pack with MSS110HK's no-meter evidence, then show the same-condition energy-monitoring result.

Nineteen current configurations document energy reporting: Shelly Plug US Gen4; Meross MSS315; Kasa EP25P2, HS300 and KP115 plus KP125MP4; and Tapo P110 V1, P110M two-/four-packs, P115 two-/four-packs, P316M and outdoor P430M. Which app displays the data is a separate question.

Kasa sources place EP25P2, KP125MP4, HS300 and KP115 reports in Kasa Smart; HS300 describes energy for smart AC outlets, not its always-on USB ports, while KP115 reports energy for its single connected plug. Tapo profiles describe Tapo-app energy. P430M's Matter control routes do not establish a third-party energy view; TP-Link specifically says SmartThings Energy currently does not support dimmer devices. P316M sources describe per-outlet measurement; that does not change its shared load limit. TP-Link describes Kasa energy readings as approximate (about 3–5%), not professional power measurement. The reviewed materials do not establish an energy view inside Apple Home. Check EP25P2, HS300 V1, KP115 V1, KP125MP4, P110, P110M two-pack, P110M four-pack, P115 two-pack, P115 four-pack, P316M and P430M, then show the documented energy-monitoring matches.

Nineteen current configurations document energy reporting, including black Shelly Gen4 packages in Shelly’s app/device path and Wave Plug LR through a compatible gateway; SmartThings metering is documented for the Wave LR mesh arrangement, not LR star. Compare black single, black 2-pack, black 4-pack, Wave Plug LR. Review the single, 2-pack and 4-pack with the other energy-monitoring reviews, then open the same-condition energy-monitoring finder.

Combining Away Mode with the Kasa app

With Away Mode required inside the Kasa app, the current set includes EP10, EP25P2, HS300, KP115 and KP125MP4; the outdoor EP40M does not document the routine.

This is a useful example of why ecosystem and automation are separate choices: the EP40M can use Kasa but its sources do not establish Away Mode. HS300 and KP115 have documented Away Mode in Kasa; their six-outlet strip and one-outlet plug are different physical tasks. Do not infer support from app membership alone. Compare EP10, EP25P2, HS300, KP115 and KP125MP4, then apply both requirements together.

Combining earlier-edition inclusion with an indoor Kasa schedule

With earlier editions included, indoor placement, Kasa control and weekly schedules match eleven profiles. The HS103P4 V1 four-pack joins because its unit-level HS103 (US) V1 guide documents Kasa schedules; it has no confirmed overall load rating, so its numeric limits remain unknown.

Those device routes serve different jobs: the HS103P2 route is a two-pack of separate one-outlet devices with per-plug 15 A / 1,800 W general-use and 1/6 hp motor figures, but its generic package-content line still needs a seller-box check; KP303 is a three-outlet strip with two always-on USB ports and a separate US 1/6 hp motor limit; HS103P3's sources document a 15 A current maximum but no watt or motor limit; KP125MP2 is Matter-capable, monitors energy in Kasa and appears in TP-Link's EOL list; HS300 is a six-outlet strip with a shared rating, and KP115 is a one-outlet energy plug. The HS103P4 V1 guide lists Kasa routines and per-appliance examples but not a universal current, watt or motor rating; see the HS103P4 V1 assessment and do not transfer numbers from the other editions. Current KP125MP4 is a separate four-pack route. Compare HS103P2 V3, KP303 V1, HS103P3, KP125MP2, HS300, KP115 and KP125MP4, then apply all four requirements together.

Combining energy monitoring with the Kasa app

When Kasa control and energy-use monitoring are both required, the current assessed library includes EP25P2 V2.6, HS300 V1, KP115 V1 and KP125MP4 V1; each documents a Kasa energy view.

They are not the same measurement task: HS300 describes reports per smart AC outlet, with three USB ports always on, while KP115 monitors one connected plug. Kasa's general energy guidance gives an approximate 3–5% accuracy range and says it is not a professional power-measurement device. The product-level filter does not claim that each reading appears in a third-party platform. Check the EP25P2, HS300, KP115 and KP125MP4 assessments and apply both app and monitoring requirements.

Combining Tapo, local control and weekly schedules

Fifteen current Tapo arrangements meet Tapo-app control, configured local access after internet loss and weekly scheduling together, including all three TP15 V1 pack routes. This local case follows configuration and is not cloud-free setup.

The matcher keeps these requirements within one documented arrangement. P110M combines Tapo LAN access with an optional Matter controller; P400M/P430M use a Tapo/Matter local-network route and their app features remain Tapo features. P115 is assessed for Tapo and named voice routes rather than Matter. None means offline initial setup or control after local Wi-Fi failure. Compare P110, P110M two-pack, P110M four-pack, P115 two-pack, P115 four-pack, P125, P125M, P400M and P430M; filter for all three needs together.

Combining Tapo energy reports, local access and a weekly schedule

Seven current Tapo arrangements match when energy reports, local app access after internet loss and weekly schedules are all required: P110 V1, both P110M routes, both P115 packages, P316M and P430M.

P110M, P115, P316M and P430M document these features within a Tapo arrangement; P110M/P316M/P430M additionally offer Matter routes, while P115's checked US materials do not establish Matter or Apple Home. P430M energy appears in Tapo, not SmartThings Energy or an established third-party Matter energy view. Package routes remain separate entries, and neither package size nor a strip's outlets multiply ratings. This is not offline first setup or operation after local Wi-Fi failure. Review P110 V1, P110M two-pack route, P110M four-pack, P115 two-pack, P115 four-pack, P316M and P430M, then apply Tapo, energy, local access and schedule together.

Combining an outdoor dimmer with energy and a Matter platform

When outdoor placement, a Matter platform and energy reports are required together, P430M is the only current match in this library. Its energy view is in Tapo, not in the selected third-party app.

For Apple Home, the route is a multi-app Tapo plus Matter arrangement; for SmartThings, TP-Link specifically says SmartThings Energy does not currently support dimmer devices, so retain Tapo for measurement. The P430M remains a lighting-only dimmer with 125 V bulb limits, not a general appliance plug. Read the P430M energy and platform notes, then compare the identical conditions for outdoor + Apple Home + energy and outdoor + SmartThings + energy.

Combining an Apple Home route, energy reports and local control

With indoor placement, Apple Home and energy monitoring, six current routes match, including MSS315 US; neither its nor Shelly Gen4’s energy dashboard is documented inside Apple Home. Meross documents MSS315's energy view in its own app; Shelly's Gen4 metering is likewise a Shelly app/device route, not an Apple Home energy report. Compare MSS315, P110M two-pack, P110M four-pack, P316M, EP25P2 and KP125MP4; inspect Shelly's white single, 2-pack and 4-pack as a separate-app example, then show this same-condition finder set.

Adding configured local control reduces that energy-and-Apple-Home screen to three Tapo routes; Shelly Gen4 is excluded because its Shelly app/web path is not established through the single Apple Home setup. MSS315 is also excluded from this stricter set because its exact US sources do not establish configured local control after internet loss. Compare the P110M two-pack, P110M four-pack and P316M, then apply all four requirements together.

Combining indoor Apple Home with weekly and countdown routines

The one-plug MSS110 US/JP, MSS110HK, MSS425F US/JP and MSS425FHK pass an indoor Apple Home screen requiring both a weekly schedule and countdown timer through their documented Meross-app routine routes; that does not move those controls into Apple Home. The MSS425F US/JP is the four-AC/four-USB strip with a shared 15 A AC limit, not the separate MSS425FHK route. Compare MSS110 US/JP, MSS110HK, MSS425F US/JP, MSS425FHK, P110M and P125, then apply all five conditions together. With earlier editions hidden, outdoor use, Apple Home, a weekly schedule and a countdown timer together return six current profiles, including original MSS620 US and unsuffixed MSS630 US. Their socket counts and 10 A-per-socket versus 15 A-device limits differ; Meross-app routine documentation does not establish third-party timer parity. Compare MSS620 US, MSS630 US, EP40M, P400M and TP25, then open the exact five-condition outdoor result.

When SmartThings scheduling and energy must coexist

In this indoor SmartThings shortlist, requiring a general/resistive load, weekly scheduling and energy reporting leaves nine profiles, including Wave Plug LR only through Z-Wave mesh with the Shelly Wave Edge driver; the model’s Long Range star path is a separate gateway route, not the documented SmartThings arrangement. The Wave LR compatibility table identifies On/Off, watts and kilowatt-hours for its mesh driver; Samsung separately documents time-triggered automations. Compare Wave Plug LR with the Tapo P110M two-pack, then open the same-condition five-answer finder.

Adding configured local control after internet loss leaves five profiles and excludes Wave Plug LR because the exact LR mesh plan does not document that behavior; keep the network hub and the local-control requirement separate. The Z-Wave hub is mandatory and not included, and Long Range mode requires a compatible ZWLR gateway. Compare the Wave Plug LR limitations with the Tapo P110M two-pack, then open the same-condition six-answer finder.

Put your load, outlet and control needs together

Build my shortlist →