For KNX integrators and smart home technicians
Every callback starts with hours you cannot bill.
Casient reads the KNX project you already commissioned and tells you what the house really does. It installs on top of your work — it does not replace your install, your ETS logic or the way you commission.
Start with the free check. One file, about a minute.
Upload your .knxproj — free
Every device setting, every automation already running on the bus, and every fault. Run it on a project you know well, so you can judge it.
Run the free checkRegister with an email and the check is yours to use, free. No card, about a minute.
How the check works, in three steps. One: your KNX project file goes in — a .knxproj from ETS. Two: it is mapped onto Casient's model of a home — rooms, devices, what each device can do, and what depends on what. Three: what comes back is the settings, the automation already running, and the faults. It takes about one minute.
What this is actually for
The install earns once. You carry it for twenty years.
None of the following is a KNX problem. They are the four places a good integration business loses margin on a job it did well.
Every callback starts by reading a job you finished two years ago
The behaviour is not in your notes. It is inside device parameters — hold times, thresholds, staircase timers, scene tables — and no tool reads those back to you as plain sentences.
So you open ETS and work out what you did. That is billable time you will not bill.
Handover documentation is work nobody pays for
It is not in the quote, it is not in the variation, and it is the last thing left when the job is already late.
So it gets written thin. Then the client rings about something the pack should have answered, and you drive out for free.
The automation stops where the platform stops
A KNX device only knows what it can sense itself. It cannot see a power price, a weather forecast, a calendar, or the room next door.
Anything needing two of those at once has nowhere to be decided — so it ends up in YAML, in a Lua block or in a flow editor, and by the third house that logic is not maintainable by anyone but you.
Your network has monitoring. Your automation layer does not
Monitoring suites such as Domotz or OvrC do their job well, and if you run one you already know when a switch drops off the network. That is not the gap.
The gap is that nothing tells you a KNX bus went quiet, a setting drifted away from the one you commissioned, or a box is filling its disk. You find out when the client rings.
The job, and the house. You build it in a few weeks. The house then runs for twenty years, and in KNX it runs exactly as you commissioned it — nothing drifts, and nobody else can change it. Handover on 2026-02-15. On that project the check found 21 automations running on the bus that appear in no documentation, 12 of them sensor-driven. That is what a callback starts by rediscovering.
Live example. A real KNX installation in Lindfield, NSW.
| Room | Address | Hold |
|---|---|---|
| Study | 1/1/31 | 10 sneeds 30 s |
| Bath 1 | 1/2/4 | 10 sneeds 30 s |
| Bath 2 | 1/2/9 | 10 sneeds 30 s |
| Laundry | 1/2/14 | 10 sneeds 30 s |
| Kitchen | 1/1/12 | 45 s |
| Living | 1/1/5 | 60 s |
Four rooms go dark while people are standing in them
The lights hold for 10 seconds. That is the lowest the detector will go. The maker's own manual says:
“A value below 30 seconds is not recommended in rooms where people remain stationary.”
Nobody chose this. Somebody left a default. It is in the project file, and no tool was reading it.
What Casient is
A box that sits on top of a house that already works.
Two things, and the same model of the house underneath both. The free check reads a project file. The appliance is a box in the rack that runs the house that file describes.
It is a KNX device first. It joins a commissioned bus through a certified KNX interface and speaks the installation's own language. It does not re-architect your install, and it does not ask you to move your logic anywhere.
What it adds is the decisions a KNX device has no way to make, because a device only knows what it can sense itself — it cannot see the power price, the weather, the calendar or the room next door. Casient maps the installation onto a model of a home — rooms, devices, what each device can do, what depends on what — and decides against that.
The engine is deterministic and it explains itself. It does not infer a rule and apply it quietly. Policies are written down, they resolve against each other in a fixed order, and every action records the policy that won, what that policy beat, and the evidence it used. That is the difference between an automation you can defend to a client and one you can only apologise for.
The rules it is built under
- It runs on the system you already commissionedThe appliance installs on top of a working KNX installation. Your ETS project, your group addressing and the way you commission do not change.
- Safety and comfort stay on the busPrimary reflexes are never moved up into our layer. Lose the box, the network and the internet, and the house still works the way you programmed it.
- Every decision is written downEach action is logged with the policy that won, what it beat, the evidence it used and the tier it acted at. You can answer a client who asks why the house did something.
- We do not hold a catalogue of your clients’ housesNo device-level detail from a live house is kept in our cloud. The appliance keeps the house in the house. What is in our cloud is the project files you chose to upload, in your workspace, under your account.
- Support access is the homeowner’s to give and to take backNot yours to grant on their behalf, and not ours to help ourselves to. Scoped to a session, time-boxed, and logged where they can read it.
- Two independent sources to change the boundary of the houseNothing that unlocks or opens the house acts on a single sensor. That is a rule in the engine, not a setting somebody can forget.
Where this is up to. It is early days. The check is live and you can use it today. The appliance is running in one house and the fleet console is a pilot — and what we are looking for now is a small number of integrators to put it into new projects with us, and to tell us where it is wrong. If that is interesting, send an email.
How we sell
We work with you, never around you.
Casient is sold through integrators. It is not sold to homeowners, and it never will be.
- —The client stays yours. The handover pack goes out under your name; ours appears only if you decide it should.
- —We do not market to your clients. When one of them contacts us directly, we tell them to call you.
- —No consumer pricing, anywhere. There is no price on this site and there is no homeowner shop. A client cannot find out what you paid, and cannot buy around you.
- —The recurring relationship is yours to sell. Monitoring, backup, restore and support access run under your name. We are your supplier, not your competitor.
- —Your projects are not our training data. Our staff do not open your project files. If you ask us for help and we need to look, you grant it — for that job, for that session, and it is written down.
One exception, and it is the one we are proudest of. The homeowner — not you, and not us — grants and revokes remote support access to their own house. Nobody lets themselves in, including us. That means a direct line to the owner exists by design, for access and for nothing else: no marketing, no offers, no upgrade path that goes around you. We built it that way because privacy-conscious clients ask for exactly this, and because a vendor who can quietly enter a house is a vendor neither of us should want in the rack.
Questions you probably have
Open the ones you care about. Skip the rest.
What does it cost?
The check is free to use. Register with an email and run it on your projects. There is no card, no trial clock counting down and no feature held back to make a point — you see what it found, including the recommendations and the reasons behind them.
What you get for nothing:
- Every device setting, every automation, every fault.
- The recommendations, and the reasoning behind each one.
- Fix it in ETS, upload the new version, and see what moved.
- Read the handover document on screen.
Your projects stay until you delete them. Delete one, or delete the whole account, and it is gone — the file, the findings, the history. If an account sits untouched for a very long time we may eventually clear it out, but not without telling you first and giving you the chance to keep it.
The appliance and the managed service are commercial products, and they are not free. We are not publishing prices for them here. Right now we are working with a small number of integrators on the first deployments, and the terms are part of that conversation rather than a page on a website.
There is no homeowner price list on this site or anywhere else, and there will not be.
What exactly do you store, and where?
The honest short answer: the project files you upload, and very little else.
- Project files you upload. They sit in your workspace, under your account, and they are the whole point of the tool — it cannot tell you what is in your project without reading it.
- No device-level data from a live house is kept in our cloud. The appliance keeps the house's state in the house. We do not run a central database of what is switched on in your clients' homes, because we did not build one.
- Backups, if the client takes them, are encrypted before they leave the box and stored in an Australian region. We hold ciphertext. They restore onto replacement hardware.
- Projects from Australian installations stay in an Australian region.
The software reads your file. The people here do not. Casient staff do not open your projects — not to browse, not to learn from, not to show anyone. If you ask us for help and we need to look, you grant it, for that job and that session, and it is written down. Same rule the appliance uses inside a house; we did not want two standards.
We do not sell your projects or share them with anyone. We would like them to improve our device catalogue, anonymously. We ask first, and no is a fine answer.
Use a strong password and turn on two-factor. That is the part that actually protects your projects, and it is good practice anyway.
If your export has a project password: give it to us at the upload. The tool needs it; the people here do not. The parser uses it to open the file, for that one read, and it is not stored, not logged and never seen by anyone who works here.
Not built yet — today a protected export is refused and you have to re-export without the password. It is next on the list.
Do I have to change how I commission?
No. Keep using ETS the way you use it. Keep your group addressing convention. Keep your logic in the devices. The check reads the project you already have, and the appliance joins a bus that is already working.
The one thing we ask is the thing you already do: export the project. Everything else is read-only until you decide otherwise.
And if the box dies, the house does not. Safety and comfort logic stays on the bus. Physical switches keep switching and the scenes you programmed keep running. That is a rule in the architecture, not a fallback mode.
Why KNX — and when should I look at another system?
Why KNX is a good choice.
- It is an open standard. Parts from different makers work together.
- The logic sits in the devices. One failure does not stop the house.
- No dealer network decides who may service the job.
- A device bought years ago still talks to one bought today.
When to consider others. Control4 and Crestron are built around AV: sources, distribution and a polished screen. Lutron is excellent at lighting and shading. Loxone puts control and interface in one stack. If a job is AV-first, or the client is buying the screen as much as the house, those products have the depth.
Many good jobs use both — a bus for control, one of those for AV. Casient is built to sit over that, not to argue with it. We integrate AV rather than control it natively. That is a real difference and we are not going to hide it.
Is this for me?
Probably yes if: you commission four or more KNX projects a year, and connecting KNX to an app, to Home Assistant or to a visualisation is painful every time.
Probably not yet if: you install and move on, and that works for you. Twenty-five jobs a year with no integration work is not a problem we solve.
Either way the check is free. Run it on one project and see.
Start with one project file.
Pick a job you already know well. See whether we tell you something you did not know about it.
Upload your .knxproj — free
About a minute. Nothing to install.
Run the free checkRegister with an email. No card.
We are a small team, in Australia and elsewhere. Right now when you write, you get Ted. Send an email, or read who we are first. If we have something wrong, tell us — we would rather be corrected.