Tweet
The Spot Price Optimizer works well with EPEX data, but when using custom market energy prices via virtual inputs, none of the available modes is good enough:
So I thought: why not emulate the EPEX API, just like the Loxone weather service is emulated by the Weather 4 Loxone plugin?
A plugin like this could fetch prices from MQTT (pool from a custom market/operator/provider API with other tools) and present them as if they were coming from an official EPEX market. This would allow the Spot Price Optimizer to display and use both current and next day prices—just like it does with official market data.
Unfortunately, I’m not a developer/programmer, so I can’t implement this myself—but perhaps this idea will inspire someone who can.
- Absolute mode allows you to set prices only for the current day. In practice, this means you can provide prices for the next day only during the last hour of the current day. However, unlike in EPEX/Market mode, the UI never shows prices for the next day, and selecting the lowest-price hours is limited to the current day only.
- Relative mode works reasonably well only if you set prices once a day and trigger the SPO once per day as well. But again, you don’t get a full 48-hour price window (today + tomorrow) like you do in EPEX/Market mode, and selecting the lowest-price hours is also limited.
So I thought: why not emulate the EPEX API, just like the Loxone weather service is emulated by the Weather 4 Loxone plugin?
A plugin like this could fetch prices from MQTT (pool from a custom market/operator/provider API with other tools) and present them as if they were coming from an official EPEX market. This would allow the Spot Price Optimizer to display and use both current and next day prices—just like it does with official market data.
Unfortunately, I’m not a developer/programmer, so I can’t implement this myself—but perhaps this idea will inspire someone who can.