And do you keep the API information if you switch from one service to another?
A small note on your second paragraph:
I think we can remove France to have just Weather as generic for the widget choice.
Yes, the API keys are saved in the database, so you can switch from one source to another without re-entering the key. And given the size of the Meteo France key, itâs better that way. But still, Meteo France is optional, only for displaying the map.
Yes, itâs planned for the text, but as I havenât yet replaced the old weather widget, for now, itâs still called Meteo France. Iâll change it once the cleanup is done.
I prefer this approach! A single weather widget, with two separate integrations.
In fact, this is how all of Gladys works: there is only one widget per type of functionality, and each brand or technology has its own integration to manage communication with the outside of Gladys.
The image is up to date for those who want to try it out:
docker pull willde71/gladys-test:meteofrance_integration
So we have an OpenWeather integration that hasnât changed and a new Meteo France integration that allows you to retrieve weather data for France only without an API key. An optional API key allows you to obtain Meteo France vigilance maps.
The weather widget is fully switched to the new design. During the update, the dashboard will be updated.
The widget configuration changes a bit as you can now choose the weather data source:
- OpenWeather
- Meteo France
Here are the details of the possible configurations depending on the source. OpenWeather in the free version does not offer the same data as Meteo France. Hence the differences.
Here are some images
I also added a trigger and actions in the scenes:
A trigger on alert level
An action to retrieve Meteo France vigilance
Variables exposed for use in messages.
An action to send the Meteo France vigilance map
Example in Telegram
I was able to test it and itâs perfect 
I didnât find any bugs on my side 