Which weather apps are supported?

[stacsk]

I tried Breezy Weather but the widget shows --.

[luantak]

The temperature on the home screen doesn't depend on an external weather app.

You need to have Internet, the location permission granted to fokus, and location turned on.

If it doesn't work then please export your logs in settings and attach them here.

[luantak]

@luames please see if you find anything as to why the weather on the home screen doesn't work for this user

[luames]

I found a possible cause in Fokus's location handling, but the attached logs don't establish which step is failing on this phone. This isn't a Breezy Weather compatibility problem.

In 1.9.7, Fokus only reads Android's last-known locations. It checks network, GPS and passive location, then falls back to a location previously saved by Fokus. It never requests a fresh location. If none is available, it skips the weather request entirely and displays --, even with location permission granted and location switched on.

The configuration confirms that home weather is enabled and AQI is off. The diagnostic export has no crash or weather-specific error identifying the cause. Unfortunately, the location and weather code silently catches exceptions, and the weather repository also returns no result for unsuccessful HTTP responses. That means these logs cannot distinguish a missing location from a failed Open-Meteo request. The configuration export intentionally excludes the saved weather location, so its absence there doesn't prove anything either.

@stacsk, could you try this comparison?

1. In Android's app settings, check that Fokus itself has location access while in use, and that the phone's Location switch is on.
2. Open OsmAnd or another maps app and use its locate-me button. Wait until it finds your current position, then return to Fokus and give it about 20 seconds. Returning to the home screen triggers another weather attempt. If the temperature appears, that strongly points to the cached-location problem above.
3. If it still shows --, open this Open-Meteo test URL on the same phone and connection. It uses Berlin, not your location. Does it show JSON containing temperature_2m, or an error? If you use a VPN, filtering DNS or a firewall, compare with it temporarily disabled if you're comfortable doing so.

The test request returned HTTP 200 with the expected fields from my environment, but that doesn't establish connectivity from your phone. Please report whether the maps step changes anything and whether the test URL loads. Those results will help separate location acquisition from API access before choosing a fix.

[luantak]

@stacsk please try this suggestion

@luames please file a pr for requesting a fresh location

[stacsk]

@luames

1. check that Fokus itself has location access
   It has permission.

It has permission.

2. Open OsmAnd...

Tried, no change. OsmAnd shows my current location withhout problem.

3. Does it show JSON containing temperature_2m, or an error?

It shows temperature_2m. I have also disabled my pi hole, tried connecting to another network. No change.

[luames]

Opened #261 to request a current location before falling back to cached coordinates. It uses the existing approximate-location permission, waits at most ten seconds, and cancels the Android request on timeout or coroutine cancellation. No additional permission or Play Services dependency is needed.

All 494 unit tests passed, including seven new location tests, and Android CI built the APK successfully. An API 35 emulator smoke test verified request cleanup and weather display through the cached fallback. The PR documents the unrelated lint errors and the security scan that could not complete because its provider returned rate-limit errors.

@stacsk, your comparison is useful: the test URL works, but locating in OsmAnd did not change the widget. This PR removes the cache-only limitation, but that does not yet establish the cause on your phone or prove it will fix your case.

[luantak]

@stacsk please check if this debug build https://github.com/luantak/FokusLauncher/actions/runs/39048373251?pr=261 solves your issue (installs as Fokus Debug alongside your existing install)

[stacsk]

sadly it's still the same :/

fokus-launcher-diagnostic debug.txt