Weather Is Missing From a Display

Weather Is Missing From a Display

This article explains why the weather block is missing from a board and how to get it back. It covers the two things that actually decide whether weather appears — whether your plan includes it, and whether it is switched on for that particular display — and what to do when weather appears but shows numbers that cannot be right.

If weather appears but shows the wrong city or the wrong unit, that is a different problem with a different fix. Read Weather Shows Wrong City or Units instead.

The one thing most people get wrong

Weather is a setting on each individual display, not on your account. Every display stores its own on/off state and its own temperature unit, which means one board in your lobby can show weather while another one, three metres away, shows none. This is by far the most common reason people report weather as broken: they switched it on once, months ago, on a display that is not the one they are looking at now.

So before anything else, check the display in front of you rather than your account in general.

Check the display first

Open Portal → Displays, click the display that is missing weather, and go to the Appearance tab. Under the section On the board you will find a field labelled Weather with an On/Off toggle. If it is Off, switch it On and save. Next to the toggle, once weather is on, a small °C / °F control appears — that is the only other weather option there is.

If the toggle is greyed out and shows the hint Not in your plan, the display is fine and your subscription is the blocker. Continue with the next section.

There is no Settings page in the portal any more. If you remember configuring weather somewhere under Settings, that path no longer exists; everything about how a board looks now lives in the display editor.

Check whether your plan includes weather

Weather is not part of Basic. It is included in Pro and in Premium.

You can confirm what your account currently has under Portal → Billing. In the list of entitlements there is a row called Weather, which reads either included or not included. The upgrade cards for Pro and Premium are on that same page, so you do not have to go looking elsewhere.

Two exceptions are worth knowing about, because the plan table alone will mislead you. Weather can be enabled for a single property by an administrator independently of the Stripe plan, so a Basic account can legitimately have weather. And complimentary accounts have every feature unlocked; the Billing page says so in place of the usual plan block.

While the entitlement is missing, the portal actively prevents weather from being switched on. The toggle in the display editor is disabled, and the older hotel settings endpoint forces the value back to off. If you have ever seen the switch appear to flip and then jump back, that is what happened.

After an upgrade, weather does not turn itself on

When you change plan, the entitlement is written to your account immediately — the Billing page will show weather as included the moment the change goes through. Nothing on your boards changes, though, and this surprises people.

The reason is that a display's weather setting is stored when the display is created, and it is created with whatever your account was entitled to at that moment. Every display you set up while on Basic therefore has weather stored as off. Upgrading grants the right to use the feature; it does not go back and rewrite settings you already saved.

After upgrading, open each display under Portal → Displays → Appearance → On the board and switch Weather to On. Displays you create after the upgrade will default to on.

The weather location is the display's airport

There is no weather location setting, no city field and no place to enter coordinates. The weather shown on a board is always the weather at that display's airport, looked up from the airport's IATA code.

If a board should show different weather, change which airport the display is assigned to: Portal → Displays → open the display → Appearance → Airport and time → Airport. Each display has exactly one airport, chosen from the airports on your account, which you manage under Portal → Airports.

This also explains a specific failure. If the airport's coordinates cannot be resolved — the code is neither in the built-in airport list nor in the airport database — no weather is returned at all, and the widget renders nothing rather than showing an error. There is no fallback to a nearby city or a larger airport. An unusual or newly added airport code is worth suspecting when weather is missing on one display and working on every other one.

Weather appears but the numbers look invented

This one has a concrete explanation. Weather comes from OpenWeatherMap. If the API key is missing or invalid, or the provider returns an error, or the request fails, the system does not display an error message — it quietly substitutes placeholder data.

Placeholder weather is designed to look plausible, which is exactly what makes it confusing. You can recognise it by these traits:

If you see that pattern, the problem is the weather provider connection on the server, not your display configuration, and there is nothing to fix in the portal. This is worth reporting to support rather than reconfiguring around.

Old data will not go away when you reload

Weather is cached on the server for 30 minutes, and the board refetches on the same 30-minute rhythm. The forecast part is cached for an hour.

Because the cache sits on the server and not in your browser, a hard reload does not help — you will be served the same up-to-30-minute-old response you already had. If the data is stale but otherwise correct, the only reliable remedy is to wait out the cache.

Checking the request yourself

If you want to see what the board is actually getting, open the display in a browser, press F12, go to the Network tab, filter for weather and reload the page. The board requests /api/weather/{IATA} with a units parameter.

That request has three possible outcomes:

Rate limiting is not part of this route, so a 429 here is not something you will encounter.

The Console tab is worth a look too. Weather failures are logged there under Weather API error: and Error fetching weather:.

A successful response contains the current temperature, the feels-like value, the day's minimum and maximum, a condition description and icon code, humidity, wind speed (in km/h with metric units, mph with imperial), pressure, visibility in kilometres, sunrise and sunset times, a three-day forecast, and the city and country. The forecast is always three days taken from the midday reading; it is not configurable and there is no setting to shorten or extend it. Condition texts are translated into the board's language where a translation exists, and otherwise shown as the provider wrote them.

If you are using the public API

The API-key endpoint GET /api/v1/weather/{IATA} is a separate route with its own errors, which are more informative than the display route's:

See API access for authentication and keys.

Turning weather off deliberately

If you would rather not show weather on a particular board, set the same Weather toggle to Off under Portal → Displays → Appearance → On the board. The display then makes no weather request at all — it does not fetch and hide the data, it simply never asks for it — and shows flights and your other content in the space.

Next steps