Otonomo — installation and activation

Updated 2026-09-27. The earlier self-install walkthrough is retired: its host guarantees, local setup screens, command examples, pricing and activation instructions must not be used as a current installation contract.

Start with suitability

Otonomo connects supported equipment to an energy-management service. Confirm the exact equipment, available interfaces and a suitable always-on host before installing anything. An AI assistant can help gather the facts and explain prerequisites; it cannot establish compatibility just from a vendor name or the presence of Linux.

The existing automated installer expects administrator access, an apt-based Linux distribution and systemd. The SDK requires Python 3.11 or later. These are prerequisites, not a certified list of every supported computer or operating-system version. Other hosts require assessment and testing. Local-network or physical interfaces must be reachable from the chosen host.

For access and installation support, use the Otonomo app or contact support@otonomo.be. Availability and account access are confirmed through Otonomo; this page does not promise immediate self-service enrollment.

Installation permission

Before privileged installation, the owner should receive a concrete plan: selected software and equipment, prerequisites, what changes on the host, required access, remaining blockers and recovery/removal steps. Owner approval for that installation is separate from approval for ongoing control and any associated billing.

Use only the installation instructions and software supplied through an authorized Otonomo process. This page is not a download or executable installer recipe. Public SDK/installer release remains on hold; use only the authorized onboarding process. No release date is promised.

Enter account, device and enrollment credentials only through the designated secure process. Do not paste passwords, private keys or enrollment tokens into an AI conversation or support message.

Connection and verification

Equipment configuration requires the applicable review and approval. Follow official manufacturer instructions for device settings and use an authorized installer where required. Local Modbus access does not require exposing a device port to the internet.

Keep these milestones separate:

1. Installed: the host software is present.
2. Enrolled: the installation is associated with the correct account.
3. Observing: expected measurements arrive and their quality is checked.
4. Commissioned: the applicable capabilities and remaining limitations have been verified.
5. Activated: eligible ongoing energy control has been enabled after the owner separately approved it.

A running service, an online indicator or an enrollment status called active does not establish that optimisation is enabled or that commissioning has passed. Missing measurements must not be treated as zero.

Owner activation and pause

New installations default to observe mode. Ordinary energy-control actuation is suppressed while observing; authorized diagnostic and management messages are a separate matter.

Use the authenticated account control page for the installation's observe/active decision. This is an installation-level setting, not the old per-capability subscription toggles. Review the current commercial terms before activation; this guide makes no price or savings guarantee.

Supported optimisation depends on the actual equipment, verified capabilities and applicable constraints. It does not imply grid charging for price arbitrage. Installation permission, telemetry access and an AI assistant's recommendation do not authorize control or billing changes.

The account control page is also the route to pause ongoing optimisation. Equipment fallback behavior depends on the validated installation; do not assume a universal return-to-previous-settings deadline.