1. Onboarding Methods — No Integration
Glow Platform
  • Welcome to Glow Data Service!
  • Getting Started
  • Glow Portals
  • Introducing the Glow System
  • API Authentication
  • Smart Meter Onboarding
    • Introducing Smart Meter Onboarding
    • Smart Meter Eligibility Check
    • Terms and Conditions APIs and Management
    • Onboarding Methods — Direct Integration
      • EUI/Postcode Check
      • AVS Check
    • Onboarding Methods — Hosted Integration
      • Glow IDV SDK
        • Introducing the Glow SDK
        • Supported Verification Methods
        • Implementation Guide — Web
        • Implementation Guide — Mobile
        • Verifiable Credentials
        • Verification Result Screen
        • Consent Capture & Onboarding
    • Onboarding Methods — No Integration
      • Invitation Functionality
      • Agent Verification Portal
  • Data Retrieval
    • Retrieving Time Series Data from Onboarded Users
  • Consent Management and Offboarding
    • Consent Management
    • Offboarding
  • Glow CADs & Fulfilment
    • Glow CAD Fulfilment
  • API Reference
    • Smart Meter Elgibility
      • eligibility
        • smets-ihd-cad
          • Check MPxN has CAD/PPMID
        • checksmetsihd
          • postcode
            • Match EUI IHD with postcode
          • Match EUI IHD with MPxN
        • checksmetsmpxn
          • Check MPXN is eligible in DCC.
    • Content System
      • content
        • {contentId}
          • get a content object
          • Update an existing content object
        • Find all the content objects of an application
        • Add a content object
      • languagecontent
        • {languageContentId}
          • get a language content object by ID
          • Update an existing language content object
        • Find all the language content objects of an application
        • Add a language content object
      • termsconditions
        • {tcId}
          • get a terms and conditions object by ID
        • current
          • Find the terms and conditions that are in force.
        • Find all the terms and conditions of an application
        • Add terms and conditions
      • termsconditionsuser
        • {tcUserId}
          • get a specified terms and conditions user obj
        • Find all the responses to terms and conditions documents.
        • Add a user's response to Terms & Conditions document
      • supportdetails
        • {supportDetailsId}
          • get a support details object
        • Find all the support detail objects of an application
        • Add a support details object
      • faq
        • {faqId}
          • get a FAQ object
        • Find all the FAQ objects of an application
        • Add a faq object
      • prompttype
        • {promptTypeId}
          • get a Prompt Type object
        • Find all the prompt type objects of an application
        • Add a Prompt Type object
      • prompt
        • {promptId}
          • get a Prompt object
        • Find all the prompt objects of an application
        • Add a Prompt object
      • promptuser
        • {promptUserId}
          • get a Prompt User object
        • Find all the prompt user objects of an application
        • Add a Prompt User object
      • useraction
        • {userActionId}
          • get a User Action object
        • Find all the user action objects of an application
        • Add a User Action object
      • useractiontype
        • {userActionTypeId}
          • get a User Action Type object
        • Find all the user action type objects of an application
        • Add a User Action Type object
    • User System
      • register
        • User self registers
      • account
        • {accountId}
          • status
            • Find the status of a specified account. If the account is using an external directory service, this call will confirm whether the user is authenticated against it. This call requires administrative application level credentials.
          • mobileapptoken
            • Add mobile app token to a user
            • Remove a mobile app token to a user
          • Find specific account of an application.
          • Updates the account's metadata.
          • Delete account
        • status
          • With a given JWT token a user can have their account status verfied. If their account is created under an external directory service, this call will establish whether a user's token to the external service is still valid.
        • email
          • Change a user's email
        • name
          • Change a user's name
        • changepassword
          • Change a user's password
        • Find all accounts of an application
        • Add an account to an existing user
      • user
        • {userId}
          • username
            • Change a user's username
          • Find specific user that has an account in an application.
          • Delete specific user. This will delete all the accounts of a user. Please refer to delete account API. This API requires specific permissions.
        • verify
          • Generate a user verification token
          • Verify a user verification token
        • resetpassword
          • Generate a token that can be used by user to reset their password.
          • A user resets their password
        • verification
          • status
            • mpxns
              • renewal
                • Renew consent for a number of meterpoints
              • revocation
                • Revoke consent for a number of meterpoints
            • mpxn
              • {mpxn}
                • renewal
                  • Get meter point consent renewals
                  • Renew meter point consent
                • revocation
                  • Get meter point consent revocations
                  • Revoke meter point consent
            • API to retrieve user's meter points' consent and verification
        • Find specific user that has an account in an application from the username.
        • Create a user
      • accountprofile
        • {profileName}
          • Find specific group of application
        • Find all the profiles of an account
        • Create an account profile under a given profileName.
      • accountsession
        • get the session of an account
        • Update an account session.
      • auth
        • token
          • {tokenId}
            • Deletes a token, specified by its tokenId.
          • Returns all the tokens that are active and valid for a specified user.
        • newToken
          • Generate a new token for an account.
        • deleteToken
          • delete a token
        • oauth
          • access
            • Exchange the Authorization Code for an Access Token.
          • Check and validate an Oauth Access token.
          • Authenticate a user and generate an OAuth 2.0 Authorization Code Grant.
        • Checks whether a user token is valid.
        • authenticate an account
    • Virtual Entity System
      • vesys
        • appstats
          • find statistics on the number of Virtual Entities per application
      • virtualentity
        • {id}
          • resources
            • Find the resources of that belong to Virtual Entity with ID
          • attribute
            • Find a Virtual Entity's metadata by ID
            • Add/Update a Virtual Entity's metadata
            • delete metadata from the Virtual Entity
          • Find Virtual Entity by ID
          • Update a Virtual Entity
          • Delete a Virtual Entity
        • Add a new Virtual Entity
        • Find all Virtual Entities
      • vetype
        • {id}
          • resources
            • Find all resources that belong to a user that satisfy the Resource Types in the Virtual Entity Type definition.
          • Find Virtual Entity Type by ID
          • Update a Virtual Entity Type
        • Add a new Virtual Entity Type
        • Find all Virtual Entity Types
    • Webhook System
      • webhook
        • {webhookId}
          • Find webhook by ID
        • error
          • {errorId}
            • Find a particular webhook error
          • Find all the webhooks that have failed
        • Find all webhooks of an application (or user)
    • Resource System
      • resource
        • {id}
          • readings
            • Get resource readings
          • current
            • Get the current resource reading.
          • first-time
            • Get the UTC time of the first available reading
          • last-time
            • Get the UTC time of the most recent available reading
          • meterread
            • Get the cumulative value reported on a metering device. (Not supported for all resource types).
          • tariff
            • Get the latest tariff that is being applied to a resource.
          • tariff-list
            • Get the tariff history that is being applied to a cost resource.
          • catchup
            • Trigger a request to retrieve the latest available readings from the DCC.
          • glowbinary
            • API that returns the resource's raw data in the Glow Binary format.
          • Find resource by ID
        • count
          • Count the number of resources per resourceType
        • Add a new resource
        • Find all resources per user or application
      • resourcetype
        • {id}
          • resource
            • Find resources of a specific resource type that belong to a user
          • appresource
            • Find resources of a specific resource type that an application has access to
          • Find resourceType by ID
        • Add a new resource type.
        • Find all resource types
    • Notification System
      • alerttype
        • {alertTypeId}
          • Find alert type by ID
          • Updates the alert type's metadata.
        • Find all alert types of an application
        • Create an alert type
      • alert
        • {alertId}
          • Get an alert by Id
        • user
          • Get the alerts sent to a user
        • Send an alert
      • template
        • {templateId}
          • Find template type by ID
          • Updates the teplate's metadata.
        • {alertTypeId}
          • {channelType}
            • {cultureCode}
              • Find template by alertTypeId, channeType and cultureCode
              • Create template by alertTypeId, channeType and cultureCode
        • Find all templates of an application
        • Create a template
      • notification
        • {notificationId}
          • log
            • Get the logs of a particular notification
          • Get a notification by Id
    • DFS
      • dfs
        • termsconditions
          • The current version of terms and conditions that is pertinent to DFS for a particular application.
        • user
          • Get all the users that have opted in the DFS functionality
          • User opts in to DFS functionality for a particular MPxN. The mpxn field is only required if a user has more than one MPxN.
          • User opts out of DFS functionality
        • event
          • {dfsEventId}
            • user
              • Get all the users that have participated in a particular DFS event
          • user
            • participation
              • API to indicate User participating in particular DFS event
            • Get all the events a user has signed up for
    • Device Management System
      • devicetype
        • {id}
          • Find Device Type by ID
        • Add a new Device Type
        • Find all device types
      • device
        • {id}
          • status
            • This call can be used to see whether a gateway device is sending packets to the Glow Platform (i.e. via WiFi).
          • Find device by ID
        • resource
          • {resourceId}
            • Find the device that sources a specified resource.
        • meter-point
          • {meterPointNumber}
            • inventory
              • Get the DCC inventory of a meter point
            • resources
              • Get the resources associated to a meter point
        • smart-meter
          • {eui}
            • inventory
              • Get the DCC inventory of a meter point by providing an EUI.
        • status
          • This call can be used to see whether a gateway device is sending packets to the Glow Platform (i.e. via WiFi).
        • Get a user's devices
        • Add a new device
      • discover
        • {hardwareId}
          • Find device by ID
  1. Onboarding Methods — No Integration

