Automation
The Automation feature is available in 2N Access Commander from firmware version 3.2 under the Advanced, Pro, and Unlimited licenses. Built on the Node-RED platform, this addition directly offers extensive flow-based programming capabilities to Access Commander. It allows users to connect Access Commander with various third-party systems and automate custom workflows based on events within the platform.
Caution
To fully utilize this versatile automation tool, it is necessary to bear in mind the following:
Customer Responsibility for Security: Users are responsible for ensuring that their Automation configurations and workflows are secure and in line with cybersecurity best practices. This includes securing the Node-RED environment, managing permissions appropriately, and safeguarding sensitive data within their automations.
Use of the REST API node: If not used properly, this node may lead to data loss or unintended modifications. It is the user's responsibility to ensure that the node is configured and implemented correctly. Please exercise caution and double-check your settings to avoid potential risks to your data.
Third-Party Nodes and Add-ons: 2N Telekomunikace is not responsible for the use or integration of any third-party nodes, add-ons, or custom modifications to Node-RED within the Automation feature. Customers should carefully evaluate and ensure the security and stability of any additional components they choose to install. Any issues arising from third-party extensions will need to be resolved by the customer or the respective third-party provider.
Technical Support Limitations: While our support team will assist with issues related to the basic functionality of the Automation feature within 2N Access Commander, including our custom Access Commander nodes, they will not be able to provide assistance with the design, development, or debugging of custom Node-RED flows. The users who wish to create complex automations may need to seek additional support from qualified Node-RED experts or consult available resources.
To get started with Node-RED, it is advisable to explore available online resources, such as detailed manuals and numerous YouTube tutorials on Node-RED, which provide guidance on creating and managing the flows.
For more information about custom Access Commander nodes and using the Automation feature within Access Commander, please refer to this manual.
This feature enhances the capabilities of Access Commander. Exploring its potential while ensuring the security of configurations is recommended.
Creating Automations
Automated tasks are created in an external editor. Access the editor from . Changes made in the editor will not take effect until deployed to the server, which is done by clicking the button in the right-hand upper corner of the editor.
The creation of automated tasks is based on the compilation of flows. The flows are formed from nodes tied to each other. The node menu is displayed in the left panel. You can search for nodes by name in the left panel. You can also add a new node after creating a new connection from an existing node.
The data transferred between the nodes is referred to as messages. Refer to here for the message details. This page also describes the basic nodes that handle the message formats or sequences such as the Change, Split, Join... nodes. Automations can work not only with the data obtained in this unique task (msg.), but also with dynamic values in the context of the entire flow history (flow.) or even all the flows in the installation (global.).
Caution
The button sends the set flows to the server. The new flows will not become effective until sent to the server!
Safe mode
The Safe Mode is a key automation troubleshooting tool. Running the editor in the safe mode allows you to make flow changes without the flows running on the background. This means that you can go to the editor, edit what you need and then deploy the changes using the button. This mode is especially useful if any of the flows causes Node-RED to malfunction or fail, due to an error in the flow or a third-party node, for example, or if the flow needs to be stopped immediately.