A white label FCU thermostat is how an HVAC brand puts its own glass on a three-speed fan-coil wall, without a retail SKU and without assuming analogue fan control. Specifiers want 230 VAC relays for fan speeds and heat or cool, a Modbus citizen, and a logo that is theirs.
White LabelFCUOEMHVACHeat PumpTemperature
Alledio’s OEM Thermostat is that class of device. It is designed in Slovenia and manufactured in the EU. Relays switch the coil and the three-speed fan. The glass, the sensors, and the bus are the brand face the occupant sees.
Who this is for
This article is for OEM product managers, FCU and AHU brand owners, and BMS device makers who need a branded relay thermostat at production volume, not a one-off installer SKU.
Typical applications on the product page are fan coil units, air handling units, DX equipment, and other local HVAC systems that need relay outputs. End markets on the OEM page include offices, schools, hotels and museums. Installers and system integrators cannot buy Alledio direct. The commercial model is high-MOQ OEM. The usual MOQ is 1,000 pcs, and it is negotiable.
This is not the Room Unit. That SKU is a low-voltage, host-driven wall UI. This post is the Alledio OEM Thermostat — 230 VAC, fan-speed relays, heat/cool relays. If you need more standalone I/O in the same family, that is the Room Controller, not this SKU.
Andivi will be at MCE Milano 2026 if you want that conversation in person. The thermostat RFQ still starts from the published relay spec, not from a retail demo.
What white label covers on an FCU relay thermostat
Buyers lose months when “white label” is treated as a logo file on a catalogue thermostat. Ask for the surfaces that change on the glass and the relays that stay on the wall. A useful RFQ lists each surface, who owns the artwork, and whether the change is NRE or a catalogue option.
Brand surfaces on the OEM Thermostat:
- Exterior logo on glass or bezel
- UI colours, widgets, and firmware features
- Housing colourways (white, black, silver, plus custom)
- Optional VOC and CO2 as listed on the product page
- Documentation, packing, and faceplate language that matches your FCU line
OEM customisation is the NRE path. You pay for the delta — logo, UI, firmware, optional hardware — not for a new radio and a new mould. If two SKUs share electronics and only differ in logo and colour, say so. That is how MOQ stays honest.
Write what you will not change. The 98 mm square, the 3.5" glass, the 230 VAC supply, and the relay fan path are the platform. White label does not add EC fan control, a KNX catalogue SKU, or a retail box unless you quoted that work separately.
A hotel FCU SKU and a commercial office SKU can share the same board and still look like two products. The hotel pack usually wants a quiet night schedule and a colourway that matches the corridor glass. The office pack usually wants the same three-speed relays and heat/cool outputs, plus a Modbus map the BMS already expects. Write those as two brand packs on one electronics revision. That is the commercial point: one NRE conversation, two faces, one relay map.
If your current indoor unit is a private-label wall thermostat from a catalogue house, treat this as a swap of the wall face and the relays, not a swap of the fan-coil chassis. The occupant only ever sees your glass. The plant still sees contact closures for fan speeds and heat or cool.
Fan speeds and relays on a branded FCU thermostat
A 3-speed FCU OEM thermostat is the sentence most FCU RFQs should start with. The published fan path is relays: speed 1, speed 2, speed 3, Auto, and off. Heat and cool are also relays. Do not assume an EC motor or a 0–10 V fan output on this SKU.
Three-speed relays vs EC
The glass shows temperature and humidity and takes a setpoint. Fan speed is manual or Auto. A weekly schedule with intervals is listed. Optional air-quality and CO2 sensors are orderable. An external NTC temperature sensor is listed. None of that turns the fan path into analogue control. If your coil uses a three-speed motor, this is the relay SKU you quote.
The product page also names AHUs, DX equipment, and other local HVAC systems that need relay outputs. Recuperation views, sanitary warm-water shortcuts, temporary fan boost, and similar application widgets are described as firmware that can sit on the same design library. Quote those as firmware NRE, not as a hidden EC option.
I/O models that sit on top of fan contacts
Four thermostat models are listed for I/O flexibility: 2 × AO, 2 × DO, 1 × AO plus 1 × DO, and 2 × relay heat/cool, on top of power, Modbus, and the fan-speed relays. Those analogue and digital options are models. If you need a voltage fan signal, say so as a separate question. The published default remains three relay speeds plus heat/cool contacts.
Relays, 230 VAC, and how to write the RFQ
Power on the thermostat page is 230 VAC. Do not copy the Room Unit’s 12–42 V DC or 24 VAC line into this RFQ. Current and consumption figures are marked “update coming soon” on the page; leave those cells blank until the datasheet is current.
Mechanics you can defend today: 98 × 98 × 14 mm, 150 g, IP20, ABS plus scratch-resistant glass, flush-mounted in a standard EU box (Ø 60 mm). Ambient on the page is −10 to +50 °C, max. 85% rH non-condensing. The display is a 3.5" LCD at 480 × 320 with capacitive touch and a brightness sensor. Colourways are white, black and silver. That is an OEM wall thermostat, not a surface-mounted retail brick.
Ask for:
- 230 VAC supply and relay outputs for fan 1 / 2 / 3 / Auto / off plus heat/cool.
- Modbus RTU on RS-485 (half-duplex). The page lists baud rates from 9600 to 115200, with 4800 also in the Modbus table; parity none / even / odd; address 1–247 (default 1).
- Wi-Fi 2.4 GHz (802.11 b/g/n) STA if the SKU is connected; the technical table notes update support. MQTT is named on the page for cloud or web services.
- Bluetooth 5 LE ready; the GATT map is a client specification, not a catalogue protocol.
- Optional VOC, optional CO2, optional external NTC — only if the FCU line needs them.
- Compliance listed on the page: CE, EN 60730-1, EN 60730-2-9, EN 300 328 V2.2.2. Security updates are listed as 5 years.
State MOQ, sample count, NRE for firmware, and who owns the register map. Ask for the ICD with the mechanical drawing. Specify the cable class you already pull for RS-485 and the slave-ID plan so commissioning is not invented on site. Bring artwork early: logo on glass, UI chrome, and the exact colour codes for housing.
Documents and NRE to ask for
Name the documents you want back: ICD, register list, mechanical drawing, and a short integration note for the FCU controls team. That pack is what turns a pretty glass into a line item your coil and your BMS can both use.
Protocols that actually ship
On the OEM Thermostat: Modbus RTU over RS-485; Wi-Fi 2.4 GHz STA as listed; Bluetooth 5 LE ready per client spec; MQTT named for cloud or proprietary web services. OTA firmware updates are listed.
Not a catalogue SKU here: KNX. Other buses are OEM firmware or hardware work, quoted separately. Do not write a KNX or Nest-style retail part number into this RFQ.
For Modbus itself, write the things that break commissioning: address, baud, parity, stop bits (the page lists 8 data bits and 2 stop bits), and whether the host expects holding registers, input registers, or both. Alledio can ship a map that matches a map you already use. It will not guess your map if the RFQ only says “Modbus.”
Wi-Fi does not replace the copper pair. Use RS-485 when the BMS is already on a bus. Use Wi-Fi when the SKU needs OTA or a named cloud path. Write that split in the RFQ so field teams do not stand up an unquoted radio feature.
Product proof
| Topic | Published spec |
|---|---|
| Product | Alledio OEM Thermostat (Modbus / relay) |
| Power | 230 VAC |
| Fan relays | Speed 1 / 2 / 3 / Auto / off |
| H/C relays | Heating / cooling |
| Display | 3.5" LCD, 480 × 320, capacitive touch, auto brightness |
| Sensors (standard) | Digital temperature and humidity |
| Sensors (optional) | VOC, CO2, external NTC |
| Bus | RS-485 Modbus RTU, half-duplex |
| Wi-Fi | 2.4 GHz (802.11 b/g/n) STA |
| Mechanics | 98 × 98 × 14 mm, 150 g, IP20, EU flush box Ø 60 mm |
| Origin | Designed Slovenia, manufactured EU |
| Standards | CE, EN 60730-1, EN 60730-2-9, EN 300 328 V2.2.2 |
| Security support | 5-year update window |
Use this table in the brand pack, then attach your logo and UI screens separately. Current and power-consumption cells are unpublished on the product page; leave them empty until the datasheet is current.
FAQ
Does it run a 3-speed FCU fan?
Yes. Fan relays are speed 1, 2, 3, Auto, and off, plus heat and cool relays, on 230 VAC. If your coil uses a three-speed motor, this is the SKU to quote.
Should we assume EC or 0–10 V fan control?
No. The published fan path is relays. There are analogue and digital I/O models, but they are not a licence to write EC into the RFQ. If you need a voltage fan signal, ask that as a separate question.
What is the MOQ?
The usual MOQ is 1,000 pcs, and it is negotiable. If you order several thermostat versions that share electronics and only differ in logo or colour, and the combined quantity is over 1,000 pcs, ask on /oem whether a path down to 500 on a version is available for this SKU.
Can we get samples?
Yes. Samples are available with demo firmware or test firmware, under NDA. This is not a webshop SKU. Start the conversation on /oem.
Can an installer buy this from a webshop?
No. Alledio sells to OEMs. Installers and SIs get devices through your channel.
Is this a Nest-style retail thermostat?
No. It is a white-label OEM thermostat for HVAC brands. There is no retail SKU and no installer webshop.
What to do next
Start on the Alledio OEM Thermostat page, then open an OEM conversation for logo, UI, firmware and samples. Bring fan type (three-speed relays, not assumed EC), 230 VAC, Modbus map, MOQ, and the artwork for the glass. That is how a white label FCU thermostat becomes a branded SKU instead of a sticker.
