Flexmeasures

Latest version: v0.25.0

Safety actively analyzes 723158 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 10

0.19.0

============================

.. note:: Read more on these features on `the FlexMeasures blog <https://flexmeasures.io/019-asset-nesting/>`__.

.. 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 <https://github.com/FlexMeasures/flexmeasures/pull/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 <https://github.com/FlexMeasures/flexmeasures/pull/977>`_]
* Enable the use of QuantityOrSensor fields for the ``flexmeasures add schedule for-storage`` CLI command [see `PR 966 <https://github.com/FlexMeasures/flexmeasures/pull/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 <https://github.com/FlexMeasures/flexmeasures/pull/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 <https://github.com/FlexMeasures/flexmeasures/pull/975>`_]
* Support for defining the storage efficiency as a sensor or quantity for the ``StorageScheduler`` [see `PR 965 <https://github.com/FlexMeasures/flexmeasures/pull/965>`_]
* Support a less verbose way of setting the same :abbr:`SoC (state of charge)` constraint for a given time window [see `PR 899 <https://github.com/FlexMeasures/flexmeasures/pull/899>`_]

Infrastructure / Support
----------------------
* Deprecate use of flask's ``FLASK_ENV`` variable and replace it with ``FLEXMEASURES_ENV`` [see `PR 907 <https://github.com/FlexMeasures/flexmeasures/pull/907>`_]
* Streamline CLI option naming by favoring ``--<entity>`` over ``--<entity>-id`` [see `PR 946 <https://github.com/FlexMeasures/flexmeasures/pull/946>`_]
* Documentation: improve index page, installation overview, feature overview incl. flex-model overview and UI screenshots [see `PR 953 <https://github.com/FlexMeasures/flexmeasures/pull/953>`_]
* Faster database queries of time series data by upgrading SQLAlchemy and timely-beliefs [see `PR 938 <https://github.com/FlexMeasures/flexmeasures/pull/938>`_]

0.18.2

============================

* Convert unit of the power capacities to ``MW`` instead of that of the storage power sensor [see `PR 979 <https://github.com/FlexMeasures/flexmeasures/pull/979>`_]
* Automatically update table navigation in the UI without requiring users to hard refresh their browser [see `PR 961 <https://github.com/FlexMeasures/flexmeasures/pull/961>`_]
* Updated documentation to enhance clarity for integrating plugins within the FlexMeasures Docker container [see `PR 958 <https://github.com/FlexMeasures/flexmeasures/pull/958>`_]
* Support defining the ``power-capacity`` as a sensor in the API [see `PR 987 <https://github.com/FlexMeasures/flexmeasures/pull/987>`_]

0.18.1

============================

.. 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 <https://github.com/FlexMeasures/flexmeasures/pull/960>`_]
* Allow showing beliefs (plot and file export) via the CLI for sensors with non-unique names [see `PR 947 <https://github.com/FlexMeasures/flexmeasures/pull/947>`_]
* Added Redis credentials to the Docker Compose configuration for the web server to ensure proper interaction with the Redis queue [see `PR 945 <https://github.com/FlexMeasures/flexmeasures/pull/945>`_]
* Fix API version listing (GET /api/v3_0) for hosts running on Python 3.8 [see `PR 917 <https://github.com/FlexMeasures/flexmeasures/pull/917>`_ and `PR #950 <https://github.com/FlexMeasures/flexmeasures/pull/950>`_]
* Fix the validation of the option ``--parent-asset`` of command ``flexmeasures add asset`` [see `PR 959 <https://github.com/FlexMeasures/flexmeasures/pull/959>`_]

0.18.0

============================

.. note:: Read more on these features on `the FlexMeasures blog <https://flexmeasures.io/018-better-use-of-future-knowledge/>`__.

.. 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 <https://github.com/FlexMeasures/flexmeasures/pull/923>`_]
* Introduce a breadcrumb to navigate through assets and sensor pages using its child-parent relationship [see `PR 930 <https://github.com/FlexMeasures/flexmeasures/pull/930>`_]
* Define device-level power constraints as sensors to create schedules with changing power limits [see `PR 897 <https://github.com/FlexMeasures/flexmeasures/pull/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 <https://github.com/FlexMeasures/flexmeasures/pull/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 <https://github.com/FlexMeasures/flexmeasures/pull/933>`_]

Infrastructure / Support
----------------------
* Align database and models of ``annotations``, ``data_sources``, and ``timed_belief`` [see `PR 929 <https://github.com/FlexMeasures/flexmeasures/pull/929>`_]
* New documentation section on constructing a flex model for :abbr:`V2G (vehicle-to-grid)` [see `PR 885 <https://github.com/FlexMeasures/flexmeasures/pull/885>`_]
* Allow charts in plugins to show currency codes (such as EUR) as currency symbols (€) [see `PR 922 <https://github.com/FlexMeasures/flexmeasures/pull/922>`_]
* Remove obsolete database tables ``price``, ``power``, ``market``, ``market_type``, ``weather``, ``asset``, and ``weather_sensor`` [see `PR 921 <https://github.com/FlexMeasures/flexmeasures/pull/921>`_]
* New flexmeasures configuration setting ``FLEXMEASURES_ENFORCE_SECURE_CONTENT_POLICY`` for upgrading insecure `http` requests to secured requests `https` [see `PR 920 <https://github.com/FlexMeasures/flexmeasures/pull/920>`_]

Bugfixes
-----------
* Give ``admin-reader`` role access to the RQ Scheduler dashboard [see `PR 901 <https://github.com/FlexMeasures/flexmeasures/pull/901>`_]
* Assets without a geographical position (i.e. no lat/lng coordinates) can be edited through the UI [see `PR 924 <https://github.com/FlexMeasures/flexmeasures/pull/924>`_]

0.17.1

============================

Bugfixes
-----------
* Show `Assets`, `Users`, `Tasks` and `Accounts` pages in the navigation bar for the ``admin-reader`` role [see `PR 900 <https://github.com/FlexMeasures/flexmeasures/pull/900>`_]
* Reduce worker logs when datetime exceeds the end of the schedule [see `PR 918 <https://github.com/FlexMeasures/flexmeasures/pull/918>`_]
* Fix infeasible problem due to incorrect estimation of the big-M value [see `PR 905 <https://github.com/FlexMeasures/flexmeasures/pull/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 <https://github.com/FlexMeasures/flexmeasures/pull/917>`_]

0.17.0

============================

.. note:: Read more on these features on `the FlexMeasures blog <https://flexmeasures.io/017-consultancy/>`__.

.. 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 <https://github.com/FlexMeasures/flexmeasures/pull/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 <https://github.com/FlexMeasures/flexmeasures/pull/846>`_]
- New accounts can set a consultancy relationship with another account to give read access to external consultants [see `PR 877 <https://github.com/FlexMeasures/flexmeasures/pull/877>`_ and `PR #892 <https://github.com/FlexMeasures/flexmeasures/pull/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 <https://github.com/FlexMeasures/flexmeasures/pull/855>`_ and `PR #874 <https://github.com/FlexMeasures/flexmeasures/pull/874>`_]
- Introduce a new format for the output of ``Scheduler`` to prepare for multiple outputs [see `PR 879 <https://github.com/FlexMeasures/flexmeasures/pull/879>`_]

Page 3 of 10

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.