Alledio OEM Room Controller

A room unit reports. A room controller decides.

The room unit sits on the wall, measures the room, takes the user's setpoint, and hands all of it to a controller somewhere else that does the thinking. Take away the central controller and the room unit is a thermometer with a nice screen.

A room controller runs the logic itself and drives its own outputs. Valve, fan, damper — it decides and it switches.

The Alledio Room Controller does both, and this is the part that matters when you're specifying: one part number covers the standalone job and the networked job. It runs its own control loops, and it also sits on a Modbus bus as a slave when there's a BMS above it. You don't stock two products for two project types.

A thermostat has one job: read temperature, switch heating or cooling. That's it, and for a lot of rooms that's genuinely enough.

A room controller is doing several things at once. Multiple sensors, staged outputs, fan speeds, valve positions, air quality, and a bus connection so the building can see what's happening in that room and override it.

Rough rule: if the room only needs a setpoint, a thermostat is fine and cheaper. If the room needs a setpoint plus a fan plus a valve plus somebody upstairs watching CO2, you need a controller. Half of the FCU projects we quote start as "we just need a thermostat" and end up here once someone remembers the ventilation.

AHUs, rooftop units, VAV boxes, fan coil units, chillers, mini-splits, heat pumps residential and commercial, and straight actuator control.

The reason it stretches that far is the I/O. Up to two universal inputs, three universal outputs and one universal I/O, each configurable digital or analog. Fan coil wants three fan speeds and a valve. An AHU wants setpoint, occupancy and a couple of analog signals. Same board, different firmware config.

If your application isn't on that list, ask. It's probably closer than it looks.

Yes. It runs standalone and you set it up on the display on the wall.

No app. No dongle. No laptop with a USB-serial adapter and a config tool that only runs on Windows 7. This one is deliberate: 3.5" capacitive touch on the front, and every parameter an installer needs is reachable from it.

It's the complaint we heard most before we designed this thing. An installer standing in a plant room being told to download an app, sign up for an account, and pair over Bluetooth just to change a setpoint. So we built the configuration into the device instead.

When there is a BMS, the same unit joins the Modbus bus as a slave. Master firmware on request if you need it the other way round.

RS485 Modbus RTU natively. WiFi with API access and Bluetooth on top. MQTT if you're pushing data to your own cloud.

Modbus details, because this is what your integrators will ask: half-duplex, 9600 through 115200 baud, parity none/even/odd, slave by default, master available if your architecture needs it.

If you're running something proprietary, that's a firmware job, not a wall. We've done it. Give us your protocol spec and we'll tell you honestly whether it's two weeks or two months.

Up to 128, because the transceiver draws a quarter unit load instead of a full one.

The RS485 standard budgets 32 unit loads per segment. Most devices eat one each, so you get 32 of them. Ours takes a quarter, so the same segment carries four times as many. On a hotel floor or an office fit-out with a controller in every room, that's the difference between one trunk and four.

Now the honest part: 128 is the electrical limit, not a promise about your installation. Long runs at 115200 baud with unterminated ends and cheap unscreened cable will fall over well before you hit it. If you're planning a big bus, drop the baud rate, terminate both ends properly, and use real twisted pair with a drain wire. We wrote up the whole thing here: Modbus busline device limits and best practices

Wire it to the RS485 bus, set the address and baud rate on the display, map the registers into your BMS. Register list is in the ALL-RC datasheet.

Realistically most of the pain isn't the device, it's the point list. If your existing product line already has a Modbus map your customers know, we'll match it — same register numbers, same scaling, same bit meanings. Then your integrators keep using the templates they've already built and nobody has to be retrained.

That's usually a small firmware change. Ask about it early, before you've ordered.

Yes, we support both Modbus client and server editions of the Room Controller. Both firmware versions are available for Modbus client or server configurations (formerly referred to as slave and master editions). Please note that there is a small surcharge for hard coding Modbus master functionality to the Alledio Room Controller.

BACnet is not supported in our standard Room Controller firmware. Custom BACnet integration can be implemented upon request for specific datapoints you require.

Yes, Alexa and Google Assistant integration will be supported through the Room Controller. You'll be able to set, raise, lower, and report your room's temperature, switch between HVAC modes (heat/cool/auto/off) and regimes (economy, economy+, comfort, unoccupied), adjust fan speed (I, II, III, auto, off), and set timers to override your schedule.

