Resources · Make integration

Domotron control Make integrationAutomate Domotron control with Make.

Can your smart home react to other apps without a single line of code? The Domotron control Make integration gives you 3 action modules: one reads a light status, one pulls your weather data, one launches an action. This guide shows how to link your account and build a first working scenario.

Try the Domotron control integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Domotron control Make integration do for you?

The Domotron control Make integration lets Make, a visual automation tool, talk to your Domotron home system. You build a scenario, the automation you assemble in Make, out of modules: each module is one brick, and here all three are actions that read something from your home or tell it to do something.

Launch a home action from another app. Put a trigger from a form, a calendar or a chat tool first, then add Launch Action. The event in the other app becomes a command for your home, and you pick which action runs.

Log the state of your lights. Get Light Status reads where a light stands. Send the result to a sheet or a message module and you keep a trace you can check without opening the Domotron app.

Let the weather decide. The weather data module returns the weather information tied to your account. Map what it returns into Launch Action, and the command sent to your home can take the weather into account.

Know the limits before you start. The app has no trigger, so a scenario starts on Make's own schedule or on another app's event. Its Make documentation is also thin: it gives no field list, no connection steps and no description of each module, so what the modules return is something you discover with a test run. If you prefer to learn the editor first, the Make training covers it, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect Domotron control to Make?

  1. 01

    Add a Domotron control module

    In a scenario, click the +, search for Domotron control and pick any of its three modules. Make asks for a connection, which is your Domotron account linked to Make once and reused by every module of the app.

  2. 02

    Create the connection

    Click Create a connection. You can give it a name, which helps if you manage several homes or accounts. Then authorize Make on the Domotron page that opens, or paste the key Domotron gives you.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and the other two Domotron control modules will offer it straight away, so you never repeat these steps for the same account.

First scenario

Your first scenario with Domotron control

GoalWhen Make runs the scenario on its schedule, it reads your weather data in Domotron control and launches the action you picked.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Add the weather data module

    Search for Domotron control, pick Get My Weather Data and select your connection. This module opens the flow, since the app has no trigger of its own.

  3. 03

    Add Launch Action

    Click the + on the right of the weather module, pick Launch Action, then fill its fields. Map data from the weather module where it helps.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles, the items passed from one module to the next, so you see exactly what the weather module returned.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set Scheduling. A new scenario runs every 15 minutes by default. Adjust it, then switch the scenario on.

Modules

What the Domotron control modules do

Domotron control gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Domotron control1

Get Light Status

ActionIn the docs only

Going by its name, you get the current state of a light in your home, passed to the next module so another app can use it. It is an action module: each run reads one light and counts as one operation, the unit Make counts on your plan.

When to use it
pick it when a scenario needs to know how a light stands before it acts, or to log that state somewhere.
Watch out
the documentation does not describe the output, so check it with Run once before mapping it.
Domotron control2

Get My Weather Data

ActionIn the docs only

Its name says it: you get the weather data linked to your Domotron account, ready to be mapped into a later module. Unlike Get Light Status, it should read conditions rather than a device.

When to use it
when an action should depend on the weather, place it right before Launch Action and map its data into the command.
Watch out
no field list is published, so run the scenario once and read the bundle before mapping anything from it.
Domotron control3

Launch Action

ActionIn the docs only

This one makes something happen: Make tells your Domotron system to run an action, so another app can drive your home. Judging by the names, it is the only one of the three that changes something rather than reading.

When to use it
choose it as the last step, after a trigger from another app or after one of the two reading modules.
Watch out
it acts on your real home, so test with Run once while you can see the result.
Need help

Need help automating Domotron control with Make?

A person reads every message.

FAQ

Domotron control and Make: common questions

01Is the Domotron control Make integration free?
Yes, Domotron control is a standard app, so it works on the Make Free plan. That plan keeps 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Each module run counts as one operation on your monthly credits. Any cost on the Domotron side is not covered here.
02What do you need to connect Domotron control to Make?
You need a Domotron account and a Make account, and that is all the documentation lists, since it names no other prerequisite. Add one of the three modules, click Create a connection, optionally name it, then authorize Make on the Domotron page or paste the key Domotron provides, and click Save. The same connection then serves all three modules, from the light status read to Launch Action. If something fails, check your Domotron account first, because the Make documentation for this app is limited.
03Does Domotron control trigger Make scenarios in real time?
No, the app has no trigger, neither scheduled nor instant, so it cannot start a scenario on its own. You have two ways around it. Let Make start the scenario on its schedule, every 15 minutes by default and never under 15 minutes on the Free plan. Or start the flow with a trigger from another app, such as a form or a calendar, and add Launch Action after it. In both cases the Domotron modules run as actions inside a flow something else started.
04What if a Domotron control module is missing in Make?
It depends on what you need, because the app offers only three modules and no Make an API Call module to reach the rest of the Domotron API. If your use case needs something beyond reading a light status, reading weather data or launching an action, look for another app in Make that covers it. The documentation is also marked as limited, with no field details. When the scenario matters to your business, the team behind this page can review it with you through the contact form below.
05Should you use Make or n8n for Domotron control?
It depends on the tool your team already runs, not on this app alone. On Make, Domotron control brings three action modules and no trigger, available from the Free plan. The same app often has an n8n node too, so check which modules it offers there before you choose. Compare the modules each side gives you for your exact use case, then build on the tool whose editor you already know. There is no speed or cost ranking to make between the two here.
Same platform

Other docs you might need on this stack.

Browse all integrations