Update DEVELOPERS.md

Author: autoSteve

DEVELOPERS.md

@@ -28,8 +28,8 @@ The tests will show up at `tests/components/solcast_solar`. `cd` to there and ex
 
 Additional test contributions will be most welcome. In fact, test contributions will be required if your code modifications introduce lines of code that are not properly tested using PyTest.
 
-Current PyTest coverage of all modules is 100%. _Every_ line of code is currently exercised, and it is expected that every circumstance is covered by a test. (This may be accomplished by extending an existing test, or by creating a new one.) This is something that should be aspired to for every pull request to this integration, and if test coverage is completely ignored and your pull request is extensive, then it will likely be rejected, even if it appears to work perfectly. (If your test does not hit PyTest 100% coverage then someone _else will_ need to code the test before the PR is merged. And they won't like that...)
+Current PyTest coverage of all modules is 100%. _Every_ line of code is currently exercised, and it is expected that every circumstance is covered by a test. (This may be accomplished by extending an existing test, or by creating a new one.) This is something that should be aspired to for every pull request to this integration, and if test coverage is completely ignored and your pull request is extensive, then it will likely be rejected, even if it appears to work perfectly. (If your test does not hit PyTest 100% coverage then _someone else_ will need to code the test before the PR is merged. And they won't like that...)
 
-Home Assistant development standards, with full type hint inclusion are also a thing here, and non-conformance will also result in PR rejection. The aim is adherence to strict type checking standards. Our recommendation is to develop suggested changes in a Home Assistant dev container, which incorporates much automated checking of code standards to help out. GitHub CoPilot is also pretty neat at calling out inefficient code.
+Home Assistant development standards, with type hint inclusion are also a thing here, and non-conformance will also result in PR rejection. A strict type checking standard is maintained. Our recommendation is to develop suggested changes in a Home Assistant dev container, which incorporates much automated checking of code standards to help out. GitHub CoPilot is also pretty neat at calling out inefficient or poorly constructed code. Verify type checking with `mypy` (e.g. `mypy solcastapi.py`)
 
-Welcome, dev! Make this a better integration!
+Welcome! Make this an even better integration!

custom_components/solcast_solar/coordinator.py

@@ -177,7 +177,7 @@ async def __check_forecast_fetch(self, *args) -> None:
                         if update_in >= 0:
                             task_name = f"pending_update_{update_in:03}"
                             _LOGGER.debug(
-                                f"Create task %s to fire at {interval.hour:02d}:{interval.minute:02d}:{interval.second:02d}",  # noqa: G004
+                                f"Create task %s to fire at {interval.hour:02d}:{interval.minute:02d}:{interval.second:02d} UTC",  # noqa: G004
                                 task_name,
                             )
                             self._update_sequence.append(update_in)

custom_components/solcast_solar/solcastapi.py

@@ -42,7 +42,6 @@
     BRK_SITE_DETAILED,
     CUSTOM_HOUR_SENSOR,
     DATE_FORMAT,
-    # DATE_FORMAT_UTC,
     DOMAIN,
     HARD_LIMIT_API,
     KEY_ESTIMATE,
@@ -172,42 +171,7 @@ class ConnectionOptions:
 
 
 class SolcastApi:  # pylint: disable=too-many-public-methods
-    """The Solcast API.
-
-    Public functions:
-        get_forecast_update: Request forecast data for all sites.
-        set_next_update: Set the next forecast update time displayed.
-        get_data: Return the data dictionary.
-        build_forecast_data: Build the forecast, adjusting if dampening or setting a hard limit.
-        check_data_records: Verify that forecasts for day 0..7 contain all forecast periods
-
-        get_real_now_utc: Get the complete time now, including seconds and microseconds
-        get_forecast_list: Service event to get list of forecasts.
-        delete_solcast_file: Service event to delete the solcast.json file.
-        get_sites_and_usage: Get the sites and usage, and validate API key changes against the cache files in use.
-        reset_api_usage: Reset the daily API usage counter.
-        load_saved_data: Load the saved solcast.json data.
-        serialise_granular_dampening: Serialise the granular dampening file.
-        granular_dampening_data: Read the current granular dampening file.
-        get_dampening: Return the currently set dampening factors for a service call.
-
-        get_last_updated: Return when the forecast was last updated.
-        is_stale_data: Return whether the forecast was last updated some time ago (i.e. is stale).
-        is_stale_usage_cache: Return whether the API usage cache needs to be reset
-        get_api_limit: Return API polling limit for this UTC 24hr period (minimum of all API keys).
-        get_api_used_count: Return API polling count for this UTC 24hr period (minimum of all API keys).
-
-        get_rooftop_site_total_today: Return total kW for today for a site.
-        get_rooftop_site_extra_data: Return information about a site.
-        get_forecast_day: Return forecast for the Nth day ahead.
-        get_forecast_n_hour: Return forecast for the Nth hour. Based from prior hour point.
-        get_forecast_custom_hours: Return forecast for the next N hours. Interpolated, based from prior 5-minute point.
-        get_power_n_minutes: Return expected power generation in the next N minutes. Based from prior half-hour point.
-        get_peak_power_day: Return max kW for site N days ahead.
-        get_peak_time_day: Return hour of max kW for site N days ahead.
-        get_forecast_remaining_today: Return remaining forecasted production for today. Interpolated, based from prior 5-minute point.
-        get_total_energy_forecast_day: Return forecast kWh total for site N days ahead.
-    """
+    """The Solcast API."""
 
     def __init__(
         self,