Energy Usage notifications
Instantaneous demand exceeds thresholds
Homestate hyperactive alert
The homestate hyperactive notification is triggered when NET2GRID Insight identifies that the instantaneous demand that is currently reported exceeds the homestate hyperactive threshold that has been calculated for the installation. The homestate mechanism is based on three thresholds (Chill / Normal / High) that are calculated by NET2GRID Analytics engine every night (using a moving window off 7 days in the past) and are stored in the SmartBridge.
| Notification Code | Description |
|---|---|
| M039 | Homestate hyperactive alert |
The app can query the actual state of the household using the Get current homestate endpoint, and get information about the thresholds themselves using the Get homestate configuration endpoint.
When the gateway detects an instantaneous power level that exceeds the High threshold, then the Hyperactive notification is dispatched.
- No attributes are defined for this notification type.
- This notification can only be enabled if PL001 notification is disabled since both are monitored by the SmartBridge and are mutually exclusive.
Consumption thresholds over a period exceeded
The end user can specify thresholds that will be monitored daily by NET2GRID Insight in order to trigger alerts if the total energy consumption has exceeded these thresholds. The end user can set these thresholds via the Put energy monitors config CE-API endpoint where there can be 2 thresholds (level 1 and level 2) that can be defined for monitoring daily, weekly, monthly and yearly consumption. The Get energy monitors config endpoint returns the thresholds that have been setup for the end user.
| Notification Code | Description |
|---|---|
| EML1D.01 | Consumption exceeded daily threshold for level 1 yesterday. |
| EML2D.01 | Consumption exceeded daily threshold for level 2 yesterday. |
| EML1W.01 | Consumption exceeded weekly threshold for level 1. |
| EML2W.01 | Consumption exceeded weekly threshold for level 2. |
| EML1M.01 | Consumption exceeded monthly threshold for level 1. |
| EML2M.01 | Consumption exceeded monthly threshold for level 2. |
| EML1Y.01 | Consumption exceeded yearly threshold for level 1. |
| EML2Y.01 | Consumption exceeded yearly threshold for level 2. |
These notifications contain the following additional attributes:
| Notification Attribute | Description |
|---|---|
| alert_status | Will always be set to true. |
| gateway | The gateway EUI for which the notification was dispatched. |
| email_address | The email address of the end-user. |
| timezone | Optional field - The timezone specified for the end-user. |
Capacity peak threshold exceeded
The end user can set up a capacity peak threshold and they will be notified when the consumption in a 15-minute interval exceeds the aforementioned threshold. The threshold value can be specified via the PUT /capacitypeaks/config CE-API endpoint and can be later retrieved via the GET /capacitypeaks/config CE-API endpoint.
When the thresholds have been setup and are exceeded the following notification is triggered:
| Notification Code | Description |
|---|---|
| CP001 | Consumption exceeded the capacity peak set by the user |
These notifications contain the following additional attributes
| Notification Attribute | Description |
|---|---|
| timestamp | The timestamp of when the device identified that the threshold was exceeded |
| gateway_eui | The gateway EUI for which the notification was dispatched. |
| capacity_peak_threshold | The threshold for energy usage set by the user in Watts |
| consumption_value | The consumption value that triggered the notification in Watts |
Updated about 2 months ago