by NOVA
Oct 06, 2026
A channel should write smart home on the line that buys the connected device estate, and home automation on the line that buys rules, scenes, and triggers. Home automation vs smart home is that split for a quote, and the difference between smart home and home automation is the same job read from the other label. The matrix below names owners, hub use, protocol, and the scene list, then points at a published MOES route for the line you mean.
Distributors meet this when a project sheet says “smart home package” and the integrator still expects the lights to run with nobody tapping an app. Shipping switches leaves the rules unwritten. Shipping a scene list with no endpoints leaves nothing for the list to move.
Write smart home when the quote is the connected products people can tap, speak to, or reach from an app. Write home automation when the quote is the schedules, triggers, and scenes that act on those products after the carton is open.
CEDIA’s homeowner note treats remote or panel control as the smart-home side and preset action as the automation side. The same note says a smart home can exist without those preset actions. That public split is the one a channel can put on a quote without inventing a second product.
A home automation system, in that usage, is the behavior layer. It can sit on top of devices the buyer already has, or it can be its own line when the endpoints are already installed on site.
Picture a corridor package. The wall controls, the app login, and the voice path are the device estate. “Lights to a dim state at dusk, unless someone is still in the hall” is the rules layer.
One purchase order can carry both lines. One vague line called “smart” carries neither.
The noun page for the connected estate is the smart home clarification. The noun page for rules, triggers, and scenes is the smart home automation clarification. Room sheets and commissioning order stay on the setup inputs page.
Pick the label only after each field below has an owner. An empty cell means the quote is still a slogan, even if the product title sounds complete.
| Field | Smart home line | Home automation line |
|---|---|---|
| Who owns the devices | Catalog item, switch, module, sensor, or hub hardware | Leave blank unless that seller also ships the endpoints |
| Who owns the rules | Leave blank when the buyer only wants app and voice control | The party who will write and keep schedules, triggers, and scenes |
| Hub dependency | Name the hub model, or write none | Name the hub only if the rules are described as running on it |
| Protocol | The radio or app path printed on the device route | Repeat it only when a rule needs a device that speaks it |
| Scene list | An on-device mode if that page names one | Rooms, trigger, and who may change the list later |
From the field: A Home Assistant forum poster treated a phone full of device apps as control, and treated rules that make those devices act on each other as automation. — source: community thread read 2026-10-06, not linked because the forum returns 403 to automated checks.
That poster’s examples were a garage door starting a camera, presence starting heat, and a late television closing shades. The camera, the heater, and the shade motor are devices. The “if this, then that” lines are the automation.
A second reply on a related thread separates a saved scene from the thing that fires it. The scene is the state you want. The automation is what runs when an event shows up.
A quote that says only “scenes included” has not named the event.
A smart home hub is optional. Reference writing allows one hub, several hubs, or none, so the quote has to say which pattern this job uses.
Put the hub on the smart-home line when you are selling the box itself. Put it on the automation line only when the rules are described as running on that box. A job with direct app control of each device can carry “hub: none” and still be a coherent device quote.
The MOES wired multi-mode gateway page is a device route that also talks about rules. It describes sub-device control for Bluetooth and ZigBee devices in the Smart Life App, plus remote control and group control. The same page says scenario and automation can execute locally if network access is absent, and it names away and stay modes together with sensors listed on that route.
That pairing is narrow. It does not transfer to every switch in the catalog. If the quote is only wall controls, the hub cell stays empty until someone adds this gateway or writes that no hub is in the job.
Ask one practical question before the cell is filled. If the internet drops, which behaviors must still run, and which box is supposed to run them?
The gateway page is the MOES route that actually discusses local scenario and automation. A wall-switch page that only names app, voice, and touch does not answer that question.
Protocol answers how the endpoints join the job. The scene list answers which saved states exist and what fires them. A Wi-Fi mark on a carton does not answer the second question.
TechTarget’s definition notes that the market often uses both labels for the same internet-connected residence, and that devices still need a shared protocol or complementary protocols if they are going to act together. Loose public wording does not erase the protocol cell.
| Question on the quote | Belongs with | What to write |
|---|---|---|
| How does this endpoint join the job? | Devices | The protocol named on that product route |
| What state should the room return to? | Rules | The scene, who saves it, and who may change it |
| What event starts that state? | Rules | A time, a sensor, or a manual tap, written apart from the saved scene |
Home Assistant’s scene page describes a scene as stored states for a group of entities, activated when something calls it. Use that idea in the quote even when the app you ship uses different screen names. Do not paste Home Assistant service names into a MOES line.
A HomeSeer member called scene control the act of setting lights to the levels that make that lighting scene. The event that calls the scene is still a separate line.
The Star Feather Wi-Fi switch page says lighting modes and scene modes can be switched with one tap in the app, alongside app, voice, and touch control. That scene mode is an on-device control printed on a device page. The project’s scene list is still a separate cell: which rooms, which trigger, and who maintains it after handover.
A buyer who wants only that tap-in-the-app behavior can keep the rules line unused. A buyer who wants dusk lighting across a floor needs the trigger and the owner written out, even if one of the switches offers a scene mode.
Public pages disagree, and a channel that copies a single page will mis-label the next job.
Wikipedia uses smart home for home automation devices that have internet access, and it calls home automation the broader set, often tied to a central hub or gateway. One commercial blog calls home automation the umbrella and places smart homes under it. Another commercial page draws the split as a wired renovation versus modular devices added with no building work.
Those stories can each be sincere and still break a purchase order. The channel version stays smaller. Devices go on one line.
Rules go on the other. Wired versus wireless is an install note when the product route says it, not a replacement for the two labels.
A smart home without automation is a real quote. It is app and voice control of the devices, with the rules line marked unused. CEDIA’s note that automation can be absent is the public backing for that choice.
The buyer who wanted self-running lights will notice the blank rules line before the goods ship, which is the point of writing it down.
One MOES module title already says home automation. The mini Wi-Fi module page offers voice control, app remote control, and a settable relay state after power returns. The title does not list triggers.
If a buyer pastes that title onto a rules line, ask whether they want the module or a scene list that uses the module.
Match the Tuya smart home products catalog when the line is the device estate. The category page describes a wholesale set of Tuya-app devices for distributors, installers, and OEM buyers, and it names four live sub-collections: Smart Switch, Smart Modules, Smart Thermostat, and Other Smart Devices.
Match the Star Feather Wi-Fi switch when the device line is a wall control whose page also names lighting modes and scene modes in the app. Match the mini Wi-Fi module when you need a device whose title already says home automation while the body stays on voice, app, and relay state. Match the wired multi-mode gateway when the device line is a hub and the rules line will quote the scenario and automation wording on that same page.
Leave the rules line blank if nobody has accepted the scene list. The catalog does not write that list for the project. Send a rules-only inquiry back for an owner and a trigger before anyone treats a switch title as the behavior layer.
If the gateway route is the hub you are quoting, keep its protocol words on the device line: ZigBee and Bluetooth sub-devices in the Smart Life App, as that page states. Keep away mode, stay mode, and the sensor story on the rules line, because that is where the page places scenario and automation.
The two lines can share one URL. They still should not share one unlabeled cell.
Yes. CEDIA’s comparison says a smart home can exist without preset actions. Write the device estate, mark the rules line unused, and ship app or voice control only if that is what the buyer asked for.
No. The rules line can name schedules, triggers, and scenes for devices already on site. If the endpoints are not identified, the quote is incomplete, because a rule needs something to act on.
The distributor can ship the hardware and leave the list to the integrator or the end customer. Say that in the rules cell. A scene mode printed on a switch page is not the same as a project list with an owner.
When you are selling the hub as hardware. The wired multi-mode gateway page is a device that also describes scenario and automation. The box itself still belongs on the device line.
The away and stay behavior belongs on the rules line.
Because several commercial articles use install method as their whole definition. One calls automation a renovation-time wired job and the smart home a modular add-on. A finance explainer reviewed with the same search notes that a connected home can be wireless, hardwired, or both.
Keep that as an install note beside the product route. It does not replace the device-versus-rules split.
The device line, the protocol on each route, and hub set to none unless a hub is actually in the cart. The Star Feather page’s app, voice, and touch wording fits that request. The rules line stays marked unused.
Open the body, not just the title. The mini Wi-Fi module title uses those words while the description talks about voice, the app, and relay state. Quote it as a device unless a separate scene list is attached.
OTHER SMART DEVICES
Jun 13,2026
OTHER SMART DEVICES
Jun 12,2026
TUYA SMART HOME PRODUCTS
Jun 12,2026
+86 137 3639 3028
