Commissioning

Cloud commissioning starts in the manufacturer's platform. Complete the preparation below before requesting activation or enabling an automatic strategy.

Information and access required

1. Confirm the exact device model, firmware and country or region in Compatibility.
2. Make sure the device is online and visible in the manufacturer's portal.
3. Prepare the required portal account, site identifier, serial number and API authorization.
4. Confirm that the account includes control permission, not only data access, when remote control is required.
5. Record the responsible technical contact for the vendor account and site network.
6. Define the safe fallback if the internet connection, vendor API or control signal becomes unavailable.

The detailed device page lists integration-specific prerequisites, such as the required account role, API application, site identifier or commissioning route.

Safe activation sequence

1. Connect or authorize one test site.
2. Verify that timestamps, measurements, units and power-sign conventions are correct.
3. Send a limited test setpoint or mode request when control is supported.
4. Confirm the resulting device behaviour and feedback in both the vendor platform and Controller.
5. Test timeout or communication-loss behaviour where possible.
6. Only then enable the intended automatic control strategy or onboard the remaining portfolio.

Acceptance checks

• Measurements update at the expected interval and do not become stale.
• Import, export, charge and discharge use the agreed sign convention.
• The device accepts only commands permitted for the selected account.
• Feedback confirms whether the requested action was applied.
• The installation returns to the agreed fallback when cloud communication is interrupted.
• Site and device names are clear enough for portfolio operation and support.

If a device is visible but cannot be controlled, check the integration's control scope in Compatibility, the account permissions and any firmware or regional restrictions.