SENSBLUE ATLAS/pt: Difference between revisions
Created page with "Home Assistant" Tag: translate-translation-pages |
Created page with "Node-RED" Tags: Mobile edit Mobile web edit translate-translation-pages |
||
| Line 33: | Line 33: | ||
</table> | </table> | ||
== '''SENSBLUE ATLAS''' == | == '''SENSBLUE ATLAS''' == | ||
É um gateway periférico universal e controlador integrado que liga sensores e ativos, executa lógica de controlo e avança para produção sem alterações de plataforma. | |||
<div lang="en" dir="ltr" class="mw-content-ltr"> | <div lang="en" dir="ltr" class="mw-content-ltr"> | ||
Revision as of 08:30, 1 October 2026
Bem vindo a um Incrível mundo novo da automação
Notas da Versão
|
Ficha Técnica
|
Atores MQTT
|
Node-RED
|
Home Assistant
|
Putty & WinSCP
|
SENSBLUE ATLAS
É um gateway periférico universal e controlador integrado que liga sensores e ativos, executa lógica de controlo e avança para produção sem alterações de plataforma.
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
| 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