LOCALSKY
Mode

Configure

Settings

Per-deployment config lives in Hardware + Logic. Per-device preferences (theme, units, nerd mode) are App-group items.

Hardware

Everything LocalSky talks to, and the yard it waters.

Logic

How LocalSky decides what to do with that hardware.

App

How LocalSky talks to you + per-browser preferences.

Configuration

Edit the selected section here. Changes save to your LocalSky config (and deploy on push).

Devices
?

Every controller, source, and sensor LocalSky uses, native or mirrored from Home Assistant. Add a source or controller here, or scan the LAN to adopt a gateway.

Read full doc →

Everything LocalSky talks to: controllers, weather sources, and the sensors they carry. Native devices are editable here; Home Assistant devices mirror in automatically. Guide →

Weather sources

Add weather coverage

Turn on a free service to cover your yard now. No station to buy, and the default for your region is already on.

Loading cloud weather services…

Add a device
or

Loading devices…

Which source provides each reading

You decide where each number comes from. Every reading has an ordered chain of sources: the top one reporting now wins, and if it goes quiet the next takes over. LocalSky sets a smart default order for your region; drag to make your own (your station for wind, a cloud service for rain, whatever fits). A source only leads while it is reporting, so a reading is never lost.

Forecast source

?

Where weather data comes in: a local station (Tempest, Ecowitt), a cloud service (Open-Meteo, WeatherKit, NWS), MQTT, or Home Assistant. When several report the same reading, the higher-priority source wins. Add and edit these in Devices.

Read full doc →

Pick which cloud service supplies your forecast: the daily and hourly outlook, rain expected tomorrow, and the evapotranspiration estimate the engine waters from. This is the main control if you have no local hardware. "Auto (follow the chain)" follows the chain of your forecast sources; Open-Meteo (free, no key) is the built-in default at the end of the chain.

Per-field priority and backup chain

?

Where weather data comes in: a local station (Tempest, Ecowitt), a cloud service (Open-Meteo, WeatherKit, NWS), MQTT, or Home Assistant. When several report the same reading, the higher-priority source wins. Add and edit these in Devices.

Read full doc →

Each reading has an ORDERED chain of sources. The top source that is reporting now wins; if it goes quiet the next takes over, so a reading is never lost. LocalSky sets a smart default order for your region (shown as "Automatic") and you can drag to make your own order ("Custom"). This is the main control whether or not you have local hardware: with cloud only, this is where you decide which service backs up which.

Soil moisture is bound per zone in the zone editor, not as a per-reading chain here.

Advanced: the raw chainmost people never open this

The region default order ("Automatic") comes from each source's per-region priority. The chains below are the explicit custom orders this page writes; a field not listed follows the default.

field_source_chains
(none, every field follows the region default)
forecast_provider
(auto, follow the chain)