Jump to content

SENSBLUE ATLAS/Fast Deploy: Difference between revisions

From ATRONIA Wiki
Created page with "= Speed Up Your Deployment = Integrating ATLAS into your scenario doesn't have to start from scratch. This section brings together sample integrations with third-party software — ready to import, test and adapt — to reduce the time between "unit connected" and "application up and running". Each example hides the complexity of ATLAS's native stack (MQTT, Node-RED, InfluxDB, Grafana, Mosquitto) behind reusable and configurable blocks, so the development team can focus..."
 
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:Fast Deploy}}
= Speed Up Your Deployment =
= Speed Up Your Deployment =
Integrating ATLAS into your scenario doesn't have to start from scratch. This section brings together sample integrations with third-party software — ready to import, test and adapt — to reduce the time between "unit connected" and "application up and running".
Integrating ATLAS into your scenario doesn't have to start from scratch. This section brings together sample integrations with third-party software — ready to import, test and adapt — to reduce the time between "unit connected" and "application up and running".
Line 5: Line 6:


=== Who it's for ===
=== Who it's for ===
{| class="wikitable"
{| class="wikitable tech-table"
!Profile
!Profile
!What they gain
!What they gain
Line 28: Line 29:


=== Available integrations ===
=== Available integrations ===
{| class="wikitable"
{| class="wikitable tech-table"
!Integration
!Integration
!What it demonstrates
!What it demonstrates
!Ideal for
!Ideal for
|-
|-
|Node-RED Simplified Flows
|[[SENSBLUE ATLAS/Node-RED|'''<u>Node-RED Simplified Flows</u>''']]
|Demonstration flows with reusable subflows for AI1..AI4, AO1/AO2 and DI/DO, with Dashboard 2.0. Adds a layer of abstraction between the user and the stack.
|Demonstration flows with reusable subflows for AI1..AI4, AO1/AO2 and DI/DO, with Dashboard 2.0. Adds a layer of abstraction between the user and the stack.
|Rapid prototyping, application logic and internal dashboards.
|Rapid prototyping, application logic and internal dashboards.
|-
|-
|[[Home Assistant|Home Assistant]]
|[[SENSBLUE ATLAS/Home Assistant|'''<u>Home Assistant</u>''']]
|Home Assistant in a Docker container, running alongside the native stack, with MQTT entities for ATLAS inputs and outputs.
|Home Assistant in a Docker container, running alongside the native stack, with MQTT entities for ATLAS inputs and outputs.
|Interface/integration with the Home Assistant automation and visualisation ecosystem.
|Interface/integration with the Home Assistant automation and visualisation ecosystem.
|}
|}
=== In the pipeline ===
Candidates for future examples (subject to priority):
* Local Grafana / shared dashboards
* InfluxDB
* Modbus RTU and TCP/IP

Latest revision as of 16:02, 14 July 2026

Speed Up Your Deployment

Integrating ATLAS into your scenario doesn't have to start from scratch. This section brings together sample integrations with third-party software — ready to import, test and adapt — to reduce the time between "unit connected" and "application up and running".

Each example hides the complexity of ATLAS's native stack (MQTT, Node-RED, InfluxDB, Grafana, Mosquitto) behind reusable and configurable blocks, so the development team can focus on the application rather than on the plumbing.

Who it's for

Profile What they gain
Integrator / customer just starting out A validated starting point, without needing to know ATLAS's internal architecture.
Developer who wants to prototype Ready-made blocks for reading inputs, controlling outputs and visualising data in minutes.
Team evaluating ATLAS A quick way to see the device communicating with tools they already know.

How it works

All examples share the same principles:

  • They are built on ATLAS's MQTT architecture — nothing bypasses the Peripherals Managers; the examples communicate through the standard topics.
  • They are additive — they add an interface/integration layer and do not replace the native stack.
  • They are a starting point, not a black box — the code is exposed and can be changed as needed.
  • They come with installation and validation steps — each subpage includes prerequisites, start-up and a final checklist.

Available integrations

Integration What it demonstrates Ideal for
Node-RED Simplified Flows Demonstration flows with reusable subflows for AI1..AI4, AO1/AO2 and DI/DO, with Dashboard 2.0. Adds a layer of abstraction between the user and the stack. Rapid prototyping, application logic and internal dashboards.
Home Assistant Home Assistant in a Docker container, running alongside the native stack, with MQTT entities for ATLAS inputs and outputs. Interface/integration with the Home Assistant automation and visualisation ecosystem.

In the pipeline

Candidates for future examples (subject to priority):

  • Local Grafana / shared dashboards
  • InfluxDB
  • Modbus RTU and TCP/IP