Agent Verification Portal

Introduction#

The Agent Verification Portal gives a trusted Agent, working on behalf of an organisation, the authority and ability to take an energy consumer through the Glow onboarding process to complete the required verification and consent protocols to start retrieving smart meter data (and potentially join a CAD to the smart meter(s). The Agent Portal is available to Hildebrand's Data Service customers.
This guide gives an overview of the Agent Verification Portal and walks an Agent through the two onboarding processes offered. We also outline the prerequisites to using the Portal and the information that the Agent needs to onboard an energy consumer.

Definitions#

TermDefinition
AgentAn trusted, trained individual working on behalf of an organisation to onboard energy consumers, using the Agent Verification Portal
ConsentSpecific to the Smart Energy Code: Mandatory process to obtain and record consent from the verified energy consumer to retrieve their energy consumption and related data (and potentially join a CAD to the smart meter(s)) from their smart meters under the Terms and Conditions in place at the time their consent is captured.
Energy consumerIndividual energy consumer at a property - they are who complete verification and consent (expected to have a valid smart meter).
HildebrandHildebrand Techology Limited is the legal entity behind the Glow Data Service. The company is a SEC Party with the role of a DCC Other User.
Hybrid onboardingAn onboarding method supported by the Agent Portal that takes place over two steps - 1) remote verification upload and 2) on-site consent capture from an energy consumer.
MPxNMeter Point Administration Number (MPAN for electricity), Meter Point Reference Number (MPRN for gas). Meter point identifier; every property has a unique MPxN for each energy source.
OnboardingThe process of creating an account, processing verification and capturing consent for an energy consumer in order to access smart meter data.
On-site onboardingAn onboarding method supported by the Agent Portal that is facilitated entirely at the property that consent is being granted for, by working with the relevant energy consumer to obtain verification evidence and consent.
SECASSmart Energy Code Administrator; administer The Smart Energy Code (SEC) which is a multi-Party agreement which defines the rights and obligations of energy suppliers, network operators and other relevant parties involved in the end to end management of smart metering in Great Britain. Hildebrand's ability to offer smart meter data service is regulated by the SEC.
Shared Terms and ConditionsTerms and Conditions outlining terms of service for an energy consumer who will be sharing data with an organisation signed up for Glow Data Service. Terms & Conditions are managed (including version control) by Hildebrand as part of the Glow Data Service and must comply with Hildebrand's SECAS obligations.
VerificationSpecific to the Smart Energy Code : Mandatory process to verify that the energy consumer who is giving consent has the right to give consent to smart meter data access for the MPxNs at that property.

