For flexibility providers and optimisers
One integration. Every fleet.
Whether you command many devices at once for flex or optimise the energy devices in a single home, with WattStack, one hardware-based integration reaches heat pumps, batteries, hot water cylinders and EV chargers on the platform, whatever the manufacturer, through one API. Protocol translation, arbitration and safety limits run on the device, so what reaches you is consistent data, behaving the same way across every model.
Piloting across heat pumps, thermal storage, and battery storage now, and every one of them is flex ready.
The challenge
Bespoke cloud integrations don't scale.
Each manufacturer has its own cloud API, auth model, telemetry schema, rules and limits, so every new device type or manufacturer is another build to specify, test and maintain. Cloud and firmware logic is often undocumented and model specific, so a dispatch or optimisation model built on one brand is rebuilt for the next, and a firmware or API update can break it without warning. WattStack's Edge is inside the device, designed in by the manufacturer or retrofitted locally and abstracts away the per device complexity so one integration reaches every manufacturer on the platform.
Today, through each manufacturer's cloud
Through WattStack
Through WattStack
What you get.
One consistent API
Telemetry and control for every WattStack-connected device flow through one public API, whatever the manufacturer. Your logic sees the same data, under the same rules, across device categories.
Devices that respond reliably
Every command is receipted, so you know whether it landed on the device. If the link drops, telemetry is cached at the Edge and forwarded when it returns, timestamped when it was measured, not when it was sent.
Less logic to build
Protocol translation, per-model mappings and the manufacturer's safety limits all run on the device. Manufacturer changes are abstracted below the interface you build against.
A smaller security surface
Access is scoped per integration and per device, so an integration sees only the devices it is entitled to. Messaging is encrypted in transit, on the module and at rest, and on the device the security boundary is enforced by hardware, not by code.
When you send a command
The device resolves it, in the home.
Your instruction is often not the only service asking a device to act. A flex dispatch, an optimiser's plan, an owner's schedule and a resident override can all overlap and cause command collisions. The Edge resolves them on the device and records which instruction was in control at every point, with an audit log of every change, so you can see exactly what happened. Whichever instruction takes precedence, the device stays clamped inside the manufacturer's safety limits.
Grid protection built in
When a cheap tariff window opens, thousands of devices switching at the same second can put real strain on the grid, and increasingly so as more devices become smart. The Edge spreads each device's start and end inside the window by a small, fixed offset, so a fleet ramps rather than steps, and no device loses its share of the window.
For flexibility providers
Fast commands to many devices, with the scope you choose.
Scope your dispatch to the market you are serving. Filter the device list by category, health or whether it is online, or search it by name, then issue the instruction to each device in scope through the same call, whatever the manufacturer. Telemetry arrives timestamped and at a rate you set and can change on a live device, not at whatever interval a manufacturer's cloud polls. Every command is timestamped and receipted, so you can evidence what each device did, and when, alongside your metered settlement.
export WS_HOST="https://api.wattstack.io" export WS_DEV="3fa85f64-5717-4562-b3fc-2c963f66afa6" # the devices in scope: two categories, online now curl -G $WS_HOST/api/v1/devices \ -d category=heat_pump,battery_storage \ -d connection_status=online \ -H "Authorization: Bearer $WS_TOKEN" # what this device can do, and what its ids mean curl $WS_HOST/api/v1/devices/$WS_DEV/descriptor \ -H "Authorization: Bearer $WS_TOKEN" # → functions, each with controls and telemetry # "functions": [ { "id": 1, "name": "Heat Pump", # "controls": [ { "id": 10, # "name": "Flow Temperature", # "unit": "degc", # "role": { "quantity": "temperature" } } ], # "telemetry": [ { "id": 12, # "name": "Power Draw", "unit": "watt", # "role": { "quantity": "power" } } ] } ] # latest state, keyed by the same ids curl $WS_HOST/api/v1/devices/$WS_DEV/state \ -H "Authorization: Bearer $WS_TOKEN" # → { "telemetry": { "12": { "value": 1850, # "measured_at": "…" } } }
From the API reference. Every device describes itself the same way, so your code finds a control by its role, not by a manufacturer's register.
Three routes to flexibility for a device.
Via a WattStack flex partner
Where an opted-in device has no flex arrangement of its own, WattStack routes its flexibility through a partner holding the market licences to bid the capacity.
Through the WattStack API
Dispatch and telemetry over the public API, for any device its owner has connected and opted in.
Directly to the device
We have committed to direct dispatch over OpenADR and other standards. When activated, a device owner can choose to set up direct command of their devices, with no WattStack cloud in the path, and arbitration and the manufacturer's safety limits still running on the module.
These are the flexibility side of the deployment options on the pricing page. Full stack and Direct API are the first two routes; direct to the device works from Direct API or Module only.
See the protocol matrix →For optimisers
Plan a home's best outcome, across all device types.
Through one API you can read telemetry and set schedules the same way for every device on the platform, whether it's a heat pump, a battery, a hot water cylinder or an EV charger, whatever the manufacturer. Consistent device data and reliable commands mean better decisions, and better results for the homeowner.
Devices can get on our platform by having the Edge built in by the manufacturer, or by retrofitting a Hub. If you have an existing fleet, you can add Hubs to those devices and become a WattStack enabled fleet operator yourself.
For fleet operators →Full telemetry, per home
Query a device's state and history over REST, or have it pushed to you as it lands, with every reading timestamped at the device.
Your plan runs on the device
Schedules are held on the device itself, not replayed live from the cloud, so a plan you set keeps running even if the connection is unstable or drops.
The household comes first
A resident's override and mandatory grid instructions sit above your plan in the device's default priority order, so optimisation never fights the people in the home.
If your service later moves into flexibility, it is the same API and the same devices, with no second integration to build.
See the API →How the money works
Shared earnings along the value chain.
For flexibility providers
- Via a WattStack flex partner. Via our App, the flex value is split between the owner, the manufacturer, the flex provider and WattStack. No platform fee applies.
- Dispatching through the WattStack API. The fleet operator pays a per-device platform fee and chooses between a lower fee with a share of API-dispatched flex to WattStack or a flat fee only. Your terms are with them, not with us.
- Dispatching directly to the device, where an owner allows it. No WattStack share of the flex value. A per-device fee may still apply if the device stays on the wider platform. A device taken fully off the platform pays nothing.
For optimisers
- Integrating via the WattStack API. A per-device platform fee. WattStack takes no share of anything.
- Integrating directly with the device. For commands directly to the device over open standards we take no cut.
Getting started
Four steps from first conversation to fleet-scale dispatch.
Your bidding and your models stay your own. The integration to WattStack is built once, against real devices, and every manufacturer's fleet that joins the platform afterwards is reachable through it, for you to use however your product needs.
-
Integration call
Tell us what you need to control, which markets you operate in, and which device types matter most to you.
-
Early API access
We set you up against real devices and simulators, with the engineers who built the interface alongside you.
-
Pilot
Dispatch or optimise against pilot devices, and reconcile the telemetry against your own settlement, load and tariff models.
-
Scale
Each manufacturer's fleet and device type that joins the platform is reachable through the integration you already have, with nothing new to build.
Reach more devices, faster.
WattStack-connected devices span categories, so one integration reaches heat pumps, batteries, hot water cylinders and EV chargers.