A smart switch uses power when it does nothing. The standby draw feeds the radio, the processor, and the night light someone decided to add, and it flows every hour of every day for the life of the installation. One watt sounds like nothing at the wall. Across a building, a housing estate, or a product line shipped by the container, it is a number that shows up on energy certificates, in regulations, and in the total cost of ownership spreadsheets that professional buyers actually read.
Where the standby watt goes
The draw splits into fixed and optional. Fixed: the power supply that converts mains to logic, which can be efficient or lazy depending on what the BOM saved; the radio, which depends on protocol and duty cycle; the processor, which depends on whether the firmware sleeps between tasks. Optional: the status LED that glows all night, the night light, the energy-measurement chip sampling continuously, the relay coil held energized by a latching design choice. Each item is a decision, and each has a range from careless to excellent. Two switches with identical features can differ by a factor of three in standby, and the datasheet usually prints only the better of the two numbers or none at all.
The regulation angle is closing in
Efficiency rules for standby power exist in most markets and keep tightening: limits on what a device may draw when it is off or idle, with exceptions for devices that must maintain network connectivity, which smart switches lobby for and largely receive. But the exceptions are not blanket, the ceilings keep dropping, and product lines that ignore the trend meet it at certification, where a power supply swap or a firmware sleep mode is discovered to be needed after tooling. For a manufacturer, standby is therefore a compliance parameter, not a green marketing line: it belongs in the requirements document with a number, a test condition, and a measurement standard, because the certification lab will apply its own.
Sleep firmware is free watt
The cheapest savings are in firmware. Radios that drop to a low-duty idle instead of polling continuously. Processors that sleep between events and wake on interrupt. LEDs that dim or blank after a timeout instead of burning all night. Energy-measurement sampling that slows when nothing changes. None of these change the user experience in any way a resident would notice, and together they often halve the standby figure. The reason they do not happen by default is scheduling: they cost engineering time at the end of a project when the feature list is already done, which is exactly why they must be written into the specification at the start. A vendor who can state a standby figure per firmware version has done this work; one who says "it is very low" has measured nothing.
Latching relays change the math
The relay choice is a hardware fork with real consequences. A standard relay holds its state with a continuously energized coil, spending power every second it is on, which on a circuit that is on all day makes the switch a small heater. A latching relay moves on pulse and holds mechanically, drawing power only at switching, at the cost of a more expensive component and slightly bulkier packaging. For always-on circuits, latching is the honest answer; for switched circuits that are off most of the day, the difference shrinks. The product line decision is per SKU, and the datasheet should say which relay each model carries, because the installer mapping a building of always-on corridor lights cares a great deal.
What to ask the supplier
The questions are concrete. What is the measured standby draw, in which state, radio idle or active, LED on or off, and by which standard measured. Does the firmware implement sleep modes, and from which version. Latching or standard relay per model. What is the draw with the energy-measurement feature enabled. And can the figures be certified to the target market's current limits with headroom for the next tightening, because the product will still be on shelves when the rule moves.
In our smart switch range on the store, the standby figure and relay type of each model are part of the model listing rather than a datasheet footnote. On the B2B side, a smart switch board built for multi-market distribution gets its standby budget, sleep firmware, and relay choice written into the requirements document per SKU, because one watt forever is a fleet problem, not a bulb problem.
Both the consumer line and the specification details behind the power budget are covered across XingLiao, and certification questions for a specific market can go straight to our contact page before the order, which is the cheapest possible time to ask them.
Top comments (0)