SmartReader lost connection notification
Introduction
When the connection between the SmartReader and the SmartBridge devices, is lost for some set period of at least one hour, a “signal lost” event is sent to EnergyAI, by the device. This triggers a notification that informs the user about the connection loss.
This notification is repeated every 90' and stops when either:
- The connection between the SmartReader and the SmartBridge is re-established (EnergyAI receives a
signal found
event from the SmartBridge), or, - The user manually cancels the recurring notification via the new PUT /notification/stop-repetitive-alarm endpoint.
In the event that the user disconnects the SmartBridge from the SmartReader on purpose, in order to connect it directly to the meter via the optical probe, then the notifications are cancelled automatically.
Disabling repetitive notifications
The followingPUT /notification/stop-repetitive-alarm disables repetitive lost connection notifications:
curl -X 'PUT' \
'http://api.net2grid.docker/v2/notification/stop-repetitive-alarm' \
-H 'accept: application/json' \
-H 'Authorization: Bearer <api_key>' \
-H 'Content-Type: application/json' \
-d '{
"code": "OL002.1R"
}'
- This endpoint currently works only for the "connection lost" recurring notification (notification code OL002.1R).
- This endpoint will return an "ok" response when:
- A recurring notification is currently active. In this case it will deactivate the recurring notification.
- A recurring notification is not active. In this case, the endpoint will not do anything.
Notification details
Notification JSON message
{
"msg_code": "OL002.1",
"msg_identifier": "OL002.1",
"gateway_eui": "gateway_eui_in_dec",
"external_installati>: "external_installation_Id"
}
Notification codes/types
Notification type | Notification message |
---|---|
OL002.1R | Connection between SmartReader and SmartBridge lost for over one hour. |
In order to seamlessly incorporate this feature, the relevant SmartBridge devices (SBLR / SPLR) should be updated to the 2.30.X firmware version or later.
Updated 5 days ago