Create automations as visual as they are powerful
Define how the building should respond using visual blocks that connect triggers, conditions and actions. Combine equipment from different technologies without any coding.
Your building's logic at a glance
Each Flow follows a visual structure: an event starts the automation, conditions check whether it should continue and actions define what should happen.
SimulationA very simplified simulation of the edalsoBMS Flow editor
Make a choice in each drop-down and watch your Flow take shape
From a simple rule to complete logic
Create an automation with just a few blocks, or add multiple conditions, branches and actions as complexity grows.
Everything is designed in the same visual editor, without writing code.
Yes / No
Each condition has two outputs: what happens if it is met and what happens if it is not.
Start
Marks where the Flow begins: the trigger from which all the logic starts.
Delay
Waits the number of seconds you set before moving on to the next block.
Countdown
Starts a countdown for the time you set.
Any
Continues as soon as any of the conditions that lead into it is met.
All
Continues as soon as all the conditions that lead into it are met.
Variables
Store a value that the Flow reads or changes. They can be local, belonging to the Flow itself, or global, for use across many Flows.
Notes
Leave comments on the canvas so anyone can understand what each part of the Flow does.
Design once. Reuse the logic across the whole building.
Turn a Flow into a template and deploy the same logic by building, floor or zone. The system identifies the corresponding devices in each location and generates the automations required.
When the logic changes, update the template and synchronise its instances without editing each Flow individually.
Instances · 4
- Off out of hours · Floor 112 devices · v3PendingSynchronised
- Off out of hours · Floor 214 devices · v3PendingSynchronised
- Off out of hours · Floor 311 devices · v3PendingSynchronised
- Off out of hours · Basement6 devices · v3PendingSynchronised
Your automations keep working even if the Internet goes down
Flows are stored and run locally on edalsoOne. If the building loses its connection, the triggers, conditions and actions that depend on local equipment keep working without an external server.
Explore the other features
Your buildings detect what is happening. Make sure they know how to respond.
Tell us what you want to automate and we'll show you how to create visual Flows that connect equipment, data and systems so that each building responds according to the rules you define.
Frequently asked questions
Do I need to know how to code to create a Flow?
No. Flows are created in the edalsoBMS visual editor, with blocks that connect triggers, conditions and actions, without writing any code.
What happens to Flows if the Internet goes down?
They keep working. Flows are stored and run locally on edalsoOne, so everything that depends on the building's equipment carries on without the need for an external server. When the connection returns, edalsoOne re-establishes communication with the cloud.
Can I use the same Flow in several buildings or floors?
Yes. You turn the Flow into a template and deploy it by building, floor or zone. The system identifies the devices in each location and generates the automations. If you change the logic, you update the template and synchronise all its instances in one go.
Can a Flow combine equipment from different technologies?
Yes. A single Flow can use equipment connected via Zigbee, LoRaWAN, Modbus TCP/IP, MQTT or BACnet/IP, and other technologies can be added using the appropriate third-party gateways or converters.
Can a Flow create incidents or connect with other systems?
Yes. The actions a Flow can take include sending notifications, creating incidents, updating modes and connecting with other systems via the API.