I went to configure the OpenWeatherMap binding. I put in the LatLong location in the Location field for the Binding in preferences, but still got the error:
2024-11-19 22:20:14.271 [DEBUG] [overy.OpenWeatherMapDiscoveryService] - Location is not set → Will not provide any discovery results.
So then I went and manually edited the file
/etc/openhab/services/runtime.cfg
To put in the Lat and Long under the entry:
org.openhab.i18n:location=
Then it started working.
That to me suggests that the GUI field isn’t wired up.
When I look at the code here:
It uses the discovery process from the centralised configuration:
import org.openhab.core.i18n.LocationProvider;
Not its own local configuration here:
So to compare it to Astro - which does use local location:
and read the configuration.
My question is: Does it seem reasonable to copy the code from Astro in a PR for OpenWeatherMaps to make it load location from the GUI instead of the file?
I don’t know the answer to your question but I moved this post to the development category where it’s more likely to get the attention of those who can.
I do not know the overall impacts of making this proposed change but it seems reasonable.