iOS Shortcuts in Remote

1. Introduction #

With version 1.15.0 of the Remote app for iOS, we have introduced native support for Shortcuts, a feature built into the iOS system. This opens up a wide range of exciting new possibilities that significantly enhance the capabilities of your smart installation!

To implement the functionality presented here, make sure your DOMIQ/Base module is running software version 3.0.2.0 or later.

2. How Do Shortcuts Work and What Can They Do? #

The Shortcuts app is a tool built into the iOS system for Apple devices that allows for task automation. It enables you to create and run sequences of actions (shortcuts) that can integrate system functions, apps, and online services.

What can the Shortcuts app do? #

• Task automation – perform multiple actions with a single tap or a voice command via Siri.
• App integration – shortcuts can access built-in Apple apps and many third-party apps.
• System actions – control device functions, e.g., enable airplane mode, send messages, save notes, play music.
• Conditions and variables – create more advanced shortcuts that respond to context like time, location, or device state.

Example uses of Shortcuts #

• “Open the gate when I get home” – automatically opens the garage gate based on your location.
• “Run selected shortcut when the alarm goes off” – executes a specific shortcut when your alarm activates.
• “I’m going to sleep” – launches an end-of-day sequence: e.g., turns off lights, arms the alarm, sets the temperature, enables airplane mode.
• “Send an SMS in case of an emergency” – automatically notifies users of an emergency situation or makes a call to a designated contact. In summary, the possibilities offered by the Shortcuts app are vast. You can now easily create rules that combine the functions of multiple apps and system actions into a single macro, executed with one tap.

How can I run shortcuts? #

Shortcuts can be run in several ways:

1. In the Shortcuts app – where all your defined shortcuts are listed. Tapping one runs it.
2. As a Home Screen icon – any shortcut can be added as an icon for quick access.
3. As a Control Center action – add shortcuts to the Control Center for easy reach.
4. As an action in another shortcut – shortcuts can call other shortcuts, enabling complex linked scenarios.
5. In response to an event in the DOMIQ system – this is built into our Remote app and the Base module. Any event in the system can trigger a specific shortcut on the mobile app. Details are described further in this guide.

3. Creating Shortcuts #

The Remote app provides a set of intents that you can use to define shortcuts in the Shortcuts app. These actions are divided into three groups:

• Predefined (actions 1–8)
• With selectable parameters (actions 9–11)
• Editable – with the ability to manually enter a parameter value (steps 12 and 13). At the time of writing this tutorial, the following steps are available:

All of the above actions result in sending a specific command (hence the prefix C.) to the Base module paired with the Remote app. On the Shortcuts side in iOS within Remote www.domiq.pl,

the Base must be configured to define actions to be performed when a given command is received.

The information flow is as follows:
Shortcuts in iOS -> DOMIQ/Remote: – (command of type DOMIQ.shortcut) -> DOMIQ/Base (event)

IMPORTANT: The Remote app must be running in the background and connected to your installation.

In the following part of this chapter, we present how to define shortcuts using individual actions. For clarity, each action is shown as a separate shortcut; however, they can be combined within other shortcuts, which is also demonstrated later in the tutorial.

3.1. Predefined Actions #

This is a group of actions provided by the Remote app with fixed parameter values. Running a shortcut using these actions will always produce the same result (sending a command with a predefined value).

Below we describe an example of creating a shortcut to open the entrance gate. Similarly, you can use all actions from group 1 to 8.

Open the gate

1. In the Shortcuts app, click + to start defining a new shortcut.
2. In the search field Search for apps and actions, type Remote. As you type, the Shortcuts app should suggest the Remote app — select it.
3. A list of available actions should now be visible — choose Open gate.
4. Tap the arrow icon at the top and choose Rename, then enter a suitable shortcut name, e.g. Open gate.
5. Optionally, tap the arrow icon again and select Choose Icon to personalize the shortcut icon.
6. If you want the shortcut to perform additional actions, e.g. from another app or within system functions, define them as desired.
7. After everything, click OK to finish defining the shortcut.
8. Done! Your shortcut is now visible on the list of shortcuts.
9. Tapping it triggers the assigned actions — in this case, sending the command:
   C.DOMIQ.shortcut.opengate=1