Most of it. Logo, colours, the whole user interface, firmware behaviour, sensor mix, I/O configuration, protocol, and the case itself.

What that looks like in practice:

Logo and branding. Your logo on the glass, over 5000 units. Send us a vector file — PDF or SVG — and it also goes on the UI welcome screen. Colour scheme matched to your corporate palette.

The interface. Layout, colours, icons, which screens exist and what's on them. New widgets too, as long as they're properly thought through and they fit the rest of the UI. We'll push back if something's going to confuse an installer at 7am. That's not us being difficult, it's the whole reason the product works.

Hardware. Case colour is easy — white, black and silver are standard, custom colours are fine. Dimensions and internals are a bigger conversation and become a proper ODM project with its own timeline.

Firmware. Features, protocol, application logic. A tweak is a tweak. A genuinely new firmware build is a project with planning, development and test cycles, and we'll quote it as one instead of pretending it's a config change.

You're paying to change a product that already works, not to invent one. That's the entire point.

MOQ starts at 1000 units. Lead time is 8–12 weeks once the design and firmware spec are signed off.

Both move depending on what you've changed. Light customization sits at the bottom of that range. Rework the hardware and it's a different conversation, and we'd rather have it upfront than discover it in week nine.

The 1000 is also where logo replacement on the glass kicks in — that's a tooling thing, not an arbitrary threshold.

Samples before you commit: yes. Cost and timing depend on how customized the sample needs to be.

The price of the Alledio Room Controller varies based on the specific hardware capabilities required (VOC, CO2 sensor and various analog or digital I/O) and the quantity ordered. To provide an accurate quote, we recommend getting in touch with one of our experts to discuss your needs in detail.
Please note that there is a minimum order quantity (MOQ) of 1000 units per order, and while all firmware modifications are possible, they are billed separately.

Yes, samples of our Room Controller are available with demo firmware. Please note that these samples need to be purchased.

Direct purchase of Alledio devices from Andivi is not possible for installers. We sell exclusively to companies that manufacture their own HVAC equipment and are seeking an OEM version of the Room Controller to integrate or bundle into their product ecosystem.

We do not offer direct sales of Alledio Room Controllers to systems integrators or installers. Our focus is on supplying companies that manufacture their own HVAC or similar equipment and require an OEM version of the Room Controller to bundle it into their existing product lineup.

CO2 if you're doing demand-controlled ventilation. VOC if you care about what people actually smell.

CO2 tracks people. More occupants, more CO2, so it's the right signal for modulating fresh air. 400–5000 ppm, ±100 ppm ±10 % of measured value.

VOC catches things CO2 can't see: cleaning products, solvents, paint, cooking, whatever the printer is doing. VOC index 1–500 points. It's not a substitute for CO2, it's a different question.

Both can go in the same unit. Meeting rooms and classrooms, take CO2. Kitchens, labs, print rooms, add VOC. Offices where someone is going to put an air quality number on a dashboard, take both.

12–24 V, AC or DC. Screened twin twisted pair, 0.75–1 mm², screen earthed at the controller end only.

That last bit matters more than it sounds. Earth the screen at both ends and you've made a loop that will inject noise into exactly the bus you were trying to protect. One end. Controller end.

RS485 wants twisted pair with a drain wire and foil screen, properly rated for RS485. Terminals are push-in CAGE CLAMP for 0.2–0.75 mm², so no screwdriver and no over-torqued terminal in a cold plant room.

The device can be installed and connected online in just minutes. Our user interface (UI) is designed to be straightforward, ensuring that installers will not encounter any issues.
Our goal was to create an intuitive device that allows for a basic setup to be completed even without consulting the handbook.

Slovenia. Designed and built by Andivi in Maribor, in the EU.

This isn't a flag-waving thing. It's practical. When a component goes end-of-life or a customer needs a firmware change in a hurry, the engineers are in close to the manufacturing line. Compliance documentation is written for the market you're selling into, not translated after the fact. And you're not managing a supply chain across eight time zones with a factory that has 400 other customers ahead of you.

Freight from Slovenia to anywhere in the EU is days, not weeks on water.