Access to the Agent Verification Portal#

Organisations signed up to use the Glow Data Service select the verification methods intend to use, they can be amended over time. Access to the Agent Verification Portal needs to requested; that request should include a list of the email addresses of the Agents who will be using the portal. Agents must be trusted employees who are trained to understand the regulatory obligations they are meeting when signing energy consumers up via the portal; the Agent will also need to have signed an NDA.
Access will be via a unique domain; unique login credentials will be provided per Agent and must not be shared. Hildebrand will conduct random audits of your process and if there are failures, the identified Agent will need to explain why the approved protocol was not followed.

Introduction to Verification and Consent#

Glow Data Service offers a variety of onboarding methods to enable organisations to capture the required verification and consent from an energy consumer in order to access their smart meter data. SEC obligations mandate that no data can be retrieved from the smart meter(s) at from a property without explicit consent from the verified energy consumer (see definitions above).
Glow's Agent Verification portal offers a trusted Agent the ability to take an energy consumer through the onboarding process, verifying an energy consumer's identity in order to capture their consent for their data to be accessed.

Verification evidence options#

There are two means of verifying energy consumers using this Portal: by uploading a photo of the meter or IHD at the property during a site visit, or by uploading a proof of address documents.
Both options are further described in the below sections.

Meter or IHD photo#

