Compatibility and device integrations

Compatibility starts with the exact device

A solar installation often combines components from several vendors: smart meters, inverters, battery storage, EV chargers and sensors use different protocols and do not expose the same values. GridFusion handles these differences through separate device drivers and a shared, normalised device model instead of relying on assumptions.

The exact model, firmware, documented local interface and actual capability always matter. A similar product name or related product family is not enough. GridFusion does not invent pins, registers or API fields. If a vendor source is incomplete or contradictory, the uncertain function remains disabled until it has been documented and verified.

Current reference devices

Shelly Pro 3EM for local grid metering

Shelly Pro 3EM is the first real reference device for three-phase measurement at the grid connection. Its driver translates documented local data into a generic meter state. The Energy Engine, user interface, REST API and storage never see Shelly-specific fields. If the connection fails or a reading becomes stale, this is safety-relevant: no new battery control decision is produced.

Solakon ONE as battery storage

Solakon ONE is the first real reference device for battery and inverter data. Reading and controlled writing are deliberately separate. The write adapter uses documented vendor contracts only and remains behind the central Solakon Safety Gate. Normal firmware does not automatically enable write capabilities; pilot approval is not a general hardware release.

“Reference device” does not automatically cover other Shelly or Solakon products. The model, network access, firmware and relevant capabilities must be reviewed before integration.

Vendor-neutral core, vendor-specific driver

Every driver explicitly advertises its connectivity and capabilities. Depending on the device, these may include metering, battery state, solar generation or approved control functions. The registry manages multiple devices and assigns generic roles. A factory only creates the appropriate driver; it contains no business or optimisation logic.

This separation has a practical benefit. A new meter does not automatically change battery planning, the UI, storage or price modelling. Its protocol is first implemented and tested in isolation. It then supplies the same generic meter state as an existing driver. GridFusion can consequently analyse different installations without rebuilding the entire system for each home.

How a new device is added

1. Identify the device: record exact model and firmware, installation role and network path.
2. Verify the source: obtain official vendor documentation for protocol, authentication, values, units and limits.
3. Define capabilities: expose only demonstrable read or write capabilities in the driver.
4. Test in the simulator: reproduce parsing, timeouts, invalid values, connection loss and normalisation.
5. Observe read-only in the field: compare readings with the vendor display and installation state without enabling control.
6. Approve in a controlled way: treat writes only after a separate safety review, tight limits and a supervised hardware test.

Routine analysis does not require USB access. With local operator consent, Control 7 can provide normalised telemetry, connectivity and bounded diagnostics through the authenticated platform contract. Secrets and raw vendor-specific payloads do not belong in that central data stream.

Planned integrations

Additional meters, battery systems and inverters will be prioritised according to pilot needs. MQTT and Home Assistant are planned as local integration paths. Flexible loads such as EV chargers and heat pumps, together with room-temperature and other environmental sensors, are also on the roadmap. This does not promise compatibility with a particular model.

Priority follows three criteria: reliable vendor documentation, access to a pilot installation and clear value for the generic energy model. Proprietary cloud APIs without a sustainable usage basis do not take precedence over a documented local connection.

Propose an installation for the pilot

An initial review needs the exact meter, inverter and battery model, firmware version, available local network connection and a simplified installation diagram. It also helps to state the objective: observation only, self-consumption analysis, or a later trial of explicitly bounded control.

Do not send passwords, tokens or Wi-Fi credentials by email. Use GridFusion contact to arrange a secure first discussion. Energy management for solar and battery storage explains the overall process.