/config/register/virtual/{reg}

The virtual register configuration.

Several virtual register names are well-known and provide special semantics:

  • use: Intended to represent total power consumption at a site. It is generally presented with the name Usage in English and the equivalent translation in other languages (subject to availablility).

  • gen: Intended to represent total power generation at a site, e.g., from local solar or wind power generation facilities. It is generally presented with the name Generation in English and the equivalent translation in other languages (subject to availability).

  • bat: Intended to represent total power coming from on-site batteries (if positive) or power going to on-site batteries for charging (if negative). It is generally presented with the name Battery in English and the equivalent translation in other languages (subject to availability).

  • bat_el: Intended to represent the amount of energy left in on-site batteries. The value of this register should be equal to the sum of each battery's state of charge times the battery's capacity (in joules). It is generally presented with the name Battery left in English and the equivalent translation in other languages (subject to availability).

Get /config/register/virtual/{reg}

SecurityApiKey
Request
path Parameters
reg
required
string

The name of a virtual register. May not be empty, contain commas (,), and may not consist entirely of digits. Virtual register names may contain a single dot (.) between a prefix and a suffix. The prefix is called the view name.

query Parameters
max-depth
integer >= 1

Limit output depth of the response. See Max-Depth.

Example: max-depth=2
filter
string

Response filter string. See Filter-Spec.

Example: filter={foo,bar}
Responses
200

Normal response.

401

Unauthorized response.

get/config/register/virtual/{reg}
Request samples
Response samples
application/json
{
  • "result": {
    },
  • "error": "Error message (present if an error occurred)."
}

Replace /config/register/virtual/{reg}

SecurityApiKey
Request
path Parameters
reg
required
string

The name of a virtual register. May not be empty, contain commas (,), and may not consist entirely of digits. Virtual register names may contain a single dot (.) between a prefix and a suffix. The prefix is called the view name.

Request Body schema: application/json
Array of objects (configRegisterVirtualRegValue)

The formula to calculate the value of this virtual register. It consists of a list of physical register names whose values are to be added or subtracted.

Responses
200

Normal response.

401

Unauthorized response.

put/config/register/virtual/{reg}
Request samples
application/json
{ }
Response samples
application/json
{
  • "status": "OK",
  • "error": "Error message (present if an error occurred)."
}

Update /config/register/virtual/{reg}

SecurityApiKey
Request
path Parameters
reg
required
string

The name of a virtual register. May not be empty, contain commas (,), and may not consist entirely of digits. Virtual register names may contain a single dot (.) between a prefix and a suffix. The prefix is called the view name.

Request Body schema: application/json
Array of objects (configRegisterVirtualRegValue)

The formula to calculate the value of this virtual register. It consists of a list of physical register names whose values are to be added or subtracted.

Responses
200

Normal response.

401

Unauthorized response.

post/config/register/virtual/{reg}
Request samples
application/json
{ }
Response samples
application/json
{
  • "status": "OK",
  • "error": "Error message (present if an error occurred)."
}

Delete /config/register/virtual/{reg}

Remove this virtual register.

SecurityApiKey
Request
path Parameters
reg
required
string

The name of a virtual register. May not be empty, contain commas (,), and may not consist entirely of digits. Virtual register names may contain a single dot (.) between a prefix and a suffix. The prefix is called the view name.

Responses
200

Normal response.

401

Unauthorized response.

delete/config/register/virtual/{reg}
Request samples
Response samples
application/json
{
  • "status": "OK",
  • "error": "Error message (present if an error occurred)."
}