The Energy API

We are onboarding the first users to our API for Distributed Energy Resources. In the webinar our engineer Emeline explains the features of the API.
Download the slides

Where can I find the documentation of the API?

Currently, we are onboarding the first users. You can sign up for the waiting list here.
Once, it is public we will also publish the documentation.

How does a battery set constraints?

We can retrieve min/max power and energy capacity from the battery driver. These values are posted as constraints to the API by our control gateway.

How is the API encrypted?

We use a TLS encryption for the communication between edge gateway and the cloud and the communication between the API caller and our cloud.

Is it possible to add new integrations?

We are constantly extending the support for more and more protocols, manufacturers and devices. There are also plans to enable third-parties to build their own integrations.

Is a local gateway always required?

To ensure quick response times and robust operations we rely on a local gateway for now. Technically speaking, it would also be possible to connect the cloud directly to the devices provided they have an internet connection.

Do you have a plan B in case the internet connection fails?

All logic is executed locally. In case the gateway loses connection to the cloud it continues with the last instructions it received or switches to a fallback mode after a pre-defined period of time.

Can you set constraints at the cluster level or only appliance level?

No, this is not possible at the moment. We are, however, planning to add this feature in the near future.

How many gridXboxes would you need to manage a ten households?

The gridBox can control any device that is connected to the same network. So if you plan a new district and connect all households in one network a single gridBox, this would suffice to manage all ten households. In practice, however, you usually require one gateway per household.

How long is the interval for controls?

The gridBox supports the communication in a frequency of up to 200ms. Most DERs, however, are slower to react and so, depending on the response time of the DER, it can take up to 10 seconds until an order is realized.

Are you planning to allow energy suppliers to control certain devices to manage the load on the grid?

Our aim is to build a flexible API for a variety of use cases. In theory this means that a user could set a constraint that allows the energy supplier or grid operator to switch off the heat pump for a brief period of time given that a certain temperature is kept.

Does the API support the sale of flexibility to the market?

The API provides all the information and functionalities to sell flexibility to the market.

Are the constraints shown in your User Interface?

In our current applications we do not show the constraints. If you want to show these to your users there is nothing that keeps you from it.

Can I integrate my house automatisation with the API?

We don't know if you can ;)... jokes aside the API certainly provides you with the required functionalities to do so.

Want to learn more about XENON?
Stay in the loop!
Sign up for our newsletter. We won't spam you. Just one update per month. Unsubscribe any time.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.