Project Inputs Installers Should Document Before the First Kit

For distributors and installers, how to set up a smart home starts by freezing project inputs before the first kit ships — hub versus Wi-Fi path, rooms and device classes, 2.4 GHz Wi-Fi readiness, app account and region, power and neutral for wall switches, sensor placement, scene ownership, commissioning order, and the evidence pack that reaches RFQ before escalation.

This page is a B2B documentation sheet for that Smart home first deployment. It is not a consumer lifestyle shopping guide. Treat it as a smart home setup worksheet the channel can archive with the first smart home kit.

Upward hub: Tuya Smart Home Products. Architecture depth for stocking stays on smart home hub vs Wi-Fi. Device-class taxonomy stays on smart home device types.

Freeze the Hub vs Wi-Fi Path Before Any SKU Ships

Freeze the radio path before packing any first kit.

A Wi-Fi path means end devices associate directly to the site access point through the companion app. A hub path means Zigbee (or similar mesh) end devices need a gateway on the bill of materials before pairing can finish. Mixing those assumptions in one pallet is how channels ship “almost complete” kits that stall on day one.

Write one line on the input sheet: Wi-Fi-direct, hub-backed, or a deliberate split with named rooms on each path. Protocol definitions live elsewhere — what is Zigbee and what is Matter — and the stocking comparison stays on the hub-versus-Wi-Fi page linked above. This sheet only needs the path freeze so SKUs match the job.

Document Rooms and Device Classes on One Sheet

List room × device class before you count SKUs.

Start with rooms that matter on day one — entry, living, kitchen, primary bedroom — and mark classes such as wall switches, plugs, sensors, hub/gateway, and any thermostat or panel the quote already named. Keep the matrix short. A first kit that tries to automate every closet usually fails commissioning before it fails sales.

Class labels are project inputs, not a rewrite of taxonomy. When buyers need the classification map, send them to smart home device types and types of smart home sensors once — then return here to freeze which classes ship in kit one.

Confirm 2.4 GHz Wi-Fi Readiness on Site

Document 2.4 GHz readiness and SSID architecture before devices leave the warehouse. That note is the network half of a reliable smart home setup.

Most smart-home radios expect the 2.4 GHz band. Independent setup guides and field reports keep repeating the same failure: a phone sitting on a merged 5 GHz “Smart Connect” SSID during pairing, or band steering that shoves a 2.4-only gadget toward a radio it cannot use. Split the bands, create a dedicated IoT SSID, or temporarily force the commissioning phone onto 2.4 GHz — then write what you did on the sheet.

Also note whether encryption is enabled and whether default router admin credentials were changed. Those are basic wireless-hygiene inputs, not optional afterthoughts. Coverage education targets such as roughly −67 dBm at the install point appear in installer blogs; treat them as site-survey language, not as a warranty number for any named SKU.

Lock App Account and Region Before Commissioning

Name the App account / region and the admin identity before the first device joins.

Commissioning under a personal login that later leaves the company creates orphan devices. Freeze: app family (manufacturer / platform app), admin identity, region or data-center choice the app requires, and whether a second phone will share access on day one. Keep QR codes and serial labels until pairing finishes — many devices print them on the back or in the carton.

When the ticket is a broken pairing screen rather than a missing account field, hand it to Tuya Smart app problems instead of expanding troubleshooting here.

Capture Power and Neutral Inputs for Wall Switches

Survey power and Neutral wire status per switch box before wall-control SKUs ship.

Line-voltage smart switches often need a neutral return in the box. Retrofit loops without a neutral become “the switch is defective” tickets when the real gap was an undocumented box.

Log voltage expectations, gang count, multi-way notes, and whether a neutral is present. Cross-class electrical depth lives on smart home devices electrical installation; single-switch copper how-tos stay on their install packages. For what a smart switch is versus how crews use it after copper is correct, see what is smart switch and how to use a smart switch once each.

Record Sensor Placement Before Permanent Mount

Test sensor placement, then log it, before anyone mounts permanently.

Sensors fail projects as remount labour: motion blind spots, door contacts on the wrong stile, presence sensors facing HVAC vents. Power the sample at the intended spot, confirm the trigger story the RFQ sold, then write room, height, orientation, and power class (battery, USB, or line). Placement is a project input; sensor taxonomy stays on the sensors classification guide linked above.

Assign Scene Ownership and Mode Rules

Name who owns scenes and which mode rules apply before the demo.

