A white label HVAC room display is how an OEM keeps the plant IP on the board they already certify, and still puts a branded face on the wall. Specifiers do not want a generic thermostat with a sticker. They want glass, sensors, and a bus citizen that already speaks RS-485, with their logo on a 3.5" panel.
White LabelOEMHVACTemperatureHumidityBMS
Alledio’s Room Unit is that class of device. It is designed and manufactured in Slovenia for HVAC original equipment manufacturers. The host still runs the plant. The wall unit is the branded display, the sensors, and the fieldbus endpoint.
Who this is for
This article is for OEM product managers, industrial designers, and BMS device makers who need a branded wall display at production volume, not a one-off installer SKU.
Typical lines: AHUs, residential and commercial heat pumps, VAV and rooftop units, ductless mini-splits, VRV, chillers, boilers and DHW, plus actuator-facing UIs. End markets 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.
If you need standalone I/O and application logic in the same family, that is the Room Controller, not this SKU. When that controller must carry your brand too, the white label room controller HVAC guide covers logo, UI, and I/O on the same glass. White label here means the display and the brand surfaces, not a transfer of your plant code onto the wall.
What a white label HVAC room display actually covers
Buyers lose months when “white label” is treated as a logo file. Ask for the surfaces that change on the glass and the ones that stay on your host. A useful RFQ lists each surface, who owns the artwork, and whether the change is NRE or a catalogue option.
Brand surfaces on the Room Unit:
- Exterior logo on glass or bezel
- UI colours, widgets, and firmware features
- Housing colourways (white, black, silver, plus custom)
- Optional sensors: T/RH standard; VOC, CO2, pressure, presence as orderable variants
- Documentation, packing, and faceplate language that matches your product family
OEM customisation is the NRE path. You pay for the delta, not for a new radio and a new mould. Hardware, firmware, and documentation can follow the same programme. 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 RS-485 citizen, and the host-driven model are the platform. White label does not mean a new radio, a new protocol stack, or a new safety board unless you quoted that work separately.
A hotel SKU and a heat-pump SKU can share the same board and still look like two products. The hotel pack usually wants a quiet night mode, a one-tap absence, and a colourway that matches the corridor glass. The heat-pump pack usually wants the same T/RH and occupancy values on Modbus, plus a UI that shows the indoor unit as the brand the homeowner already bought. Write those as two brand packs on one electronics revision. That is the commercial point of a white label HVAC room display: one NRE conversation, two faces, one host map.
If your current indoor unit is a private-label thermostat from a catalogue house, treat this as a swap of the wall face, not a swap of the outdoor unit. The plant sequence stays on the board you already certify. The occupant only ever sees your glass.
Host vs wall
The display is host-driven. Setpoints, fan, schedule and alarms sit on the glass. Sequences, safeties and plant algorithms stay on your controller. Recuperation views or a sanitary hot-water shortcut are firmware options, but they are still requests to a host unless you specified the Room Controller.
That split is the point of a white label HVAC room display. Occupants see your brand. You keep control IP. Modbus RTU on RS-485 is the default copper pair. Wi-Fi is for OTA and, for verified partners, MQTT or REST. Bluetooth 5 LE is ready; the GATT map is yours.
Industrial designers should treat the wall unit as a faceplate programme: one electronics pack, several brand skins. Controls engineers should treat it as a slave that publishes sensors and accepts setpoints. When those two teams write one RFQ, the NRE stays on logo, UI and options instead of on a second hardware project.
Glass and housing the brand programme sits on
A 3.5 inch OEM HVAC touch panel is large enough for temperature, humidity, air quality and a one-tap absence, and small enough to stay in a 98 mm square. Capacitive touch plus a brightness sensor keeps the glass readable in a lobby and quiet in a bedroom.
Flush-friendly OEM wall UI flush mount (98 × 98 × 23 mm), IP20, ABS plus scratch-resistant glass. That is an OEM wall UI flush mount, not a surface-mounted retail thermostat. Power is 12–42 V DC (24 V recommended) or 24 VAC ±25%. Do not assume 230 VAC. That is the thermostat family.
Hotels and offices usually care about the glass and the colourway first. Heat-pump and AHU brands usually care about the bus and the host map first. The same 3.5" panel can carry both if the brand surfaces and the register map are written as separate lines in the RFQ.
The Room Unit was on the floor at Smart Building Expo Milan 2025 as a branded HVAC wall UI, not a DIY thermostat. How the room feels, not only how the glass looks, is also the thread of Beyond design: it’s how it feels.
MOQ, NRE, and how to write the RFQ
State MOQ, sample count, NRE for firmware, and who owns the register map. Ask for the ICD with the mechanical drawing. If you need a unique widget, a sanitary shortcut, or a hotel-style absence key, list it as firmware NRE, not as “the display should feel premium.”
Ask for:
- Slave Modbus RTU on RS-485 (9600–115200, parity none/even/odd, software-defined termination). Master only if you need it.
- Host-driven architecture: glass for setpoints; plant on your board.
- Default T/RH, optional VOC, CO2 (400–5000 ppm), pressure, presence.
- Wi-Fi 2.4 GHz and partner MQTT/REST if the SKU is connected.
- Compliance you can defend: RED 2014/53/EU, RoHS, 10-year security-update window.
Bring artwork early: logo on glass, UI chrome, and the exact colour codes for housing. Late artwork is what turns a white-label date into a second tool-shop date. If several brand SKUs share one electronics revision, say that in the RFQ so MOQ is counted on the common board, not on each logo.
Protocols that actually ship
On the Room Unit: Modbus RTU over RS-485 (slave default; master on request); Wi-Fi 2.4 GHz (STA/AP), OTA, HTTPS; Bluetooth 5 LE per client spec; REST and MQTT for authorised partners. The product page also lists a 0–10 V analogue output as a connectivity option.
Not a catalogue SKU here: native BACnet on this product (native BACnet lives on the Multi-Sensor family); KNX; 230 VAC relays (white label FCU thermostat / Room Controller). For three-speed fan coils on that relay family, see the 3-speed FCU OEM thermostat buyer guide.
White label does not invent a KNX or BACnet catalogue SKU. If the brand needs those buses, quote them as OEM work or keep sensing on the Multi-Sensor and keep this unit as the occupant display.
Product proof
| Topic | Published spec |
|---|---|
| Display | 3.5" LCD, 480 × 320, capacitive touch, auto brightness |
| Sensors (standard) | Digital temperature and humidity |
| Sensors (optional) | VOC, CO2 (400–5000 ppm), pressure, presence |
| Bus | RS-485 Modbus RTU, 9600–115200 baud |
| Power | 12–42 V DC or 24 VAC ±25%; ~0.3 W at 50% brightness |
| Mechanics | 98 × 98 × 23 mm, 150 g, IP20 |
| Origin | Slovenia, EU |
| Security support | 10-year update window |
Use this table in the brand pack, then attach your logo and UI screens separately. The electronics line stays Alledio. The face the occupant sees is yours.
FAQ
What does white label actually change?
The surfaces occupants see: logo, UI colours and widgets, housing colour, optional sensors, packing and docs. The 98 mm square, the 3.5" glass, the RS-485 citizen, and the host-driven model stay the platform.
Can two of our SKUs share one board?
Yes. A hotel pack and a heat-pump pack can share electronics and still look like two products. Write that in the RFQ so MOQ stays honest.
Does the Room Unit run the plant?
No. It is host-driven. Occupants see setpoints and sensors on the glass. Sequences and safeties stay on your controller, unless you specified the Room Controller.
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.
What is the MOQ?
The usual MOQ is 1,000 pcs, and it is negotiable. If you order several different versions of Room Unit or Room Controller and the combined quantity is over 1,000 pcs, we can go down to 500 on a version.
Can an installer buy this from a webshop?
No. Alledio sells to OEMs. Installers and SIs get units through your channel.
What to do next
Start on the Alledio Room Unit page, then open an OEM conversation for logo, UI, firmware and samples. Bring artwork early: logo on glass, UI chrome, and the exact colour codes for housing. Late artwork is what turns a white-label date into a second tool-shop date. If several brand SKUs share one electronics revision, say that in the RFQ so MOQ is counted on the common board, not on each logo.
