flexmeasures icon indicating copy to clipboard operation
flexmeasures copied to clipboard

The intelligent & developer-friendly EMS to support real-time energy flexibility apps, rapidly and scalable.

Results 179 flexmeasures issues
Sort by recently updated
recently updated
newest added

Currently, posted data is checked for its resolution, but not for whether events start exactly an integer number of resolutions past midnight (for example, 0, 15, 30 or 45 minutes...

API

The class should get a name more indicative of what it is for. Probably becomes AggregatedAsset. However, this still needs some more discussion, because we actually use Resource in both...

Data

This PR adds documentation to the /api/sensor//schedules/trigger endpoint to better understand how to describe a flexibility model. Also in preparation for more flexibility modes to come, right now we only...

The timerange of sensor data shown on the asset page can take some time to load, especially if showing many sensors that have a lot of data. In most cases,...

We want to be able to automatically produce data derived from existing data, for reporting. An example are KPIs, but often it's data which is used to better explain to...

The default data source, for data made by scripts, is now "Seita". This is not what users want, of course. It should be "FlexMeasures" per default, and ideally a config...

Data

https://github.com/SeitaBV/timely-beliefs/pull/111 will make it possible to import time series data from CSV (or excel) where datetimes are given in non-UTC local time. `flexmeasures add beliefs` could use a `timezone` flag...

Data
CLI

This (optional) link between sources and users is still from the time before we introduced accounts. Accounts are a more informative way of describing where information is coming from. We...

Data

Latitude and longitude values seem to be rounded off to 4 decimal place. As a result, assets with a more precisely defined location will be moved to a new location...

bug
good first issue