********************** FlexMeasures Changelog ********************** v0.33.0 | June 01, 2026 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. note:: It is recommended to assign a worker to the ``ingestion`` queue (or configure existing workers to handle it, as well), so that sensor data posted via the API is processed asynchronously [see `PR #2101 `_]. For instance, using: .. code-block:: bash $ flexmeasures jobs run-worker --queue "forecasting|scheduling|ingestion" .. warning:: We are deprecating ``FLEXMEASURES_MONITORING_MAIL_RECIPIENTS`` in favor of ``FLEXMEASURES_DEFAULT_MONITORING_MAIL_RECIPIENTS``. New features ------------- * Added API and UI support for copying assets and their subtrees [see `PR #2017 `_ and `PR #2120 `_] * Improve UX after deleting a child asset through the UI [see `PR #2119 `_] * Improve source filtering in the sensor data GET endpoint by exposing the documented query parameters in Swagger and allowing filtering by the account linked to data sources [see `PR #2083 `_ and `PR #2151 `_] * Support sensor references for efficiency fields in storage flex-models [see `PR #2142 `_] * Introduce the ``consumption`` and ``production`` flex-model fields for the ``StorageScheduler`` to save schedules to [see `PR #2190 `_ and `PR #2213 `_] * Added a unified job status endpoint ``GET /api/v3_0/jobs/`` to retrieve the current execution status and result message for any background job [see `PR #2141 `_] * Add ``flexmeasures jobs inspect-job`` CLI command to show job status and metadata information (similar to the job status endpoint in the API) [see `PR #2202 `_] * New ``GET /api/v3_0/sources`` endpoint to list accessible data sources and defined types, with ``only_latest=true`` by default to return only the most recent version per source [see `PR #2126 `_] * Add support for filtering sensor data GET requests by ``source-type`` on ``/api/v3_0/sensors//data`` [see `PR #2127 `_] * Making monitoring alerts more flexible: allow ``flexmeasures monitor`` alerts to target one or more user IDs or email addresses with ``--recipient``; ``flexmeasures monitor last-seen`` can now narrow monitored users to one or more accounts with ``--account`` or to client accounts with ``--consultancy`` [see `PR #2158 `_] * Improve LightGBM daily seasonal lag handling for sub-hourly forecasting sensors [see `PR #2157 `_] Infrastructure / Support ---------------------- * Move sensor data ingestion to a job queue for improved performance when POSTing large amounts of data to the sensor data API, returning a ``202 Accepted`` response with a job status URL when queued [see `PR #2101 `_ and `PR #2207 `_] * Remove legacy rolling viewpoint forecasting code and utilities after migrating to fixed-point forecasting [see `PR #2082 `_] * Upgraded dependencies [see `PR #2114 `_, `PR #2148 `_, `PR #2161 `_ and `PR #2177 `_] * Let RQ Dashboard job page load even when job data includes non-JSON-serializable values [see `PR #2200 `_] * Run ``flexmeasures jobs run-worker`` with RQ's embedded scheduler on by default so jobs created with ``enqueue_in`` are promoted from the scheduled registry when due; pass ``--without-scheduler`` to disable [see `PR #2112 `_] * Support filtering time series data by data source account [`PR #2065 `_] * Speed up finding the data sources associated with a sensor and the sensors associated with a data source [`PR #2151 `_] * Speed up sensor stats, especially potent when viewing sensors stats over a large sensor history [`PR #2173 `_] * Various smaller fixes in documenting scheduling endpoints and flex-model fields [`PR #2122 `_] * Add cross-cutting Copilot instruction files to ``.github/instructions/`` covering atomic commits, changelog format, docstrings, error handling, Marshmallow schemas, pre-commit hooks, testing, timezone awareness, and UI terminology [see `PR #2198 `_] Bugfixes ----------- * Fix forecasting covariate assembly to retain the latest known value per regressor when regressors have different belief times for the same event [see `PR #2155 `_] * Fix ``StorageScheduler`` crash (``AttributeError: 'NoneType' object has no attribute 'event_resolution'``) when scheduling a site whose asset tree contains non-storage devices with only a ``power-capacity`` in their ``flex-model`` (no ``sensor`` key) [see `PR #2085 `_] * Fix DST transition handling by supporting both native Python ``datetime`` and pandas ``Timestamp`` objects in time series segment processing, preventing ``AttributeError`` when processing segments with differing UTC offsets [see `PR #2197 `_] * Fix forecasting regressor filtering to use only regressor beliefs known at the forecast ``belief_time`` [see `PR #2134 `_] * Make the sensor page forecast button train from available sensor history instead of the default 30-day window [see `PR #2187 `_] * Check read permissions for sensors referenced in forecasting and scheduling config payloads, and return a clearer 403 error when a referenced sensor is not readable [see `PR #2096 `_ and `PR #2125 `_] * Add the missing ``force-new-job-creation`` field for triggering a schedule on an asset (tree) [see `PR #2182 `_] * Clean up stale sensor references from ``flex-config`` and ``sensors_to_show`` when deleting a sensor, using JSONB queries to find affected assets before pruning those references [see `PR #2106 `_] * Standardize resolution formatting across API endpoints for consistent response payloads [see `PR #2152 `_] * Make the auth check for CLI commands work with ``flask``, too, instead of only with the ``flexmeasures`` alias [see `PR #2169 `_] * Fix ``flexmeasures show asset`` for assets whose ``sensors_to_show`` uses the standardized ``plots`` schema [see `PR #2189 `_] * Distinguish data sources with duplicate names in chart legends without showing source IDs [see `PR #2185 `_] * Fix broken API endpoint links in Read the Docs output by post-processing both known API index layouts and rewriting ``(id)`` anchors [see `PR #1753 `_] * Wrap Darts training ``ValueError`` about no common feature times as a clearer ``NotEnoughDataException`` when there is insufficient history for the requested forecast horizon [see `PR #2192 `_] * Make Sentry also ignore 404 events, if we only log them without exc_info [`PR #2212 `_] v0.32.3 | May 15, 2026 ============================ Bugfixes ----------- * Fix account UI page exposing details to users from other accounts; any logged-in user could previously view the page and see account attributes (introduced in v0.32.0), but no user/asset/sensor details [see `PR #2163 `_] * Fix auth on asset creation: regular users can now create child assets (the permission check now targets the parent asset, not the current user's account), and account-admins can no longer nest assets under parents from other accounts [see `PR #2163 `_] * Fix off-by-one error on sensor data deletion (button on the sensor page), which lead to not deleting the last data point in the selected time window [see `PR #2175 `_] * Prevent JSON parsing failures when updating an asset's flex-config [see `PR #2162 `_] v0.32.2 | May 12, 2026 ============================ Bugfixes ----------- * Fix removal of unchanged beliefs when saving data [see `PR #2159 `_] * Fix soc-fields set to fixed quantities [see `PR #2160 `_] * Fix disappearing plots on asset graphs during playback [see `PR #2147 `_] v0.32.1 | May 5, 2026 ============================ Bugfixes ----------- * Fix account attribute saving via the API for accounts that have a consultancy account set; the PATCH endpoint no longer incorrectly rejects requests that do not include ``consultancy_account_id`` in the body [see `PR #2140 `_] * Make the sensor page load much faster for sensors with lots of data, by avoiding to load statistics over all of its history by default [see `PR #2129 `_] * Return a clear validation error (instead of a server ZeroDivisionError) when posting instantaneous (0-minute) data to non-instantaneous sensors via ``[POST] /sensors/(id)/data`` [see `PR #2116 `_] * Fix asset form overwriting attributes [see `PR #2138 `_] * Fix a bug where toast messages in flex-config modal are broken due to unexpected JSON structure [see `PR #2124 `_] * Fix asset context page for asset names containing apostrophes [see `PR #2117 `_] * Fix removal of unchanged beliefs by comparing per event [see `PR #2150 `_] v0.32.0 | April 15, 2026 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ------------- * Upgrade graph modal to support flex-config references in plots [see `PR #1926 `_ and `PR #1904 `_] * Add a button to create forecasts from the sensor page, visible to users with permission to record data on the sensor, and enabled when at least two days of data are present [see `PR #1985 `_] * Button on sensor page to delete data (by date range and source) [see `PR #2095 `_] * Support inferring ``soc-at-start`` from configured ``state-of-charge`` sources and fail early when those values are stale or missing near schedule start [see `PR #2026 `_] * UI support for editing JSON attributes on sensors, assets and accounts [see `PR #2093 `_] * Support fetching a schedule in a different unit still compatible to the sensor unit [see `PR #1993 `_] * Support saving state-of-charge schedules to sensors with ``"%"`` unit, using the ``soc-max`` flex-model field as the capacity for unit conversion [see `PR #1996 `_] * Version headers (for server and API) in API responses [see `PR #2021 `_] * Support forecasting from a given time in the past, by allowing to specify a ``prior`` belief time in the forecasting API endpoint (as already possible with CLI command) [see `PR #1978 `_] * Show sensor attributes on sensor page, if not empty [see `PR #2015 `_] * Separate the ``StorageScheduler``'s tie-breaking preference for a full :abbr:`SoC (state of charge)` from its reported energy costs [see `PR #2023 `_ and `PR #2108 `_] * Improve asset graph hover interaction with a vertical ruler across subcharts, while keeping hover dots for easier visual tracking [see `PR #2079 `_] * Improve asset audit log messages for JSON field edits (especially ``sensors_to_show`` and nested flex-config values) [see `PR #2055 `_] Infrastructure / Support ---------------------- * Support coupling data sources to accounts, and preserve user ID and account ID references in audit logs and data sources for traceability and compliance [see `PR #2058 `_] * Stop creating new toy assets when restarting the docker-compose stack [see `PR #2018 `_] * Migrate from ``pip`` to ``uv`` for dependency management, and from ``make`` to ``poe`` [see `PR #1973 `_] * Improve contact information to get in touch with the FlexMeasures community [see `PR #2022 `_] * Expand audit logging for password life-cycle: password_reset, password_changed and reset_password_instructions_sent events [see `PR #2036 `_] * Upgraded some dependencies for security reasons [see `PR #2037 `_] * Remove unused ``dictdiffer`` dependency after replacing JSON audit-diff logic with internal formatting utilities [see `PR #2055 `_] * Upgraded dependencies, including sphinx from v8 to v9 [see `PR #2061 `_] * Improve error logging for various exceptions [see `PR #2045 `_] * Update agent instructions and workflows to customize the primary entry point and to make the test environment used by agents and by the test workflow identical [see `PR #2066 `_, `PR #1998 `_ and `PR #2068 `_] * Filter out 404 (Not Found) errors from Sentry reports by default, configurable via ``FLEXMEASURES_DO_NOT_SEND_NOTFOUND_TO_SENTRY`` [see `PR #2071 `_] * Document scripting with the client and in the CLI [see `PR #2097 `_] * Document fallback schedule mechanism: explain how 303 (See Other) redirects work for infeasible schedules, with a client-side code example [see `PR #2107 `_] Bugfixes ----------- * Fix the Swagger endpoint for fetching a schedule [see `PR #2109 `_] v0.31.3 | April 11, 2026 ============================ Bugfixes ----------- * Fix regression in upsampling speed [see `PR #2060 `_] * Fix forecasting with multiple regressors in ``flexmeasures add forecasts`` by combining regressor time series as parallel components [see `PR #2088 `_] * Fix a bug where ``save_to_db`` could silently drop a changed belief when the prior beliefs in the database happened to be ordered by descending belief time [see `PR #2086 `_] * Prevent ``save_to_db`` from failing on saving duplicate beliefs in case ``FLEXMEASURES_ALLOW_DATA_OVERWRITE = False`` [see `PR #2059 `_ and `PR #2098 `_] * Fix :abbr:`DST (Daylight Saving Time)` bug in processing time series segments [see `PR #2069 `_] v0.31.2 | March 18, 2026 ============================ Bugfixes ----------- * Fix bug with resampling time series of e.g. SoC minima with different belief times for adjacent time slots [see `PR #2012 `_] * Fix an issue where asset context was accessed in schemas that do not define a ``context`` attribute [see `PR #2014 `_] * Fix wrap-up forecasting job [see `PR #2011 `_] * Stop failure in the API endpoint that lists available endpoints (/api/v3_0/) [see `PR #2032 `_] Infrastructure / Support ------------------------ * Re-add bcrypt dependency [see `PR #2029 `_] v0.31.1 | March 6, 2026 ============================ Bugfixes ----------- * Fix CLI command ``flexmeasures add forecasts`` [see `PR #2007 `_] * Add missing field documentation for ``aggregate-power`` and ``state-of-charge`` fields, which can be used to reference a sensor on which to record extra scheduling results [see `PR #2003 `_ and `PR #2006 `_] v0.31.0 | February 28, 2026 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. warning:: As of this version, power schedules will no longer appear flipped (in UI charts) when they are recorded on *consumption* sensors. Please note that: - Schedules obtained via the dedicated API endpoints for scheduling are not affected by this change! - The ``consumption_is_positive`` sensor attribute governs the sign of schedules saved to the database. The sign convention of UI charts is to simply match what is in the database. - If you inadvertently make use of the `sensor data API endpoint `_ to fetch *schedules*, or have reporters that compute reports on *schedules*, rather than on *measurements*, be advised that you may experience flipped results. You may need to adjust your client-side code or reporter configuration accordingly. (Updating a reporter configuration automatically leads to a fresh data source for the saved time series.) - Finally, if you maintain a plugin with a custom ``Scheduler`` class that returns time series to be saved on power sensors, we recommend incrementing the version of the ``Scheduler`` class. This will yield a fresh data source for new schedules and allow you to discriminate your flipped schedules, which, for instance, will make it easier to flip back the historical schedules if you later want to. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ------------- * New API endpoints to create annotations for accounts, assets, and sensors: `[POST] /annotations/accounts/(id) `_, `[POST] /annotations/assets/(id) `_ and `[POST] /annotations/sensors/(id) `_ [see `PR #1968 `_] * New forecasting API endpoints, and all timing parameters in forecasting CLI got sensible defaults for ease of use `[POST] /sensors/(id)/forecasts/trigger `_ and `[GET] /sensors/(id)/forecasts/(uuid) `_ to forecast sensor data [see `PR #1813 `_, `PR #1823 `_, `PR #1917 `_ and `PR #1982 `_] * Improve CSV upload validation by inferring the intended base resolution even when data contains valid gaps, instead of requiring perfectly regular timestamps [see `PR #1918 `_] * Support setting a resolution when triggering a schedule via the API or CLI [see `PR #1857 `_] * Support variable peak pricing and changes in commitment baselines [see `PR #1835 `_] * Support storing the aggregate power schedule [see `PR #1736 `_] * Make listing public assets on account page optional [see `PR #1872 `_] * Step-by-step replay in the UI, using the **n** key to go to the **n**\ ext time step [see `PR #1898 `_] * Support changing a sensor's timezone in the UI [see `PR #1900 `_] * Improved the UX for creating sensors, clicking on ``Enter`` now validates and creates a sensor [see `PR #1876 `_] * Show zero values in bar charts even though they have 0 area [see `PR #1932 `_ and `PR #1936 `_] * Added ``root`` and ``depth`` fields to the `[GET] /assets` endpoint for listing assets, to allow selecting descendants of a given root asset up to a given depth [see `PR #1874 `_] * Support creating schedules with only information known prior to some time, now also via the CLI (the API already supported it) [see `PR #1871 `_] * Added capability to update an asset's parent from the UI [`PR #1957 `_] * Add ``fields`` param to the asset-listing endpoints, to save bandwidth in response data [see `PR #1884 `_] .. note:: For backwards-compatibility, the new ``fields`` parameter will only be fully active, i.e. also returning less fields per default, in v0.32. Set ``FLEXMEASURES_API_SUNSET_ACTIVE=True`` to test the full effect now. * Allow testing out the scheduling CLI without saving anything, using ``flexmeasures add schedule --dry-run`` [see `PR #1892 `_] * Allow unsupported ``flex-context`` or ``flex-model`` fields to be shown in the UI editors (they will be un-editable) [see `PR #1915 `_] * Add back save buttons to both ``flex-context`` and ``flex-model`` UI editors [see `PR #1916 `_] * Add a documentation section on the concept of ``Commitments`` [see `PR #1849 `_] * Add resolution column to sensors list on asset context page [see `PR #1986 `_] Infrastructure / Support ---------------------- * Upgraded dependencies [see `PR #1847 `_] * End support for Python3.9 [see `PR #1965 `_] * Improve general description on SwaggerDocs page and add three settings for hosts: FLEXMEASURES_SUPPORT_PAGE, FLEXMEASURES_SIGNUP_PAGE and FLEXMEASURES_TOS_PAGE [see `PR #1851 `_ and `PR #1889 `_] * Allow plugins to register forecasters [see `PR #1863 `_] * Support setting a ``custom-scheduler`` by name [see `PR #1924 `_] * Allow plugin schedulers to skip saving any sensor data, while still making their results retrievable [see `PR #1933 `_] * Migrated JSON fields to JSONB, so they can be used to look up sensors, attributes, sources [see `PR #1867 `_] * Use ``flexmeasures jobs stats`` to show statistics of the job queueing system [see `PR #1838 `_] * Less verbose error logs given common HTTP requests such as those leading to 404 (Not Found) responses [see `PR #1883 `_] * Refactor base.html template from 1500 to ~300 lines [see `PR #1868 `_] * 2FA UX: Hide rescue form by default & improve main message [see `PR #1875 `_] * Add extra security layer to check for breached passwords [see `PR #1919 `_] * Support and document data container in docker compose stack better [see `PR #1790 `_] * Improve reported test coverage by including doctests and bringing back CLI tests to GitHub Actions [see `PR #1914 `_ and `PR #778 `_, respectively] * Add DEFAULT_DATASOURCE_TYPES and use it in CLI and status page [see `PR #1938 `_] * Fix README badges [see `PR #1913 `_] * Allow seeing complete datetimes in the audit log [see `PR #1949 `_] * Add latest dependabot alert suggestions [see `PR #1959 `_] * Add standardized GitHub Copilot agent environment setup file for consistent development environment across agent sessions [see `PR #1962 `_, `PR #1963 `_ and `PR #1964 `_] Bugfixes ----------- * Fix: schedules are no longer saved upside down [see `PR #1348 `_] * Fix: visiting the job page for any forecasting job led to a server error ("Object of type datetime is not JSON serializable"), by storing serialized kwargs in forecasting job meta [see `PR #1990 `_] * Fix: flex-context dialogue is empty when flex-context has two booleans with the same value [see `PR #1907 `_] * Bring back the ability to show (timed) annotations on the sensor page, and add some color highlighting, too, while we're at it [see `PR #1967 `_] * Fixed toast notification display on the sensor detail upload form [see `PR #1921 `_] * Fix: return validation errors instead of database errors for API/CLI fields that map to database objects [see `PR #1923 `_] * Correct field documentation for flex-config fields that strictly allow sensor references [see `PR #1951 `_] * Have the ``StorageScheduler`` correctly combine multiple sessions targeting the same sensor [see `PR #1948 `_] * Mutate job state when running ``flexmeasures jobs run-job `` [see `PR #1929 `_ and `PR #1930 `_] * Prevent inplace operation when using ``simplify_index`` [see `PR #1931 `_] * Fix API tests failing with 401 UNAUTHORIZED when run in isolation by properly setting Flask-Security's ``fs_authn_via`` attribute in the ``requesting_user`` fixture [see `PR #1960 `_] * Fix ReadTheDocs build pipeline [see `PR #1972 `_] v0.30.3 | January 12, 2026 ============================ Bugfixes ----------- * Fix graphs & KPI data failing to load when daily KPIs are configured for the asset [see `PR #1909 `_] * Fix ``delete-beliefs`` CLI command to correctly apply the ``--source`` filter when deleting beliefs, preventing unintended removal of beliefs from other sources [see `PR #1903 `_] * Fix concatenation of DataFrames with mixed-order index level when dropping unchanged beliefs, which could cause saving data to fail in rare cases of running ``flexmeasures add report`` [see `PR #1905 `_] v0.30.2 | January 6, 2026 ============================ Bugfixes ----------- * Make ``soc-usage`` & ``soc-gain`` fields editable again in the UI [see `PR #1860 `_] * New sensors created through the API and UI get the server timezone rather than :abbr:`UTC (Coordinated Universal Time)` [see `PR #1894 `_] * Correctly derive the shared unit in charts showing multiple temperature sensors [see `PR #1890 `_] * Prevent duplicate forecasts from being saved when re-running the forecasting pipeline within the same resolution window by preserving the non-floored ``belief_time`` using a new ``save_belief_time`` field [see `PR #1853 `_] * Keep around finished forecasting jobs just as long as finished scheduling jobs (configurable through the ``FLEXMEASURES_PLANNING_TTL`` config setting) [see `PR #1870 `_] v0.30.1 | December 9, 2025 ============================ Bugfixes ----------- * Greatly reduce the number of various deprecation warnings when dealing with time series data [see `PR #1858 `_] v0.30.0 | December 2, 2025 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. warning:: If you make use of ``flexmeasures add report`` with the ``--start-offset`` and/or ``--end-offset`` options (for instance, in a cron job), please check whether the report period logged by the CLI command still fits your use case. Your offsets may need to be adjusted in relation to your ``FLEXMEASURES_TIMEZONE`` config setting (its offset with respect to :abbr:`UTC (Coordinated Universal Time)`). .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``) and ``flexmeasures add initial-structure``. New features ------------- * Improve ``flexmeasures add forecasts`` CLI command with clearer success and error messages when creating jobs or beliefs [see `PR #1822 `_] * Major overhaul of ``flexmeasures add forecasts`` (use the ``--help`` option to learn more) [see `PR #1546 `_, `PR #1744 `_ and `PR #1834 `_] * The new ``commitments`` field in the ``flex-context`` can be used to specify previous commitments (e.g. market positions) that the scheduler needs to take into account [see `PR #1754 `_ and `PR #1793 `_] * Many more field descriptions in Swagger, including flex-model and flex-context fields [see `PR #1777 `_ and `PR #1841 `_] * Maps auto-zoom to cover the asset portfolio visible to the user, with fresh users prompted to pan to their own location when adding their first asset [see `PR #1644 `_] * Sticky replay button for asset and sensor pages [see `PR #1739 `_] * The ``flexmeasures delete beliefs``, ``flexmeasures delete nan-beliefs`` and ``flexmeasures delete unchanged-beliefs`` CLI commands now support limiting the action to a given set of data sources [see `PR #1770 `_] * Let consultants see client assets on dashboard and group by account [see `PR #1763 `_] * More explicitly represent the unit of sensors that record dimensionless data [see `PR #1802 `_] * Allow modifying asset trees with the CLI using ``flexmeasures edit transfer-parenthood`` [see `PR #1773 `_] * Expanded the sorting columns of "latest jobs" table [see `PR #1821 `_] * Let users specify the unit, which uploaded data is based on [see `PR #1836 `_] * Allow to keep legend combined below graphs, even with many plots (useful on narrow screens) [see `PR #1816 `_] Infrastructure / Support ---------------------- * Upgraded dependencies [see `PR #1752 `_, `PR #1820 `_ and `PR #1842 `_] * Speed up data searches by refactoring our filter for selecting data from the latest version of a data generating model [see `PR #1698 `_] * Add new tutorial for PV curtailment and multi-asset scheduling [see `PR #1804 `_ and `PR #1846 `_] * Drop need for .env file in favour of more adaptation of flexmeasures.cfg config file [see `PR #1759 `_] * Support saving beliefs with a ``belief_horizon`` in the ``AggregatorReporter`` [see `PR #1735 `_] * Support skipping a ``PandasReporter`` transformation if any of its (keyword) arguments has no data [see `PR #1669 `_] * Assets now have an `external_id` field so data from external sources can be linked to the right FlexMeasures asset in custom integrations [see `PR #1774 `_ and `PR #1806 `_] * Save buttons in UI editors (flex-model, flex-context and data dashboards) [see `PR #1764 `_] * Improve performance of the endpoint profiler and support configuration using the new ``FLEXMEASURES_PROFILER_CONFIG`` setting [see `PR #1799 `_] * Use ``SimpleWorker`` instead of fork-based ``Worker`` on macOS to prevent segmentation faults when running ``flexmeasures jobs run-worker`` for development purposes on macOS [see `PR #1818 `_] * Move flex model UI schema to server side [see `PR #1830 `_] * Fewer version details in OpenAPI specs, to make pre-commit step complain less [see `PR #1845 `_] Bugfixes ----------- * Fix unit conversion when scheduling a storage asset that deals with power sensors recording data in kWh units [see `PR #1784 `_] * Fix interpretation of ``--start-offset`` and ``--end-offset`` options in ``flexmeasures add report`` [see `PR #1758 `_] * Let users search for flex context sensors on whole site tree again [see `PR #1826 `_] * Fix unintended date range hopping, a UI bug where date ranges set in URL parameters would be overridden by the user's previously selected date range (a session variable) [see `PR #1821 `_] * Fix off-center map markers [see `PR #1840 `_] * Resolved a crash in the "latest jobs" table when sorting was applied, and corrected a typo in the Jobs API Swagger UI documentation [see `PR #1821 `_] * Enhance dates on UI(sensor page) to be human friendly when representing future dates [see `PR #1832 `_] * Fix spinner not disappearing on the asset graph page [see `PR #1831 `_] * Fix links to API endpoint docs in Sphinx documentation [see `PR #1843 `_] v0.29.1 | November 5, 2025 ============================ Bugfixes ----------- * Support different but still compatible units in time series segments of variable quantities [see `PR #1792 `_] * Fix account and `/assets/owned_by` pages rendering, giving them asset icons [see `PR #1772 `_] * Fix bug when sending one sensor in flex-model when triggering schedule on asset [see `PR #1795 `_] * Allow consultants to view client users [see `PR #1755 `_] * Fix bug where removed flex-model fields don't show up under the dropdown for new fields, except after a page refresh [see `PR #1775 `_] * Fix bug in displaying user audit log (incl. expanding its API schema) [see `PR #1779 `_] * Support flex-context prices with SI-prefixed currencies (e.g. kEUR) [see `PR #1844 `_] v0.29.0 | October 14, 2025 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ------------- * Added a UI editor (form modal) to edit an asset's flex-model [see `PR #1429 `_ and `PR #1565 `_] * New CLI command for scheduling, with full flex-context and flex-model support as well as the option to set your scheduler class [see `PR #1713 `_] * Full coverage of flex-context fields in the UI editor [see `PR #1689 `_] * Touch up the KPI cards [see `PR #1731 `_] * Touch up asset context page [see `PR #1732 `_] * Allow ``PandasReporter`` configurations to skip a transformation in case any of the transformation ``args`` or ``kwargs`` is missing all data [see `PR #1717 `_] * The ``flexmeasures delete unchanged-beliefs`` CLI command now supports limiting the action to a given period [see `PR #1720 `_] Infrastructure / Support ---------------------- * Migrate data for the ``flex-model`` of an asset to a dedicated column in the database table for assets [see `PR #1429 `_] * Updated dependencies [see `PR #1707 `_] * Upgraded Docker Image Ubuntu 24, which uses Python 3.12 [see `PR #1723 `_] * Include finished and canceled jobs in the overview printed by the CLI command ``flexmeasures jobs show-queues`` [see `PR #1712 `_] * Improved flex-context modal UI and UI-backend functionalities&structure [see `PR #1704 `_] * Removed the use of ``consumption_price_sensor`` from the ``ProcessScheduler`` and replaced with now mandatory ``consumption_price`` in the ``flex-context`` [see `PR #1729 `_] * Removed obsolete UI view [see `PR #1743 `_] Bugfixes ----------- * Changed 422 response for asset PATCH endpoint to the format also used elsewhere [see `PR #1722 `_] * Fix UI flex-context editor for flex-contexts with boolean fields (that were set through the API) [see `PR #1733 `_] * Fix floating spinner on asset graphs page [see `PR #1738 `_] * Make monitoring tasks & users robust against db issues [see `PR #1715 `_] v0.28.2 | October 3, 2025 ============================ Bugfixes ----------- * Fix horizons in UI chart tooltips [see `PR #1730 `_] * Fix UI chart for Charge Point sessions [see `PR #1699 `_] * Fix two audit logs in the sensor API, which were not committed to db [see `PR #1721 `_] v0.28.1 | September 18, 2025 ============================ Bugfixes ----------- * Fix schema validation in ``PATCH /assets/(id)`` [see `PR #1711 `_] * Fixed example values for peak pricing and improved error message for incompatible price units set in the ``flex-context`` [see `PR #1710 `_] v0.28.0 | September 10, 2025 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). This upgrade may take a few minutes, depending on how much time series data you have in your database (the data will be reindexed). New features ------------- * Display KPIs for asset sensors with daily event resolution [see `PR #1608 `_, `PR #1634 `_ and `PR #1656 `_] * Ability to add users via API (POST /users) and in the UI (from an account page) [See `PR #1678 `_] * Improved timestamp on sensor detail page to be more friendly [see `PR #1632 `_] * Asset types support: new API endpoint (`GET /assets/types`), better docs and fix CLI command ``flexmeasures show asset-types`` [see `PR #1663 `_] * Add ``--combine-legend`` option to flexmeasures show chart. When used, all legends are combined and displayed at the bottom of the chart. If not used (default = False), each chart will display its own separate legend (as on the asset page) [see `PR #1696 `_] * Add support for using Swagger to generate API documentation [see `PR #1703 `_] Infrastructure / Support ---------------------- * Upgraded dependencies [see `PR #1616 `_, `PR #1672 `_, `PR #1668 `_ and `PR #1690 `_] * Removed support for Python3.8 [see `PR #1615 `_] * Better support for using ``Sensor`` objects as dictionary keys [see `PR #1650 `_] * Removed obsolete API blueprint for play mode and underlying backup file-based functionality [see `PR #1622 `_ and `PR #1630 `_] * Faster data loading for the UI by vectorization of dictionary representations of sources and sensors, and of epoch conversion [see `PR #1641 `_] * Refactor: Remove clunky calls to the API from within the UI view code [see `PR #1683 `_] * Compress chart data sent to the UI charts [see `PR #1645 `_ and `PR #1691 `_] * Better representation of changes in JSON structures in audit logs [see `PR #1700 `_] Bugfixes ----------- * Fixed usage of slow query for status page [see `PR #1638 `_] * Fix editing of public assets in the UI [see `PR #1636 `_] * Fix issue with :abbr:`DST (Daylight Saving Time)` transitions when processing variable quantities using the time series specification format, in flex-contexts and/or flex-models [see `PR #1681 `_] * Add audit log entries when creating sensors, assets and accounts via the CLI [see `PR #1623 `_] v0.27.4 | August 27, 2025 ============================ Bugfixes ----------- * Fix ``flexmeasures show reporters`` and ``flexmeasures show schedulers`` [see `PR #1674 `_] * Show job information again on the job page on rq-dashboard, for scheduling jobs that set a specific ``belief_time`` and/or ``resolution`` [see `PR #1670 `_] v0.27.3 | August 19, 2025 ============================ Bugfixes ----------- * Fix the time window in the UI from being replaced with :abbr:`NaN (not a number)` values when refreshing the asset graphs page [see `PR #1667 `_] * Fix scheduling storage devices within a single time step [see `PR #1619 `_] v0.27.2 | August 13, 2025 ============================ Bugfixes ----------- * Resolve issue where concatenating sensor data from updated reporters leads to a :abbr:`NaN (not a number)` source and crashing the asset graphs page [see `PR #1660 `_] Infrastructure / Support ---------------------- * Faster data loading for the UI by caching dictionary representations of sources and sensors [see `PR #1647 `_] * Modify a query to speed up a data availability check for forecasting [see `PR #1658 `_] v0.27.1 | August 11, 2025 ============================ Bugfixes ----------- * Flex-context price sensors can have any shared unit [see `PR #1628 `_] * Fix a few UI grievances in asset creation, esp. child assets [see `PR #1629 `_] * Fix updating the URL query parameters upon date selection in the UI of servers in play mode [see `PR #1649 `_] Infrastructure / Support ---------------------- * Automate release process to PyPI [see `PR #1657 `_] v0.27.0 | July 20, 2025 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. note:: Preparatory warning: The following release will not support Python 3.8 anymore. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ------------- * New API endpoint `[POST] /assets/(id)/schedules/trigger `_ to schedule a site with multiple flexible devices [see `PR #1065 `_] * Add form to upload sensor data to the database [see `PR #1481 `_, `PR #1573 `_, `PR #1583 `_, `PR #1585 `_, `PR #1588 `_ and `PR #1590 `_] * Improved the UX for creating child-assets and sensors in the UI [see `PR #1605 `_] * Added :abbr:`2FA (two-factor authentication)` support for email and one time recovery, and also added ``_macros.html`` for UI components [see `PR #1555 `_, `PR #1564 `_ and `PR #1562 `_] * Give consultants more permissions, so they can edit their client's accounts, assets and sensors. Also add test cases to check if these permissions work as expected [see `PR #1539 `_ and `PR #1550 `_] * Allow editing users in the UI [see `PR #1502 `_] * Scheduling job descriptions on the tasks page (RQ Dashboard) shows the whole flex-model and flex-context, including any server-side configuration of e.g. capacities [see `PR #1579 `_ and `PR #1601 `_] * Smarter date range navigation [see `PR #1531 `_] * Smarter toast notifications [see `PR #1530 `_] * Move various warnings to toast notifications [see `PR #1529 `_] * Document how to set a parent asset when creating an asset through the API, and show parent assets in ``flexmeasures show account`` [see `PR #1533 `_ and `PR #974 `_] * Add ``flexmeasures show assets`` CLI command for listing public assets and option ``--account `` to list assets owned by a specific account [see `PR #1536 `_] * Add ``flexmeasures jobs run-job`` CLI command to run a single job [see `PR #1602 `_] * Add toggle to show sensor statistics based on selected date range [see `PR #1535 `_, `PR #1543 `_ and `PR #1589 `_] * Scale sensor data to the lowest unit on graphs with multiple sensors and same dimension [see `PR #1534 `_ and `PR #1544 `_] * Group statistics on the UI's sensor page by data source ID, and show the description and ID of each data source [see `PR #1548 `_] Infrastructure / Support ---------------------- * Upgraded dependencies [see `PR #1450 `_, `PR #1527 `_, `PR #1532 `_, `PR #1567 `_, `PR #1611 `_ and `PR #1613 `_] * Improved authorization checks for modifying roles [see `PR #1517 `_] * In authorization, prevent accidental errors by not matching empty principals [see `PR #1556 `_] * Tests: guarantee a clean db upon creating the test db [see `PR #1518 `_] * Stopped testing Python3.8 in our GitHub Actions CI [see `PR #1541 `_] * Stopped auto-deploying to Seita's staging server on commits to main. Kept scripts and documentation how to do it. Added short description of the two existing CI workflows [see `PR #1552 `_] * Explain white-labeling in documentation [see `PR #1587 `_] * Changed example ``docker-compose.yaml`` to persist database on local volume [see `PR #1584 `_] Bugfixes ----------- * Prevent redundant second call to fetch chart data on page load and start replay button [see `PR #1586 `_ and `PR #1596 `_] * On the asset context page, send the highest ancestor as site_asset (then the asset context view uses this to look up sensors for the flex-context) [see `PR #1581 `_] * Fix support for using 3-digit hex colors in account color scheme [see `PR #1569 `_] * Fix deletion of sensors in the UI, also move the delete button for assets & sensors to the bottom of the page [see `PR #1597 `_] v0.26.1 | June 9, 2025 ============================ Bugfixes ----------- * Fixed backwards compatibility for users still using deprecated flex-context fields [see `PR #1528 `_] * Show job information again on the job page on rq-dashboard [see `PR #1526 `_] v0.26.0 | June 3, 2025 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ------------- * Support saving the scheduled :abbr:`SoC (state of charge)` by referencing an appropriate sensor in the ``flex-model`` field ``state-of-charge`` [see `PR #1392 `_ and `PR #1406 `_] * Allow relaxing :abbr:`SoC (state of charge)` minima and maxima, by setting penalties for not meeting these constraints, using two new ``flex-context`` fields [see `PR #1300 `_] * Allow relaxing device-level power constraints, by setting penalties for not meeting these constraints, using two new ``flex-context`` fields [see `PR #1405 `_] * Add flex-context fields to toggle on/off relaxation of various constraints [see `PR #1511 `_] * Add sensor attribute (``frequency``) to align incoming measurements to a specified time interval [see `PR #1461 `_] * Save changes in asset flex-context form right away [see `PR #1390 `_] * Extending sensor CRUD functionality to the UI [see `PR #1394 `_ and `PR #1413 `_] * Marker clusters on the dashboard map expand in a tree to show the hierarchical relationship of the assets they represent [see `PR #1410 `_] * Load the sensors individually on the Sensors status page. Reload the jobs table using Ajax calls. Improve page performance and avoid timeouts [see `PR #1425 `_ and `PR #1466 `_] * New pages for `Properties`, `Graphs`, `Context`, `Status` and `Audit Log`. Simplified the main asset page [see `PR #1416 `_, `PR #1387 `_, `PR #1442 `_, `PR #1470 `_, `PR #1473 `_, `PR #1478 `_, `PR #1480`_ and `PR #1482 `_] * Only show important sensors statuses (flex-context and graph sensors) on the status page [see `PR #1439 `_] * Let the user interact with the breadcrumbs on asset graphs page when the graphs are loading [see `PR #1472 `_] * Added DB migrations to apply server defaults to ``generic_asset`` and ``data_sources`` tables [see `PR #1488 `_] * Show visually distinct siblings and children in the assets dropdown [see `PR #1504 `_] * Add resolution back to the CLI belief plotting [see `PR #1500 `_] * Improved permission validation for user role updates [see `PR #1465 `_] * Statistics shown in the UI default to that of the freshest source [see `PR #1399 `_] Infrastructure / Support ---------------------- * Move to using a ``pyproject.toml`` [see `PR #1419 `_] * Upgraded dependencies [see `PR #1400 `_, `PR #1444 `_, `PR #1448 `_, `PR #1484 `_, `PR #1490 `_ and `PR #1497 `_] * Save last N jobs from any queue and registry to a file, and support filtering by asset ID or sensor ID [see `PR #1411 `_] * Prevent accidentally still logging a warning in case a reporter already stopped using the ``use_latest_version_only`` argument [see `PR #1510 `_] * Describe four supported user roles explicitly (docs and code) [see `PR #1451 `_] * Updated the directory structure for crud operations for assets, sensors, users and accounts [see `PR #1467 `_ and `PR #1471 `_] * Docs: Add tutorial scripts [see `PR #1505 `_] * Docs: fix graphs page for assets in toy tutorial, display plotted sensors when CLI shows asset info [see `PR #1501 `_] Bugfixes ----------- * Fixed two alternatives for expressing a variable quantity as a time series; specifically, those involving the ``duration`` field [see `PR #1433 `_] * Fix the preference to delay curtailment of any device [see `PR #1498 `_ and `PR #1499 `_] * The data dashboard now supports overlapping sensors with instantaneous and non-instantaneous resolutions [see `PR #1407 `_] * Fix map not loading when editing an asset [see `PR #1414 `_] * Fix ``flexmeasures add schedule for-storage`` after flex-context database migration [see `PR #1417 `_ and `PR #1449 `_] * Fix overriding of flex-context when asset is edited on the UI [see `PR #1469 `_] * Support entering audit log entries by detached user instances [see `PR #1483 `_] * Make flex context usage safer against this field being `None` [see `PR #1503 `_] v0.25.0 | April 1, 2025 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ------------- * Added a UI editor (form modal) to edit an asset's flex-context [see `PR #1320 `_, `PR #1365 `_ and `PR #1364 `_] * Improve asset status page - distinguish better by data source type [see `PR #1022 `_] * Better y-axis titles for charts that show multiple sensors with a shared unit [see `PR #1346 `_] * Add CLI command ``flexmeasures jobs save-last-failed`` (since v0.26: ``flexmeasures jobs save-last``) for saving the last failed jobs [see `PR #1342 `_ and `PR #1359 `_] * Add CLI command ``flexmeasures jobs delete-queue`` for deleting an obsolete queue [see `PR #1351 `_] Infrastructure / Support ---------------------- * Support multi-asset scheduling in the ``StorageScheduler`` and job queueing - functionality for (plugin) developers (incl. prep work for future API endpoint for multi-asset scheduling) [see `PR #1313 `_] * Support PV curtailment in the ``StorageScheduler`` [see `PR #1395 `_] * Validate shared units are used in time series segments of flex-context prices [see `PR #1396 `_] * Migrate data for the ``flex-context`` of an asset to a dedicated column in the database table for assets [see `PR #1293 `_, `PR #1354 `_ and `PR #1380 `_] * Enhance reporting infrastructure by ensuring that all ``Sensor.search_beliefs`` filters can be used as report parameters [see `PR #1318 `_] * Improve searching for multi-sourced data by returning data from only the latest version of a data generator (e.g. forecaster or scheduler) by default, when using ``Sensor.search_beliefs`` [see `PR #1306 `_] * Extra reporter tests [see `PR #1317 `_] * Catch invalid time windows passed to ``flexmeasures add report`` [see `PR #1324 `_] * Test utility function for device scheduling in a multi-asset setting (sequential and simultaneous) [see `PR #1341 `_] * Add utils doctests to our CI pipeline [see `PR #1347 `_] * Clarify default limitations to concurrent connections [see `PR #1391 `_] v0.24.1 | February 27, 2025 ============================ Infrastructure / Support ---------------------- * Update cache and Ubuntu versions used for testing in GitHub Actions [see `PR #1329 `_] Bugfixes ----------- * Fix map not loading when editing an asset [see `PR #1310 `_] * Add missing support for fallback attribute for the ``soc-usage`` and ``soc-gain`` fields of the ``flex-model`` [see `PR #1340 `_] v0.24.0 | January 7, 2025 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ------------- * Allow scheduling against energy contracts, capacity contracts and peak contracts simultaneously, using various new ``flex-context`` fields [see `PR #1144 `_] * Allow using numeric values for ``flex-model`` fields accepting dimensionless quantities [see `PR #1144 `_] * The data chart on the asset page splits up its color-coded sensor legend when showing more than 7 sensors, becoming a legend per subplot [see `PR #1176 `_ and `PR #1193 `_] * Speed up loading the users page, by making the pagination backend-based and adding support for that in the API [see `PR #1160 `_] * X-axis labels in CLI plots show datetime values in a readable and informative format [see `PR #1172 `_] * Enhanced API for listing sensors: Added filtering and pagination on sensor index endpoint and created new endpoint to get all sensors under an asset [see `PR #1191 `_ and `PR #1219 `_] * Speed up loading the accounts page by making the pagination backend-based and adding support for that in the API [see `PR #1196 `_] * Speed up loading the account detail page by by switching to server-side pagination for assets, replacing client-side pagination [see `PR #1202 `_] * Added form to edit an asset's sensors_to_show data directly from the UI [see `PR #1212 `_] * Speed up loading on audit log tables page by switching to server-side pagination, replacing client-side pagination [see `PR #1274 `_ and `PR #1272 `_] * Simplify and globalize UI messages, using Toast [see `PR #1207 `_] * Power sensors created through the CLI no longer require a capacity attribute to be set [see `PR #1234 `_] Infrastructure / Support ---------------------- * The breadcrumbs on asset and sensor pages can now be customized [see `PR #1257 `_] * The monitoring command to check for users who have been absent too long now can be used to keep data volume low and be more effective [see `PR #1268 `_] * Speed up status page by choosing for a faster query (only latest belief needed) [see `PR #1142 `_] * Speed up user page (for users with many assets) [see `PR #1286 `_] * For MacOS developers, install HiGHS solver automatically [see `PR #1187 `_] * Migrate data for the ``sensors_to_show`` asset attribute to a dedicated column in the database table for assets [see `PR #1200 `_ and `PR #1282 `_] * Add support for installing FlexMeasures under Python 3.12 [see `PR #1233 `_] * Better error handling in UI, for example, in case of a forgotten ``flexmeasures db upgrade`` [see `PR #1302 `_] Bugfixes ----------- * Fix table sorting on the assets, accounts and users page (regression from `PR #988 `_) [see `PR #1239 `_, `PR #1242 `_, `PR #1248 `_, `PR #1247 `_ and `PR #1272 `_] * Fix ``flexmeasures delete measurements`` and ``flexmeasures delete prognoses`` which had an error in counting affected rows after SQLAlchemy2.0 upgrade [see `PR #1095 `_ and `PR #1303 `_] * Fix asset count on the user page, which showed 0 assets after (de)activating a user or resetting their password [see `PR #1251 `_] * The UI footer now stays at the bottom even on pages with little content [see `PR #1204 `_] * Correct stroke dash (based on source type) for forecasts made by forecasters included in FlexMeasures [see `PR #1211 `_] * Show the correct :abbr:`UTC (Coordinated Universal Time)` offset for the data's time span as shown under sensor stats in the UI [see `PR #1213 `_] * Fixed issue where audit log buttons are visible to users without the necessary permissions [see `PR #1228 `_] * Fix issue with displaying ``deactivate user`` and ``reset password`` buttons for non admin users [see `PR #1220 `_] * Resolve overlapping time series segments in several flex-model and flex-context fields in a way befitting their nature [see `PR #1223 `_] v0.23.2 | December 16, 2024 ============================ Bugfixes ----------- * Correct source filters on reporter input, and support piping additional transformations in the ``PandasReporter`` [see `PR #1284 `_] v0.23.1 | November 12, 2024 ============================ Bugfixes ----------- * Correct unit conversion of reporter output to output sensor [see `PR #1238 `_] v0.23.0 | September 18, 2024 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ------------- * New chart type on sensor page: histogram [see `PR #1143 `_] * Add basic sensor info to sensor page [see `PR #1115 `_] * Add `Statistics` table on the sensor page and also add `api/v3_0/sensors//stats` endpoint to get sensor statistics [see `PR #1116 `_] * Support adding custom titles to the graphs on the asset page, by extending the ``sensors_to_show`` format [see `PR #1125 `_ and `PR #1177 `_] * Support zoom-in action on the asset and sensor charts [see `PR #1130 `_] * Speed up loading the assets page, by making the pagination backend-based and adding support for that in the API, and by enabling to query all accounts one can see in a single call (for admins and consultants) [see `PR #988 `_] * Added Primary and Secondary colors to account for white-labelled UI themes [see `PR #1137 `_] * Added Logo URL to account for white-labelled UI themes [see `PR #1145 `_] * Added PopUp form to edit account details [see `PR #1152 `_] * When listing past jobs on the `Tasks` page, show the most recent jobs first [see `PR #1163 `_] * Introduce the ``VariableQuantityField`` to allow three ways of passing a variable quantity in most of the ``flex-model`` and ``flex-context`` fields [see `PR #1127 `_ and `PR #1138 `_] * Support directly passing a fixed price in the ``flex-context`` using the new fields ``consumption-price`` and ``production-price``, which are meant to replace the ``consumption-price-sensor`` and ``production-price-sensor`` fields, respectively [see `PR #1028 `_] Infrastructure / Support ---------------------- * Save beliefs faster by bulk saving [see `PR #1159 `_] * Support new single-belief fast track (looking up only one belief) [see `PR #1067 `_] * Add new annotation types: ``"error"`` and ``"warning"`` [see `PR #1131 `_ and `PR #1150 `_] * When deleting a sensor, asset or account, delete any annotations that belong to them [see `PR #1151 `_] * Removed deprecated ``app.schedulers`` and ``app.forecasters`` (use ``app.data_generators["scheduler"]`` and ``app.data_generators["forecaster"]`` instead) [see `PR #1098 `_] * Introduced dynamic, JavaScript-generated toast notifications [see `PR #1152 `_] Bugfixes ----------- * Fix string length exceeding the 255-character limit in the `event` field of `AssetAuditLog` by truncating long updates and logging each field or attribute change individually [see `PR #1162 `_] * Fix image carousel on the login page [see `PR #1154 `_] * Fix styling for User and Documentation menu items [see `PR #1140 `_] * Fix styling of sensor page, especially the graph chart dropdown [see `PR #1148 `_] * Fix posting a single instantaneous belief [see `PR #1129 `_] * Allow reassigning a public asset to private ownership using the ``flexmeasures edit transfer-ownership`` CLI command [see `PR #1123 `_] * Fix missing value on spring :abbr:`DST (Daylight Saving Time)` transition for ``PandasReporter`` using daily sensor as input [see `PR #1122 `_] * Fix date range persistence on session across different pages [see `PR #1165 `_] * Fix issue with account creation failing when the ``--logo-url`` option is omitted [see related PRs `PR #1167 `_ and `PR #1145 `_] * Fix ordering of audit logs (asset, account) and job list on status page [see `PR #1179 _` and `PR #1183 `_] v0.22.0 | June 29, 2024 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. New features ------------- * Add `/asset//auditlog` to view asset related actions [see `PR #1067 `_] * On the `/sensor/id` page, allow to link to it with a date range and to copy current view as URL [see `PR #1094 `_] * Flex-context (price sensors and inflexible device sensors) can now be set on the asset page (and are part of GenericAsset model) [see `PR #1059 `_] * On the asset page's default view, facilitate comparison by showing the two default sensors together if they record the same unit [see `PR #1066 `_] * Add flex-context sensors to status page [see `PR #1102 `_] * Show tooltips on (mobile) touch screen [see `PR #1062 `_] Infrastructure / Support ---------------------- * Add MailHog to docker-compose stack for testing email functionality [see `PR #1112 `_] * Allow installing dependencies in docker-compose worker [see `PR #1057 `_] * Add unit conversion to the input and output data of the ``PandasReporter`` [see `PR #1044 `_] * Add option ``droplevels`` to the ``PandasReporter`` to drop all the levels except the ``event_start`` and ``event_value`` [see `PR #1043 `_] * ``PandasReporter`` accepts the parameter ``use_latest_version_only`` to filter input data [see `PR #1045 `_] * ``flexmeasures show beliefs`` uses the entity path (`/../`) in case of duplicated sensors [see `PR #1026 `_] * Add ``--resolution`` option to ``flexmeasures show chart`` to produce charts in different time resolutions [see `PR #1007 `_] * Add ``FLEXMEASURES_JSON_COMPACT`` config setting and deprecate ``JSONIFY_PRETTYPRINT_REGULAR`` setting [see `PR #1090 `_] Bugfixes ----------- * Fix ordering of jobs on the asset status page [see `PR #1106 `_] * Relax max staleness for status page using 2 * event_resolution as default instead of immediate staleness [see `PR #1108 `_] v0.21.0 | May 16, 2024 ============================ .. note:: Read more on these features on `the FlexMeasures blog `_. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ------------- * Add `/asset//status` page to view asset statuses [see `PR #941 `_ and `PR #1035 `_] * Add `/account//auditlog` and `/user//auditlog` to view user and account related actions [see `PR #1042 `_] * Support ``start_date`` and ``end_date`` query parameters for the asset page [see `PR #1030 `_] * In plots, add the asset name to the title of the tooltip to improve the identification of the lines [see `PR #1054 `_] * On asset page, show sensor IDs in sensor table [see `PR #1053 `_] Bugfixes ----------- * Prevent the time window in the UI from moving to the latest data when refreshing the asset page [see `PR #1046 `_ and `PR #1056 `_] Infrastructure / Support ---------------------- * Include started, deferred and scheduled jobs in the overview printed by the CLI command ``flexmeasures jobs show-queues`` [see `PR #1036 `_] * Make it as convenient to clear deferred or scheduled jobs from a queue as it was to clear failed jobs from a queue [see `PR #1037 `_] v0.20.1 | May 7, 2024 ============================ Bugfixes ----------- * Prevent **p**\ lay/**p**\ ause/**s**\ top of replays when editing a text field in the UI [see `PR #1024 `_] * Skip unit conversion of :abbr:`SoC (state of charge)` related fields that are defined as sensors in a ``flex-model`` (specifically, ``soc-maxima``, ``soc-minima`` and ``soc-targets`` [see `PR #1047 `_] v0.20.0 | March 26, 2024 ============================ .. note:: Read more on these features on `the FlexMeasures blog `__. .. warning:: From this version on, the config setting ``FLEXMEASURES_FORCE_HTTPS`` decides whether to enforce HTTPS on requests - and it defaults to ``False``. Previously, this was governed by ``FLASK_ENV`` or ``FLEXMEASURES_ENV`` being set to something else than ``"documentation"`` or ``"development"``. This new way is more clear, but you might be in need of using this setting before upgrading. New features ------------- * Add command ``flexmeasures edit transfer-ownership`` to transfer the ownership of an asset and its children from one account to another [see `PR #983 `_] * Support defining the ``site-power-capacity``, ``site-consumption-capacity`` and ``site-production-capacity`` as a sensor in the API and CLI [see `PR #985 `_] * Support defining the ``soc-minima``, ``soc-maxima`` and ``soc-targets`` as sensors in the API [see `PR #996 `_] * Support defining inflexible power sensors with arbitrary power and energy units [see `PR #1007 `_] * Support saving beliefs with a ``belief_horizon`` in the ``PandasReporter`` [see `PR #1013 `_] * Skip the check of the output event resolution in any ``Reporter`` with the field ``check_output_resolution`` [see `PR #1009 `_] Bugfixes ----------- * Use minimum event resolution of the input (instead of the output) sensors for the belief search parameters [see `PR #1010 `_] Infrastructure / Support ---------------------- * Align map layers with custom asset types in the UI's dashboard, also facilitating capturing asset types defined within FlexMeasures plugins [see `PR #1017 `_] * Improve processing time for deleting beliefs via CLI [see `PR #1005 `_] * Support deleting beliefs via CLI for all offspring assets at once [see `PR #1003 `_] * Add setting ``FLEXMEASURES_FORCE_HTTPS`` to explicitly toggle if HTTPS should be used for all requests [see `PR #1008 `_] * Make flexmeasures installable locally on macOS [see `PR #1000 `_] * Align API endpoint policy w.r.t. trailing slash [see `PR #1014 `_] v0.19.2 | March 1, 2024 ============================ .. note:: Optionally, run ``flexmeasures db upgrade`` after upgrading to this version for enhanced database performance on time series queries. * Upgrade timely-beliefs to enhance our main time series query and fix a database index on time series data, leading to significantly better performance [see `PR #992 `_] * Fix server error on loading the asset page for a public asset, due to a bug in the breadcrumb's sibling navigation [see `PR #991 `_] * Restore compatibility with the `flexmeasures-openweathermap plugin `_ by fixing the query for the closest weather sensor to a given asset [see `PR #997 `_] v0.19.1 | February 26, 2024 ============================ * Support defining the ``power-capacity`` as a sensor in the API and CLI [see `PR #987 `_] v0.19.0 | February 18, 2024 ============================ .. note:: Read more on these features on `the FlexMeasures blog `__. .. warning:: This version replaces ``FLASK_ENV`` with ``FLEXMEASURES_ENV`` (``FLASK_ENV`` will still be used as a fallback). New features ------------- * List child assets on the asset page [see `PR #967 `_] * Expand the UI's breadcrumb functionality with the ability to navigate directly to sibling assets and sensors using their child-parent relationship [see `PR #977 `_] * Enable the use of QuantityOrSensor fields for the ``flexmeasures add schedule for-storage`` CLI command [see `PR #966 `_] * CLI support for showing/savings time series data for a given type of source only, with the new ``--source-type`` option of ``flexmeasures show beliefs``, which let's you filter out schedules, forecasts, or data POSTed by users (through the API), which each have a different source type [see `PR #976 `_] * New CLI command ``flexmeasures delete beliefs`` to delete all beliefs on a given sensor (or multiple sensors) or on sensors of a given asset (or multiple assets) [see `PR #975 `_] * Support for defining the storage efficiency as a sensor or quantity for the ``StorageScheduler`` [see `PR #965 `_] * Support a less verbose way of setting the same :abbr:`SoC (state of charge)` constraint for a given time window [see `PR #899 `_] Infrastructure / Support ---------------------- * Deprecate use of flask's ``FLASK_ENV`` variable and replace it with ``FLEXMEASURES_ENV`` [see `PR #907 `_] * Streamline CLI option naming by favoring ``--`` over ``---id`` [see `PR #946 `_] * Documentation: improve index page, installation overview, feature overview incl. flex-model overview and UI screenshots [see `PR #953 `_] * Faster database queries of time series data by upgrading SQLAlchemy and timely-beliefs [see `PR #938 `_] v0.18.2 | February 26, 2024 ============================ * Convert unit of the power capacities to ``MW`` instead of that of the storage power sensor [see `PR #979 `_] * Automatically update table navigation in the UI without requiring users to hard refresh their browser [see `PR #961 `_] * Updated documentation to enhance clarity for integrating plugins within the FlexMeasures Docker container [see `PR #958 `_] * Support defining the ``power-capacity`` as a sensor in the API [see `PR #987 `_] v0.18.1 | January 15, 2024 ============================ .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). Bugfixes ----------- * Fix database migrations meant to clean up deprecated tables [see `PR #960 `_] * Allow showing beliefs (plot and file export) via the CLI for sensors with non-unique names [see `PR #947 `_] * Added Redis credentials to the Docker Compose configuration for the web server to ensure proper interaction with the Redis queue [see `PR #945 `_] * Fix API version listing (GET /api/v3_0) for hosts running on Python 3.8 [see `PR #917 `_ and `PR #950 `_] * Fix the validation of the option ``--parent-asset`` of command ``flexmeasures add asset`` [see `PR #959 `_] v0.18.0 | December 23, 2023 ============================ .. note:: Read more on these features on `the FlexMeasures blog `__. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). If this fails, update to ``flexmeasures==0.18.1`` first (and then run ``flexmeasures db upgrade``). New features ------------- * Better navigation experience through listings (sensors / assets / users / accounts) in the :abbr:`UI (user interface)`, by heading to the selected entity upon a click (or CTRL + click) anywhere within a row [see `PR #923 `_] * Introduce a breadcrumb to navigate through assets and sensor pages using its child-parent relationship [see `PR #930 `_] * Define device-level power constraints as sensors to create schedules with changing power limits [see `PR #897 `_] * Allow to provide external storage usage or gain components using the ``soc-usage`` and ``soc-gain`` fields of the ``flex-model`` [see `PR #906 `_] * Define time-varying charging and discharging efficiencies as sensors or as constant values which allows to define the :abbr:`COP (coefficient of performance)` [see `PR #933 `_] Infrastructure / Support ---------------------- * Align database and models of ``annotations``, ``data_sources``, and ``timed_belief`` [see `PR #929 `_] * New documentation section on constructing a flex model for :abbr:`V2G (vehicle-to-grid)` [see `PR #885 `_] * Allow charts in plugins to show currency codes (such as EUR) as currency symbols (€) [see `PR #922 `_] * Remove obsolete database tables ``price``, ``power``, ``market``, ``market_type``, ``weather``, ``asset``, and ``weather_sensor`` [see `PR #921 `_] * New flexmeasures configuration setting ``FLEXMEASURES_ENFORCE_SECURE_CONTENT_POLICY`` for upgrading insecure `http` requests to secured requests `https` [see `PR #920 `_] Bugfixes ----------- * Give ``admin-reader`` role access to the RQ Scheduler dashboard [see `PR #901 `_] * Assets without a geographical position (i.e. no lat/lng coordinates) can be edited through the UI [see `PR #924 `_] v0.17.1 | December 7, 2023 ============================ Bugfixes ----------- * Show `Assets`, `Users`, `Tasks` and `Accounts` pages in the navigation bar for the ``admin-reader`` role [see `PR #900 `_] * Reduce worker logs when datetime exceeds the end of the schedule [see `PR #918 `_] * Fix infeasible problem due to incorrect estimation of the big-M value [see `PR #905 `_] * [Incomplete fix; full fix in v0.18.1] Fix API version listing (GET /api/v3_0) for hosts running on Python 3.8 [see `PR #917 `_] v0.17.0 | November 8, 2023 ============================ .. note:: Read more on these features on `the FlexMeasures blog `__. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ------------- - Different site-level production and consumption limits can be defined for the storage scheduler via the API (``flex-context``) or via asset attributes [see `PR #884 `_] - Scheduling data better distinguishes (e.g. in chart tooltips) when a schedule was the result of a fallback mechanism, by splitting off the fallback mechanism from the main scheduler (as a separate job) [see `PR #846 `_] - New accounts can set a consultancy relationship with another account to give read access to external consultants [see `PR #877 `_ and `PR #892 `_] Infrastructure / Support ---------------------- - Introduce a new one-to-many relation between assets, allowing the definition of an asset's parent (which is also an asset), which leads to a hierarchical relationship that enables assets to be related in a structured manner [see `PR #855 `_ and `PR #874 `_] - Introduce a new format for the output of ``Scheduler`` to prepare for multiple outputs [see `PR #879 `_] v0.16.1 | October 2, 2023 ============================ Bugfixes ----------- * Fix infeasible problem due to incorrect parsing of :abbr:`SoC (state of charge)` units of the ``soc-minima`` and ``soc-maxima`` fields within the ``flex-model`` field [see `PR #864 `_] v0.16.0 | September 27, 2023 ============================ .. note:: Read more on these features on `the FlexMeasures blog `__. New features ------------- * Introduce new reporter to compute profit/loss due to electricity flows: ``ProfitOrLossReporter`` [see `PR #808 `_ and `PR #844 `_] * Charts visible in the UI can be exported to PNG or SVG formats in a more automated fashion, using the new CLI command flexmeasures show chart [see `PR #833 `_] * Chart data visible in the UI can be exported to CSV format [see `PR #849 `_] * Sensor charts showing instantaneous observations can be interpolated by setting the ``interpolate`` sensor attribute to one of the `supported Vega-Lite interpolation methods `_ [see `PR #851 `_] * API users can ask for a schedule to take into account an explicit ``power-capacity`` (flex-model) and/or ``site-power-capacity`` (flex-context), thereby overriding any existing defaults for their asset [see `PR #850 `_] * API users (and hosts) are warned in case a fallback scheduling policy has been used to create their schedule (as part of the the `[GET] /sensors//schedules/` response message) [see `PR #859 `_] Infrastructure / Support ---------------------- * Allow additional datetime conversions to quantitative time units, specifically, from timezone-naive and/or dayfirst datetimes, which can be useful when importing data [see `PR #831 `_] * Add a new tutorial to explain the use of the ``AggregatorReporter`` to compute the headroom and the ``ProfitOrLossReporter`` to compute the cost of running a process [see `PR #825 `_ and `PR #856 `_] * Updated admin dashboard for inspecting asynchronous tasks (scheduling, forecasting, reporting, etc.), and improved performance and security of the server by upgrading Flask and Flask extensions [see `PR #838 `_] * Script to update dependencies across supported Python versions [see `PR #843 `_] * Test all supported Python versions in our CI pipeline (GitHub Actions) [see `PR #847 `_] * Have our CI pipeline (GitHub Actions) build the Docker image and make a schedule [see `PR #800 `_] * Updated documentation on the consequences of setting the ``FLEXMEASURES_MODE`` config setting [see `PR #857 `_] * Implement cache-busting to avoid the need for users to hard refresh the browser when new JavaScript functionality is added to the :abbr:`UI (user interface)` in a new FlexMeasures version [see `PR #860 `_] v0.15.2 | October 2, 2023 ============================ Bugfixes ----------- * Fix infeasible problem due to incorrect parsing of :abbr:`SoC (state of charge)` units of the ``soc-minima`` and ``soc-maxima`` fields within the ``flex-model`` field [see `PR #864 `_] v0.15.1 | August 28, 2023 ============================ Bugfixes ----------- * Fix infeasible problem due to floating point error in :abbr:`SoC (state of charge)` targets [see `PR #832 `_] * Use the ``source`` to filter beliefs in the ``AggregatorReporter`` and fix the case of having multiple sources [see `PR #819 `_] * Disable HiGHS logs on the standard output when ``LOGGING_LEVEL=INFO`` [see `PR #824 `_ and `PR #826 `_] * Fix showing sensor data on the asset page of public assets, and searching for annotations on public assets [see `PR #830 `_] * Make the command ``flexmeasures add schedule for-storage`` to pass the soc-target timestamp to the flex model as strings instead of ``pd.Timestamp`` [see `PR #834 `_] v0.15.0 | August 9, 2023 ============================ .. note:: Read more on these features on `the FlexMeasures blog `__. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). .. warning:: Upgrading to this version requires installing the LP/MILP solver HiGHS using ``pip install highspy``. .. warning:: If your server is running in play mode (``FLEXMEASURES_MODE = "play"``), users will be able to see sensor data from any account [see `PR #740 `_]. New features ------------- * Add ``ProcessScheduler`` class to optimize the starting time of processes one of the policies developed (``INFLEXIBLE``, ``SHIFTABLE`` and ``BREAKABLE``), accessible via the CLI command ``flexmeasures add schedule for-process`` [see `PR #729 `_ and `PR #768 `_] * Users can select a new chart type (daily heatmap) on the sensor page of the UI, showing how sensor values are distributed over the time of day [see `PR #715 `_] * Added API endpoints `[GET] /sensors/` for fetching a single sensor, `[POST] /sensors` for adding a sensor, `/sensors/` (PATCH) for updating a sensor and `/sensors/` (DELETE) for deleting a sensor [see `PR #759 `_] and [see `PR #767 `_] and [see `PR #773 `_] and [see `PR #784 `_] * Users are warned in the UI on when the data they are seeing includes one or more :abbr:`DST (Daylight Saving Time)` transitions, and heatmaps (see previous feature) visualize these transitions intuitively [see `PR #723 `_] * Allow deleting multiple sensors with a single call to ``flexmeasures delete sensor`` by passing the ``--id`` option multiple times [see `PR #734 `_] * Make it a lot easier to read off the color legend on the asset page, especially when showing many sensors, as they will now be ordered from top to bottom in the same order as they appear in the chart (as defined in the ``sensors_to_show`` attribute), rather than alphabetically [see `PR #742 `_] * Users on FlexMeasures servers in play mode (``FLEXMEASURES_MODE = "play"``) can use the ``sensors_to_show`` attribute to show any sensor on their asset pages, rather than only sensors registered to assets in their own account or to public assets [see `PR #740 `_] * Having percentages within the [0, 100] domain is such a common use case that we now always include it in sensor charts with % units, making it easier to read off individual charts and also to compare across charts [see `PR #739 `_] * The ``DataSource`` table now allows storing arbitrary attributes as a JSON (without content validation), similar to the ``Sensor`` and ``GenericAsset`` tables [see `PR #750 `_] * Users will be able to see (e.g. in the UI) exactly which reporter created the report (saved as sensor data), and hosts will be able to identify exactly which configuration was used to create a given report [see `PR #751 `_ and `PR #788 `_] * The CLI ``flexmeasures add report`` now allows passing ``config`` and ``parameters`` in YAML format as files or editable via the system's default editor [see `PR #752 `_ and `PR #788 `_] * The CLI now allows to set lists and dicts as asset & sensor attributes (formerly only single values) [see `PR #762 `_] Bugfixes ----------- * Add binary constraint to avoid energy leakages during periods with negative prices [see `PR #770 `_] Infrastructure / Support ---------------------- * Add support for profiling Flask API calls using ``pyinstrument`` (if installed). Can be enabled by setting the environment variable ``FLEXMEASURES_PROFILE_REQUESTS`` to ``True`` [see `PR #722 `_] * The endpoint `[POST] /health/ready `_ returns the status of the Redis connection, if configured [see `PR #699 `_] * Document the ``device_scheduler`` linear program [see `PR #764 `_] * Add support for `HiGHS `_ solver [see `PR #766 `_] * Add support for installing FlexMeasures under Python 3.11 [see `PR #771 `_] * Start keeping sets of pinned requirements per supported Python version, which also fixes recent Docker build problem [see `PR #776 `_] * Removed obsolete code dealing with deprecated data models (e.g. assets, markets and weather sensors), and sunset the fm0 scheme for entity addresses [see `PR #695 `_ and `project 11 `_] v0.14.3 | October 2, 2023 ============================ Bugfixes ----------- * Fix infeasible problem due to incorrect parsing of :abbr:`SoC (state of charge)` units of the ``soc-minima`` and ``soc-maxima`` fields within the ``flex-model`` field [see `PR #864 `_] v0.14.2 | July 25, 2023 ============================ Bugfixes ----------- * The error handling for infeasible constraints in ``storage.py`` was given too many arguments, which caused the response from the API to be unhelpful when a schedule was requested with infeasible constraints [see `PR #758 `_] v0.14.1 | June 26, 2023 ============================ Bugfixes ----------- * Relax constraint validation of ``StorageScheduler`` to accommodate violations caused by floating point precision [see `PR #731 `_] * Avoid saving any :abbr:`NaN (not a number)` values to the database, when calling ``flexmeasures add report`` [see `PR #735 `_] * Fix browser console error when loading asset or sensor page with only a single data point [see `PR #732 `_] * Fix showing multiple sensors with bare 3-letter currency code as their units (e.g. EUR) in one chart [see `PR #738 `_] * Fix defaults for the ``--start-offset`` and ``--end-offset`` options to ``flexmeasures add report``, which weren't being interpreted in the local timezone of the reporting sensor [see `PR #744 `_] * Relax constraint for overlaying plot traces for sensors with various resolutions, making it possible to show e.g. two price sensors in one chart, where one of them records hourly prices and the other records quarter-hourly prices [see `PR #743 `_] * Resolve bug where different page loads would potentially influence the time axis of each other's charts, by avoiding mutation of shared field definitions [see `PR #746 `_] v0.14.0 | June 15, 2023 ============================ .. note:: Read more on these features on `the FlexMeasures blog `__. New features ------------- * Allow setting a storage efficiency using the new ``storage-efficiency`` field when calling `[POST] /sensors//schedules/trigger` through the API (within the ``flex-model`` field), or when calling ``flexmeasures add schedule for-storage`` through the CLI [see `PR #679 `_] * Allow setting multiple :abbr:`SoC (state of charge)` maxima and minima constraints for the ``StorageScheduler``, using the new ``soc-minima`` and ``soc-maxima`` fields when calling `[POST] /sensors//schedules/trigger` through the API (within the ``flex-model`` field) [see `PR #680 `_] * New CLI command ``flexmeasures add report`` to calculate a custom report from sensor data and save the results to the database, with the option to export them to a CSV or Excel file [see `PR #659 `_] * New CLI commands ``flexmeasures show reporters`` and ``flexmeasures show schedulers`` to list available reporters and schedulers, respectively, including any defined in registered plugins [see `PR #686 `_ and `PR #708 `_] * Allow creating public assets through the CLI, which are available to all users [see `PR #727 `_] Bugfixes ----------- * Fix charts not always loading over https in secured scenarios [see `PR #716 `_] Infrastructure / Support ---------------------- * Introduction of the classes ``Reporter``, ``PandasReporter`` and ``AggregatorReporter`` to help customize your own reporter functions (experimental) [see `PR #641 `_ and `PR #712 `_] * The setting ``FLEXMEASURES_PLUGINS`` can be set as environment variable now (as a comma-separated list) [see `PR #660 `_] * Packaging was modernized to stop calling setup.py directly [see `PR #671 `_] * Remove API versions 1.0, 1.1, 1.2, 1.3 and 2.0, while making sure that sunset endpoints keep returning ``HTTP status 410 (Gone)`` responses [see `PR #667 `_ and `PR #717 `_] * Support Pandas 2 [see `PR #673 `_] * Add code documentation from package structure and docstrings to official docs [see `PR #698 `_] .. warning:: The setting ``FLEXMEASURES_PLUGIN_PATHS`` has been deprecated since v0.7. It has now been sunset. Please replace it with :ref:`plugin-config`. v0.13.3 | June 10, 2023 ======================= Bugfixes --------- * Fix forwarding arguments in deprecated util function [see `PR #719 `_] v0.13.2 | June 9, 2023 ======================= Bugfixes --------- * Fix failing to save results of scheduling and reporting on subsequent calls for the same time period [see `PR #709 `_] v0.13.1 | May 12, 2023 ======================= Bugfixes --------- * ``@deprecated`` not returning the output of the decorated function [see `PR #678 `_] v0.13.0 | May 1, 2023 ============================ .. warning:: Sunset notice for API versions 1.0, 1.1, 1.2, 1.3 and 2.0: after upgrading to ``flexmeasures==0.13``, users of these API versions may receive ``HTTP status 410 (Gone)`` responses. See the `documentation for deprecation and sunset `_. The relevant endpoints have been deprecated since ``flexmeasures==0.12``. .. warning:: The API endpoint (`[POST] /sensors/(id)/schedules/trigger `_) to make new schedules sunsets the deprecated (since v0.12) storage flexibility parameters (they move to the ``flex-model`` parameter group), as well as the parameters describing other sensors (they move to ``flex-context``). .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). .. note:: Read more on these features on `the FlexMeasures blog `__. New features ------------- * Keyboard control over replay [see `PR #562 `_] * Overlay charts (e.g. power profiles) on the asset page using the ``sensors_to_show`` attribute, and distinguish plots by source (different trace), sensor (different color) and source type (different stroke dash) [see `PR #534 `_] * The ``FLEXMEASURES_MAX_PLANNING_HORIZON`` config setting can also be set as an integer number of planning steps rather than just as a fixed duration, which makes it possible to schedule further ahead in coarser time steps [see `PR #583 `_] * Different text styles for CLI output for errors, warnings or success messages [see `PR #609 `_] * Added API endpoints and webpages `/accounts` and `/accounts/` to list accounts and show an overview of the assets, users and account roles of an account [see `PR #605 `_] * Avoid redundantly recomputing jobs that are triggered without a relevant state change, where the ``FLEXMEASURES_JOB_CACHE_TTL`` config setting defines the time in which the jobs with the same arguments are not being recomputed [see `PR #616 `_] Bugfixes ----------- * Fix copy button on tutorials and other documentation, so that only commands are copied and no output or comments [see `PR #636 `_] * GET `/api/v3_0/assets/public` should ask for token authentication and not forward to login page [see `PR #649 `_] Infrastructure / Support ---------------------- * Support blackout tests for sunset API versions [see `PR #651 `_] * Sunset API versions 1.0, 1.1, 1.2, 1.3 and 2.0 [see `PR #650 `_] * Sunset several API fields for `[POST] /sensors//schedules/trigger` that have moved into the ``flex-model`` or ``flex-context`` fields [see `PR #580 `_] * Fix broken ``make show-data-model`` command [see `PR #638 `_] * Bash script for a clean database to run toy-tutorial by using ``make clean-db db_name=database_name`` command [see `PR #640 `_] v0.12.3 | February 28, 2023 ============================ Bugfixes ----------- - Fix premature deserialization of ``flex-context`` field for `[POST] /sensors//schedules/trigger` [see `PR #593 `_] v0.12.2 | February 4, 2023 ============================ Bugfixes ----------- * Fix CLI command ``flexmeasures schedule for-storage`` without ``--as-job`` flag [see `PR #589 `_] v0.12.1 | January 12, 2023 ============================ Bugfixes ----------- * Fix validation of (deprecated) API parameter ``roundtrip-efficiency`` [see `PR #582 `_] v0.12.0 | January 4, 2023 ============================ .. warning:: After upgrading to ``flexmeasures==0.12``, users of API versions 1.0, 1.1, 1.2, 1.3 and 2.0 will receive ``"Deprecation"`` and ``"Sunset"`` response headers, and warnings are logged for FlexMeasures hosts whenever users call API endpoints in these deprecated API versions. The relevant endpoints are planned to become unresponsive in ``flexmeasures==0.13``. .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). .. note:: Read more on these features on `the FlexMeasures blog `__. New features ------------- * Hit the replay button to visually replay what happened, available on the sensor and asset pages [see `PR #463 `_ and `PR #560 `_] * Ability to provide your own custom scheduling function [see `PR #505 `_] * Visually distinguish forecasts/schedules (dashed lines) from measurements (solid lines), and expand the tooltip with timing info regarding the forecast/schedule horizon or measurement lag [see `PR #503 `_] * The asset page also allows to show sensor data from other assets that belong to the same account [see `PR #500 `_] * The CLI command ``flexmeasures monitor latest-login`` supports to check if (bot) users who are expected to contact FlexMeasures regularly (e.g. to send data) fail to do so [see `PR #541 `_] * The CLI command ``flexmeasures show beliefs`` supports showing beliefs data in a custom resolution and/or timezone, and also saving the shown beliefs data to a CSV file [see `PR #519 `_] * Improved import of time series data from CSV file: 1) drop duplicate records with warning, 2) allow configuring which column contains explicit recording times for each data point (use case: import forecasts) [see `PR #501 `_], 3) localize timezone naive data, 4) support reading in datetime and timedelta values, 5) remove rows with NaN values, and 6) filter by values in specific columns [see `PR #521 `_] * Filter data by source in the API endpoint `[GET] /sensors/data` [see `PR #543 `_] * Allow posting ``null`` values to `[POST] /sensors/data` to correctly space time series that include missing values (the missing values are not stored) [see `PR #549 `_] * Allow setting a custom planning horizon when calling `[POST] /sensors//schedules/trigger`, using the new ``duration`` field [see `PR #568 `_] * New resampling functionality for instantaneous sensor data: 1) ``flexmeasures show beliefs`` can now handle showing (and saving) instantaneous sensor data and non-instantaneous sensor data together, and 2) the API endpoint `[GET] /sensors/data` now allows fetching instantaneous sensor data in a custom frequency, by using the "resolution" field [see `PR #542 `_] Bugfixes ----------- * The CLI command ``flexmeasures show beliefs`` now supports plotting time series data that includes NaN values, and provides better support for plotting multiple sensors that do not share the same unit [see `PR #516 `_ and `PR #539 `_] * Fixed JSON wrapping of return message for `[GET] /sensors/data` [see `PR #543 `_] * Consistent CLI/UI support for asset lat/lng positions up to 7 decimal places (previously the UI rounded to 4 decimal places, whereas the CLI allowed more than 4) [see `PR #522 `_] * Stop trimming the planning window in response to price availability, which is a problem when :abbr:`SoC (state of charge)` targets occur outside of the available price window, by making a simplistic assumption about future prices [see `PR #538 `_] * Faster loading of initial charts and calendar date selection [see `PR #533 `_] Infrastructure / Support ---------------------- * Reduce size of Docker image (from 2GB to 1.4GB) [see `PR #512 `_] * Allow extra requirements to be freshly installed when running ``docker-compose up`` [see `PR #528 `_] * Remove bokeh dependency and obsolete UI views [see `PR #476 `_] * Fix ``flexmeasures db-ops dump`` and ``flexmeasures db-ops restore`` not working in docker containers [see `PR #530 `_] and incorrectly reporting a success when ``pg_dump`` and ``pg_restore`` are not installed [see `PR #526 `_] * Plugins can save BeliefsSeries, too, instead of just BeliefsDataFrames [see `PR #523 `_] * Improve documentation and code w.r.t. storage flexibility modelling ― prepare for handling other schedulers & merge battery and car charging schedulers [see `PR #511 `_, `PR #537 `_ and `PR #566 `_] * Revised strategy for removing unchanged beliefs when saving data: retain the oldest measurement (ex-post belief), too [see `PR #518 `_] * Scheduling test for maximizing self-consumption, and improved time series db queries for fixed tariffs (and other long-term constants) [see `PR #532 `_] * Clean up table formatting for ``flexmeasures show`` CLI commands [see `PR #540 `_] * Add ``"Deprecation"`` and ``"Sunset"`` response headers for API users of deprecated API versions, and log warnings for FlexMeasures hosts when users still use them [see `PR #554 `_ and `PR #565 `_] * Explain how to avoid potential ``SMTPRecipientsRefused`` errors when using FlexMeasures in combination with a mail server [see `PR #558 `_] * Set a limit to the allowed planning window for API users, using the ``FLEXMEASURES_MAX_PLANNING_HORIZON`` setting [see `PR #568 `_] .. warning:: The API endpoint (`[POST] /sensors/(id)/schedules/trigger `_) to make new schedules will (in v0.13) sunset the storage flexibility parameters (they move to the ``flex-model`` parameter group), as well as the parameters describing other sensors (they move to ``flex-context``). .. warning:: The CLI command ``flexmeasures monitor tasks`` has been deprecated (it's being renamed to ``flexmeasures monitor last-run``). The old name will be sunset in version 0.13. .. warning:: The CLI command ``flexmeasures add schedule`` has been renamed to ``flexmeasures add schedule for-storage``. The old name will be sunset in version 0.13. v0.11.3 | November 2, 2022 ============================ Bugfixes ----------- * Fix scheduling with imperfect efficiencies, which resulted in exceeding the device's lower :abbr:`SoC (state of charge)` limit [see `PR #520 `_] * Fix scheduler for Charge Points when taking into account inflexible devices [see `PR #517 `_] * Prevent rounding asset lat/long positions to 4 decimal places when editing an asset in the UI [see `PR #522 `_] v0.11.2 | September 6, 2022 ============================ Bugfixes ----------- * Fix regression for sensors recording non-instantaneous values [see `PR #498 `_] * Fix broken auth check for creating assets with CLI [see `PR #497 `_] v0.11.1 | September 5, 2022 ============================ Bugfixes ----------- * Do not fail asset page if none of the sensors has any data [see `PR #493 `_] * Do not fail asset page if one of the shown sensors records instantaneous values [see `PR #491 `_] v0.11.0 | August 28, 2022 =========================== New features ------------- * The asset page now shows the most relevant sensor data for the asset [see `PR #449 `_] * Individual sensor charts show available annotations [see `PR #428 `_] * New API options to further customize the optimization context for scheduling, including the ability to use different prices for consumption and production (feed-in) [see `PR #451 `_] * Admins can group assets by account on dashboard & assets page [see `PR #461 `_] * Collapsible side-panel (hover/swipe) used for date selection on sensor charts, and various styling improvements [see `PR #447 `_ and `PR #448 `_] * Add CLI command ``flexmeasures jobs show-queues`` [see `PR #455 `_] * Switched from 12-hour AM/PM to 24-hour clock notation for time series chart axis labels [see `PR #446 `_] * Get data in a given resolution [see `PR #458 `_] .. note:: Read more on these features on `the FlexMeasures blog `__. Bugfixes ----------- * Do not fail asset page if entity addresses cannot be built [see `PR #457 `_] * Asynchronous reloading of a chart's dataset relies on that chart already having been embedded [see `PR #472 `_] * Time scale axes in sensor data charts now match the requested date range, rather than stopping at the edge of the available data [see `PR #449 `_] * The docker-based tutorial now works with UI on all platforms (port 5000 did not expose on MacOS) [see `PR #465 `_] * Fix interpretation of scheduling results in toy tutorial [see `PR #466 `_ and `PR #475 `_] * Avoid formatting ``datetime.timedelta`` durations as nominal ISO durations [see `PR #459 `_] * Account admins cannot add assets to other accounts any more; and they are shown a button for asset creation in UI [see `PR #488 `_] Infrastructure / Support ---------------------- * Docker compose stack now with Redis worker queue [see `PR #455 `_] * Allow access tokens to be passed as env vars as well [see `PR #443 `_] * Queue workers can get initialised without a custom name and name collisions are handled [see `PR #455 `_] * New API endpoint to get public assets [see `PR #461 `_] * Allow editing an asset's JSON attributes through the UI [see `PR #474 `_] * Allow a custom message when monitoring latest run of tasks [see `PR #489 `_] v0.10.1 | August 12, 2022 =========================== Bugfixes ----------- * Fix some UI styling regressions in e.g. color contrast and hover effects [see `PR #441 `_] v0.10.0 | May 8, 2022 =========================== New features ----------- * New design for FlexMeasures' UI back office [see `PR #425 `_] * Improve legibility of chart axes [see `PR #413 `_] * API provides health readiness check at /api/v3_0/health/ready [see `PR #416 `_] .. note:: Read more on these features on `the FlexMeasures blog `__. Bugfixes ----------- * Fix small problems in support for the admin-reader role & role-based authorization [see `PR #422 `_] Infrastructure / Support ---------------------- * Dockerfile to run FlexMeasures in container; also docker-compose file [see `PR #416 `_] * Unit conversion prefers shorter units in general [see `PR #415 `_] * Shorter CI builds in Github Actions by caching Python environment [see `PR #361 `_] * Allow to filter data by source using a tuple instead of a list [see `PR #421 `_] v0.9.4 | April 28, 2022 =========================== Bugfixes -------- * Support checking validity of custom units (i.e. non-SI, non-currency units) [see `PR #424 `_] v0.9.3 | April 15, 2022 =========================== Bugfixes -------- * Let registered plugins use CLI authorization [see `PR #411 `_] v0.9.2 | April 10, 2022 =========================== Bugfixes -------- * Prefer unit conversions to short stock units [see `PR #412 `_] * Fix filter for selecting one deterministic belief per event, which was duplicating index levels [see `PR #414 `_] v0.9.1 | March 31, 2022 =========================== Bugfixes -------- * Fix auth bug not masking locations of inaccessible assets on map [see `PR #409 `_] * Fix CLI auth check [see `PR #407 `_] * Fix resampling of sensor data for scheduling [see `PR #406 `_] v0.9.0 | March 25, 2022 =========================== .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ----------- * Three new CLI commands for cleaning up your database: delete 1) unchanged beliefs, 2) NaN values or 3) a sensor and all of its time series data [see `PR #328 `_] * Add CLI option to pass a data unit when reading in time series data from CSV, so data can automatically be converted to the sensor unit [see `PR #341 `_] * Add CLI option to specify custom strings that should be interpreted as NaN values when reading in time series data from CSV [see `PR #357 `_] * Add CLI commands ``flexmeasures add sensor``, ``flexmeasures add asset-type``, ``flexmeasures add beliefs`` (which were experimental features before) [see `PR #337 `_] * Add CLI commands for showing organisational structure [see `PR #339 `_] * Add CLI command for showing time series data [see `PR #379 `_] * Add CLI command for attaching annotations to assets: ``flexmeasures add holidays`` adds public holidays [see `PR #343 `_] * Add CLI command for resampling existing sensor data to new resolution [see `PR #360 `_] * Add CLI command to delete an asset, with its sensors and data [see `PR #395 `_] * Add CLI command to edit/add an attribute on an asset or sensor [see `PR #380 `_] * Add CLI command to add a toy account for tutorials and trying things [see `PR #368 `_] * Add CLI command to create a charging schedule [see `PR #372 `_] * Support for percent (%) and permille (‰) sensor units [see `PR #359 `_] .. note:: Read more on these features on `the FlexMeasures blog `__. Infrastructure / Support ---------------------- * Plugins can import common FlexMeasures classes (like ``Asset`` and ``Sensor``) from a central place, using ``from flexmeasures import Asset, Sensor`` [see `PR #354 `_] * Adapt CLI command for entering some initial structure (``flexmeasures add structure``) to new datamodel [see `PR #349 `_] * Align documentation requirements with pip-tools [see `PR #384 `_] * Beginning API v3.0 - more REST-like, supporting assets, users and sensor data [see `PR #390 `_ and `PR #392 `_] v0.8.0 | January 24, 2022 =========================== .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). .. warning:: In case you use FlexMeasures for simulations using ``FLEXMEASURES_MODE = "play"``, allowing to overwrite data is now set separately using :ref:`overwrite-config`. Add ``FLEXMEASURES_ALLOW_DATA_OVERWRITE = True`` to your config settings to keep the old behaviour. .. note:: v0.8.0 is doing much of the work we need to do to move to the new data model (see :ref:`note_on_datamodel_transition`). We hope to keep the migration steps for users very limited. One thing you'll notice is that we are copying over existing data to the new model (which will be kept in sync) with the ``db upgrade`` command (see warning above), which can take a few minutes. New features ----------- * Bar charts of sensor data for individual sensors, that can be navigated using a calendar [see `PR #99 `_ and `PR #290 `_] * Charts with sensor data can be requested in one of the supported [`vega-lite themes `_] (incl. a dark theme) [see `PR #221 `_] * Mobile friendly (responsive) charts of sensor data, and such charts can be requested with a custom width and height [see `PR #313 `_] * Schedulers take into account round-trip efficiency if set [see `PR #291 `_] * Schedulers take into account min/max state of charge if set [see `PR #325 `_] * Fallback policies for charging schedules of batteries and Charge Points, in cases where the solver is presented with an infeasible problem [see `PR #267 `_ and `PR #270 `_] .. note:: Read more on these features on `the FlexMeasures blog `__. Deprecations ------------ * The Portfolio and Analytics views are deprecated [see `PR #321 `_] Bugfixes ----------- * Fix recording time of schedules triggered by UDI events [see `PR #300 `_] * Set bar width of bar charts based on sensor resolution [see `PR #310 `_] * Fix bug in sensor data charts where data from multiple sources would be stacked, which incorrectly suggested that the data should be summed, whereas the data represents alternative beliefs [see `PR #228 `_] Infrastructure / Support ---------------------- * Account-based authorization, incl. new decorators for endpoints [see `PR #210 `_] * Central authorization policy which lets database models codify who can do what (permission-based) and relieve API endpoints from this [see `PR #234 `_] * Improve data specification for forecasting models using timely-beliefs data [see `PR #154 `_] * Properly attribute Mapbox and OpenStreetMap [see `PR #292 `_] * Allow plugins to register their custom config settings, so that FlexMeasures can check whether they are set up correctly [see `PR #230 `_ and `PR #237 `_] * Add sensor method to obtain just its latest state (excl. forecasts) [see `PR #235 `_] * Migrate attributes of assets, markets and weather sensors to our new sensor model [see `PR #254 `_ and `project 9 `_] * Migrate all time series data to our new sensor data model based on the `timely beliefs `_ lib [see `PR #286 `_ and `project 9 `_] * Support the new asset model (which describes the organisational structure, rather than sensors and data) in UI and API - until the transition to our new data model is completed, the new API for assets is at `/api/dev/generic_assets` [see `PR #251 `_ and `PR #290 `_] * Internal search methods return most recent beliefs by default, also for charts, which can make them load a lot faster [see `PR #307 `_ and `PR #312 `_] * Support unit conversion for posting sensor data [see `PR #283 `_ and `PR #293 `_] * Improve the core device scheduler to support dealing with asymmetric efficiency losses of individual devices, and with asymmetric up and down prices for deviating from previous commitments (such as a different feed-in tariff) [see `PR #291 `_] * Stop automatically triggering forecasting jobs when API calls save nothing new to the database, thereby saving redundant computation [see `PR #303 `_] v0.7.1 | November 8, 2021 =========================== Bugfixes ----------- * Fix device messages, which were mixing up older and more recent schedules [see `PR #231 `_] v0.7.0 | October 26, 2021 =========================== .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). .. warning:: The config setting ``FLEXMEASURES_PLUGIN_PATHS`` has been renamed to ``FLEXMEASURES_PLUGINS``. The old name still works but is deprecated. New features ----------- * Set a logo for the top left corner with the new ``FLEXMEASURES_MENU_LOGO_PATH`` setting [see `PR #184 `_] * Add an extra style-sheet which applies to all pages with the new ``FLEXMEASURES_EXTRA_CSS_PATH`` setting [see `PR #185 `_] * Data sources can be further distinguished by what model (and version) they ran [see `PR #215 `_] * Enable plugins to automate tests with app context [see `PR #220 `_] .. note:: Read more on these features on `the FlexMeasures blog `__. Bugfixes ----------- * Fix users resetting their own password [see `PR #195 `_] * Fix scheduling for heterogeneous settings, for instance, involving sensors with different time zones and/or resolutions [see `PR #207 `_] * Fix `/sensors//chart` view [see `PR #223 `_] Infrastructure / Support ---------------------- * FlexMeasures plugins can be Python packages now, and we provide `a cookie-cutter template `_ for this approach [see `PR #182 `_] * Set default timezone for new users using the ``FLEXMEASURES_TIMEZONE`` config setting [see `PR #190 `_] * To avoid databases from filling up with irrelevant information, only beliefs data representing *changed beliefs are saved*, and *unchanged beliefs are dropped* [see `PR #194 `_] * Monitored CLI tasks can get better names for identification [see `PR #193 `_] * Less custom logfile location, document logging for devs [see `PR #196 `_] * Keep forecasting and scheduling jobs in the queues for only up to one day [see `PR #198 `_] v0.6.1 | October 23, 2021 =========================== Bugfixes ----------- * Fix (dev) CLI command for adding a ``GenericAssetType`` [see `PR #173 `_] * Fix (dev) CLI command for adding a ``Sensor`` [see `PR #176 `_] * Fix missing conversion of data source names and ids to ``DataSource`` objects [see `PR #178 `_] * Fix GetDeviceMessage to ensure chronological ordering of values [see `PR #216 `_] v0.6.0 | September 3, 2021 =========================== .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). In case you are using experimental developer features and have previously set up sensors, be sure to check out the upgrade instructions in `PR #157 `_. Furthermore, if you want to create custom user/account relationships while upgrading (otherwise the upgrade script creates accounts based on email domains), check out the upgrade instructions in `PR #159 `_. If you want to use both of these custom upgrade features, do the upgrade in two steps. First, as described in PR 157 and upgrading up to revision ``b6d49ed7cceb``, then as described in PR 159 for the rest. .. warning:: The config setting ``FLEXMEASURES_LISTED_VIEWS`` has been renamed to ``FLEXMEASURES_MENU_LISTED_VIEWS``. .. warning:: Plugins now need to set their version on their module rather than on their blueprint. See the `documentation for writing plugins `_. New features ----------- * Multi-tenancy: Supporting multiple customers per FlexMeasures server, by introducing the ``Account`` concept, where accounts have users and assets associated [see `PR #159 `_ and `PR #163 `_] * In the UI, the root view ("/"), the platform name and the visible menu items can now be more tightly controlled (per account roles of the current user) [see also `PR #163 `_] * Analytics view offers grouping of all assets by location [see `PR #148 `_] * Add (experimental) endpoint to post sensor data for any sensor. Also supports our ongoing integration with data internally represented using the `timely beliefs `_ lib [see `PR #147 `_] .. note:: Read more on these features on `the FlexMeasures blog `__. Infrastructure / Support ---------------------- * Add possibility to send errors to Sentry [see `PR #143 `_] * Add CLI task to monitor if tasks ran successfully and recently enough [see `PR #146 `_] * Document how to use a custom favicon in plugins [see `PR #152 `_] * Allow plugins to register multiple Flask blueprints [see `PR #171 `_] * Continue experimental integration with `timely beliefs `_ lib: link multiple sensors to a single asset [see `PR #157 `_] * The experimental parts of the data model can now be visualised, as well, via ``make show-data-model`` (add the ``--dev`` option in ``Makefile``) [also in `PR #157 `_] v0.5.0 | June 7, 2021 =========================== .. warning:: If you retrieve weather forecasts through FlexMeasures: we had to switch to OpenWeatherMap, as Dark Sky is closing. This requires an update to config variables ― the new setting is called ``OPENWEATHERMAP_API_KEY``. New features ----------- * Allow plugins to overwrite UI routes and customise the teaser on the login form [see `PR #106 `_] * Allow plugins to customise the copyright notice and credits in the UI footer [see `PR #123 `_] * Display loaded plugins in footer and support plugin versioning [see `PR #139 `_] .. note:: Read more on these features on `the FlexMeasures blog `__. Bugfixes ----------- * Fix last login date display in user list [see `PR #133 `_] * Choose better forecasting horizons when weather data is posted [see `PR #131 `_] Infrastructure / Support ---------------------- * Add tutorials on how to add and read data from FlexMeasures via its API [see `PR #130 `_] * For weather forecasts, switch from Dark Sky (closed from Aug 1, 2021) to OpenWeatherMap API [see `PR #113 `_] * Entity address improvements: add new id-based `fm1` scheme, better documentation and more validation support of entity addresses [see `PR #81 `_] * Re-use the database between automated tests, if possible. This shaves 2/3rd off of the time it takes for the FlexMeasures test suite to run [see `PR #115 `_] * Make assets use MW as their default unit and enforce that in CLI, as well (API already did) [see `PR #108 `_] * Let CLI package and plugins use Marshmallow Field definitions [see `PR #125 `_] * Add ``time_utils.get_recent_clock_time_window`` function [see `PR #135 `_] v0.4.1 | May 7, 2021 =========================== Bugfixes ----------- * Fix regression when editing assets in the UI [see `PR #122 `_] * Fixed a regression that stopped asset, market and sensor selection from working [see `PR #117 `_] * Prevent logging out user when clearing the session [see `PR #112 `_] * Prevent user type data source to be created without setting a user [see `PR #111 `_] v0.4.0 | April 29, 2021 =========================== .. warning:: Upgrading to this version requires running ``flexmeasures db upgrade`` (you can create a backup first with ``flexmeasures db-ops dump``). New features ----------- * Allow for views and CLI functions to come from plugins [see also `PR #91 `_] * Configure the UI menu with ``FLEXMEASURES_LISTED_VIEWS`` [see `PR #91 `_] .. note:: Read more on these features on `the FlexMeasures blog `__. Bugfixes ----------- * Asset edit form displayed wrong error message. Also enabled the asset edit form to display the invalid user input back to the user [see `PR #93 `_] Infrastructure / Support ---------------------- * Upgraded dependencies, including Flask-Security-Too [see `PR #82 `_] * Improved documentation after user feedback [see `PR #97 `_] * Begin experimental integration with `timely beliefs `_ lib: ``Sensor`` data as ``TimedBelief`` objects [see `PR #79 `_ and `PR #99 `_] * Add sensors with CLI command currently meant for developers only [see `PR #83 `_] * Add data (beliefs about sensor events) with CLI command currently meant for developers only [see `PR #85 `_ and `PR #103 `_] v0.3.1 | April 9, 2021 =========================== Bugfixes -------- * PostMeterData endpoint was broken in API v2.0 [see `PR #95 `_] v0.3.0 | April 2, 2021 =========================== New features ----------- * FlexMeasures can be installed with ``pip`` and its CLI commands can be run with ``flexmeasures`` [see `PR #54 `_] * Optionally setting recording time when posting data [see `PR #41 `_] * Add assets and weather sensors with CLI commands [see `PR #74 `_] .. note:: Read more on these features on `the FlexMeasures blog `__. Bugfixes -------- * Show screenshots in documentation and add some missing content [see `PR #60 `_] * Documentation listed 2.0 API endpoints twice [see `PR #59 `_] * Better xrange and title if only schedules are plotted [see `PR #67 `_] * User page did not list number of assets correctly [see `PR #64 `_] * Missing *postPrognosis* endpoint for >1.0 API blueprints [part of `PR #41 `_] Infrastructure / Support ---------------------- * Added concept pages to documentation [see `PR #65 `_] * Dump and restore postgres database as CLI commands [see `PR #68 `_] * Improved installation tutorial as part of [`PR #54 `_] * Moved developer docs from Readmes into the main documentation [see `PR #73 `_] * Ensured unique sensor ids for all sensors [see `PR #70 `_ and (fix) `PR #77 `_] v0.2.3 | February 27, 2021 =========================== New features ------------ * Power charts available via the API [see `PR #39 `_] * User management via the API [see `PR #25 `_] * Better visibility of asset icons on maps [see `PR #30 `_] .. note:: Read more on these features on `the FlexMeasures blog `__. Bugfixes -------- * Fix maps on new asset page (update MapBox lib) [see `PR #27 `_] * Some asset links were broken [see `PR #20 `_] * Password reset link on account page was broken [see `PR #23 `_] Infrastructure / Support ---------------------- * CI via Github Actions [see `PR #1 `_] * Integration with `timely beliefs `__ lib: Sensors [see `PR #13 `_] * Apache 2.0 license [see `PR #16 `_] * Load js & css from CDN [see `PR #21 `_] * Start using marshmallow for input validation, also introducing ``HTTP status 422 (Unprocessable Entity)`` in the API [see `PR #25 `_] * Replace ``solarpy`` with ``pvlib`` (due to license conflict) [see `PR #16 `_] * Stop supporting the creation of new users on asset creation (to reduce complexity) [see `PR #36 `_]