Enode

Data Access token

Read and control connected vehicles, chargers, batteries and inverters through Enode from any Windmill script, flow or app.

Set up in 3 steps

Get an access token

In the Enode developer dashboard, take your client id and secret and exchange them for an access token, then copy it.

Add the resource in Windmill

Open Resources, add a resource of type enode, and paste the token.

Run your first script

Fork any script below and read before writing anything. There are dozens here, so search by the verb you need.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Resource type

enode — the shape of the credential every script on this page expects.

View raw schema →

Field	Type	Required	What it is
token	string	Yes

Questions

The token stops working

Enode access tokens are short-lived. For anything scheduled, have the flow exchange the client credentials each run rather than pasting a token that expires.

A device returns nothing

Enode reads through links your users authorised. If the user has not linked that vehicle or charger, there is nothing to read.

Is my token stored on the hub?

Never. It lives only in your own Windmill workspace, encrypted at rest.

Set up in 3 steps

Get an access token

Add the resource in Windmill

Run your first script

Scripts

Get Inverter Statistics

Get Webhook

Control Charging

Refresh Vehicle Data

Get User

Set Operation Mode for Battery

List User Vehicles

Disconnect Vendor

Check Available Vehicle Vendors

Get Location

Get Vehicle Action

List Interventions

List Solar Inverters

List User HVAC units

Refresh meter data

List Vehicles

Get Battery

List User Solar Inverters

Create Schedule

Update Location

Check Available Charger Vendors

Link User

List User Meters

Delete Schedule

Get Charger Action

Set HVAC unit to follow device schedule

Get Schedule

Set Max Current

List User Batteries

Cancel Charger Action

Resource type

Questions