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

Your .knxproj already knows what is wrong. Nothing has read it.

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 · 191 Tryon Rd
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. 191 Tryon Rd is 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  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.

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
§4  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.

§5  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
TitleKNX project check — scope of findings
DrawnCasient
RegionSydney, Australia
SheetA / 1