This issue would create such an endpoint (e.g. /asset/<id>/schedules/trigger), but probably not provide an implementation for the case of multiple flexible assets (sensors), unless we come up with a base case that is doable (e.g. only batteries and heat pumps).

The main use case here is after #9 is done, where a custom algorithm can be provided in a plugin to solve the specific problem.