Choosing a model
A selection method for matching a load, an enclosure and an interface requirement to a model page, without publishing a parameter that has not been signed off.
| Document revision | r0.1-draft |
|---|---|
| Status | draft |
| Applies to | LS-WS-1G, LS-WS-2G, LS-WS-3G, LS-RC-16A, LS-RC-25A, LS-DIN-4CH, LS-GW-100, LS-GW-300, LS-SN-TH, LS-SN-MT |
| Regions | global |
| Published | Oct 15, 2026 |
| Review due | Apr 15, 2027 |
| Author | Engineering documentation (owner unassigned) |
| Reviewer | Engineering sign-off pending (reviewer unassigned) |
Model selection is a sequence of questions about the installation, answered in order. Each answer narrows the family; the specific ratings are then read only from the model page and its datasheet, never inferred from this document.
Preconditions
- The load type is known (lighting circuit, small motor, dry contact) and its supply characteristics are recorded from the site, not assumed.
- Whether the position is a flush indoor wall, a plant-room DIN rail, or a sheltered monitoring point is decided.
- The destination market's band and electrical route are known, because both restrict which revision is lawful there.
Selection order
1. Classify the load and the point of control
Decide first whether the switching happens at the wall (a flush device replaces an existing wall position) or near the load (a DIN-rail module sits in a panel and the existing control cable becomes a dry-contact input). That single decision separates the wall-switch family from the relay and controller family.
2. Count the independent circuits
The number of circuits switched at one position is a family-level fact and appears in the model name. It is not a distinction you should infer from a photograph.
3. Decide the enclosure class
A flush wall device and a DIN-rail module are not the same installation. Modules are supplied needing a suitable enclosure; the enclosure class, ingress protection and mounting depth are decided by the installer and must be confirmed, not assumed from a family description.
4. Decide whether a field protocol is required
If a building or industrial system must read the site's data, the model choice changes: an edge controller introduces field-protocol and historian behaviour that a compact gateway does not. Both are documented in MQTT, Modbus and BACnet.
5. Read the model page for the actual values
Only now open the model page. Supply voltage, load rating, radio band, transmit power, operating temperature, ingress protection and certification are per-SKU, and each model page shares its revision with the datasheet and the API. Ask for the current datasheet when a value you need is not published.
Failure modes
- Over-specifying a wall device for a plant-room load: the installation, not the rating, is usually the mismatch. A dry-contact input on a module is the intended pattern when the load is remote.
- Under-specifying the enclosure: a module chosen without an enclosure decision is not installable outdoors or in a wet plant room.
- Selecting by transmit power instead of by link: power is not the variable that fixes a link; position and antenna are. See Coverage and site survey.
Placeholder — pending engineering sign-off: the selection matrix that maps load class and enclosure class to a specific SKU id is not published yet and is being completed with the model data.
Limitations
- This page carries no electrical or radio figures on purpose. Every rating depends on the SKU and the revision, and both are stated on the model page.
- Roadmap capabilities are not part of a shipping specification. If a model page marks a capability as planned, it must not be specified into a live design; the rule is set out on the model page under its stated limits.
What this document does not cover: a comparison against non-LoRa control technologies belongs to the comparison pages, and the compliance route belongs to Radio and electrical routes.