Domotron Control
Utilities & PersonalConnect AI agents to Domotron, a Slovak smart home control system. Agents read environment sensors and control lighting, climate, shading, ventilation, and scenes, and read the stream URLs behind each camera.
What This Integration Enables
Domotron is a Slovak smart home and building control system, and the first thing to understand is that the API is served by the controller itself, so the base URL is specific to each installation. This is not a cloud service with a shared endpoint. You are talking to a box in a building, over a Bearer token that box issued, which changes the security posture and the failure modes: when the controller is unreachable, the building is unreachable, and there is no vendor-side cache standing in for it. The connector is a fair reflection of a real property. Twenty-nine actions read and write across lighting in four separate flavors, comfort zones, shielding devices, heat-recovery ventilation, and global scenes, plus a weather station and system diagnostics.
Worth stating plainly, because the summary language around this service overreaches: cameras here are read-only. List Video Cameras and Get Video Camera return identifiers and stream URLs, and that is the entire camera surface. There is no pan, no tilt, no recording control, and no arming. Everything else is genuinely writable. Lighting splits into switching (on/off) through Set Switching Light, dimming through Set Dimming Light, color through Set RGB Light, and warm-to-cool white through Set Tunable White Light, each with its own list and get. Set Climate Zone sets a desired temperature and optionally selects a hold program. Set Shading Device drives blinds, shutters, and shades by position (0 to 100 percent closed) and tilt (0 to 3), and can enable or disable automatic control. Set Ventilation Status toggles manual operation on the recuperation unit and chooses the bypass mode, against a Get Ventilation Status that reports power state, bypass, CO2 and humidity readings, filter status, current and set airflow, and timers. Fire Scene runs a global scene. The controller publishes no event subscription, so this service ships no triggers: a flow watches the building by calling Get Weather Data, Get Ventilation Status, or a zone read on a schedule, and reacts to what it finds. Every write on this list changes a physical space that people are in, which is why human-in-the-loop orchestration is not a nicety here.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Solar gain answered before anyone complains
A south-facing floor overheats on bright afternoons long before the thermostat notices, because the thermostat measures air and the problem is light. On a schedule the agent calls Get Weather Data, which returns temperature, feels-like temperature, illumination, humidity, pressure, wind force, gust force, and wind direction from the building's own weather station. High illumination combined with a rising outdoor temperature is the signal, and it arrives ahead of the indoor consequence. The agent reads the affected zone with Get Climate Zone, lists the relevant blinds with List Shading Devices, and proposes a partial close: a position that cuts the gain with a tilt that keeps the daylight. Because the floor is occupied, the proposal goes to a person rather than to the controller. Wind force from the same reading is part of the case, since shutters and external shades have runtime and exposure constraints a flow should not ignore.
Air quality that gets reported instead of argued about
Get Ventilation Status returns CO2 and humidity readings, filter status, bypass mode, and current versus set airflow from the recuperation unit. On a schedule the agent logs those to Google Sheets and posts a summary to Slack when CO2 crosses a threshold or the filter status changes. This is the read half of the connector doing the work it is best at: the building already knows its own condition, and the only reason nobody acts on it is that the information lives in a panel. Filter status in particular is a maintenance signal that turns into a comfort problem weeks later, and it costs nothing to surface early.
Evening shutdown that knows what it is turning off
At the end of a working day the agent walks the building rather than firing a single command. List Switching Lights, List Dimming Lights, List RGB Lights, and List Tunable White Lights each return their devices with identifiers, titles, and rooms, and the get actions report live status, so the flow can distinguish a light somebody deliberately left on in a lab from one forgotten in an empty meeting room. It turns off what is safe to turn off with Set Switching Light and steps the rest down with Set Dimming Light rather than cutting them. Fire Scene would do all of this in one call, which is precisely why the flow does not use it here.
Human-in-Loop Highlight
Fire Scene is the action to gate, and the reason is that its blast radius is invisible from the data the connector gives you. List Scenes returns each scene's identifier and title. Get Scene returns details of a single scene. What a scene actually is, in Domotron's own description, is a bundle of multiple device actions fired together, and the title is whatever a person typed when they saved it. "Night" might mean two corridor lights. It might mean every blind in the building closing, every comfort zone dropping to a setback temperature, and the recuperation unit changing mode, all at once, across floors that are still occupied because a team is working late. An agent reading the title cannot tell those apart, and Domotron will execute either one on a single call with no confirmation step and no undo. Reversing it is not one call back, it is reconstructing the prior state of every device the scene touched, and the flow did not record that state because it did not know which devices were in scope. Set Ventilation Status carries a quieter version of the same problem: toggling manual operation takes the recuperation unit off automatic control, and a building that has stopped managing its own air does not announce it. The CO2 number in Get Ventilation Status is the only witness, and it moves slowly enough that nobody notices until the afternoon. So the agent builds the case before it asks. It calls Get Scene for the scene it intends to fire, Get Weather Data for outdoor conditions, Get Ventilation Status for CO2 and bypass state, and the relevant zone and shading reads for current setpoints and positions, then posts to the facilities owner in Slack: "I want to fire the scene titled Night at 18:40. Domotron reports 14 devices bundled into it, including 6 shading devices on the third floor and 2 comfort zones currently held at 21 degrees. Badge data shows the third floor still occupied. Ventilation is on automatic with CO2 at 780 ppm. Firing this changes all 14 at once and I cannot restore their current values afterwards because I did not capture them. Fire it, fire it after 20:00, or should I set only the two ground floor zones instead?" A person answers. Set Climate Zone, Set Shading Device, and Set Ventilation Status sit behind the same gate whenever the space is occupied, for the simple reason that a machine changing the temperature, the light, or the air around a person should be a decision somebody made rather than a schedule nobody reviewed.
Agent Capabilities
29 actionsSystem and Environment
3- Get System Status Returns the current operating status of the Domotron system as reported by the controller. A cheap first call to establish that the controller is reachable before a flow depends on it.
- Get System Information Returns detailed information about the controller including firmware version, connectivity (GSM, internet), supply voltage, system time, last synchronization, last restart, and hardware identifiers. Supply voltage and last restart are worth watching, since an installation-local controller is the single point every other action depends on.
- Get Weather Data Returns live readings from the Domotron weather station, including temperature, feels-like temperature, illumination, humidity, relative and absolute pressure, wind force, gust force, and wind direction. Illumination and wind force are the readings that justify shading decisions the indoor thermostat cannot.
Lighting
13- List Light Rooms Returns all light rooms (room groupings used to organize lighting) configured in the system, each with its identifier and title.
- List Switching Lights Returns all switching (on/off) lights configured in the system, each with its identifier, title, and room.
- Get Switching Light Returns the configuration and live status of a single switching (on/off) light identified by its UID.
- Set Switching Light Turns a switching (on/off) light on or off. Select the target light by UID and the desired state.
- List Dimming Lights Returns all dimming lights configured in the system, each with its identifier, title, room, and the minimum and maximum dim values it accepts. Read the range here rather than assuming 0 to 100.
- Get Dimming Light Returns the configuration and live status of a single dimming light identified by its UID.
- Set Dimming Light Sets the brightness level of a dimming light. The status value ranges between the light's configured minimum and maximum, typically 0 to 100, which Get Dimming Light or List Dimming Lights reports.
- List RGB Lights Returns all RGB (color) lights configured in the system, each with its identifier, title, room, and configured favorite color slots.
- Get RGB Light Returns the configuration and live status of a single RGB (color) light identified by its UID.
- Set RGB Light Sets the color and intensity of an RGB light. Provide either the red, green, and blue channels (each 0 to 255) or a hex color hash. Intensity (0 to 100) sets brightness, and enabling toggle switches the light on or off.
- List Tunable White Lights Returns all warm-white and cool-white (tunable white) lights configured in the system, each with its identifier, title, room, and the minimum and maximum values it accepts.
- Get Tunable White Light Returns the configuration and live status of a single tunable white light identified by its UID.
- Set Tunable White Light Sets the color temperature and intensity of a tunable white light. Color shifts the white temperature between warm and cool; intensity sets brightness.
Climate and Ventilation
5- List Climate Zones Returns all comfort (heating and cooling climate) zones configured in the system, each with its identifier and title.
- Get Climate Zone Returns the configuration and live status of a single comfort zone identified by its UID. Call this before writing, so a flow knows the setpoint it is about to replace.
- Set Climate Zone Sets the desired temperature for a comfort zone, and optionally selects a hold program. This changes the temperature of a space people occupy, which is the argument for approving it rather than scheduling it.
- Get Ventilation Status Returns the live status of the recuperation (heat-recovery ventilation) unit, including power state, bypass mode, CO2 and humidity readings, filter status, current and set airflow percentages, and timers. The CO2 and filter values are the building's own account of its air.
- Set Ventilation Status Controls the recuperation unit: toggle manual on/off operation and choose the bypass mode. Switching to manual takes the unit off automatic control, and nothing announces that afterwards except a CO2 number moving slowly in the wrong direction.
Shading
3- List Shading Devices Returns all shielding devices (blinds, shutters, and shades) configured in the system, each with its identifier, title, whether it is a shade, and its defined runtime.
- Get Shading Device Returns the configuration and live status of a single shielding device identified by its UID.
- Set Shading Device Sets the position and tilt of a shielding device. Position runs 0 to 100 (percent closed) and tilt runs 0 to 3. Auto enables or disables automatic control, which is a separate decision from the position itself and outlives it.
Scenes
3- List Scenes Returns all global scenes configured in the system, each with its identifier and title. Scenes bundle multiple device actions that fire together, and the title is the only description a flow gets.
- Get Scene Returns details of a single global scene identified by its UID. Call this before firing, so a person can see how many devices the scene actually reaches.
- Fire Scene Activates a global scene, running every device action bundled into it. One call, building-wide reach, and no captured prior state to restore from.
Cameras
2- List Video Cameras Returns all video cameras configured in the system, each with its identifier and stream URL. Read-only.
- Get Video Camera Returns details, including the stream URL, for a single video camera identified by its UID. Read-only. This connector exposes no camera control, so a flow can surface a stream URL for a person to open but cannot pan, record, or arm anything.
Frequently Asked Questions
What can FlowRunner do with Domotron Control?
FlowRunner agents can run Get System Status, Get System Information, and Get Weather Data in Domotron Control, plus 26 more actions.
Does connecting Domotron Control to FlowRunner require OAuth?
No. Domotron Control connects to FlowRunner with an API key, no OAuth flow required.
Can Domotron Control trigger a FlowRunner workflow automatically?
Domotron Control doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Domotron Control
$100 in credits. No card required. Connect in minutes.