-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[energidataservice] Remove obsoleted advanced channel hourly-prices
#16190
Conversation
hourly-prices
ac8e6e2
to
2a72e1c
Compare
Signed-off-by: Jacob Laursen <[email protected]>
2a72e1c
to
9cfc5e5
Compare
### Persistence Configuration | ||
|
||
```java | ||
Strategies { | ||
default = everyChange | ||
} | ||
|
||
Items { | ||
SpotPrice, | ||
GridTariff, | ||
SystemTariff, | ||
TransmissionGridTariff, | ||
ElectricityTax: strategy = forecast | ||
} | ||
``` | ||
|
||
In case persistence is only needed for charts and/or accessing prices from rules, [InMemory Persistence](https://www.openhab.org/addons/persistence/inmemory/) can be used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Many thank for providing this example, this is something missing in " InMemory Persistence" service.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you
Signed-off-by: Jacob Laursen <[email protected]> Signed-off-by: Andras Uhrin <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]> Signed-off-by: Jørgen Austvik <[email protected]>
This pull request has been mentioned on openHAB Community. There might be relevant details there: |
Signed-off-by: Jacob Laursen <[email protected]>
With the introduction of openhab/openhab-core#3597 and #15063 in openHAB 4.1, the advanced channel
hourly-prices
is now fully obsoleted.It was already possible to use binding-specific Thing actions for importing future prices into rules, but since 4.1.1 it's also possible to access future prices through in-memory persistence, i.e. persisted time series.
Therefore, the binding can be simplified by removing this channel.