|  Help center

MiOS search


Actions are the ‘then do this’ part of a meshbot. They are the responses that you want to implement once the conditions of your trigger group become ‘True’. 

Here’s a few example actions you might want to set up in a meshbot:

  • Set your lights to randomly turn on and off in various rooms when you’re on vacation to give the illusion that there’s people at home.
  • Dynamically update a Google Sheet with the engagement statistics from your latest outreach campaign at work.
  • Have the dimmer lights in your bedroom slowly illuminate in the morning as part of a wake-up scene. Ease-open the blinds and play soft-music too.
  • Send a Slack notification to the sales team if you sign up a new customer through a web-form.
  • Make a water-sensor in your basement notify you if there is a flood and have the system turn-off the water mains for good measure.

You can run your actions immediately when the trigger conditions are true, or set a delay period.

See the following items for more help with actions:


The action interface

  • Login to MiOS EZlogic
  • Click ‘Meshbot Automation’
  • Click ‘Create New Meshbot’

Once you have decided on your trigger conditions you are ready to choose the action(s) you want the trigger to initiate. The ‘Action’ panel is underneath the trigger panel and lets you choose and configure the response you want:

The entity that will implement your action is known as a ‘controllable’. This is the device, service, meshbot or type of data that you want to respond when the trigger is true:

  • Device – Commands a device to perform an action if the conditions of your triggers are met. See the controllable devices page if you want to learn more about devices in an action at this point.
  • Meshbot – Activates a different meshbot if the conditions of your trigger become ‘true’. For example, you might want your trigger to activate your ‘I’ve left the house’ meshbot. Think of running a meshbot in your actions as like running a subroutine in a program. The meshbot as an action page has more information about this type of controllable.
  • Notification – Lets you send push messages and emails to selected recipients if the conditions of your trigger are met. See the notifications page if you want to learn more about this type of controllable right now.
  • Lua Script – Runs a Lua script to implement an action if the conditions of your triggers are met. You can find some sample scripts in a community post here. Advanced users and developers can learn more about scripts in our API documentation here.
  • NuCAL – Send a command or a request for data to one of EZlogic’s integrated services. For example:
    • Create an action to update your Prospectio CRM when a customer makes a purchase from your website
    • Automatically create a Shipday delivery to a customer when your CRM registers that your business has fulfilled an order.
    • Pull today’s forecast from Accuweather and put this data in a tile on your dashboard.
    You can find a full list of integrated NuCAL services at https://mios.com/integrations/cloud/
  • Http Request – Send a HTTP command to retrieve information from a server or implement a custom action. See the Http Request page to learn more about this type of controllable.

True and False actions

There are two halves to each action — the true and false actions. ‘True’ actions run when all conditions in your triggers have been met (all trigger conditions are ‘true’). ‘False’ actions run when the conditions cease to be true. EZLogic continuously evaluates the true/false state of the triggers so it can implement the corresponding action. For example, you set up a rule to turn on your closet dimmer light at 50% whenever the closet door is opened after sunset. This is your ‘TRUE’ action, but the light would remain on unless you specify otherwise. In the ‘FALSE’ tab you can set an action that sets the light to ‘Off’ if any of your trigger conditions are not met. In this example, these are if the door is not open (you closed the door) OR it is not after sunset.

Not all actions you set up will need a ‘False’ setting. Examples include ‘one-off’ actions like sending an alert if your door is open, having Alexa speak a voice-message, or making a http request. Some actions may be stopped naturally by another meshbot you have running. For example, your kitchen lights might be switched on by a ‘wake-up’ scene but turned off when you activate your ‘House is vacant’ meshbot. Or maybe it’s an action that you want to terminate manually or by voice-command (e.g. turning the shower or toaster-oven off).

Other actions will most definitely require a false state or they will keep running forever. Experimentation is key to discovering the sequence of rules that work for your unique set of devices, apps and services.

Action Groups

Click the ‘Add Action’ button to specify multiple responses to a trigger. For example, ‘Enable motion sensors’ AND ‘Enable Alarms’ AND ‘Enable Security Cameras’ after 11 PM. You need to set a ‘False’ action to stop the activity unless the action is a ‘one-off’, terminated manually, or will be stopped later by some other rule.

The following example shows a bot designed to slowly illuminate a bedroom dimmer light, switch on the shower and run a ‘wake-up routine’ meshbot at 6.30 AM:

Unlike triggers, you can’t link actions with operators like ‘OR’, ‘XOR’ etc. They are implicitly linked with an ‘AND’ operator so all actions in a group will run according to the settings you apply to each.