Ctrlable Pro — Savant Profile

A Savant RacePoint Blueprint component profile that connects a Savant control system to Ctrlable Pro over the WebSocket API — with real-time two-way state feedback.

Download the latest ctrlable_pro.xml from Releases, import it into your Blueprint user library, and add the component to your layout.

Supported domains

Domain	Control	Feedback
Light — on/off, dimming	✅	✅
Light — color (RGB / Hue)	✅	✅
Light — color temperature (Kelvin)	✅	✅
Light — effects	✅	✅
Switch	✅	✅
Fan (percentage)	✅	✅
Lock	✅	✅
Garage door	✅	✅
Cover / shade — position + tilt	✅	✅
Climate — temp / mode / fan / preset	✅	✅
Media player — transport, volume, source, power	✅	✅
Alarm panel — arm/disarm (with code)	✅	✅
Sensor / binary sensor	—	✅
Camera / image (snapshot URL)	—	✅
Any domain — GenericService escape hatch	✅	—

How it works

The profile is a single self-contained XML. On the Savant host it installs a small co-processor that bridges Savant to the Ctrlable Pro WebSocket API (port 25804). All control is sent over WebSocket; entity state changes stream back to Savant in real time.

Setup

1. Import ctrlable_pro.xml and add the component to the layout.
2. Set the IP Address on the wire (in Blueprint) to the Savant host's IP. This is required for the co-processor to install.
3. In the component's state variables, set:
   • auth_token — a Ctrlable Pro Long-Lived Access Token
   • server_address — host/IP (default ctrlable.local)
   • server_port — API port (default 8123)
   • alarm_code — (optional) arm/disarm code
   • FanSet_0..3 — fan speed percentages (defaults 0 / 33 / 66 / 100)
4. Entity addresses are Ctrlable Pro entity_ids (e.g. light.living_room, climate.hallway, media_player.den) — put the entity_id in Address 1.
5. Allow a few minutes after upload/boot for the co-processor to install. It logs to ~/ctrlable_pro.log on the Savant host. If it will not start, set user_zone to a short zone name that has General Programmable Service Requests enabled.

Notes

• Color-temperature slider scaling, native Savant thermostat/security/AV/camera UI resource types, and camera streaming are being validated on hardware; climate, media, alarm, cover and camera currently work via actions + state feedback.