HVAC brands that want their logo on the wall and I/O behind the glass do not start from a retail thermostat. A white label room controller HVAC programme puts capacitive glass, sensors, universal I/O, and optional local apps under your brand - designed in Slovenia, manufactured in the EU, sold only as high-MOQ OEM.
White LabelOEMRoom ControllerHVACModbusUniversal I/O
Who buys a white-label Room Controller
This article is for OEM product managers and BMS device makers who need a branded wall controller with field I/O - not a display-only room face and not a 230 VAC relay thermostat. Installers buy through your channel, not from Alledio direct.
If the programme is a 230 VAC relay thermostat or a display-only room face, the white-label FCU thermostat and white-label HVAC room display articles cover those families. Here the focus is the Room Controller: glass, sensors, and universal I/O that runs its own control loops.
The difference is simple. A room unit reports; a room controller decides. The Alledio Room Controller runs its own loops and drives its own outputs, and it can also sit on a Modbus bus as a slave when a BMS sits above it. One part number covers the standalone job and the networked job, so you do not stock two products for two project types.
Commercial model: MOQ 1,000 negotiable; 500 possible if several Room Unit or Room Controller versions combined exceed 1,000. Samples use demo or test firmware under NDA via the OEM programme.
Bring purchasing into the conversation early. A white-label controller that shares a mould with your Room Unit line reduces tooling risk, but only if the RFQ keeps I/O versions explicit and does not assume every glass ships every terminal.
A white-label Room Controller is a B2B platform SKU with MOQ, NRE and a pin map, not a retail smart-thermostat story.
White label room controller HVAC - brand pack needs I/O
Branding without I/O is a display. The Room Controller published maximum is 2x UI, 3x UO, and 1x UIO on TH / TH1 / TH2 / TH3 versions. Analogue 0-10 V sits in the UO class for valves and EC fans; digital paths take contacts you already stock.
On a fan coil, the published Room Controller map typically puts room temperature and occupancy on UI, a 0-10 V or staged fan signal on UO, and heating and cooling valves as on/off or 0-10 V. Window contacts and condensate overflow can take the remaining inputs.
Need 3-speed fans or on/off valves? Pair the controller with the MR5 relay extender, a 5-channel Modbus relay module, so up to five relays switch fan speeds, valves, or shading while the controller keeps its own universal I/Os for sensors and low-voltage signals.
Application logic you specify in firmware - sequences, schedules, OEM widgets - can run locally while safeties stay on the host you certify. Start from the universal I/O pillar when the RFQ is about terminals, not only chrome.
Power is 18-42 V DC (24 V recommended) or 24 VAC +/-25%. Never put 230 VAC on this SKU - that is the Thermostat family covered by OEM Modbus relay thermostat.
When the programme also needs an analogue FCU map, the 4-pipe fan coil room controller 0-10V article covers valves and fan signals in detail. Branding is one conversation; pipe topology is another.
Brand surfaces that survive an RFQ
White label means logo, colourway, boot splash, widget set, packing, and docs - not a new mould for every hotel chain. OEM customisation quotes the delta against a modular platform.
A hotel SKU and a commercial office SKU can share one electronics revision and still look like two products. Write the brand pack early so artwork lands before the first production lot.
What the brand pack covers
- Logo on the glass and on the UI welcome screen, supplied as a vector PDF or SVG.
- Colour scheme matched to your corporate palette.
- UI layout, icons, screen set, and new widgets that fit the rest of the interface.
- Case colour: white, black, and silver are standard; custom colours are possible.
- Firmware features, protocol, and application logic.
Dimensions and internals are a bigger conversation. Changing them turns the request into an ODM project with its own timeline, so most programmes keep the 98 x 98 mm platform and differentiate on glass, UI, and firmware.
NRE, lead time, and what gets quoted separately
Firmware modifications are possible, but they are billed separately from the unit price. A tweak stays a tweak; a genuinely new firmware build is planned, developed, and tested as a project, and it is quoted as one.
Published lead time is 8-12 weeks once the design and firmware specification are signed off. Put that sign-off date in your launch plan before artwork and packaging, not after.
Protocols, bus, and what is not a catalogue checkbox
Modbus RTU on RS-485 is the default copper citizen. Native BACnet and KNX are not catalogue SKUs - budget a separate quote.
If you only need a host-driven UI without wall I/O, start the Room Unit RFQ instead - it is the display-first sibling on the same glass.
Keep the Modbus map your integrators already know
Most of the integration pain is the point list, not the device. If your current line already ships a Modbus map, Alledio can match the register map - same register numbers, scaling, and bit meanings - so integrators keep the templates they have built.
Bus facts your BMS team will ask for: half-duplex RS-485, 9600 to 115200 baud, parity none, even, or odd, and slave by default with master available on request. Wi-Fi 2.4 GHz handles over-the-air updates, and MQTT/REST access is restricted to authorised partners.
Commissioning lives on the device itself. The built-in touch display handles configuration, so the installer does not need a separate app or account just to change a setpoint.
Mechanics and EU origin
Mechanics publish as 98 x 98 x 23 mm, 150 g, IP20. Display is 3.5 inch 480x320 capacitive. Designed in Slovenia; manufactured in the EU.
Compliance references RED 2014/53/EU and RoHS. The EU Declaration of Conformity is on the Documents page.
For a rebranded product, you receive the CE file behind it: LVD and EMC test reports, the EU Declaration of Conformity, and a RoHS declaration. Alledio helps you assemble what your importer asks for when your brand goes on the box.
The published secure support period is 10 years of security updates and vulnerability handling from first placement on the market. That matters more each year as connected HVAC devices come under the Cyber Resilience Act.
Product proof
Published white-label proof is brand surfaces + universal I/O + Modbus on one EU Room Controller.
| Topic | Published spec |
|---|---|
| Display | 3.5" LCD, 480 x 320, capacitive touch, auto brightness |
| Sensors (standard) | Temperature and humidity |
| Sensors (optional) | VOC, CO2 (400-5000 ppm), pressure, presence |
| Universal I/O (max) | 2x UI, 3x UO, 1x UIO (TH / TH1 / TH2 / TH3) |
| I/O classes | Analogue 0-10 V / 4-20 mA; digital open-collector / 0-30 V input |
| Fan path on RC | Analogue 0-10 V / EC on UO - not 3-speed 230 VAC relays |
| Bus | RS-485 Modbus RTU (slave default; master on request), 9600-115200 |
| Radio / API | Wi-Fi 2.4 GHz with OTA; MQTT/REST for authorised partners; BLE 5 ready |
| Power | 18-42 V DC (24 V recommended) or 24 VAC +/-25%; never 230 VAC on RC |
| Mechanics | 98 x 98 x 23 mm, 150 g, IP20 |
| Origin | Designed Slovenia, manufactured EU |
| Commercial | OEM-only; MOQ 1,000 (negotiable; 500 if several RU/RC versions combined exceed 1,000); samples with demo/test firmware |
Not in the published catalogue: native BACnet; KNX SKU; installer webshop; 230 VAC relays.
FAQ
Is this the same as white-label FCU thermostat?
No. That live post covers the 230 VAC relay Thermostat. This page is the Room Controller with universal I/O.
Can we keep our own control sequences?
Yes. Local apps and widgets are part of the OEM firmware scope; plant safeties stay on the host you certify.
Can we get samples?
Yes. Samples ship with demo or test firmware under NDA via the OEM conversation.
What is the MOQ?
MOQ starts at 1,000 and is negotiable. 500 is possible when several Room Unit or Room Controller versions combined exceed 1,000.
Is there a KNX catalogue SKU?
No. Modbus RTU on RS-485 is the default. KNX or native BACnet requires a separate quote.
Can an installer buy from a webshop?
No. Alledio sells OEM-only.
What is the lead time after sign-off?
8-12 weeks once the design and firmware specification are approved.
Can you match our existing Modbus register map?
Yes. Register numbers, scaling, and bit meanings can follow your current product line so integrators keep their templates.
What to do next
Open the Alledio OEM Room Controller page, then start an OEM conversation for logo, UI, I/O version, NRE, and samples with demo firmware.