A meter or IHD photo can be used for verification during an On-site onboarding journey, providing the energy consumer has a SMETS2 meter.
The photo must clearly show the 16-digit identifier on the front of the meter. This is commonly referred to as an EUI.
You can also navigate to the screen on an IHD at the property that shows either the EUI. This is usually found from the setting page.
What is the difference between SMETS1 and SMETS2?
There are two variants of smart meters: SMETS1 and SMETS2. SMETS1 is an older generation of meter, while SMETS2 meters are the current, second-generation standard. Both are supported by our service, however, SMETS1 meters do not have the EUI we require for verification printed on the front of the meter.
If you are onboarding a customer at a property with SMETS1 meters, we will not present you with the option to upload a meter or IHD photo.

Proof of Address Documents#

Proof of address documents are used for verification in the following scenarios:
1.
When completing Hybrid onboarding journey
2.
A meter or IHD photo cannot be provided during a site visit
3.
There is a SMETS1 meter on site
For Scenario 3, the Glow system will detect if a meter is SMETS1 based on the MPAN provided. An Agent will automatically be presented with the Proof of document upload screen when onboarding an energy consumer with SMETS1 meters.
The below table defines the document options and their requirements regarding what information they must convey and the validity period. Only these options are acceptable; the regulator mandates that evidence is UK government approved.
The document uploaded must show all the information in the Evidence Requirements column, and follow the Date Requirements outlined.
Document TypeEvidence RequirementsDate Requirements
Energy billName, address, dateLast 3 months
Council tax billName, address, dateLast 12 months
Tenancy agreementName, address, dateCurrent date must be within the tenancy period
Drivers licenseName, address, dateLicense must be valid and in date

Consent capture#

The energy consumer must consent to their data being accessed by an organisation and by Glow.
Consent can be captured digitally at the end of the process, providing the energy consumer has an email address. Once verification has been completed, the Agent inputs the energy consumer's email address. They will receive a verification code, which is to be entered on the next screen in the process.
After verifying the email address, the full terms and conditions appear on the next screen for the consumer to read.
The Agent presents the energy consumer with the full terms and conditions to read and sign digitally. Once they have ticked the boxes and provided their signature, consent has been obtained.
A copy of the terms and conditions will also be sent to their email; they should be encouraged to retain the document for their records. They should also be told that the document tells them how they can revoke / withdraw consent.
❓
What if the energy consumer doesn't have an email address?
In this case, onboarding cannot be completed via the Agent Portal, though functionality to support this case is coming soon.
To onboard this energy consumer, you will need to securely share the verification evidence captured for that energy consumer and a copy of a signed physical consent form to the Glow team, alongside your chosen reference for this energy consumer's account.
We will then manually create the account using the reference provided and process the verification documents.

Requirements#

