Strategy Engine
EnergyThe site-level optimiser. Battery, PV, heat pump and charging are solved as one plan instead of by four controllers arguing with each other.
By OptiBee
Apps
New capability arrives as an app, not as another box.
Smart charging, heat-pump control, PV forecasting, grid response, Home Assistant, a flow editor — installed on the controller from its own app store. Nothing in the cabinet changes, and none of it has to be decided on the day of installation.
- In the store
- 11
- Categories
- 5
- Cabinet changes
- None
The store
What you can install.
Every app is installed and removed on the device itself. Some add a capability to hardware that is already wired; some are the open-source projects your customers already run, packaged for the controller.
PV Forecast
EnergyDay-ahead generation at 15-minute resolution, per inverter. The model trains on that inverter’s own measured output joined with local weather.
By OptiBee
EV Plus
EnergySmart charging on top of the wallbox already on the wall: solar surplus first, dynamic tariffs, a target by departure time, or PV-only.
By OptiBee
Heat Pump Plus
EnergyWeather- and tariff-aware scheduling that moves heating into the cheaper hours without giving up comfort.
By OptiBee
evcc
EnergyThe open-source charge controller with its own web interface, packaged for the device. Meters, wallbox and vehicles are configured in evcc itself.
Open source, packaged for the device
Node-RED
AutomationThe low-code flow editor: wire devices, APIs and logic together in the browser. Community nodes install from the palette.
Open source, packaged for the device
Home Assistant Integration
AutomationA native integration — devices, entities and state appear in Home Assistant, with the safe controls exposed.
By OptiBee
EEBus Gateway
CommunicationPresents the site to the grid operator’s control box as one controllable system: §14a EnWG power limits are received and spread across the controlled devices, with a fail-safe state.
By OptiBee
Tailscale
CommunicationReach the device’s interface over your own tailnet, and forward through it to other devices on the LAN.
Open source, packaged for the device
ZeroClaw
AIAn on-device agent that reads the platform’s own data and proposes control intents — with chat, schedules and stored procedures.
Open source, packaged for the device
Sandbox
DevelopmentA browser terminal and access to the device API, for building and debugging on the device itself.
By OptiBee
Write your own
Your own logic, wired in the browser.
The strategies we ship cover the cases we have seen. When a site needs something else, Node-RED is in the store: drag the nodes you need onto a sheet, wire them together, and the flow runs on the controller.
Prices, forecasts, meter readings and device state are nodes like any other — so are the setpoints you write back. Community nodes install from the palette.
No new hardware, no firmware release, no waiting for us.
How it works
Three things that stay true whatever you install.
01
The store is on the device
Open the controller’s interface and browse what is there. Installing and removing happens on the device, not through a portal in between.
02
Nothing in the cabinet changes
An app adds a capability to hardware that is already wired. No new module on the DIN rail, no re-commissioning, no second visit for something that was not decided on day one.
03
What ran before keeps running
Metering, the local optimiser and the device drivers are part of the controller, not an app you can lose. Adding or removing an app does not take the site offline.
Start with the hardware. Decide about the apps later.
The controller does its job on day one. Apps are how a site grows afterwards — a new tariff, a new wallbox, a new idea from the installer.