Double-clicking on your Action in the Actions Overview will open your Action Editor. This is where you put your actions together. Actions consist of separate steps which you can string together, create “decision trees” and create inputs and outputs.
The general view of an Action Step looks like this:
We can split that view into separate parts which you will recognise in the step editor:
|A|| This button will open the available Action Variables, which are prefixed with
|B|| This button will open the property inspector. Properties are prefixed with
|C||This is the button to run the Action manually. Note, not all actions may run without any sensor input.|
|D||This button opens or closes the console, where you can see debug information while running the Action.|
|E||This button takes you back to the device editor where you can set and configure devices and sensors.|
|F||This is where you can add the Steps (consisting of components) to your Action. You can also drag and drop the components back and forth inside this row. Steps will be processed from left to right.|
|G||The properties part shows the settings of the properties in the currently selected step component. These vary significantly between different components.|
|H||With this button you can toggle the various component property variable names. More details about various variable and property types can be found under Available Variables in Actions|
|I||Pre-mappings are happening before the component runs. They represent and process the data input.|
|J||Post-mappings are happening after the component has run. They represent and process the data output. Please ensure that the input of the next step is always in line with the outputs of the previous step.|
Need more help with this?
Join our slack community for help