--- title: "CAP Alerts" description: "CAP Alerts is a Marketplace integration for Home Assistant. It has 83 installs sharing analytics, needs the vendor's cloud and was last updated November 4, 2026." canonical: "https://vulpo.app/integrations/marketplace/seevee-cap-alerts" url: "https://vulpo.app/integrations/marketplace/seevee-cap-alerts.md" last-updated: "2026-11-05" version: "1.4" --- # CAP Alerts > CAP Alerts is a Marketplace integration for Home Assistant. It has 83 installs sharing analytics, needs the vendor's cloud and was last updated November 4, 2026. From the [repository description](https://github.com/seevee/cap_alerts): > HA multi-region weather alerts integration: one entity per active weather alert, modeled on CAP fields. Solves the 16KB attribute limit. [Open in My Home Assistant](https://my.home-assistant.io/redirect/marketplace_repository/?owner=seevee&repository=cap_alerts&category=integration) On Home Assistant 2026.10 or older? [Open it in HACS](https://my.home-assistant.io/redirect/hacs_repository/?owner=seevee&repository=cap_alerts&category=integration) ## Supports - **Uses the vendor's cloud**: Needs an internet connection and an account with the vendor. - **Device triggers**: Its devices can start automations directly. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### NWS Zone - **Zone ID(s)**: Comma-separated UGC zone codes (e.g. OHC049,OHC035) ### NWS GPS Location - **GPS Coordinates**: Latitude,Longitude (e.g. 40.1234,-83.5678) ### NWS GPS Tracker - **Tracker Entity** Also asked when at the eccc gps tracker step. ### ECCC Province - **Province Code**: 2-letter province code (e.g. ON, BC, AB) ### ECCC GPS Location - **GPS Coordinates**: Latitude,Longitude (e.g. 43.6532,-79.3832) ### MeteoAlarm Country - **Country**: Select your country ### MeteoAlarm GPS Location - **GPS Coordinates**: Latitude,Longitude (e.g. 52.5200,13.4050). Filters by per-warning polygons; fails loud if the country does not publish geometry. ### After setup - **Polling interval (seconds)**: How often to check for new alerts (60–3600). ECCC: applies only when real-time streaming is off. - **API timeout (seconds)**: Per-request API timeout (5–120) - **Language**: Preferred alert language. ECCC: auto/en-CA/fr-CA. MeteoAlarm: auto plus 2-letter ISO codes. WMO: auto, or any BCP 47 tag the source publishes (e.g. zh-Hans); the source falls back to English when it does not carry your language. BBK: auto, de, de-LS (easy-read German), en or one of the app's other translations. GeoSphere Austria: de (the source text, default) or en (GeoSphere's translation). - **Real-time streaming**: Stream ECCC alerts over the NAAD real-time feed for near-instant updates (recommended). When off, alerts are polled from the GeoRSS feed on the polling interval. ECCC only. - **Alert feed source**: ECCC: which NAAD GeoRSS host(s) to fetch. 'auto' combines both feeds so no alert carried by only one is missed (recommended); Pelmorex has announced that the legacy host will retire, so pin a single host only to work around a specific feed issue. WMO: 'auto' reads the feed the weather service publishes itself and merges in the SWIC mirror where it still answers (recommended); SWIC retired the mirror for nearly every source in October 2026. 'mirror' or 'authority' reads one of them only. ECCC and WMO only. - **Exclude marine alerts**: Hide alerts issued for marine/water zones (boating, open water). NWS and ECCC only. - **Event types**: Which GDACS hazards to track. Filtering happens before any alert is fetched, so narrowing this also cuts the fetch cost. Leave every type selected (the default) to track them all, including hazards GDACS adds later. GDACS only. - **Minimum alert level**: GDACS: lowest alert level to fetch, Green (all), Orange, or Red, on GDACS's own impact scale; it decides which events are fetched, not how they are shown. Raise it to cut the volume of green earthquakes. Australia: lowest Australian Warning System tier to keep, All, Advice, Watch and Act or Emergency Warning; All also keeps the informational tiers below the ladder (planned burns, incidents with no warning). A warning with no tier at all, such as a WA hazmat warning, ranks by its own severity. GDACS and Australia only. - **Area codes (prefix match)**: Optional. Comma-separated area-code prefixes (e.g. 13,37). Keeps only alerts whose area codes start with one of them, on top of the location filter chosen at setup. Codes are hierarchical, so a shorter prefix covers a wider area (13 = Hebei, 1307 = Zhangjiakou). Matched against every code scheme the source publishes. Code lengths vary within a scheme, so pasting a full code may match nothing — prefer the leading digits. Leave empty to disable. Texts from the code of [seevee/cap\_alerts](https://github.com/seevee/cap_alerts). ## Entities - **Binary sensors**: Real-time stream - **Buttons**: Refresh - **Sensors**: Alert count, Last updated ## Troubleshooting - **Diagnostics**: Downloads a diagnostics file to attach to a bug report. ## From the README > Weather and hazard alerts for Home Assistant, one entity per active alert. > > Single-entity alert integrations pack every alert into one attribute blob and run into Home Assistant's 16 KB attribute limit. CAP Alerts gives each alert its own sensor. The state is a normalized severity, the attributes are the alert's CAP 1.2 fields, and an event fires when an alert is created, updated or removed. From the README of [seevee/cap\_alerts](https://github.com/seevee/cap_alerts#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Weather and alerts](https://vulpo.app/integrations/category/weather-and-alerts.md), Public warnings - Number: 83 installs sharing analytics; 13 GitHub stars - Connection: Needs the vendor's cloud - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: v0.7.1, last updated November 4, 2026 - Domain: `cap_alerts` - Source: - Issues: In Vulpo: Button card, Chart card, Apple Watch Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-11-05. Source: https://vulpo.app/integrations/marketplace/seevee-cap-alerts --- - HTML version of this page: https://vulpo.app/integrations/marketplace/seevee-cap-alerts - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml