Thanks, there is now a beta version for the binding.
However, I’m having an afterthought because I created this:
openmeteo bridge → forecast thing → channel groups → channels
Where the forecast thing has a location property, one channel group for hourly and one for daily, where the channels in those groups are not exactly identical.
When I use MainUI to create “Equipment from thing” and select all channels, they are created in the model all at the same level, effectively ignoring the channel groups they were assigned to.
This makes it quite hard to identify which channel belongs to what when browsing the model. For instance, here are pairs of channels that exist in both groups:
Without looking at their Id, it’s impossible to know which group they originate from.
This is why I wonder if it wouldn’t be better if I was to create the following situation:
openmeteo bridge → location bridge → daily forecast thing → channels
openmeteo bridge → location bridge → hourly forecast thing → channels
This would also allow for later adding AirQuality and MarineForceast things that depend on the location bridge.
The downside thought is added setup complexity and the fact hourly and daily data can be retrieved together with the same API call, while air quality and marine forecast are separate calls, even if the latter has the ability to retrieve daily and hourly at the same time.
Or maybe I should suffix the channel labels with " - hourly" and " - daily" ?
But wouldn’t that be redundant with the channel groups?
Any opinion is most welcome.