...
The system actively tracks the national loadshedding stage and the schedule for each suburb for the upcoming week per stage. The system updates the stage every hour, while the suburb schedules refresh every 24 hours. Consequently, the number of API requests depends on the number of suburbs (different sites can be part of the same suburb), along with 24 requests to query the stage. It is possible that the system will trigger additional queries if, for example, the location of the unit has changed.
To facilitate this, a new "Load Shedding" group has been added to relevant organizations, where schedules are stored for each site based on its suburb (below Additional Information - Load Shedding). Each schedule includes:
Suburb ID: Identifies the suburb where the site is located, obtained from the API reply, based on the site’s latitude and longitude. The user can override the API query by specifying the id in the following format: 'subrub_id@Manual'.
Stage Municipality - In certain instances, cities or municipalities may override the national stage and declare a different stage for the suburbs they supply power to. This field will be populated by the API to determine the specific municipal stage applicable to the unit's suburb.
API Status - the status of the API requests. Can include the following results:
Last updated: [update time] - The API query was successful, and the information for the unit was last updated at the specified time.
Invalid suburb ID - The API query failed due to an invalid suburb ID format. This issue typically happens if the suburb ID was entered manually.
Invalid location - The API query failed because the unit does not have location data.
Suburb ID not found for location (Lat, Lng) - The API query failed because the suburb ID could not be determined from the provided location data.
Non-stationary unit - No API query was made as the unit is no a stationary unit, therefore not relevant to the loadshedding schedule.
Off-Grid unit - No API query was made as the unit is off-grid, therefore not relevant to the loadshedding schedule.
Schedule: Highlights the next anticipated outages based on declared stages and the suburb weekly schedule. In the absence of any relevant declaration by Eskom or no outages expected during the declared stages, these fields will remain empty.
For example, on 19/10, there is no load shedding from 00:00 to 16:00, but stage 2 is expected from 19/10 16:00 to 20/10 05:00. According to the suburb's schedule for stage 2, an outage is anticipated from 19/10 22:00 to 20/10 00:30. In this case, the load shedding fields will display only this particular outage, as there are no other planned outages before 20/10 at 05:00 and no declarations for the subsequent stage.
...