How openstuder/openstuder-gateway works
Project type and purpose
• This is a native C++ “gateway” daemon plus companion CLI tool, designed to bridge Studer Innotec energy devices to external clients via WebSocket or Bluetooth.
• The README confirms: “Gateway enabling access to Studer Innotec devices from Web or via Bluetooth.”
File structure
• Top-level:
• CMakeLists.txt and cmake/ → build system
• config/ → runtime configuration (drivers, extensions, users, datalog, gateway settings)
• src/api/ → core API library defining abstractions (authorize, device access, extension, storage)
• src/drivers/ → plugin implementations for each API:
– deviceaccess (e.g., demo, XCOM485i)
– extension (webstorage, usermanagement, wificonfig)
– storage (sqlite)
• src/sigatewayd/ → the gateway daemon’s components: initialization, Bluetooth protocol, WebSocket protocol, datalog, device-access operations, extension manager, main, settings
• src/sigwctl/ → command-line control tool reusing the same API
• Patterns:
• Layered architecture (API layer vs. drivers vs. daemon vs. CLI)
• Plugin/registry pattern for drivers and extensions
• Modular subsystems in the daemon (bluetooth, websocket, datalog, device operations, extension)
README for additional insights
• Mentions broader OpenStuder documentation online but no architecture detail here.