Capabilities: Thermostat Hardware, Firmware, and Integration

The engineering envelope

This page describes what we design and build, and where we will tell you that a requirement sits outside our process. It is not a catalog. Configurations are set per program, and the specification you approve governs.

Electrical platforms

Low-voltage models run from a 24 VAC transformer and switch conventional equipment: single and multi-stage heating and cooling, heat pumps with auxiliary and emergency heat, and fan coils with three-speed fans. Outputs are relay-based where isolation and ruggedness matter, and solid-state where silent switching or frequent cycling is required.

Line-voltage models operate directly at 120, 208, 240, or 277 VAC for baseboard heat, unit heaters, fan coils, and hydronic valves. These designs carry the isolation, creepage, and thermal design that line voltage demands, including terminals sized for field wiring and a metal or flame-rated enclosure where the application calls for it.

Control behavior

We implement the sequence of operation your equipment needs: staging, deadbands, minimum run and off times, fan delays, economizer interlocks, freeze and high-limit protection, occupancy and unoccupied setback, and remote setback inputs. Schedules can be seven-day, five-two, or a simple occupancy model, depending on how the building is run.

Where a customer has an existing control board and wants the thermostat to behave like the incumbent, we work from a behavior matrix rather than from a marketing description. Recording what the old device does at each state is usually the fastest path to a replacement that nobody notices.

Connectivity

• BACnet MS/TP for building automation networks
• Modbus RTU over RS-485 for equipment and legacy controls
• Wi-Fi and Bluetooth Low Energy for connected products and commissioning
• Dry-contact and analog inputs for sensors, economizers, and remote enable

Protocol work includes the object or register map, point naming, and a written integration guide. If the product connects to a cloud service, the API contract and the data ownership terms are agreed before firmware work begins, and the customer chooses whether the backend is theirs, ours, or a third party's.

Sensing and user interface

On-board temperature sensing with remote sensor support, occupancy input, and optional humidity sensing. Displays range from a segmented LCD with physical buttons to a dot-matrix panel with capacitive touch, depending on the cost target and the hands that will use it. Overlays, icons, and language sets are part of the design, not an afterthought.

Enclosure work covers wall-mount housings, flush plates, gaskets, and mounting adapters for junction boxes and retrofit plates. We build appearance models and functional prototypes so the industrial design can be judged in a room rather than on a screen.

Firmware and documentation

Firmware is written for the specific product, with parameter storage, watchdog behavior, brown-out handling, and a defined safe state on sensor fault. We can supply source code under a license agreement, provide a binary with a documented parameter interface, or take responsibility for maintenance releases. That choice is made in the contract, not after the first bug.

Manufacturing and test

SMT assembly, in-circuit or functional test fixtures, programming and calibration, burn-in where the program requires it, and serialized traceability. Test coverage is designed with the product, because a fixture built after the design freeze tends to test what is easy rather than what matters.

Where we are not the right fit

We are not an installer or a service contractor, and we do not sell stock thermostats to end users. We are not a good match for a buyer who wants the lowest piece price on a generic retail thermostat with no documentation, or for a program that needs a certification claim before a design exists. If another supplier fits better, we will say so.

Send the requirement through contact; the OEM process page shows what happens after that.