Casient Pro
FOR INTEGRATORS · TECHNICAL OVERVIEW

How Casient works, in the detail you’ll want before a trial.

The architecture, what belongs on the bus and what belongs on Keystone, real examples, and the specifications. Questions this doesn’t answer: write to Ted.

A · Architecture

How Casient decides.

Your ETS project and everything else in the building feed one model of the building. The rules decide every action Keystone takes. AI can suggest, draft and explain, but never acts on its own. The KNX bus keeps the safety logic. Limits that must hold with Keystone off are set on the bus; behaviours held by Keystone stop when Keystone stops. Every decision is recorded.

Exploded clay model of a home in three layers: KNX and CAT6 wiring, rooms, and connected devices
Three layers of one home: KNX loop and CAT6 star, rooms, devicesIllustrative
Architecture · loopsIllustrative

A layered diagram. Your ETS project and everything else in the building feed a model of the building. AI asks and drafts, but its requests wait at the rules engine. The rules engine resolves written policies in a fixed order and decides every action, which goes to the KNX bus and connected systems. Every decision is written to the decision log.

Your ETS project
Imported, read and mapped to rooms
Everything else in the building
Power prices, weather, AV, calendars
Building map
Rooms, devices and what each can do. Each type of room has its own rules.
AI → requests
Asks, drafts, explains. Never acts on its own.
Rules
Written rules, checked in a fixed order. They decide every action Keystone takes.
KNX bus
Safety logic stays here. Limits that must hold with Keystone off are set here.
Connected systems
Blinds, AV, energy, garden
Log
Every action: the rule that won, what it beat and the evidence it used.

When a client wants something the rule library doesn’t cover: describe it to Ask Casient. It drafts a new rule or changes an existing one. Fixed code checks it against the building model and the safety limits, and shows you exactly what will change. No new rule goes live until you approve it. Every change is logged.

B · What goes where

Commission the bus first. Let Keystone add the rest.

Anything the building must do with Keystone switched off belongs on the bus. Keystone adds what a KNX device can’t decide alone.

Put on the KNX bus
Switches, scenes and basic presence lighting
Heating and cooling basics
Safety logic, and limits that must hold without Keystone
Anything a fire or access system depends on
Leave to Keystone
Behaviours that depend on time, season or who’s home
Decisions across KNX and other systems: power price, weather, AV, blinds
Room-type behaviours shared across buildings
Ask Casient, the decision log and Fleet monitoring

If the internet drops

Keystone keeps running every rule, automation and log entry. Ask Casient and remote access through Fleet pause until it’s back.

If Keystone is off

Everything on the bus keeps working. Links to non-KNX systems, room behaviours beyond the bus, Ask Casient and the decision log pause.

Before and after a fault

Fleet raises an alert on your console when a site stops reporting. It does not know why, so you check or fix it.

C · Examples

You could build any one of these by hand, per house. Casient makes them the default in every building.

Ask or situationOn a typical controller, even with AI helpIn Casient
11 p.m.: “Turn every light on full.”
Typical controller
Possible with a per-room exception in each house’s logic
In Casient
While Keystone is running, a generic command does not light a child’s bedroom after dark. Ask for the room by name and it lights. The log says which rule applied
“Why did the ensuite light stay on at 2 a.m.?”
Typical controller
Other systems show what ran. Casient also shows why.
In Casient
The rule that acted, what it overrode, and the sensor evidence
“Which presence detectors hold for less than the maker recommends?”
Typical controller
Device parameters stay inside the ETS project
In Casient
Rooms, group addresses and settings, with the manual’s recommendation
“Which automations are set inside the devices?”
Typical controller
Only knows what someone configured
In Casient
Automations inside KNX devices that appear in no handover document
Heat protection wants blinds down; the owner wants the view
Typical controller
Possible with override lockouts, built per house
In Casient
A fixed order of rules: emergency; request for that room; room behaviour; generic command or scene. The log shows which won
Childcare centre, sleep time: staff run a building-wide “lights on” scene
Typical controller
Possible with a per-room exception in each site’s logic
In Casient
While Keystone is running, the rest rooms stay dim under a generic command or scene, unless someone asks for that room by name or there is an emergency. The log shows which rule won
“Has anything changed since handover?”
Typical controller
No commissioning baseline to compare against
In Casient
Drift from the commissioned project, listed
“Set every meeting room to the same rules, across all 40 sites.”
Typical controller
Copied site by site
In Casient
One rule, applied to every room of that type across the fleet
“Change the arrival temperature in every apartment in the block.”
Typical controller
Opened and changed unit by unit
In Casient
One rule change, applied to every unit, each with its own log
D · AI in detail

What AI does, where it runs, and what it sees.

AI in Casient does
  • +Answers questions about the building in plain language
  • +Drafts new behaviours for you to review and approve
  • +Troubleshoots from the decision log
  • +Reads device behaviour from a curated knowledge base of KNX products
  • +Ask Casient: owners talk to their building by voice or chat, within the limits you set
AI in Casient never does
  • ×Acts outside a written rule
  • ×Changes the safety logic on the KNX bus
  • ×Opens or unlocks anything by itself
  • ×Enters a building without the owner granting access
  • ×Learns from your clients’ buildings without permission

Where it runs: Ask Casient uses a cloud AI model for complex questions today. An on-premises option is in testing for sites that need the AI to stay in the building.

D2 · Integrations

KNX, working with everything else in the building.

Sigenergy
TESTED
Solar and battery
Amber Electric
TESTED
Live power prices
iZone
TESTED
Ducted air conditioning
UniFi Protect
TESTED
Cameras
UniFi Access
TESTED
Door access
TESTED
Sonos
Multi-room audio
All tested integrations, and what’s next →
E · Specifications

Keystone and Fleet, specified.

KNX connection
Direct to the bus through a certified KNX interface, handled by Keystone’s own KNX layer. No KNX IP gateway needed; if the site already has one, Keystone can use it.
Non-KNX integrations
Through Casient’s integration layer, pinned and tested before each release. See tested integrations →
Fleet data
Fleet receives health and status, including counts such as how many devices a box sees, and encrypted backups if a client takes the backup service.
Support access
Support access is only with the owner’s permission. Our policy is one session at a time, with an end time. AI-supported troubleshooting works from the decision log and the building model, to find the cause faster.

Ready to try it on a real job?

Pilot partners get direct engineering support while they run Casient on real pilot sites. We’ll walk you through the roadmap on the call.

Talk to Ted about a pilot siteRun a free ReadbackBook 20 minutes with Ted