kodaaone
Lights and AV.
One command.
Press Movie on a Control4 keypad. The screen comes up, the Casambi lights fall to a warm 10%, the blinds close. One scene, no second app — and nothing leaves the house.
Walk in. Lights up, music low, screen dark.
- Display off
- Cinema audio on standby
- Playlist on · low
- Cove 100% · cool white
- Wall slats 60%
- Blinds open
- AC on · cool
- Ceiling fan low
One system to sell.
One system to live in.
For the integrator
One Composer project
Casambi loads land as Control4 devices — programmed like any load.
Two-way, not assumed
Change it anywhere. Control4 and the Casambi app agree.
No cloud in the path
Every command stays on the LAN. Nothing to expire.
Licensed per project
One signed key. Continuity mode never lets it go dark.
For the homeowner
One keypad by the door
Lights, blinds, fan, AC, screen — the same buttons.
Scenes that include light
Lighting is part of the scene, not a second app.
Works when the internet doesn't
The house behaves the same on a bad connection or none.
The Casambi app still works
Tuning stays where the lighting designer left it.
Nothing leaves
the house.
Control4 talks to the Casambi lights over your own home network. The internet can drop, the cloud can have a bad day — the keypad by the door still works.
The Casambi cloud is only used for setup and the phone app. It is never in the path of a button press.
Everything as usual.
- Keypad by the door
- Movie and Goodnight scenes
- Casambi app on the home Wi-Fi
- Two-way status
The cloud sits beside the path, never in it.
Everything the datasheet says.
Drivers, specifications and what you need on site — for the person doing the Casambi Control4 integration.
01Ten drivers. One key.10 drivers
Each Casambi device, group or scene is exposed to Control4 as the matching device type, so it behaves like any other load in the app, on touchscreens, and in Programming.
| Driver | Controls |
|---|---|
| Dimmer (Zone) | Single-channel brightness for a device or group |
| CCT Light | Brightness + tunable white, bounded to the fixture's Kelvin range |
| RGB Light | Full RGB / HSV colour |
| Color | All-in-one RGB / RGBW / tunable white |
| Curtain / Blind | Open · close · stop, with two-way status |
| Fan | Multi-speed fan control |
| Relay | Four independent relay / element triggers |
| IR Blaster | Eight IR / element channels (on · off · pulse) |
| On Button | Single "Casambi On" experience tile |
| License Manager | Activates the whole suite from one key (project-wide) |
02Technical specifications9 rows
| Control4 OS | OS 3.x — verified on OS 3.3.1; drivers declare minimums from OS 2.9 |
|---|---|
| Casambi gateway | Casambi Lithernet Ethernet Gateway (BACnet/IP) |
| Protocol | BACnet/IP over UDP 47808 — ASHRAE Standard 135 |
| Addressing | By Casambi device, group or scene number — gateway object layout auto-detected |
| Colour | RGB · HSV · RGBW · tunable white, with per-fixture Kelvin min/max |
| Feedback | Two-way status polling; state reflected in Control4 and back from the Casambi app |
| Cloud dependency | None — 100% local control |
| Licensing | Per-deployment signed key, bound to the controller; continuity mode keeps a licensed system running |
| Packaging | Standard .c4z drivers installed in Composer Pro |
04How the control path worksBACnet/IP · LAN
Control4 talks to the Casambi Lithernet gateway over BACnet/IP, and the gateway talks to the Bluetooth mesh. The Casambi cloud stays available for commissioning and the mobile app — but it is never in the control path.
Control4
App, Control4 keypads and touchscreens run the Kodaa One drivers.
lighting · fan · blind · relayLithernet Gateway
Casambi's BACnet/IP gateway, on the same local network as the controller.
UDP 47808 · ASHRAE 135Casambi network
Fixtures, curtain, fan and relay nodes — addressed by device, group or scene.
Two-way status polling03What you need on site.6 items
Add Casambi to
your next project.
Standard .c4z drivers, installed in Composer Pro, licensed per deployment. Talk to us about a project key.
Talk to usCasanode · Mumbai, Maharashtra, India