Skip to content
CASIENT
CASIENTSheet 1 of 1Rev BScale NTS
§1  Scope

ETS shows you what you programmed. Not what it does.

Drop the project file in. You get back what the installation is actually doing — the parameters inside the devices, the automation already running on the bus, and the defects nobody wrote down.

Free, permanently. No card. You do not talk to anyone unless you want to.

Upload a .knxproj≈ 60 s · nothing leaves your control
Detector schedule — extract4 redlines
RoomAddressHold
Garage1/1/8120 s
Hall1/1/290 s
Living1/1/560 s
Kitchen1/1/1245 s
Study1/1/3110 s≥ 30 s
Bath 11/2/410 s≥ 30 s
Bath 21/2/910 s≥ 30 s
Laundry1/2/1410 s≥ 30 s
4 rooms hold their lights for 10 seconds — the detector's own minimum. The manufacturer's manual says“a value below 30 seconds is not recommended in rooms where people remain stationary.”Source: the device's own parameter table + manufacturer datasheet
§2  Schedule of findings

One real project, read in full

Every figure below is counted, not estimated. We publish no saving, no percentage and no payback figure, because we cannot measure one.

Instrumented reference installation · Lindfield, NSW 2070
QtyItemNote
668Group addressesThe complete address map
234Addressed, wired to nothingDeclared, never terminated
113Addressing issuesConflicts and orphans
1403Device parameters resolved100% — hold times, staircase timers, thresholds, scene tables
21Automations already runningOn the devices themselves. In no documentation
12…of those, sensor-drivenActing without anyone knowing
25RecommendationsEach traced to the parameter that produced it
4959Owner edits since handoverFrom the project's own ETS log, since 2026-02-15

Disclosure. The reference installation is a house in Lindfield, NSW 2070 — the author's own house. It is the only installation we have analysed in full, and we would rather say so than imply a client base we do not have.

§3  Method

A tool for Tuesday, not a report you read once

The findings are the start. What follows is the part that saves the day: fix what you agree with, put the file back in, and see precisely what moved.

The working loop between ETS and CasientA project file goes from ETS into Casient, which returns findings. The integrator applies corrections in ETS and exports again; the revised file returns to Casient and is compared against the previous revision. Two further outputs hang below: a handover pack issued under the integrator's name, and the project kept in a searchable workspace.ETSyour project01.knxprojCASIENTread · ask · work≈ 60 s02findingseach traced03you fixin ETS04rev B back in → diffed05handover packissued under your namekept, searchablestill there in eighteen monthsLoop closes at 05. Everything above it is free.
Fig. 2The return line is the difference between a tool and a report. Fix what you agree with, put the file back in, and see exactly what moved.
  1. 01UploadA .knxproj. About a minute.
  2. 02ReadAddresses, devices, topology, and every parameter the products declare.
  3. 03AskA model trained on the devices in your project — not general advice about KNX.
  4. 04WorkGroup addresses, devices and device-local behaviour in one workspace, beside ETS rather than instead of it.
  5. 05FixTake the recommendations into ETS. Each names the parameter that produced it.
  6. 06DiffPut the new file in. Two revisions compared: what changed, what did not, what is still open.
  7. 07Hand overA handover document for your client, generated from the project, under your name.
  8. 08KeepThe project stays in your workspace. When they ring in eighteen months, it is a search.

Registration, no card. Exports are included during the trial. The check itself stays free — that is a decision, not an introductory offer.

§4  Boundary

Where the bus stops

Not because KNX is limited — because a device acts on what it alone can sense. That is a wiring fact, not an opinion about one system being better than another.

Section through one room, drawn twiceOn the left, a presence detector and a luminaire in the same room form a closed loop on the KNX bus. On the right, the same room needs a tariff, a weather forecast, a calendar, a person's phone and the occupancy of another room — each drawn as a dashed line that leaves the drawing and ends unconnected.Detail A · decided in the room1/1/5senses → switchesone device, one room, one wireruns with everything else switched offDetail B · not reachable from hereshould it?next roomtariffforecastcalendarphoneeach needs a second systemthe bus cannot reach any of them
Fig. 1Not because KNX is limited — because a device acts on what it alone can sense. Detail B is what the appliance is for.

A device decides this on its own

  • —Presence in the room it is in
  • —Lux at its own sensor
  • —A staircase timer it holds itself
  • —A scene it was told to store

These need two systems at once

  • ×Occupancy across rooms
  • ×A tariff
  • ×A forecast
  • ×A calendar
  • ×A person's phone

Everything in the right-hand column is what the next section is about.

§5  Appliance — beta

A house that decides, and writes down why

To read a project properly you need a model of a house: what a room is, what a device can do, what depends on what. We spent two years building one, and it is the reason the check finds things — and the reason software can be trusted to make decisions in a house continuously, because a guardrail has to be written against something.