Shortcut handling in DOMIQ/Base

1. Add a new event in the Events tab and define it as follows:
2. Channel: C.DOMIQ.shortcut.opengate
3. Data: 1
4. In the Actions section, define commands to open the gate. It’s also worth adding commands to turn on lights on the driveway, path to the house, etc.

3.2. Actionswith Selectable Parameter Value #

Actions in this group (9–11) allow the user to choose an input parameter from a list of predefined values.

For the three mentioned actions, we defined two values to choose from: on and off. Such shortcuts can either have the action preset or use the Ask Each Time option — which allows the value to be selected at runtime.

Example:

1. In the Shortcuts app, click + to start defining a new shortcut.
2. In the Search for Actions search box, type Remote. As you type, the Shortcuts app should suggest Remote in the results; select it.
3. From the list, choose Heating.
4. In the top bar, click the down arrow icon, select Rename and enter a name for the shortcut that suits you, e.g. Heating.
5. Optionally, you can click the down arrow icon again and select Choose Icon to customize the icon that represents this shortcut.
6. If you want the shortcut to perform additional actions, e.g. from another app or within system functions, define them as desired.
7. Na ekranie powinieneś widzieć aktywne pole state. Kliknij na nim.
   1. If you want the shortcut to give you the option to choose the value of the input parameter on an ongoing basis, select the option: Ask every time.
   2. If you want to assign a specific value to an action, select one of the available options. For this action, either on or off. In this case, it’s worth giving the shortcut a name that clearly describes what will happen when the shortcut is triggered. For example, if you selected on, the shortcut could be named: Turn on the heating.
8. Done! Your shortcut is now visible on the list of shortcuts.
9. Clicking on it will trigger the actions assigned to it. In our case, sending the command C.DOMIQ.shortcut.heating=on or off

Similarly, you can use the Cooling and Alarm System actions.

Shortcut handling in DOMIQ/Base

1. Add a new event in the Events tab and define it as follows:
2. Channel: C.DOMIQ.shortcut.heating
3. Data:on
4. In the Actions section, define the commands to turn on the heating.

3.3. Actionswith an editable parameter #

Actions from this group give you the greatest flexibility, because their input value can be arbitrary and entered at the stage of launching the shortcut. However, it is also an option to provide the parameter value already at the stage of defining the shortcut. All about this in the examples.

Heating mode

For convenient heating control, it’s good to have several operating modes, which will automatically set the desired temperatures in specified rooms. Later, choosing a specific heating mode causes a global change of settings according to the adopted assumptions.

You can read about defining heating modes in the DOMIQ system in the tutorial Heating under control: https://domiq.pl/wiki/ogrzewanie-pod-kontrola/

With this functionality in mind, we have added an action to the Shortcuts app that can pass information to the DOMIQ system about which heating mode should be activated.

1. In the Shortcuts app, click + to start defining a new shortcut.
2. Search for the action using the Search for actions field and select Heating mode.
3. Set the name and icon of the shortcut.
4. If you want the shortcut to perform additional actions, e.g. from another app or within system functions, define them as desired.
5. On the screen you should see the active mode field. Click on it.
   1. If you want the shortcut to give you the ability to enter the heating mode name on the fly, choose the option: Ask Each Time. 2. If you want to assign a specific value to the action, then click on the mode field and enter the name of the mode. In this case, it is worth giving the shortcut a name that clearly describes what will happen when the shortcut is launched. For example, if you entered the mode eco, then the shortcut can be named: Eco Heating.
6. After everything, click OK to finish defining the shortcut.
7. Done! Your shortcut is now visible on the list of shortcuts.
8. Clicking on it causes the execution of the actions assigned to it. In our case, sending the command: C.DOMIQ.shortcut.heatingmode=eco IMPORTANT: The value of the command will be sent as text consisting only of lowercase letters.

Shortcut handling in DOMIQ/Base

