Victor

As an alternative, we could use the function `get_timerange` individually to each of the sensors involved to get `end_date = min(end_date_sensor1, end_date_sensor_2, ...)`, or even just get the maximum (latest)...

> I guess a workaround could be to set the -end-offset option to 2D,DB and making sure that the command is only called on D-1. Actually, we would need to...

> I noticed that there are fewer assets in the /assets listing compared to before this PR, so there must still be something wrong. Also, the asset icons (which are...

Reminder: this PR requires an API changelog entry.

> Why can't we get the resolution of the final output from `self.sensor.event_resolution` instead? The idea is, by default, check that the output `event_resolution == self.sensor.event_resolution`, happening in the `Reporter`...

> Can we think of some alternatives? Is this resolution only passed to make that check succeed? If so, maybe we want that check only on proper BeliefsDataFrames, and want...

Hello Rajath! The planned cost per device is returned by the function `device_scheduler` in [line 196]( https://github.com/FlexMeasures/flexmeasures/blob/e4c77cc90187ea9e64b531287becdb74d55e8be1/flexmeasures/data/models/planning/storage.py#L196). You can see how it is computed [here](https://github.com/FlexMeasures/flexmeasures/blob/e4c77cc90187ea9e64b531287becdb74d55e8be1/flexmeasures/data/models/planning/linear_optimization.py#LL323C2-L323C2). As far as I can...

> @victorgarcia98 can `sensor_search_configs` be used to select only sensor data sourced by the scheduler? At the moment, the `sensor_search_configs` can take a source id in its values so you...

Indeed, this PR lacked a test. Other than that, I also added the changelog entry.

Added the unit conversion from in the output stage. Please, let me know what you think. :D