How to create a flex automation
A flex automation is the automation behind Energy flexing. It's built in the same node editor as cloud automations, but aimed at reducing power over short periods — what makes a building able to take part in the flexibility market.
How to create a flex automation
- Open the building you want to work on. See How to switch building and search for a building.
- Go to Energy flexing in the sidebar.
- Click New flex automation.
- The Flex automation editor opens. Build the logic with nodes from the panel.
- Add the output node targeting the setpoints to be changed — Write setpoint or Change setpoints.
- Click Save.
You get the confirmation Flex automation saved.
If the New Flex Automation app is available to you, Open the Flex Automation app takes you there. The older variant is marked Legacy Flex module.
What a flex automation does, relative to the others
Type | Purpose |
|---|---|
Virtual sensor | calculates a value |
Cloud automation | changes operation on an ongoing basis |
Flex automation | reduces power over short, planned periods |
A flex automation is therefore a cloud automation with a specific purpose: carrying out the actual power reduction when a measure is activated. The measures and activations are controlled separately — see How to create an energy flexing measure and How to schedule an activation.
The nodes and the error handling
The same library as elsewhere: Mathematics, Logic, Aggregate and Advanced. See How to create a virtual sensor for the full overview.
Error handling is critical here, for the same reason as with cloud automations: an automation writing to the installation that loses its input data leaves the setpoint at the last value written. Set the Fallback, Time period without data before fallback is applied: and Time period without data before calculation stops:
Note: For flex this matters especially, because power reduction is temporary by nature. If the automation loses input data mid-activation without a fallback, the building can sit in reduced operation longer than planned — and recovery doesn't happen by itself.
How to build the analysis behind it
Create energy flexing analysis produces an analysis aimed at flex, so you can see the effect of activations in the data. See How to create a timeseries analysis.
Frequently asked questions
Can I copy a flex automation to another building?
Yes, Make a copy — just make sure to point the setpoints at the new installation's own.
How do I understand a flex automation somebody else built?
Use Ask me about the flex automation.
Why does nothing happen when I run it?
Check the priority level of the setpoint write. If a manual override sits at a higher priority, the automation runs with no effect — see How to create a cloud automation.
Do I need a HAN port?
The power potential is calculated from measured data, and the measure list shows Online HAN-Ports. The hint Historical usage may be lower when HAN ports were inactive is worth noting when assessing the potential.
Tip!
Set the Recovery time in the measure alongside the error handling in the automation. The two go together: the measure describes how long the setpoint needs to return to normal, and the error handling makes sure it actually does so even if the data disappears along the way.