For developers
Everything an OptiBee app can do, a third-party app can do.
The controller is a platform before it is an appliance. There is no privileged interface that only our own apps are allowed to use: the twins, the API and the store are the same ones we build on.
Device twins
Every device the platform speaks to appears as a twin: a set of named points carrying live values, and — where the integration goes that far — points you can write.
That indirection is the reason an app can be written once. Subscribe to the twin of a battery and you get state of charge, power and limits without knowing which of the brands in the catalogue is behind it; the driver did the translating. The same holds for control: you write a setpoint to the twin, and how that becomes a register write or a protocol command is the driver's problem, not yours.
What a twin will accept is bounded by the integration depth of that device. Device support explains what each level allows, and The Edge Platform explains why values live on the platform rather than inside the app that produced them.
Where to go next
- The kit — API, tools, samples and the sandbox
- AI agents — the same surface, driven by an agent
- Publishing — getting an app into the store