Description
It would be great if ImmichFrame could support configuring the weather location using an OpenWeather City ID in addition to the existing latitude/longitude option.
Use Case
When using coordinates, the OpenWeather API sometimes returns the name of a nearby town instead of the actual municipality where the coordinates are located. Although the weather data itself is correct, the displayed location name can be misleading.
Details
For example:
Coordinates: 47.7628, 19.5409
Actual location: Erdőtarcsa, Hungary
OpenWeather response: "name": "Héhalom"
Using the OpenWeather City ID (for example, 7284908 for Erdőtarcsa) would ensure that the intended location name is displayed consistently.
Proposed solution
Add an optional configuration value, for example:
WeatherCityId: 7284908
If WeatherCityId is set, ImmichFrame could query:
/data/2.5/weather?id=
Otherwise, it would continue using the existing coordinate-based request (WeatherLatLong), maintaining full backward compatibility.
This would provide users with a reliable way to display the correct location name while preserving the current behavior for existing configurations.
Thanks for considering this feature!
Pre-Submission Checklist
Description
It would be great if ImmichFrame could support configuring the weather location using an OpenWeather City ID in addition to the existing latitude/longitude option.
Use Case
When using coordinates, the OpenWeather API sometimes returns the name of a nearby town instead of the actual municipality where the coordinates are located. Although the weather data itself is correct, the displayed location name can be misleading.
Details
For example:
Coordinates: 47.7628, 19.5409
Actual location: Erdőtarcsa, Hungary
OpenWeather response: "name": "Héhalom"
Using the OpenWeather City ID (for example, 7284908 for Erdőtarcsa) would ensure that the intended location name is displayed consistently.
Proposed solution
Add an optional configuration value, for example:
WeatherCityId: 7284908
If WeatherCityId is set, ImmichFrame could query:
/data/2.5/weather?id=
Otherwise, it would continue using the existing coordinate-based request (WeatherLatLong), maintaining full backward compatibility.
This would provide users with a reliable way to display the correct location name while preserving the current behavior for existing configurations.
Thanks for considering this feature!
Pre-Submission Checklist
This is a feature request and not a bug report
I have checked for related issues and checked the documentation