Thermostat Platforms for OEM Programs: Low Voltage to Connected

Reference platforms, configured to your program

We do not publish a price list or a stock catalog, because the products we ship are built for a named customer and a named market. The platform families below are the starting points for most programs. Each can be rebranded, reconfigured, or re-spun into something that carries your model number.

Low-voltage programmable

A 24 VAC platform for conventional rooftop units, split systems, and heat pumps. Typical configuration is two heat and two cool stages, heat pump with auxiliary and emergency heat, a seven-day or five-two schedule, and adjustable setpoint limits. Outputs are relay-based. Display options run from a segmented LCD to a dot-matrix panel with touch keys.

This family is the usual starting point for equipment manufacturers who need a control that matches a specific unit's sequence rather than a generic aftermarket behavior. It also suits replacement programs where a legacy control is out of production and the installed base still needs a functional equivalent.

Line-voltage

Direct-line models for baseboard and fan-forced heaters, unit heaters, and hydronic zone valves at 120, 208, 240, or 277 VAC. These designs live or die on thermal management, terminal accessibility, and isolation distance. Enclosures can be engineered for surface mounting over a junction box or for a specific panel cutout.

Where a program needs a line-voltage control that also reports to a building system, we can pair the switching stage with a low-voltage communication board inside the same enclosure.

Communicating

A low-voltage platform with BACnet MS/TP or Modbus RTU for building automation integration, aimed at VAV boxes, fan coils, and packaged equipment that has to appear as points on a supervisor. Each program includes a written point map, naming convention, and integration notes so the controls contractor is not reverse-engineering the register table on site.

Gateways to IP-based systems are handled as part of the program rather than as an accessory, because the gateway's behavior becomes part of what the customer supports.

Connected

Wi-Fi and Bluetooth Low Energy models for products that need commissioning from a phone, remote diagnostics, or a building-owner app. The mobile application, cloud backend, and data ownership model are decided at the specification stage. Options include a customer-hosted backend, a third-party platform, or a firmware-only product that exposes a local API and leaves the cloud to the brand.

We are explicit about the boundary: a connected thermostat is a security-relevant device on someone's network. Firmware update policy, credential handling, and vulnerability response need an owner before launch, and we will not ship a connected product without one.

Sensors and accessories

Remote temperature sensors, occupancy inputs, outdoor air sensors, and mounting adapters. These are usually the parts that determine whether a retrofit takes twenty minutes or two hours, so they get designed with the thermostat rather than sourced afterwards.

What is fixed and what moves

Fixed: the safety architecture, the certified component set where a certification exists, and the test limits that define a passing unit. Movable: branding, color, overlay artwork, terminal labeling, default parameters, feature set, packaging, language, and accessories.

If a requested change would move something fixed, we say so and quote the validation work required. That is a slower conversation at the start and a much shorter one at the end.

Selecting a platform

Send the equipment, the voltage and load, the sequence of operation, the market, and the annual volume. We will tell you which platform is closest, what has to change, and whether the honest answer is a new design. The OEM process explains the stages, and contact is where the review begins.