Configuring Notifications
Enabling/Disabling Notifications for a System
The different types of notifications that can be automatically generated for a system can be turned off for a given system.
Note that if you turn off a type of notification for a system, then such notifications will also be turned off for the subsystems of that system as well!
To set these system-specific settings, open the site details page (from the sites list page or using the sites quick-access drop-down). Then, click on the little envelope next to the given system:
You can turn COM ERR and/or NOT PRODUCING notifications on or off, and you can also set a timeout. For an overview of the options available, see System-specific Issue Generation Settings in the Mana Administrator's Manual.
A Word on Timeouts
There are two timeouts that affect system status notifications.
First, the website can be configured to wait a specified amount of minutes before setting a system's status to COM ERR. This is to allow some lag in communications between the device(s) and Mana. This timeout can be set on the system form:
Second, the website can be configured to wait a specified amount of minutes after a system has stopped reporting before creating a COM ERR issue. Similarly, a timeout can be set after a system has stopped reporting non-null values before a NOT PRODUCING issue should be created.
Note that the issue generation timeout is not in addition to the COM ERR timeout, but the COM ERR timeout must elapse before a system state is set to COM ERR. In other words, the largest value set in either the system COM ERR timeout or the system COM ERR Notifications timeout must elapse before a COM ERR notification is created.
Notifications Q&A
We shall extend the notification threshold to 48 hours for Enphase, Fronius & APsystems sites. It shall be applied both for "communication error" and "not producing" notifications. Please let me know what needs to be configured
Answer: Depends on what you want. Assuming that a system hasn't reported for over a day, do you want:
- the system status to show COM ERR, you just don't want any issues created
- you want the system status to remain in whatever it was (normal/over/underproducing) for up to 2 days if readings aren't coming in (and since the status doesn't change, no notifications are sent)
If you want the system status (and icon on the map) to show that there is a COM ERR, but just don't want issues to be created (#1 above), then set the timeouts on the notification control panel for the system:
If you want the system status to stay in "PRODUCING" even if the system hasn't reported in over a day (#2 above), then just set the COM ERR timeout on the system form. I would start by just doing this, so just set the system COM ERR timeout to 2880 minutes on the system form:
This was the system should tolerate timeouts of at least this long before the status enters COM ERR or NOT PRODUCING. And since the system status doesn't change no issues should be generated.
Note for administrators: if this is what you do, then also update the timeout in ID!
f you set the timeouts on the notifications control panel for the system, then you don't need to update anything in initial data.
Also see:
- Notifications in the appendix
If you are an administrator, refer to the Mana Administrator's Manual, System-specific Issue Generation Settings for a technical overview of how issue generation and notifications work, or the System Statuses and Icons chapter to understand when a system status change occurs that can trigger a notification.
No Comments