I personally don’t like the opt-in decision but that’s just my opinion. Yes they keep it 100% compatible but
- the data is now faulty to a certain degree
- users which are not aware will run with this data for probably a long time without noticing
- when Tibber decides the opt-in is now default the hard break is just delayed
Would be more happy with opt-out strategy, because everybody will notice the changes immediately plus if you’ve problems you can restore the old state. But everybody knows now they’ll have something to do!
Yes, binding is prepared and can handle whatever price duration is provided. Of course the opt-in isn’t in but it doesn’t require any code change - only the graphql query needs to be corrected which is a text file within the binding jar. You can even edit the jar with e.g. 7-zip and modify the query.
To sum up
- Marketplace version contains all changes/bugfixes prior to first OH5 release including quarter-hourly prices
- There’s also a link to the legacy binding with hourly query
- Both versions based on latest OH4 baseline and are compatible with OH5
- Ideally all changes are part of next 5.0.2