How rubengameztorrijos/solaxpower-sk-su5000e works
Main Components
• Node-RED: The heart of the project, responsible for gathering data from the inverter via RESTful API calls (both local and cloud endpoints) and processing it.
• InfluxDB 2.0: The time-series database receiving the data for indefinite storage and data query.
• Grafana (Optional): The layer for advanced data visualization and dashboard design.
• Solax Inverter & External Data Sources: Represents the device (or endpoints) from which real-time or historical data is retrieved using HTTP GET calls.
• (Optional) MySQL: Mentioned as an alternative storage option in the README, though InfluxDB is recommended.
Component Relationships & Data Flow
• The inverter exposes API endpoints (via local network and cloud) for real-time and historical data.
• Node-RED acts as the data acquisition engine. It calls these endpoints, processes the received data (translating and formatting), and then forwards it.
• Data Flow: API Calls (via GET) from the inverter → Node-RED (processing flow, as seen in the Node-RED flow directory) → Data storage in InfluxDB 2.0.
• (Optional) Grafana connects with InfluxDB to fetch stored data and render dashboards.
Architectural Patterns & Design Principles
• Separation of concerns: Node-RED handles data acquisition and transformation, while InfluxDB handles time-series data storage and Grafana provides the analytics/visualization layer.
• The design leverages a modular and decoupled architecture making it easy to replace or add components (for example, switching MySQL in place of InfluxDB if necessary).
• Use of Docker in the overall deployment for Node-RED, InfluxDB, and Grafana as per the prerequisites, indicating containerized environments and potential orchestration.
Relevant Technologies, Frameworks, and Libraries
• Node-RED (illustrated with a dedicated directory containing flows).
• InfluxDB 2.0 (time-series database).
• Grafana (dashboard and visualization tool).
• Docker (as the common deployment platform for these components).
• HTTP GET calls for real-time data and historical data retrieval.