Push Notifications

n3rgy Push Notifications provide an event-driven mechanism to notify customers when meter data has been successfully received, processed and persisted by the n3rgy platform.

Push Notifications apply to both smart meters (SMETS) and Advanced Meters (AMR/HH), providing a consistent approach across SMETS-only, AMR/HH-only and mixed meter portfolios. The n3rgy API provides a common set of endpoints for accessing data from SMETS and AMR/HH meters.

How are Push Notifications configured?

Push Notifications are configured through the n3rgy Business Portal (n3rgy data - accessing smart energy data) based on the required utility / reading type combinations.

You configure:

• the webhook URL;
• the API key; and
• the utilities and reading types for which they want to receive notifications.

The configuration is not specific to the meter type. Once Push Notifications are configured for a utility / reading type combination, the configuration applies to the relevant data irrespective of whether the portfolio contains SMETS meters, AMR/HH meters, or a mixture of both.

The Customer Service API also provides endpoints to retrieve, edit or delete the Push Notification configuration and check its status.

How do Push Notifications work for SMETS meters?

For SMETS meters, n3rgy retrieves data via the DCC according to the data collection frequency associated with the customer's consent for the relevant utility and reading type.

The consent configuration supports separate collection frequencies for:

• electricity import;
• electricity export; and
• gas import 

Once the data is received and persisted by n3rgy, the applicable Push Notification is triggered.

How do Push Notifications work for Advanced Meters (AMR/HH)?

For Advanced Meters, AMR/HH data is provided to the n3rgy platform by the relevant Data Collector rather than being retrieved directly from the meter via the DCC.

Once an AMR/HH reading batch has been successfully processed and persisted, n3rgy identifies customers with Push Notifications enabled for the matching HAN, utility and reading type and sends the webhook notification.

For AMR/HH data, the notification is therefore associated with a successful data ingestion and processing event, rather than specifically indicating that the reading represents the latest available interval.

What happens when AMR/HH data arrives late?

If historical AMR/HH data arrives later, passes validation and is successfully processed and persisted, a Push Notification can be generated for the applicable configured utility / reading type.

This means a notification may relate to historical data rather than only the latest available interval.

What happens when previously provided AMR/HH data is corrected?

A Push Notification can also be triggered when previously provided AMR/HH data is revised and the corrected data is successfully processed and persisted.

For example, if an initial 0.0 value is subsequently replaced by the actual reading, successful processing of that corrected data can generate another notification.

What should I do after receiving a Push Notification?

A Push Notification indicates that an applicable data processing event has occurred. The notification itself is not the meter data.

After receiving the notification, the customer should retrieve the applicable meter data using the n3rgy Customer Service API.

The Customer Service API provides the following endpoint for retrieving data by MPxN, utility and reading type:

GET /mpxn/{mpxn}/utility/{utility}/readingtype/{readingType}

The same API structure supports access to SMETS and AMR/HH meter data, simplifying integration for customers managing mixed meter portfolios.

For further technical detail, see the n3rgy Customer Service API Developer's Guide, including the API specification for Push Notification configuration and meter data retrieval.