iOS Shortcuts in Remote

1. Introduction #

With version 1.15.0 of the Remote app for iOS, we’ve introduced native support for Shortcuts, a feature built into the iOS system. This opens up a huge range of exciting new possibilities that significantly expand what your smart installation can do!

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 built-in tool on iOS devices from Apple used for task automation. It allows you to create and run sequences of actions (shortcuts) that can combine system functions, apps, and web 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 use built-in functions of Apple apps as well as many third-party apps.
• System actions – allows you to control the device, e.g. turning on airplane mode, sending messages, saving notes, or playing music.
• Conditions and variables – create more advanced shortcuts that respond to context like time, location, or device state.

Example uses of Shortcuts #

• “Open the entrance gate when I’m coming home” – automatically opens the garage gate based on location.
• “Run a selected shortcut when the alarm goes off” – runs a chosen shortcut linked to your daily alarm.
• “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 when an alarm situation occurs” – automatically notifies system users about an alarm situation. An alternative could be making a voice call to a specified person.
  To sum up, the possibilities offered by the Shortcuts app are truly enormous. You can now easily create rules that combine the actions of multiple apps and system functions into a single macro, triggered with a single tap.

How can I run shortcuts? #

Shortcuts can be run in several ways:

2.1 In the Shortcuts app – opening the Shortcuts app shows you a list of all the shortcuts you’ve defined. Tapping a shortcut runs it.

2.2 As an icon on the Home Screen – any shortcut you’ve defined can also be placed as an icon on the Home Screen, which makes it much faster to find.

2.3 As an action in Control Center – shortcuts can be added to Control Center, so you always have them at hand.

2.4 As an action within another shortcut – shortcuts can trigger other shortcuts, letting you build powerful scenarios of interconnected actions.

2.5 In response to an event in the DOMIQ system – we’ve built this capability directly into our Remote app and the Base module. In response to any event in the system, the Base module can trigger an action on the mobile app’s side, causing it to run a specified shortcut. You’ll find the details of this functionality later in this tutorial.

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 rest of this section, we present how to define shortcuts using each of these actions. For clarity, each action is presented as a separate shortcut, but they can also be part of other shortcuts, which we also demonstrate 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. You can use all the actions from group 1 to 8 in the same way.

Open the gate

1. In the Shortcuts app, tap + to start defining a new shortcut.

2. In the Search for actions field, type Remote. As you type, the Shortcuts app should suggest the Remote app in the results — select it.

3. At this point, you should see a list of available actions — choose Open the gate.

3. In the top bar, tap the down-arrow icon, select Rename, and enter a name of your choice for the shortcut, e.g. Open the gate.

4. Optionally, you can tap the down-arrow icon again and select Choose Icon to customize the icon representing this shortcut.

5. If you want this shortcut to perform additional actions, e.g. from another app or within system functions, define them as you see fit.

6. When done, tap OK to finish defining the shortcut.

7. Done! Your shortcut is now visible in the shortcuts list.

8. Tapping it triggers the actions assigned to it. In our case, this sends 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 the commands to open the gate. It’s worth adding commands to the sequence that turn on lighting on the driveway, the path to the house, etc.

3.2. Predefwith Selectable Parameter Value #

Actions in this group (9–11) differ in that they let the user choose an input parameter from a list of predefined values when running the shortcut.

For these three actions, we’ve defined two values to choose from: on and off. This type of shortcut can be defined with a fixed action, or using the Ask Each Time option, which means the Shortcuts app will display an interface for choosing the parameter value at the moment the shortcut is run.

Example:

1. In the Shortcuts app, tap + to start defining a new shortcut.

2. In the Search for actions field, type Remote. As you type, the Shortcuts app should suggest the Remote app in the results — select it.

3. At this point, you should see a list of available actions — choose Heating.

4. In the top bar, tap the down-arrow icon, select Rename, and enter a name of your choice for the shortcut, e.g. Heating.

5. Optionally, you can tap the down-arrow icon again and select Choose Icon to customize the icon representing this shortcut.

6. If you want this shortcut to perform additional actions, e.g. from another app or within system functions, define them as you see fit.

7. On the screen, you should see an active state field. Tap it.

1. If you want the shortcut to let you choose the input parameter value each time, select the Ask Each Time option.
2. If you want to assign a specific value to the action, choose one of the available options — for this action, on or off. In this case, it’s worth naming the shortcut so that it clearly describes what will happen when it’s run. For example, if you chose on, the shortcut could be named: Turn on heating.

8. Done! Your shortcut is now visible in the shortcuts list.

9. Tapping it triggers the actions assigned to it. In our case, this sends 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. Predefwith 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 useful to have several operating modes that automatically set target temperatures in specific rooms. Selecting a given heating mode then causes a global change of settings according to the assumptions you’ve adopted.

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

With this functionality in mind, we’ve 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, tap + to start defining a new shortcut.

2. Search for the action using the Search for actions field and select Heating mode.

3. Set the shortcut’s name and icon.

4. If you want this shortcut to perform additional actions, e.g. from another app or within system functions, define them as you see fit.

5. On the screen, you should see an active mode field. Tap it.

1. If you want the shortcut to let you enter the name of the heating mode each time, select the Ask Each Time option.
2. If you want to assign a specific value to the action, tap the mode field and enter the mode’s name. In this case, it’s worth naming the shortcut so that it clearly describes what will happen when it’s run. For example, if you entered the mode eco, the shortcut could be named: Eco Heating.

6. When done, tap OK to finish defining the shortcut.

7. Done! Your shortcut is now visible in the shortcuts list.

8. Tapping it triggers the actions assigned to it. In our case, this sends the command C.DOMIQ.shortcut.heatingmode=eco.

IMPORTANT: the command value 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 the commands to switch the heating mode.