The Agent Verification Portal can be used if the following criteria are met:
Consent can only be captured from the energy consumer during a site visit.
During site visits the Agent must use a mobile device (phone, tablet or laptop).
Mobile device must have the ability to capture images of the required evidence from the energy consumer and upload them to the Portal.
The Agent must carry printed copies of the Glow approved Consent Form and a full printed copy of our Shared Glow Terms and Conditions for customers who are not digitally enabled; the Terms & Conditions and a copy of the Consent Form must be left with the customer in this scenario.
The following descriptions assume that:
1.
the Agent is logged into the Portal, and
2.
the application the energy consumer is to be associated to is known (if the organisation has multiple projects in Glow or is managing different groups of users, it may have different applications configured. Select whichever is relevant. If not, proceed by onboarding all your energy consumers within the sole application.

Onboarding journeys supported by the Agent Verification Portal#

The Agent Verification Portal supports two onboarding journey and either can be used as appropriate to the scenario:
1.
On-site onboarding (at energy consumer's property)
2.
Hybrid onboarding (verification phase completed prior to site visit, requires organisation to have verification evidence collated - typically this will be Tenancy Agreements for the energy consumers).
Consent can only be captured on-site with the energy consumer. The following descriptions assume the Agent is logged into the Portal with their unique credentials.
Optional: For organisations installing a Glow CAD at a property, while on-site the Agent can use the Portal to add a Glow device to the energy consumer’s account; full description later in this Guide.
Later in this document we present full details behind the steps described below.

On-site onboarding, high level overview#

The process is:
1.
The Agent is on-site with the energy consumer.
2.
The Agent asks the energy consumer what evidence they have available to verify the energy consumer has the right to give consent to access the smart meter data at that property.
3.
Using the evidence provided, the Agent completes the onboarding process to create an account, upload verification evidence and capture consent from the energy consumer.

Hybrid onboarding, high level overview#

This two-step onboarding journey is appropriate where verification documents are available to the organisation (typically provided by the landlord in the form of Tenancy Agreements). The site visit is used to obtain the energy consumer's consent. The process is:
1.
An Agent obtains the required verification evidence for an energy consumer, which includes the energy consumer's name, address, MPxN and a document proving identity and proof of address. If the MPxN is not known, a lookup can be used during the onboarding journey.
2.
An Agent uses the Agent Verification Portal to create an account for an energy consumer and uploads the related verification evidence.
3.
If verification is passed, a record of the verification will be stored against the property's address as an indication that the account has verification in place.
4.
An Agent makes a site visit to the property to obtain consent from the energy consumer for their data to be accessed. Note: it does not need to be the same Agent who processed the verification evidence.
5.
While on-site the Agent selects 'Capture Consent' under Hybrid Onboarding in the Agent Portal. They then select the relevant verification submission for that property.
6.
To unlock the verification, the energy consumer will need to provide their first name and their postcode; this ensures that the person (energy consumer) is part of the process.
7.
The Agent captures consent from the energy consumer.

Detailed On-site onboarding journey#

This journey is completed on site with the energy consumer who has verification evidence. Our set-up wizard splits the process into three stages (four, if optional Glow hardware is being added):
1.
Create an account for the user
2.
Verification
3.
Consent

Step 1: Create a user account#

Start the onboarding process by creating an account for the energy consumer in your application. For an explanation on applications, see our guide to the Glow System here.
1.
Select 'On-site onboarding journey'
2.
Select the application in which you want to onboard the energy consumer if you have more than one. - if you have multiple projects or are managing different groups of users, you may have different applications configured within your organisation. Select whichever is relevant.
3.
Enter their MPxN (if you do not know the MPxN, select MPxN Look Up and proceed with either an EUI, postcode or UPRN for the property).
4.
Add a username or reference for the consumer; this creates an account for them in the application. It can be their email address or a unique reference you use to identify them in your systems. Alternatively, you can generate a random reference code for this user by selecting 'Generate reference'.
💡
You must keep a record of which reference you assign to each energy consumer, as this information is required to located this energy consumer in our systems later on. You cannot search for an energy consumer based on their address details in the Glow platform - the username will be required.

Step 2: Verification#

With an energy consumer account, the Agent now needs to complete verification by uploading evidence that the energy consumer is a resident at that property and can therefore grant consent later on.
1.
Enter the energy consumer’s name and address.
2.
Upload evidence to verify the consumer’s residency and identity, and to confirm that the provided details are correct.
If the customer has a SMETS1 meter, which we will identify based on their provided MPAN, you will be asked to upload one document serving as a proof of address.
If a customer has a SMETS2 meter, you will be asked to upload either a photo of their electricity meter or an installed IHD from their supplier, OR a proof of address document.
3.
The uploaded evidence will be automatically checked. If there is an error, you will be prompted to resubmit the evidence. If the check is successful, you will be prompted to move on to the next step.
A detailed description of the available verification methods via the Agent Portal are outlined in the earlier section.

Step 3: Consent#

The final stage of the onboarding process is capturing consent to retrieve the smart meter data from the energy consumer. A detailed description of consent capture via the Agent Portal are outlined in the earlier Consent capture section.
Once consent is granted, there is an option to add Glow hardware to their account. Please see the Optional Hardware section.

Detailed Hybrid onboarding journey#

The Hybrid onboarding journey splits the functionality of the On-site onboarding journey into two steps, blending a remote document upload with an on-site consent granting process. This is helpful in cases where verification documents are available for energy consumers ahead of time.
The two steps in the journey are:
1.
Create account and Upload verification documents, remote
2.
Capture consent, on-site

Step 1: Create account and Upload verification documents#

The agent uploads verification documents for an energy consumer they will be onboarding, with the intention of later obtaining consent on site.
1.
Select the application to be associated to (if more than one).
2.
Enter their MPxN (if you do not know the MPxN, select MPxN Look Up and proceed with either an EUI, postcode or UPRN for the property).
3.
Enter the energy consumer’s name and address. IMPORTANT: the name given will be used to unlock this verification submission during the site visit, so make sure it is accurate to who will be granting consent later on.
4.
Add a username or reference for the consumer to create an account for them in the application selected. This can be their email address or a unique reference you use to identify them in your systems, if you have one. Alternatively, you can generate a random reference code for this user by selecting 'Generate reference'.
5.
Upload a proof of address document as evidence to verify the consumer’s residency and identity, and to confirm that the provided details are correct. Supported types and criteria for a proof of address document are outlined in the above section and found here.
6.
If the uploaded document is approved, the verification will be completed and the approved verification will be added to a vault, labelled with the energy consumer's generated reference and their address.

Step 2: Capture consent#

The second step of the Hybrid onboarding journey is to capture consent during a site visit.
1.
Once on site, select 'Capture consent' from the home screen of the portal.
2.
You will be presented with a list of approved verifications, labelled with their reference and address. Select the relevant verification for the property.
3.
Have the energy consumer provide their postcode and their first name to 'unlock' the verification.
4.
Obtain consent as described in the previous Consent capture section.
Once consent is granted, there is an option to add Glow hardware to their account. If you are installing hardware on site, please see the Optional Hardware section.

Adding Optional Hardware#

Once the consent step has been completed successfully, the option will be given to add Glow hardware to the newly created account. If you are adding hardware, select ‘Add Hardware’ to proceed.
You will be prompted to enter the Hardware ID for the Glow CAD you are installing - this is the MAC address on the unit. The MAC address is a 12-digit code located either on the top of the device if it is a Glow Delta, or on top of the second barcode on the back of the unit if it is a Display / CAD.
Note: You MUST fulfil a SMETS1 CAD to a SMETS1 meter, and a SMETS2 CAD to a SMETS2 meter. Otherwise, the association will fail.
Inputting the Hardware ID will automatically fulfil the CAD to the account - but it will not automatically result in a join unless the below criteria are met:

1. The CAD has been connected to internet#

The WiFi connection process depends on the type of Glow device being installed.
Glow Display / CAD: Input WiFi credentials directly on the Display CAD.
Glow Delta CAD, WiFi variant: Use the Connect app to set WiFi credentials for the device.
Glow Delta CAD, NBIoT variant: Use the Connect app to set WiFi credentials for the device OR connect the device over NBIoT and send a command to the device to set the WiFi credentials remotely.

2. The CAD is in range of the energy consumer’s meters#

Ensure the CAD isn't too far from the meters - if there are many floors between the unit and the meters, or large pieces of metal, the unit may not be able to join.

Glow CAD Status Check#

There is a page in the Agent Portal that allows you to check the status of a Glow CAD - this can be found by navigating the the Menu at the top left of the Portal and selecting the Glow CAD Status Check.
Using this tool, you can search a CAD using its MAC address to verify if it is:
Associated to an account
Connected to the internet (Online / Offline)
Joined to the meter
This helps an Agent check if a device is fully set up at a property before they leave the site.

FAQs#

General#

What is the purpose of the Agent Portal?
What is the difference between the two onboarding journeys presented?
How can new agent logins be added to our organisation?
What do I need before making a site visit?

Verification#

I can’t upload a meter or IHD photo - what do I do?
Do I have to upload both a meter photo and an additional document?
How do I know if a document is within a valid date?
The energy consumer on site is not the energy bill payer, how can I verify them?
If I upload a verification document remotely, how do I get consent for it later?
How long is a successful verification valid?
I'm confident my verification evidence is correct, but I am getting an error.

Consent#

How long is consent valid?
Does consent renewal require a site visit?

Hardware#

How do I add a CAD to a property?
Can I join a CAD to a property later on?
What if a CAD is not joining the meter?
Modified at 2026-08-14 16:18:53
Previous
Invitation Functionality
Next
Retrieving Time Series Data from Onboarded Users
Built with