TerraLyra / How it works & sources

A CLOSER LOOK

Understand the information
behind your map.

Coverage, data freshness and the settings behind IGNIS. Explore the details when you need them.

Data sourcesPrivacyDashboard examples

FROM OBSERVATION TO CONTEXT

Separate observations. One useful picture.

01

Observe

Geographically relevant sources supply timestamped satellite detections.

02

Connect

IGNIS filters and groups related detections, retaining the evidence behind each incident.

03

Follow

Track nearby activity on your map and use Home Assistant events to trigger updates.

DATA WITH CONTEXT

Know your sources. Understand your coverage.

Sources are assigned to monitored locations according to their geographic coverage and your configured credentials.

MTG · MSG-IODC

EUMETSAT LSA SAF

Geostationary fire observations within the supported MTG and Indian Ocean coverage areas.

LSA SAF account requiredNominal products: 10–15 min
Source details

GOES-18 · GOES-19

NOAA GOES

Public fire and hot-spot observations for geographically supported locations in the Western Hemisphere.

No account requiredNominal full-disk products: 10 min
Source details

SENTINEL-3A · SENTINEL-3B

Sentinel-3

Public SLSTR observations between 82°S and 82°N, collected as the satellites pass over an area.

No account requiredPolar overpasses · Publication delay
Source details

VIIRS · MODIS

NASA FIRMS

Optional near-real-time satellite observations for monitored areas around the world.

Personal MAP_KEY requiredOverpass and provider dependent
Source details

Coverage is source-dependent. Product cadence is not a guaranteed alert time: clouds, overpasses, publication delays and outages affect the observations you receive.

READING SOURCE HEALTH

A successful download can contain older observations.

Retrieval and freshness

IGNIS distinguishes whether a source request succeeded from whether its retained data is within that provider’s freshness threshold. The download time and observation time can be different.

Source-health documentation

Empty is different from unavailable

A valid empty response means no matching observations were returned. It does not prove a recent satellite pass or an absence of fire. A failed refresh retains the last successful data with its status, rather than inventing a zero.

DIFFERENT KINDS OF INFORMATION

What is being observed? What are the conditions?

Active-fire observations

Satellite sensors detect thermal activity. IGNIS groups the available observations into incidents; independent sources may corroborate them. This is not an official fire confirmation.

Fire-risk forecasts

The European FRMv3 product describes conditions favourable to fire, with daily forecasts for today and the following nine days. Forecast entities use your configured Home location where coverage is supported.

Keep the observation in context.

Clouds, the satellite orbit, filtering and publication delays can all affect the result. No detection does not prove that no fire exists. Source health and the age of the observation matter alongside the incident itself.

LOOKING BACK

Incident history and report calendars.

Local incident history

IGNIS records observed incidents locally for up to 30 days, capped at 500 incidents. The calendar retains observation times, monitored places and contributing sources. This is the activity your installation recorded, not a complete historical fire archive.

Optional official-report context

Separate, opt-in calendars provide supported NSW RFS, Queensland QFD, BM OKF and GDACS reporting. Coverage, filtering and date meanings vary by source. Reports are not extra satellite detections or automatic confirmation of an incident.

NSW RFSQueensland QFDBM OKFGDACS

PRIVACY & DATA

Local processing, direct provider access.

No TerraLyra Cloud account is required. Incident processing, history and bundled place-name lookup run in Home Assistant. Provider requests still use the internet.

Sentinel-3 requests include monitoring-area bounding boxes. Optional NASA FIRMS requests include the requested area and your personal API key. Optional land-surface temperature requests include Home coordinates. Credentials are sent to the relevant provider where required.

Read the provider data-flow details

ADDITIONAL CONTEXT

Optional land-surface temperature

MTLST can add a satellite estimate of the radiative temperature of the ground. It is optional, coverage-dependent and different from shaded air temperature.

The integration is open source. Provider data retains its own attribution, usage terms and service limits.

OPTIONAL SETUP DETAILS

Make it part of your dashboard.

Add a map to your dashboard.

Add a Map card and select the terralyra_ignis geolocation source, or use this example in the card editor. Markers appear when recent incidents are available.

Map card · YAML
type: map
geo_location_sources:
  - source: terralyra_ignis
    label_mode: icon
hours_to_show: 24

Show your monitoring areas.

Add the monitoring-area source to show the radius around each enabled place. These circles represent your chosen search boundaries, not fire perimeters, evacuation zones or safe areas.

Map with monitoring areas · YAML
type: map
geo_location_sources:
  - source: terralyra_ignis
    label_mode: icon
  - source: terralyra_ignis_monitoring_areas
    label_mode: icon
    focus: false
cluster: false
hours_to_show: 24

Make an update your own.

Use the new-incident event in an automation. Replace the example notification action with the notification service for your device.

Notification example · YAML
alias: IGNIS — new fire notification
triggers:
  - trigger: event
    event_type: terralyra_ignis_new_fire
actions:
  - action: notify.mobile_app_your_phone
    data:
      title: "{{ trigger.event.data.notification_title }}"
      message: "{{ trigger.event.data.notification_message }}"
mode: queued

BRING THE CONTEXT HOME

Start with the places that matter to you.

Install IGNIS, choose a location and explore the observations available in your area.

Get started with IGNISHow it works & sources