Start the scene

Finally, we’ll describe the action that offers the greatest possibilities: triggering a scene with any given name. In essence, this action is a generalized form of all the actions presented so far. What it does is send a command to the Base module whose value contains the scene’s name. On the Base module’s side, you need to create an event that handles receiving this command and then executes predefined actions.

1. In the Shortcuts app, tap + to start defining a new shortcut.

2. Search for the action using the Search for actions field and select Run a scene.

3. Set the shortcut’s name and icon.

4. If you want this shortcut to perform additional actions, e.g. from another app or within system functions, define them as you see fit.

5. On the screen, you should see an active scene field. Tap it

1. If you want the shortcut to let you enter the name of the scene you want to run each time, select the Ask Each Time option.
2. If you want to assign a specific scene name, tap the scene field and enter the name. In this case, it’s worth naming the shortcut so that it clearly describes what will happen when it’s run.

6. When done, tap OK to finish defining the shortcut.

7. Done! Your shortcut is now visible in the shortcuts list.

8. Tapping it triggers the actions assigned to it. In our case, let’s assume the user selected a scene named relax.
The command C.DOMIQ.shortcut.scene=relax will then be sent to the Base module.

IMPORTANT: the command value 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 are, in essence, definitions for a given scene (macro definitions). All these events will have the same value in the Channel field, but will differ in the value of 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 relax scene, this could be dimming the lights, playing selected music, and muting the phone.

You can read more about how to define macro definitions, which you can also call scenes, in the tutorial: https://domiq.eu/wiki/ogolne/home-entry-exit-scenario/

4. Running shortcuts #

The most basic way to run a shortcut is to tap it in the Shortcuts app. However, we’ll go a step further and show you how to run shortcuts you’ve created in more complex scenarios — that is, how to use the Automation feature in the Shortcuts app. We’ll demonstrate this with two examples: running the Good morning shortcut linked to an alarm clock, and the Open the gate shortcut linked to a GPS location.

We’ll then show you how to speed up access to shortcuts by placing them on the iPhone/iPad Home Screen and in Control Center.

4.1. GoodMorning #

Automating your morning routine can make starting the day easier and, over the course of a year, represents a real time saving. Your morning routine might include, for example, raising the temperature and ventilation output, opening the blinds, turning on selected lights, and playing your favorite music.

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

As a starting assumption, we assume you’ve created a shortcut called Good morning, which uses the action of the same name provided by the Remote app.

1. In the Shortcuts app, select Automation, then tap + to add a new rule.

2. Select Alarm and set the input parameters:

1. When: 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.

3. Select the Good morning shortcut from the list.

4. Done!

5. In the Base module’s configurator, go to the Events tab and add a new event:

1. Channel: C.DOMIQ.shortcut.goodmorning
2. Data: 1
3. In Actions, define the activities to be performed in the system.

Another interesting example of using automation in Shortcuts is capturing the activation of a given Focus mode on the iPhone, e.g. Sleep mode, to trigger the Good night shortcut, which runs the end-of-day actions.

4.2. Back Home #

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

As a starting assumption, we assume you’ve created a shortcut called Coming home, which uses the action of the same name provided by the Remote app.

1. In the Shortcuts app, select Automation, then tap + to add a new rule.

2. Select Arrive and set the input parameters:

1. Location: select a 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.

3. Tap Next and select the Coming home shortcut from the list.

4. Done!

5. In the Base module’s configurator, go to the Events tab and add a new event:

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 get faster access to your most frequently used shortcuts, you can place them on the iPhone/iPad Home Screen or in Control Center.

Home screen

1. In the Shortcuts app, find the shortcut you’re interested in and press and hold it. This will bring up an additional menu — select Share -> Add to Home Screen.

Control Center

1. Open Control Center (swipe down from the top-right corner of the screen).
2. Press and hold anywhere for about a second — the view will switch to edit mode.
3.Select the Add a Control option.

4. From the list of available options, find Shortcuts and select the Shortcut option.

5. Then select 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 for this purpose. However, its content must follow a specific format:
RS:<shortcut_name>;<additional_data>, e.g. RS:alarm sms;alarm in zone 1
RS: (REMOTE Shortcut) is a prefix that allows the Remote app to interpret the notification differently from other notifications.

IMPORTANT: If this type of notification is received while the phone is locked or the Remote app is not running, the shortcut will only be executed once you tap the notification label that appears on the screen. If the Remote app is running and visible on the screen, the notification’s content will not be displayed at all — instead, the Remote app will trigger the iOS shortcut in the background.

To illustrate this, we’ll present an example of triggering a shortcut that sends SMS messages to specified recipients in the event of an alarm situation. Let’s assume this happens when an alarm occurs in zone 1 on a Satel Integra alarm panel. Here, it’s worth narrowing down the group of notification recipients to avoid the shortcut being triggered multiple times. That’s why, in our example, we present sending the notification to a specific user profile containing two responsible individuals.

1. In the Base module’s configurator, go to the Events tab and add a new event:

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
5. Value: RS:alarm sms;alarm in zone 1
6. Save the Events tab.

2. In the Shortcuts app, tap +

3. In the Search for actions field, type: Send Message

4. Tap the message field.

1. You can type the SMS content manually if you want it to be a fixed text assigned to the shortcut.
2. Tap the Select Variable option.

3. Tap the Shortcut Input field. This way, the shortcut will capture the additional data sent in the notification’s content (the text after the semicolon — see point 5.1.5).

5. Tap the recipients field and define the message recipients. You can select more than one contact.
6. Rename the shortcut to alarm sms (IMPORTANT!)
7. Tap OK to confirm the shortcut.

8. Done! From now on, every alarm event of this type will trigger the specified 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 about it!