Troubleshooting
This page covers common issues and how to resolve them.
City Not Found
You searched for a city but landed on the City Not Found page.
This page appears when the weather API cannot resolve the city name you entered — not when the city doesn't exist in the world.
Possible causes and fixes:
Check the spelling
Weather providers are strict about city names. Try the most common English spelling (e.g. Munich instead of München, Rome instead of Roma).
Use the autocomplete
Instead of pressing Enter with a freehand query, type the city name into the search bar and select a result from the dropdown. This ensures the exact canonical city name is sent to the weather API.
Search for a nearby city
Very small towns may not be indexed by weather providers. Try the name of the nearest large city or the regional capital instead.
Drop the country or region qualifier
If you searched for "Springfield, IL", try just "Springfield" and then select the correct one from the autocomplete dropdown.
Weather Data Looks Stale
The page loaded but the observation time in the description or the fetched-at time in the footer looks old.
Cache windowAll weather data is cached on the server for 5 minutes. Data will never be more than 5 minutes old under normal circumstances.
Provider lagThe upstream providers themselves update at different intervals (typically every 10–30 minutes).
Fix: Reload the page. If the fetched-at time is less than 5 minutes ago, the data is as fresh as possible. If it is older, the server cache may not have been invalidated — try again in a few minutes.
The Hourly Strip is Missing
The Hourly Forecast section is not showing on the weather page.
The hourly strip is intentionally hidden when the upstream provider returns no hourly data for a city. This is a known limitation of some smaller cities.
This happens when:
- The weather provider serving this city doesn't support hourly forecasts.
- The hourly API call timed out or failed. The page still loads successfully using the current and daily data — the hourly section is simply skipped.
There is nothing you need to do. The rest of the page (hero, 5-day forecast, and details grid) will still show correct data.
Something Went Wrong Page
You see a ⛈️ Something Went Wrong error page instead of weather data.
Click Try Again
Use the Try Again button on the error page. This re-runs the data fetch without a full browser reload.
Check your connection
Make sure your device has a working internet connection. The app fetches live data on every page load.
Try another city
Click Go Home to return to the search page and try a different city. If other cities load fine, the issue may be specific to that city's data source.
Wait and retry
If the error message mentions "API server may be offline", the upstream weather service may be experiencing an outage. These are usually brief — try again in a few minutes.
Search Dropdown Not Appearing
You're typing in the search bar but no results dropdown appears.
Query too shortResults appear after at least 1 character. Make sure you've typed something.
Search unavailableIf the city search service is temporarily down, the dropdown will show a message: "Search unavailable — press Enter to try anyway." You can still navigate by pressing Enter.
No matchesIf no cities match your query a "No cities found" message appears in the dropdown. Try a different or shorter query.
Temperatures Look Wrong
The temperatures on the page seem much higher or lower than expected.
Dekipi Weather uses metric units (°C) by default. If you're used to
Fahrenheit, a temperature of 22°C is approximately 72°F.
A quick conversion reference:
| °C | °F |
|---|---|
| 0 | 32 |
| 10 | 50 |
| 20 | 68 |
| 30 | 86 |
| 40 | 104 |
If the temperature looks genuinely wrong (e.g. −40°C in summer), the weather
provider may have returned data for the wrong city. Try searching again using
the autocomplete dropdown to ensure the correct city is selected.
URL / Sharing Issues
You shared a weather link but the recipient sees a different city or a 404.
City URLs use a slug format derived from the city name:
The safest way to get a shareable link is to navigate to the city using the search bar and copy the URL from your browser's address bar. This guarantees the slug is correctly encoded.