### System details

Intel Core i5-8400, NVIDIA GeForce RTX 2070, Omarchy 4.0.4-1, Linux 7.2.5-3-omarchy, Quickshell 0.3.1-1, Hyprland 0.56.2-2 (x86_64).

### What's wrong?

Observed on September 22, 2026, approximately 14:12 UTC. The weather panel combines a Tel Aviv location label with current conditions for Orient, Illinois.

## Actual behavior

With no ~/.local/state/omarchy/settings/weather.json, the weather panel displays Tel Aviv but shows 16°C, feels like 15°C, humidity 82%, and wind 9 km/h. The weather JSON actually describes Orient, Illinois, United States (37.918, -88.978). This also explains why automatic units initially selected Fahrenheit.

## Reproduction (network-dependent)

On the affected connection, run these independent requests:

```sh
curl -fsS 'https://wttr.in/?format=%l'
curl -fsS 'https://wttr.in/?format=j1'
curl -fsS 'https://wttr.in/Tel%20Aviv?format=j1'
```

The first returns `Tel Aviv, Tel Aviv, IL`. The second has `nearest_area` in Orient, Illinois and `temp_C: "16"`. The explicit Tel Aviv request returns coordinates 32.083, 34.783 in Israel and `temp_C: "28"`. Explicit coordinates 32.0853,34.7818 also return 28°C. Open-Meteo returns 28.5°C at those coordinates.

This is a reproduction of the live data path plus a matching user screenshot; no claim is made that all networks reproduce the provider discrepancy.

## Code behavior

In shell/plugins/panels/weather/Panel.qml:

- locationProc fetches `https://wttr.in/?format=%l` independently and sets wttrLocation.
- forecastProc fetches `https://wttr.in/?format=j1` in automatic mode.
- reportLocation prefers wttrLocation over the report’s nearest_area.
- Current conditions, country-based unit selection, and automatic forecast coordinates come from the JSON response.

The panel therefore combines a city label from one response with weather from another location. There is no consistency check. The reason the provider returns different locations for these two requests remains unconfirmed (for example provider geolocation or caching); the UI mismatch is confirmed.

## Expected behavior / possible fix

Display a location label derived from the same response as the displayed weather. Avoid letting the separate automatic-location label override the weather response’s nearest_area. This addresses the misleading label; correcting upstream IP geolocation is a separate problem.

## Workaround

Set explicit city coordinates:

```sh
omarchy weather location --set 'Tel Aviv' '32.0853,34.7818'
```

## Related discussion

https://github.com/omacom/omarchy/discussions/5707 was resolved by adding manual location selection. This report concerns the remaining mismatch between the auto-detected city label and the location supplying the displayed conditions.

## Captured evidence

The screenshot shows TEL AVIV, 16°C, feels like 15°C, wind 9 km/h, and humidity 82%. All four weather values match the Orient, Illinois response. The following excerpt is from the saved live responses, rather than synthetic test data:

```json
{
  "label_request_result": "Tel Aviv, Tel Aviv, IL",
  "weather_request_result": {
    "areaName": "Orient",
    "country": "United States of America",
    "region": "Illinois",
    "latitude": "37.918",
    "longitude": "-88.978",
    "temp_C": "16",
    "FeelsLikeC": "15",
    "humidity": "82",
    "windspeedKmph": "9",
    "observation_time": "01:08 PM"
  }
}
```