SENSBLUE ATLAS/Fast Deploy - Revision history

WikiManagement: /* Available integrations */

2026-07-14T16:02:58Z

Available integrations

← Older revision		Revision as of 16:02, 14 July 2026
Line 34:		Line 34:
	!Ideal for		!Ideal for
	\|-		\|-
	\|[[SENSBLUE ATLAS/Node-RED\|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.
	\|-		\|-
	\|[[SENSBLUE ATLAS/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.

WikiManagement at 15:20, 14 July 2026

2026-07-14T15:20:39Z

← Older revision		Revision as of 15:20, 14 July 2026
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".

WikiManagement: /* Available integrations */

2026-07-14T15:10:43Z

Available integrations

← Older revision		Revision as of 15:10, 14 July 2026
Line 28:		Line 28:

	=== Available integrations ===		=== Available integrations ===
	{\| class="wikitable"		{\| class="wikitable tech-table"
	!Integration		!Integration
	!What it demonstrates		!What it demonstrates

WikiManagement: /* Who it's for */

2026-07-14T15:10:29Z

Who it's for

← Older revision		Revision as of 15:10, 14 July 2026
Line 5:		Line 5:

	=== Who it's for ===		=== Who it's for ===
	{\| class="wikitable"		{\| class="wikitable tech-table"
	!Profile		!Profile
	!What they gain		!What they gain

WikiManagement at 15:08, 14 July 2026

2026-07-14T15:08:36Z

← Older revision		Revision as of 15:08, 14 July 2026
Line 41:		Line 41:
	\|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

WikiManagement: /* Available integrations */

2026-07-14T15:06:35Z

Available integrations

← Older revision		Revision as of 15:06, 14 July 2026
Line 33:		Line 33:
	!Ideal for		!Ideal for
	\|-		\|-
	\|[[Node-RED\|Node-RED Simplified Flows]]		\|[[SENSBLUE ATLAS/Node-RED\|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.		\|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\|Home Assistant]]
	\|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.
	\|}		\|}

WikiManagement: /* Available integrations */

2026-07-14T15:05:10Z

Available integrations

← Older revision		Revision as of 15:05, 14 July 2026
Line 33:		Line 33:
	!Ideal for		!Ideal for
	\|-		\|-
	\|[[Node-RED ~~Simplified Flows~~\|Node-RED]]		\|[[Node-RED\|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.		\|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.

WikiManagement: /* Available integrations */

2026-07-14T15:04:54Z

Available integrations

← Older revision		Revision as of 15:04, 14 July 2026
Line 33:		Line 33:
	!Ideal for		!Ideal for
	\|-		\|-
	\|Node-RED Simplified Flows		\|[[Node-RED Simplified Flows\|Node-RED]]
	\|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.

WikiManagement: 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..."

2026-07-14T15:04:05Z

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..."

New page

= 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 ===
{| class="wikitable"
!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 ===
{| class="wikitable"
!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]]
|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.
|}