1. Add a new event in the Events tab and define it as follows:
2. Channel: C.DOMIQ.shortcut.heatingmode
3. Data: eco
4. In the Actions section, define commands to switch the heating mode.

Start the scene

At the end, we will describe the action that gives the most possibilities, i.e., launching a scene of any name. In essence, this action is a generalized form of all actions presented so far. Its operation boils down to sending a command to the Base module, whose value contains the name of the scene. On the Base module side, you need to create an event that will handle receiving this command and then execute predefined actions.

1. In the Shortcuts app, click + to start defining a new shortcut.
2. Search for the action using the Search for actions field and select Run scene.
3. Set the name and icon of the shortcut.
4. If you want the shortcut to perform additional actions, e.g. from another app or within system functions, define them as desired.
5. On the screen you should see the active scene field. Click on it.
   1. If you want the shortcut to give you the ability to enter the scene name on the fly, choose the option: Ask Each Time. 2. If you want to assign a specific scene name, then click on the scene field and enter the name. In this case, it’s worth giving the shortcut a name that clearly describes what will happen when the shortcut is launched.
6. After everything, click OK to finish defining the shortcut.
7. Done! Your shortcut is now visible on the list of shortcuts.
8. Clicking on it causes the execution of the actions assigned to it. In our case, let’s assume the user selected the scene named relaks.
   Thus, the command C.DOMIQ.shortcut.scene=relaks will be sent to the Base module. IMPORTANT: The value of the command will be sent as text consisting only of lowercase letters.

Shortcut handling in DOMIQ/Base

In the Base module, you can have any number of events that will be nothing more than definitions for a given scene (macro definitions). All these events will have the same value in the Channel field, but they will differ in the Data field.

Definition of an example scene is as follows:

1. Add a new event in the Events tab and define it as follows:
2. Channel: C.DOMIQ.shortcut.scene
3. Data: relaks
4. In the Actions section, define the commands for your scene. For example, for the scene relaks, it could be dimming the lights, turning on selected music, and silencing the phone.

You can read more about how to define macro definitions, which you can also call scenes, in the tutorial: https://domiq.pl/wiki/scenariusz-na-wejscie-wyjscie-z-domu/

4. Running shortcuts #

he most basic way to run a shortcut is to click on it in the Shortcuts app. But we’ll go a step further and show how to run created shortcuts in more complex scenarios, that is, how to use the Automation option in the Shortcuts app. We’ll show this with two examples: running the Good Morning shortcut in combination with an alarm clock, and the Open Gate shortcut in combination with GPS location.

Then we will show how to speed up access to shortcuts by placing them on the home screen of iPhone/iPad and in Control Center.

4.1. GoodMorning #

Automating morning activities can ease the start of the day and, over the course of a year, is a real time saver. Morning activities may include e.g. increasing temperature and ventilation efficiency, opening blinds, turning on selected lights, and playing your favorite music.

Linking morning activities to alarm clock settings seems to us a very useful application of the Shortcuts app, because it brings great flexibility — actions performed in the smart home are directly tied to your daily rhythm.

The initial assumption is that you have a shortcut named Good Morning, which uses the action of the same name provided by the Remote app.

1. In the Shortcuts app, select Automation, then click + to add a new rule.
2. Wybierz Alarm i ustal parametry wejściowe:
   1. When: it turns on
   2. Alarms: Existing, then choose which alarm you want to use.
   3. If you want the shortcut to run without your input, choose the Run Immediately option. The Run After Confirmation option will require your approval.
   4. Choose the Good Morning shortcut from the list.
   5. Done!
3. W konfiguratorze modułu Base przejdź do zakładki Zdarzenia i dodaj nowe zdarzenie:
   1. Channel: C.DOMIQ.shortcut.goodmorning
   2. Data: 1
   3. In Actions, define the activities to be performed in the system.

Another example worth considering is capturing the activation of a specific Focus mode on iPhone, e.g. Sleep mode, to launch the Good Night shortcut, which will trigger end-of-day actions.

4.2. Back Home #

In this example, we will show how to use location information to trigger actions when you return home.

