Signup & Reconsent

A detailed guide to the signup/reconsent process can be found here. A flow chart can also be found here.

Hildebrand provide a number of different methods of gaining consent to access a smart meter. We use the method that requires the full IHD MAC and postcode of the user. This is different from the previous n3rgy connection where the MPxN and last 4 digits of IHD MAC were required.

Hildebrand require users to confirm reconsent and acceptance of the terms and conditions every year. This is a requirement that comes from their DCC agreement.

When starting the consent process, if one or more meter consents is found for the user, the postcodes are listed in a drop down list and the user can select the postcode of the meter they would like to reconsent. If the user would like to consent a different meter, they can check the box ‘My current postcode is not listed’ and enter a different postcode.

If a meter is being reconsented, after the selection of a postcode, the user must select the MPxN to identify the unique meter consent object. This is required because it’s possible for a user to have multiple meters for the same postcode.

If no meter consent is associated with a user, they will be asked to enter their postcode as the first step. Once this has been done, the user will be asked to enter their IHD MAC (also called EUI). This is required to validate that the user has access to that meter data.

Before consenting the user’s meter, we check that their meter is accessible with Hildebrand eui-postcode check. If the check is successful, we present the user with the joint Carbon Co-op and Hildebrand terms and conditions for use of the service. Once the user has accepted these terms and conditions, an onboarding call is made to Hildebrand with the necessary details and a user is created on their system with the associated meter. If the user already exists, the meter will be added to their user account.

The terms and conditions are kept up to date on the Hildebrand system. Any updates get pulled and stored in the database with the fetch_latest_tncs task.