Of many platforms, one.

Ten apps, or one

A house collects systems by itself. The switches sit on a bus, the inverter on the roof has its own portal, the heat pump its own app, the doorbell too, and the car one more. Each of them does its job well. They just know nothing of one another.

The doorbell does not know the gate. The heat pump does not see the sun on the roof. The battery does not know what power costs tomorrow. And whoever comes home opens four apps to set up one evening.

Lenou lays one layer over all of it. One app on iPhone and iPad, one screen on the wall, one web app on the box. The same rooms, the same tiles, the same rules — whatever brand is behind them.

One set of rules, across brands

Only when everything lives in one house can one device answer another. A few examples of what works today:

• The doorbell opens the gate. A press on a DoorBird or a 2N is an event in Lenou. A rule can pulse the gate on KNX and switch on the hall light.
• The heat pump follows the sun and the tariff. Lenou picks the SG-Ready state from the day-ahead price and from what flows to the grid — on a CTC straight over Modbus, on another make through two relays.
• The battery follows the plan. Every quarter of an hour a plan from the solar forecast, the house's own consumption and tomorrow's prices. A SigenStor or an SMA Sunny Island takes it as an order.
• The car charges on what the roof leaves over, or at the cheapest hours before seven, and always under the quarter-hour peak of the capacity tariff.
• The screens go up in the wind. A KNX weather station on the roof feeds a wind rule for the screens, even when they are another make.

Rules are written by whoever runs the house. Lenou switches none on by itself.

Local where it can be

Most systems Lenou speaks to directly, on the house's own network: KNX over IP, Modbus TCP, OpenWebNet, MQTT, and the local API of the bridge or gateway that is already there. That needs no internet and no account with the manufacturer.

Some makes offer only their own cloud: the cars, Miele, Mitsubishi Electric, Hunter Hydrawise, the new Innova units. Then it says so. If the line goes down, those devices show "unavailable" — and the rest of the house carries on.

• Local straight on the house network, without internet.
• Online once fetch a key from the make once, local after that.
• Cloud only through the make's service; no internet, no control.
• In progress built, but not yet checked on a real device. See below.

What “in progress” means

Some integrations are in the code but have not been checked on a device that actually runs, or rest on a register map nobody at Lenou has yet held next to a working machine. Those are called "in progress" here. What they control is checked on site first, with the installer present. Where a register map is not yet confirmed, they control nothing.

The reverse holds too: where something has been measured on a real installation, the brief says so.

Your make not here?

Much that is not named here still comes in: over Modbus with a register profile, over MQTT, over a simple JSON API, or through Home Assistant as a bridge. Just ask: info@lenou.be.

How the app itself works is on Lenou Home. What happens to your data, in the privacy policy.