Initial assumption: you have a shortcut named Back Home, which uses the action of the same name provided by the Remote app.

1. In the Shortcuts app, select Automation, then click + to add a new rule.
2. Wybierz Przybycie i ustal parametry wejściowe:
   1. Location: choose the location.
   2. Set the execution time of the shortcut.
   3. If you want the shortcut to run without your input, choose the Run Immediately option. The Run After Confirmation option will require your approval.
   4. Click Next and choose the Back Home shortcut from the list.
   5. Done!
3. W konfiguratorze modułu Base przejdź do zakładki Zdarzenia i dodaj nowe zdarzenie:
   1. Channel: C.DOMIQ.shortcut.backhome
   2. Data: 1
   3. In Actions, define the activities to be performed in the system.
   4. Optionally, in the Condition field, you can define a check, e.g. of the alarm system state, to avoid actions being performed when someone is already home.

4.3. Faster shortcut launching #

To have quicker access to frequently used shortcuts, you can place them on the iPhone/iPad Home screen or in the Control Center.

Home screen

1. In the Shortcuts app, find the shortcut you’re interested in and press it longer. As a result, an additional menu will appear – choose Share -> Add to Home Screen.
2. In the next step, set the label, icon, and background color.
3. Done!

Control Center

1. Open Control Center (swipe down from the upper right corner of the screen).
2. Press anywhere for about a second – the view will enter edit mode.
3. Choose the Add Widget option.
4. From the list of available options, find Shortcuts and choose Shortcut.
5. Then choose the shortcut you’re interested in.

5. Running shortcuts from the DOMIQ system #

In our system, the opposite action is also possible — triggering a shortcut with a given name directly in the iOS system. The data flow is as follows:

DOMIQ/Base -> push notification (REMOTE.notify) -> DOMIQ/Remote -> Shortcuts in iOS. As you can see, we use the standard command for sending notifications to mobile devices.

However, its content must have a specific format: RS:; e.g. RS:alarm sms;alarm in zone

1
RS: (Remote Shortcut) is a prefix that allows the Remote app to interpret the notification slightly

differently from other notifications.

IMPORTANT: If such a notification is received when the phone is locked or the Remote app is not running, the shortcut will only execute if you tap on the notification label that appears on the screen.
If the Remote app is running and visible on the screen, the content of the notification will not be shown at all, but the Remote app will run the shortcut in iOS in the background.

To illustrate this, here is an example of triggering a shortcut that sends SMS messages to designated recipients in an emergency. Let’s assume this occurs in the case of an alarm in zone 1 in the Satel Integra panel. At this point, it is worth narrowing the group of notification recipients to avoid multiple executions of the shortcut. Therefore, in our example, we present sending the notification to a specific user profile, containing two responsible people.

1. Add a new event in the Events tab:
2. Channel: E.IDS.alarm.1
3. Data: 1
4. Actions -> +Command 1. Name: C.REMOTE.notify.administratorzy

2. Value: RS:alarm sms;alarm in zone 1

5. Save the Events tab.
6. In the Shortcuts app, click +
7. In the Search for actions field, enter: Send Message
8. Kliknij w pole wiadomość
   1. You can manually enter the SMS content if you want it to be statically assigned to the shortcut.
   2. Click the Choose variable option, then Shortcut Input Data. This way, the shortcut will capture the additional data sent in the notification content (the text after the semicolon – see section 4.2).
9. Click on the recipients field and define message recipients. You can choose more than one contact.

Click OK to confirm the shortcut.
Finally, rename the shortcut to alarm sms.

12. Done! From now on, each such alarm event will trigger the indicated shortcut.

6. Summary #

Even though this was quite an extensive tutorial, we’ve only scratched the surface of available possibilities.
The spectrum of applications is truly wide. In more advanced scenarios, you can perform HTTP requests (e.g. for integration with devices via WEB API), run scripts via SSH, or use actions from the Scripts group to create a highly personalized shortcut.

If you have an idea for an interesting shortcut use-case, write to us — we’d love to hear your ideas!