The Casient appliance is one box: a KNX bus interface, a bus monitor, that model, a policy engine, the guardrails, and an AI layer that proposes. Home Assistant runs inside it, hardened — integrating two thousand products is a solved problem and we did not re-solve it. The operating system is kept separate from the automation platform, so the monitoring is still running while the automation is being changed.

The Casient appliance, exploded elevationSix layers drawn stacked and separated: a certified KNX bus interface, a bus monitor, the house model drawn as a sealed block, a policy engine, the guardrails, and an AI layer that proposes. A bracket down the left marks the operating system as separate from the automation platform.Appliance — exploded elevation · betaAI — proposes06 · suggests, never executesnothing it says reaches a wire directlyguardrails05 · the gateboundary changes need two sourcespolicy engine04 · policies propose, arbiter resolvesevery outcome written downthe house model03 · not publishedtwo years of it. Oursbus monitor02 · watches, logsa silent bus is an alert, not a blank screenKNX bus interface01 · certified module, inside the boxthe box is the interfaceto the busautomation platformOS + monitoring
Fig. 3One box. The monitoring keeps running while the automation is being changed — which is the whole reason the two are drawn apart.

Policies propose. An arbiter resolves. Every action is written down — with the policy that won, the ones it beat, the evidence, and the tier it resolved on.

Anything that changes the boundary of the house needs two independent sources. Two readings from the same detector count as one. A refused action is still a line in the log.

Primary reflexes stay on the bus. Staircase timers, motion holds, scene tables and central-off keep running on the actuators. Lose the box, the network and the internet, and the house still behaves.

A Basalte Core, a Logic Machine, a Comfortclick Jigsaw, a 1Home server all do a real job and do it well: they bridge a bus to an interface and run rules somebody wrote. If that is what your project needs, buy one. They are mature, they are supported, and we are not yet.

What none of them does — because it is not what they are for — is decide. A rule does not learn that this house goes to bed at eleven except on Fridays, and a rule that has never been wrong has also never been audited.

This is in beta, in one house, which is ours. We are looking for the second one. If you think something here is wrong, or already exists, tell us — we would rather be corrected than flattered.

§6  Values

Decisions we wrote down before we needed them

These are architecture decisions, not slogans. Each one is recorded and dated, and each one rules out something we might otherwise have built.

  • Nothing leaves the house unless the owner opens the door.
  • We cannot let ourselves in. Support access is granted by the owner, for a set time, and every session is logged.
  • We keep a written list of what we are allowed to store. Anything not on that list is refused.
  • A break-in at our end cannot reach a house. The box checks signatures itself and rejects anything it cannot verify.
  • Australian homes' data stays in Australia.
  • Backups are encrypted and kept off the box. A replacement box is running again within the hour.
  • The house keeps working without us. Safety and comfort run on the bus, not on our software.
  • Every decision is written down: what was chosen, what it beat, and why.
§7  Commercial

Every job you finish stops earning

You install for weeks and invoice once. The client's expectations keep moving, because they came from a phone. Your competitor quotes the same hardware you do.

Time

Reading a project you did not commission takes hours. The check takes about a minute, and the handover pack writes itself.

Something to say

A finding quoted from the manufacturer's own manual is not an opinion. It changes what you can tell a client, and what you can charge to fix.

More from the same equipment

The sensing and the actuation are already in the wall. What is missing is anything able to use two systems at once.

Revenue after handover

Monitoring, backup, support and improvement — in your name. White-labelled, with a fleet view across every house you run.

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, and when one of them contacts us directly, we tell them to call you.

§8  Origin

One person, one house, and a project file that would not stop being wrong

I am Ted, and Casient is mine. The house in the schedule above is where I live. I commissioned it, I have had ETS open at eleven at night, and I built the check because I wanted to know what my own project was actually doing and nothing would tell me.

There is no sales team. If you write, I answer.

Write to Ted

§9  Applicability

This is for a specific person

Condition 1

You commission four or more KNX projects a year.

Condition 2

You get asked to connect KNX to a control system — an app, Home Assistant, a visualisation — and it is painful every time.

Condition 3

You have a project attached right now, not a general interest.

Twenty-five projects a year with no integration work is not a problem we solve. If that is you, we are probably not what you need yet — and the check stays free regardless, so run it anyway if you are curious.

§10  Issue

Drop your .knxproj in and see what it says about your project.

Not a demo. Not a call. The file goes in, the findings come out, and you decide whether any of it is worth a conversation.

Upload a .knxprojRegister, no card · exports included during trial

If it is the rest of it you want to talk about,write to Ted. There is no form to fill in first.

TitleKNX project check — scope of findings
DrawnCasient
RegionSydney, Australia
SheetB / 1