SENSBLUE ATLAS: Difference between revisions

(46 intermediate revisions by the same user not shown)

Line 3:

</div>

~~[[File~~:~~SENSBLUE-ATLAS-Gateway.png|~~center~~|frameless|360x360px]]~~

Welcome to a <span style="color: #BFFF00; background: #111; padding: 2px 12px; border-radius: 6px;">Brave New World</span> of Automation

</h1>

</div>

[[File:ATLAS Lottie 500px.svg|center|frameless|500x500px]]

<tr>

<span class="atlas-btn">[[SENSBLUE ATLAS/Release Notes|Release Notes]]</span>

</td>

<span class="atlas-btn">[[SENSBLUE ATLAS/Datasheet|Datasheet]]</span>

</td>

<span class="atlas-btn">[[SENSBLUE ATLAS/~~Realease Notes~~|~~Realease Notes~~]]</span>

<span class="atlas-btn">[[SENSBLUE ATLAS/MQTT Actors|MQTT Actors]]</span>

</td>

<span class="atlas-btn">[[SENSBLUE ATLAS/Node-RED|Node-RED]]</span>

</td>

<span class="atlas-btn">[[SENSBLUE ATLAS/Home Assistant|Home Assistant]]</span>

</td>

<span class="atlas-btn">[[SENSBLUE ATLAS/Putty & WinSCP|Putty & WinSCP]]</span>

</td>

</tr>

Line 20:

Line 38:

Designed for industrial teams who need one dependable path from experiments to operations.

= 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 tech-table"

!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 tech-table"

!Integration

!What it demonstrates

!Ideal for

|-

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

|Rapid prototyping, application logic and internal dashboards.

|-

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

|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