Scenes are not the same as a single on/off. Someone must own naming, edits, and which rockers are lighting circuits versus scene triggers. On MOES Star Feather multi-gang faces, lighting modes and scene modes can be switched in the app, with an explicit collection note that Light Mode and Scene Mode cannot be used at the same time.

Important: For the first smart-home kit, write which mode the multi-gang face will ship in. On Star Feather, Light Mode and Scene Mode are exclusive — leaving the sample in the wrong mode makes rockers look broken during handover when they are actually firing a scene map. — source: MOES Star Feather collection

Publish a Commissioning Order the Crew Can Follow

Publish a smart home commissioning order: network and accounts first, then hub if any, then devices one at a time, then scenes.

Out-of-order labour is expensive. A practical sequence for the first smart home setup:

1. Confirm 2.4 GHz / SSID notes and encryption hygiene on site.
2. Create or unlock the named admin account and region.
3. Power and update the hub or gateway if the path is hub-backed; wait for firmware to settle before adding end devices.
4. Add one device at a time through the manufacturer app; name by room + function.
5. Prove local control where the product has a wall surface, then app on/off, then one scene.
6. Only then link voice assistants if the RFQ requires them.

Topology and RACI depth for automation jobs stays on smart home automation installation project inputs. This page only needs the order written so crews do not invent a new sequence per house.

What Evidence Must Reach RFQ Before Escalation

Attach the freeze pack before any “device is broken” escalation.

Support teams cannot debug a missing path freeze from a screenshot of a red LED. The evidence table is the gate between project inputs and RFQ escalation.

Which MOES Products Fit a Documented First Smart-Home Kit?

For a documented Wi-Fi first kit, start with the page-stated Star Feather US switch on the MOES Star Feather US Wi-Fi product page; for a hub path, add the ZigBee gateway and a hub-required ZigBee dimmer module.

The Star Feather US switch is the bounded Wi-Fi starter for this path.

Live product evidence for the Wi-Fi starter (product page read 2026-09-23): Wireless Protocol Wi-Fi; Voltage 90–250V AC, 50/60Hz; Max.Current 10A/Gang, Total 10A; Frequency Band 2.412~2.484 GHz.

Fact-package notes describe US Star Feather gang entries as neutral-wire products and record that Light Mode and Scene Mode cannot run simultaneously. Those are the only ratings this recommendation uses — no Matter claim is present on that Wi-Fi SKU page, and none is invented here.

When the path freeze says hub-backed, quote a companion gateway such as the MOES ZigBee Wireless Smart Gateway Hub ZHUB-W (page states ZigBee hub for Tuya ZigBee 3.0 products, must work on 2.4 GHz Wi-Fi, Electrical Parameters 5V 2A) together with a hub-required end device such as the MOES ZigBee 3.0 smart dimmer module (page states Tuya ZigBee hub required). Do not ship the ZigBee dimmer module row without the hub row when that path is frozen.

FAQ

Do I need a hub to set up a smart home for a first kit?

Only if the frozen path uses Zigbee or other hub-required radios. Many Wi-Fi devices commission directly to the site access point. Freeze the path on the input sheet before packing so the kit is not missing a gateway.

Why document 2.4 GHz Wi-Fi before devices arrive?

Most smart-home radios use 2.4 GHz. Merged dual-band SSIDs and band steering commonly break pairing when the commissioning phone sits on 5 GHz. Write the SSID architecture before the pallet ships.

What rooms and device classes should be listed first?

List the rooms in kit one and the classes that ship with them — switches, plugs, sensors, hub, and any named thermostat or panel. Keep kit one small enough to commission in one visit.

Who should own the app account and region?

Name a durable admin account and the app region before the first device joins. Personal logins that leave with a contractor create orphan devices and unresolvable tickets.

What power and neutral facts must installers log for wall switches?

Per box: expected voltage class, gang count, multi-way notes, and whether a neutral return is present. Missing neutrals are a survey failure, not a mystery product failure.

What evidence should reach RFQ before escalation?

Path freeze, SSID/2.4 GHz note, admin account and region, power/neutral survey for wall SKUs, placement notes for sensors, commissioning step log, and scene/mode ownership. Without those, escalation is guessing.

References

1. CISA — Secure Our World
2. FTC — How To Secure Your Home Wi-Fi Network
3. WIRED — Everything You Need to Know About the Smart Home
4. Gabellioni — Smart Home Installation Guide
5. SmartThings Community — Automated switches wiring (US)