[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-82181":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":16,"stars30d":17,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":18,"rankGlobal":10,"rankLanguage":10,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":22,"hasPages":20,"topics":23,"createdAt":10,"pushedAt":34,"updatedAt":35,"readmeContent":36,"aiSummary":37,"trendingCount":15,"starSnapshotCount":15,"syncStatus":16,"lastSyncTime":38,"discoverSource":39},82181,"tide-wise","TheWillMiller\u002Ftide-wise","TheWillMiller","Home Assistant dashboard card for NOAA tides and fishing bite-window scoring.","",null,"JavaScript",28,1,4,0,2,6,42.5,"Other",false,"main",true,[24,25,26,27,28,29,30,31,32,33],"custom-card","dashboard","fishing","hacs","home-assistant","lovelace","noaa","tide","tides","weather","2026-06-06 12:49:10","2026-06-07 05:20:47","# TideWise\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002FTheWillMiller\u002Ftide-wise\u002Fmain\u002Ftidewise-icon.png\" alt=\"TideWise wave icon\" width=\"96\">\n\u003C\u002Fp>\n\n[![GitHub release](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fv\u002Frelease\u002FTheWillMiller\u002Ftide-wise)](https:\u002F\u002Fgithub.com\u002FTheWillMiller\u002Ftide-wise\u002Freleases)\n[![Validate](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Factions\u002Fworkflow\u002Fstatus\u002FTheWillMiller\u002Ftide-wise\u002Fvalidate.yml?branch=main&label=validate)](https:\u002F\u002Fgithub.com\u002FTheWillMiller\u002Ftide-wise\u002Factions\u002Fworkflows\u002Fvalidate.yml)\n[![GitHub stars](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002FTheWillMiller\u002Ftide-wise?label=stars)](https:\u002F\u002Fgithub.com\u002FTheWillMiller\u002Ftide-wise\u002Fstargazers)\n\n\n**Latest release:** `v0.7.2`\n\nTideWise is a Home Assistant dashboard (Lovelace) custom card for tide predictions, current tide height, next high\u002Flow tides, and optional fishing bite-window scoring. The default provider is NOAA CO-OPS, with early Canada CHS\u002FDFO support and experimental UKHO Admiralty support available for testing.\n\n## Screenshots\n\n### Main TideWise Card\n\n\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002FTheWillMiller\u002Ftide-wise\u002Fmain\u002FTIDE_CARD.png\" alt=\"TideWise card showing current tide, tide chart, moon phase, and fishing window\" width=\"720\">\n\n### Theme Modes\n\nTideWise keeps its ocean-glass style by default. It can also follow Home Assistant theme colors more closely with `theme_mode: auto`.\n\n\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002FTheWillMiller\u002Ftide-wise\u002Fmain\u002FTIDE_CARD_THEME_TIDEWISE.png\" alt=\"TideWise default ocean-glass theme mode\" width=\"720\">\n\n\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002FTheWillMiller\u002Ftide-wise\u002Fmain\u002FTIDE_CARD_THEME_AUTO_DARK.png\" alt=\"TideWise Home Assistant theme mode on a dark dashboard\" width=\"720\">\n\n### NOAA Station Picker\n\n\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002FTheWillMiller\u002Ftide-wise\u002Fmain\u002FTideStations.png\" alt=\"TideWise NOAA station picker in the visual editor\" width=\"720\">\n\n### Visual Editor\n\n\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002FTheWillMiller\u002Ftide-wise\u002Fmain\u002FThemeEditor.png\" alt=\"TideWise visual editor showing the theme selector and live preview\" width=\"720\">\n\nIt combines tide data with local Home Assistant entities such as weather, wind, water temperature, surf height, pressure, rain, and rip current risk. Missing optional entities are allowed; TideWise falls back to neutral scoring where possible.\n\n> **Beta notice:** TideWise is still early beta software. Please expect occasional layout issues, missing-data fallbacks, and station-specific quirks while testing.\n\n## Beta Feedback\n\nTideWise is in beta. If it works for your setup, please consider starring the repo so I can gauge interest and so you can follow development:\n\n[Star TideWise on GitHub](https:\u002F\u002Fgithub.com\u002FTheWillMiller\u002Ftide-wise)\n\nIf you run into issues or want to confirm your station works, please open one of these quick reports:\n\n- [Beta Install Report](https:\u002F\u002Fgithub.com\u002FTheWillMiller\u002Ftide-wise\u002Fissues\u002Fnew?template=beta-install-report.yml)\n- [Works For Me \u002F Confirmed Station](https:\u002F\u002Fgithub.com\u002FTheWillMiller\u002Ftide-wise\u002Fissues\u002Fnew?template=works-for-me-confirmed-station.yml)\n\nHelpful details include Home Assistant version, HACS version, TideWise version, browser\u002Fdevice, NOAA station ID, and a screenshot or console error if something broke.\n\n## Features\n\n- NOAA tide predictions using a configurable station ID\n- Early Canada CHS\u002FDFO water-level prediction and forecast support\n- Experimental UKHO Admiralty tide support with a user-provided UKHO API key\n- Current interpolated tide height\n- Water temperature display when available\n- Wind display when available\n- Next high and low tide\n- 24-hour tide chart\n- High\u002Flow fallback for NOAA stations without full interval predictions\n- Visual editor support\n- Opt-in Home Assistant theme color support with `theme_mode: auto`\n- 50-station NOAA preset picker plus custom NOAA station ID\n- Canada region picker with CHS station discovery\n- UKHO station picker and API key field\n- Optional fishing bite-window score\n- Fishing modes for general, surf, inlet, flounder, trout\u002Fredfish, and sheepshead use\n- Optional NOAA\u002FNWS public data fetching\n- Optional Home Assistant entity overrides for weather, wind, water temperature, surf height, pressure, rain, and rip current risk\n- Safety-aware fishing display that can cap the current score without globally flattening future bite windows\n- Hidden YAML-only debug panel for troubleshooting fishing inputs, score components, caps, and data sources\n- Legacy support for `custom:cherry-grove-tides-card`\n\n## Installation\n\n### Recommended: HACS Custom Repository\n\n[![Open TideWise in HACS](https:\u002F\u002Fmy.home-assistant.io\u002Fbadges\u002Fhacs_repository.svg)](https:\u002F\u002Fmy.home-assistant.io\u002Fredirect\u002Fhacs_repository\u002F?owner=TheWillMiller&repository=tide-wise&category=plugin)\n\nTideWise is not yet listed in the default\u002Fsearchable HACS store. Until it is accepted into the default HACS list, install it as a custom HACS repository.\n\n1. Open **HACS** in Home Assistant.\n2. Open the three-dot menu in the top right.\n3. Choose **Custom repositories**.\n4. Add this repository URL:\n\n```text\nhttps:\u002F\u002Fgithub.com\u002FTheWillMiller\u002Ftide-wise\n```\n\n5. For category, choose **Dashboard**.\n\n   If your HACS version uses older wording, choose the dashboard\u002Fcard\u002Ffrontend\u002Fplugin-style option.\n\n6. Install **TideWise**.\n7. Refresh Home Assistant.\n\nA hard browser refresh is recommended after installing or updating:\n\n- Windows\u002FLinux: `Ctrl + F5`\n- Mac: `Cmd + Shift + R`\n\nThen add the card from your dashboard editor:\n\n1. Edit your dashboard.\n2. Add a new card.\n3. Search for **TideWise**.\n4. Open the visual editor.\n5. Select a NOAA station or enter a custom station ID.\n6. Save.\n\n### Manual Install\n\n1. Download or copy `tidewise-card.js`.\n2. Place it in your Home Assistant `www` directory.\n3. Add it as a dashboard resource:\n\n```yaml\nurl: \u002Flocal\u002Ftidewise-card.js\ntype: module\n```\n\n4. Refresh Home Assistant and hard-refresh your browser.\n5. Add the card to a dashboard.\n\n### Test From GitHub CDN\n\nFor quick testing before installing locally, you can add this dashboard resource:\n\n```yaml\nurl: https:\u002F\u002Fcdn.jsdelivr.net\u002Fgh\u002FTheWillMiller\u002Ftide-wise@v0.7.2\u002Ftidewise-card.js\ntype: module\n```\n\nAfter changing resources, refresh Home Assistant and hard-refresh the browser tab.\n\n> CDN testing is not the preferred long-term install method. HACS is recommended for normal use.\n\n## Quick Start\n\n```yaml\ntype: custom:tidewise-card\ntitle: Local Tides\nstation: \"8661070\"\nunits: english\nmode: general\nauto_sources: true\nauto_surf_forecast: true\ngrid_options:\n  rows: full\n  columns: 18\n```\n\n## Minimal Config\n\n```yaml\ntype: custom:tidewise-card\ntitle: Local Tides\nstation: \"8661070\"\nunits: english\nmode: general\n```\n\n## Cherry Grove Example\n\n```yaml\ntype: custom:tidewise-card\ntitle: Cherry Grove Tides\nstation: \"8661070\"\nunits: english\nmode: inlet\nauto_sources: true\nauto_surf_forecast: true\nweather_entity: weather.nws_33_8552645_78_6761264_kmyr\nwater_temp_entity: sensor.noaa_surf_water_temperature\nwave_height_entity: sensor.noaa_surf_surf_height\nrip_current_risk_entity: sensor.noaa_surf_rip_current_risk\nwind_speed_entity: sensor.noaa_weather_wind_speed\nwind_direction_entity: sensor.noaa_weather_wind_direction\npressure_entity: sensor.noaa_weather_barometric_pressure\nrain_today_entity: sensor.rain_sensor_rain_last_24h\ngrid_options:\n  rows: full\n  columns: 18\n```\n\n## Tide-Only Config\n\n```yaml\ntype: custom:tidewise-card\ntitle: Local Tides\nstation: \"8661070\"\nunits: english\nshow_fishing_score: false\ngrid_options:\n  rows: full\n  columns: 18\n```\n\n## Canada CHS Example\n\nCanada support uses the Canadian Hydrographic Service \u002F DFO IWLS API. The visual editor can load Canadian regions and station lists, so most users should choose a station from the editor instead of writing the object ID by hand.\n\n```yaml\ntype: custom:tidewise-card\ntitle: Pointe-du-Chene Tides\nprovider: chs_iwls\nca_region: atlantic\nca_station: \"64b6e5ec8027cb190816a0c0\"\nca_station_code: \"01804\"\nunits: metric\nmode: general\nauto_sources: false\ngrid_options:\n  rows: full\n  columns: 18\n```\n\nCanadian tide predictions can render the tide chart and high\u002Flow times. NOAA\u002FNWS auto sources are US-focused, so Canadian fishing inputs such as weather, wind, surf, water temperature, and pressure should come from Home Assistant entities when available.\n\n## UK UKHO Example\n\nUK support uses the UKHO Admiralty API directly from the browser. Each user must provide their own UKHO API key. This is experimental because browser-side API calls depend on UKHO\u002FAzure allowing CORS from Home Assistant dashboards.\n\n```yaml\ntype: custom:tidewise-card\ntitle: Portsmouth Tides\nprovider: ukho\nukho_station: \"0390\"\nukho_api_key: \"YOUR_UKHO_API_KEY\"\nunits: metric\nmode: general\nauto_sources: false\nauto_surf_forecast: false\ngrid_options:\n  rows: full\n  columns: 18\n```\n\nUKHO tide heights are provided in metres. TideWise displays them as metres with `units: metric`, or converts them to feet with `units: english`.\n\n> **UKHO key note:** This is a frontend dashboard card, so the API key is stored in your dashboard configuration and is visible to browsers\u002Fusers who can inspect that dashboard. Use your own UKHO key and follow UKHO's API terms.\n\n## Dashboard Size\n\nTideWise is a dense chart card. In Home Assistant section\u002Fgrid dashboards, give it enough horizontal space:\n\n```yaml\ngrid_options:\n  rows: full\n  columns: 18\n```\n\nOn narrower dashboards, use:\n\n```yaml\ngrid_options:\n  rows: full\n  columns: full\n```\n\n## Theme Support\n\nTideWise defaults to its built-in ocean-glass styling:\n\n```yaml\ntheme_mode: tidewise\n```\n\nTo make the card follow Home Assistant theme colors more closely, use:\n\n```yaml\ntheme_mode: auto\n```\n\nThe visual editor includes a **Theme** dropdown for this setting. Theme mode only changes the card styling; it does not change tide fetching, NOAA\u002FNWS data, or fishing score behavior.\n\n## Visual Editor\n\nTideWise includes a Home Assistant visual editor. When adding the card from the dashboard editor, you can:\n\n- Choose 50 common NOAA tide stations from a dropdown\n- Enter a custom NOAA station ID\n- Switch to Canada CHS \u002F DFO and choose a region-fed station dropdown\n- Switch to UK UKHO Admiralty, choose a UKHO station, and enter your own UKHO API key\n- Set fishing\u002Fforecast latitude and longitude\n- Fill coordinates from the selected NOAA station\n- Use your Home Assistant home latitude\u002Flongitude when that matches your fishing area\n- Select English or metric units\n- Select fishing mode\n- Choose TideWise styling or Home Assistant theme colors\n- Enable or disable fishing score\n- Enable or disable public NOAA\u002FNWS auto sources\n- Enable or disable NWS surf\u002Frip forecast parsing\n- Set the recommended dashboard size\n\nThe station dropdown is a 50-station starter list, not a complete NOAA station database. If your station is not listed, choose **Custom station ID** and paste the NOAA CO-OPS station ID.\n\nLatitude and longitude are used for fishing-score context such as NWS forecast lookup, surf\u002Frip forecast lookup, and moon\u002Fsolunar timing. For best results, use coordinates near the tide gauge, beach, inlet, or fishing area.\n\n## Auto Sources\n\nFor NOAA\u002FUS cards, TideWise can fetch extra public NOAA\u002FNWS data directly from the browser when `auto_sources` is enabled:\n\n- NOAA CO-OPS water temperature, wind, and air pressure where the selected station supports those products\n- NWS hourly forecast weather and wind from latitude\u002Flongitude\n- NWS Surf Zone Forecast text for surf height, rip current risk, and water temperature where the local forecast office issues an SRF product\n\nManual Home Assistant entities take priority. If a manual entity is configured, TideWise uses it instead of the auto-fetched value.\n\nSurf Zone Forecasts are text products and vary by NWS office. TideWise parses common formats such as:\n\n- `high rip current risk`\n- `surf height 2 to 4 feet`\n- `water temperature in the mid 80s`\n\nSome locations may still show unknown surf or rip data. Manual entities or dedicated integrations remain the most reliable override.\n\nRecent rainfall totals are not yet reliably auto-filled. They work best through a local rain sensor or Home Assistant weather integration.\n\n## Fishing Score\n\nThe fishing score is advisory only. It is intended to give a quick glance at likely better and worse bite windows.\n\nDepending on available data, TideWise may consider:\n\n- Tide movement\n- Tide direction\n- Time to next high\u002Flow tide\n- Current tide height\n- Moon\u002Fsolunar timing\n- Time of day\n- Weather condition\n- Wind speed\n- Wind direction\n- Water temperature\n- Surf\u002Fwave height\n- Rip current risk\n- Pressure\n- Pressure trend\n- Rainfall\u002Frunoff\n\nWhen optional data is missing, TideWise falls back to the data it has available.\n\nCurrent safety conditions such as high rip current risk can cap the **Now** score while still allowing the future curve to show improving bite potential. This is why a card may show **Slow now** with a better bite window later in the day.\n\n## Hidden Debug Panel\n\nFor troubleshooting, TideWise includes a YAML-only debug panel. It is hidden from normal users and is not exposed in the visual editor.\n\nEnable it manually only when diagnosing a station, data source, or fishing score:\n\n```yaml\ndebug:\n  enabled: true\n  panel: true\n```\n\nThe debug panel is collapsed by default and scrolls internally when expanded. It shows the current\u002FNow score target, future curve mode, source availability, component weights, moon multiplier, safety caps, final current score, display score, and whether the future curve is globally capped.\n\n## Configuration\n\n| Option | Required | Default | Description |\n| --- | --- | --- | --- |\n| `type` | Yes |  | Use `custom:tidewise-card`. The legacy `custom:cherry-grove-tides-card` alias also works. |\n| `title` | No | `TideWise` | Card title. |\n| `provider` | No | `noaa_coops` | Tide data provider. Use `noaa_coops` for US NOAA CO-OPS, `chs_iwls` for early Canada CHS\u002FDFO support, or `ukho` for experimental UKHO Admiralty support. |\n| `station` | Required for NOAA |  | NOAA tides and currents station ID. |\n| `ca_region` | No | `atlantic` | Canada station picker region: `atlantic`, `great_lakes`, `quebec`, `pacific`, or `arctic`. |\n| `ca_station` | Required for Canada |  | Canadian CHS\u002FDFO IWLS station object ID. Prefer choosing it from the visual editor. |\n| `ca_station_code` | No |  | Optional Canadian CHS display code. |\n| `ukho_station` | Required for UKHO | `0390` | UKHO Admiralty tide station ID. Prefer choosing it from the visual editor. |\n| `ukho_api_key` | Required for UKHO |  | User-provided UKHO Admiralty API key. This is stored in dashboard config and visible to browsers that can load the card. |\n| `units` | No | `english` | Display units. Usually `english` or `metric`. Canadian CHS and UKHO data are metric and are converted to feet when `english` is selected. |\n| `mode` | No | `general` | Fishing score mode: `general`, `surf`, `inlet`, `flounder`, `trout_redfish`, or `sheepshead`. |\n| `theme_mode` | No | `tidewise` | Visual style mode. Use `tidewise` for the default ocean-glass look or `auto` to follow Home Assistant theme colors more closely. |\n| `show_fishing_score` | No | `true` | Set to `false` for a tide-only card. |\n| `auto_sources` | No | `true` | Fetch public NOAA\u002FNWS weather and marine observations directly where available. US-focused; non-US providers should use Home Assistant entities for fishing context. |\n| `auto_surf_forecast` | No | `true` | Try to parse NWS Surf Zone Forecast text for surf height, rip current risk, and water temperature. US-focused. |\n| `srf_region` | No |  | Optional internal grouping for NWS-listed Surf Zone Forecast offices. Usually set by the visual editor. |\n| `nws_office` | No | Auto from NWS point metadata | Optional NWS office code such as `ILM`, `CHS`, or `SGX` for Surf Zone Forecast products. |\n| `beach_state` | No |  | Optional beach forecast state used by the visual editor. |\n| `beach_area` | No |  | Optional NWS beach\u002Fsurf area preset used for rip risk and surf context. |\n| `surf_zone` | No | Auto from NWS point metadata | Optional NWS surf\u002Fbeach forecast zone such as `SCZ054`; overrides coordinate-derived zone for SRF parsing. |\n| `latitude` | No | Home Assistant home latitude, then Cherry Grove fallback | Fishing\u002Fforecast latitude for NWS lookup and moon\u002Fsolunar scoring. |\n| `longitude` | No | Home Assistant home longitude, then Cherry Grove fallback | Fishing\u002Fforecast longitude for NWS lookup and moon\u002Fsolunar scoring. |\n| `weather_entity` | No | First available weather entity | Weather condition source. |\n| `water_temp_entity` | No |  | Water temperature sensor. Fahrenheit and Celsius are supported. |\n| `wave_height_entity` | No |  | Wave\u002Fsurf height sensor. Feet and meters are supported. |\n| `rip_current_risk_entity` | No |  | Rip current risk sensor. |\n| `unsafe_to_swim_entity` | No |  | Boolean or text entity for unsafe surf\u002Fswim conditions. |\n| `wind_speed_entity` | No | Weather attribute fallback | Wind speed sensor. mph, km\u002Fh, m\u002Fs, and knots are supported. |\n| `wind_direction_entity` | No | Weather attribute fallback | Wind bearing in degrees. |\n| `pressure_entity` | No | Weather attribute fallback | Barometric pressure. hPa and inHg are supported. |\n| `pressure_trend_entity` | No |  | Pressure trend entity. |\n| `rain_today_entity` | No |  | Rainfall in the last 24 hours. Inches and mm are supported. |\n| `debug` | No | disabled | Hidden troubleshooting object. Use `debug: { enabled: true, panel: true }` only when diagnosing score\u002Fdata issues. Not available in the visual editor. |\n\n## Finding a NOAA Station\n\nUse a NOAA tides and currents station ID near your location. TideWise uses the NOAA CO-OPS data API, so station IDs must support tide predictions.\n\nIf your station does not work, try a nearby NOAA station that supports tide predictions.\n\n## Finding a Canadian Station\n\nSet **Tide provider** to **Canada CHS \u002F DFO** in the visual editor, choose a Canadian region, then choose a CHS water-level station from the station dropdown. Canadian Great Lakes stations are under **Great Lakes \u002F Ontario**.\n\nCanada support uses CHS\u002FDFO IWLS water-level predictions where available. Some Great Lakes stations publish water-level forecasts instead, so TideWise falls back from `wlp` predictions to `wlf` forecasts when needed. The Great Lakes picker includes a small official CHS seed list because those stations may not appear in the CHS bulk station API. Selected stations may still need testing because CHS availability can vary by station and forecast window.\n\nNOAA\u002FNWS auto sources are US-focused. For Canadian fishing context, configure Home Assistant entities for weather, wind, pressure, water temperature, surf, rain, or safety\u002Frip-risk data when available.\n\n## Finding a UKHO Station\n\nSet **Tide provider** to **UK UKHO Admiralty** in the visual editor, choose a UKHO station, then enter your own UKHO API key. The key is required because TideWise calls the UKHO API directly from the browser.\n\nUKHO support is experimental. It can render UK tide heights and high\u002Flow events where the selected station, API key, subscription tier, and browser access allow it. Weather, wind, water temperature, surf, rain, pressure, and fishing safety context should come from Home Assistant entities for UK cards.\n\nBecause this is a frontend card, the UKHO key is not secret storage. Anyone with access to inspect the dashboard\u002Fbrowser traffic can see it. If UKHO blocks browser-side CORS for your subscription, TideWise will need a future Home Assistant\u002Fbackend helper for UKHO rather than a pure Lovelace-only fetch.\n\n## Beach \u002F Surf Forecast Area\n\nFor US surf and rip-current context, TideWise can use a beach forecast area instead of relying only on latitude\u002Flongitude. The tide station still controls the tide curve, but the beach area controls NWS Surf Zone Forecast scoping for rip risk and surf height.\n\nTideWise includes a guided list of **NWS-listed SRF offices** for areas where the National Weather Service publishes Surf Zone Forecast products. This is not the same as every U.S. coastal county; some coastal offices may handle beach hazards through other products such as Hazardous Weather Outlooks.\n\nThe visual editor keeps this simple: choose a **State**, then choose the closest **Area**. Where TideWise has an exact beach\u002Fsurf-zone preset, that area is used. Otherwise, the area maps to the closest NWS-listed SRF office and TideWise still uses your coordinates for local forecast context.\n\nThe first built-in precise beach-area set covers the NWS Wilmington, NC office beaches for the Grand Strand and nearby NC\u002FSC beaches. Broader NWS-listed SRF offices are available for other supported states\u002Fregions, and more precise beach-zone presets can be added as confirmed.\n\nExample:\n\n```yaml\nsrf_region: Atlantic\u002FGulf\u002FCaribbean\nbeach_state: SC\nbeach_area: sc-horry\nnws_office: ILM\nsurf_zone: SCZ054\n```\n\n## Troubleshooting\n\nIf TideWise works for you after troubleshooting, please consider starring the repo or opening a Works For Me \u002F Confirmed Station report. If it breaks, a Beta Install Report with your versions and station ID helps a lot.\n\n### TideWise does not show in the card picker\n\n1. Confirm TideWise is installed in HACS.\n2. Hard-refresh the browser.\n3. Restart Home Assistant if needed.\n4. Check that the card resource exists.\n5. Open the browser console and look for TideWise errors.\n\n### HACS shows an old README or old version\n\nHACS may cache repository metadata.\n\nTry:\n\n1. Open HACS.\n2. Open TideWise.\n3. Open the three-dot menu.\n4. Select **Redownload**.\n5. Choose the latest version.\n6. Hard-refresh your browser.\n\nIf HACS still shows an old README, the installed card file may still be current while the HACS display cache is stale.\n\nIf HACS shows a short value like `214b6c2` instead of `v0.7.2`, that is a GitHub commit hash. HACS shows commit hashes when a repository has tags but no full GitHub Release yet. Publishing a full GitHub Release makes HACS show the release version instead.\n\n### Card does not show up\n\n1. Confirm TideWise is installed.\n2. Confirm the dashboard resource exists.\n3. Hard-refresh the browser.\n4. Redownload the latest release in HACS.\n5. Restart Home Assistant if needed.\n6. Check the browser console for `tidewise-card.js` loading errors.\n\n### Visual editor does not show\n\n1. Confirm the latest TideWise JS is loaded.\n2. Hard-refresh the browser.\n3. Redownload the latest HACS release.\n4. Check the browser console for custom element errors.\n\n### Tide data unavailable\n\n1. Verify the NOAA station ID.\n2. Try a known preset station.\n3. Confirm your browser\u002FHome Assistant can reach NOAA.\n4. Open the browser console and check for network or station errors.\n\n### Fishing score looks limited\n\nThis usually means optional weather, wind, water temperature, surf, pressure, rain, or rip current data is unavailable.\n\nThe card should still work, but the score may be based on fewer inputs.\n\nFor deeper troubleshooting, temporarily enable the hidden debug panel in YAML:\n\n```yaml\ndebug:\n  enabled: true\n  panel: true\n```\n\nRemove it again after testing.\n\n## Privacy\n\nTideWise does not include telemetry, tracking pixels, external analytics, or phone-home behavior.\n\nWhen `auto_sources` or `auto_surf_forecast` are enabled, the card fetches the public NOAA\u002FNWS data needed to render the configured dashboard card. Adoption tracking is based only on GitHub-native signals such as stars, issues, release activity, and tester reports.\n\nMaintainer notes for GitHub-native adoption signals are in [PROJECT_INSIGHTS.md](PROJECT_INSIGHTS.md).\n\n## Beta Tester Checklist\n\nThe full checklist is also available in [BETA_TESTER_CHECKLIST.md](BETA_TESTER_CHECKLIST.md).\n\nIf you are testing TideWise, please report:\n\n- Home Assistant version\n- HACS version\n- TideWise version\n- Browser\u002Fdevice\n- NOAA station ID used\n- Whether you installed from HACS custom repository, manual resource, or CDN\n- Screenshot of any layout issue\n- Browser console errors, if any\n- Whether the issue happens after a hard refresh\n\nBasic test steps:\n\n1. Install TideWise from HACS custom repository.\n2. Add the card from the dashboard card picker.\n3. Open the visual editor.\n4. Select a preset station.\n5. Save.\n6. Refresh the dashboard.\n7. Confirm the card still loads.\n8. Change fishing mode.\n9. Save and refresh again.\n10. Test on desktop and phone.\n11. Test with missing optional entities.\n12. Screenshot or copy any errors.\n\n## Safety\n\nTideWise is informational. It is not a marine safety, navigation, emergency, or surf safety tool.\n\nAlways check official local forecasts, marine advisories, beach warnings, and on-site conditions before entering the water or boating.\n\nDo not use TideWise for navigation, hazardous surf decisions, boating safety, swimming safety, or life-safety decisions.\n\n## License\n\nFree for personal and non-commercial use under PolyForm Noncommercial License 1.0.0.\n\nCommercial use requires separate written permission.\n\n## Development\n\nThe distributable card is:\n\n```text\ntidewise-card.js\n```\n\nFor HACS default repository submission, TideWise is a dashboard\u002Fcustom card. HACS validation\u002Fsubmission uses the `plugin` category internally for dashboard plugins.\n\nRun the local syntax check before opening a pull request:\n\n```bash\nnpm run check\n```\n\n## Roadmap\n\nPlanned areas for future releases:\n\n- Map-based fishing\u002Fforecast coordinate picker\n- More station presets and station discovery improvements\n- International tide-provider research for non-NOAA regions\n- Further fishing outlook calibration based on tester feedback\n- Additional mobile layout polish\n\n### International Provider Notes\n\nTideWise uses explicit provider adapters instead of stretching NOAA-specific code paths. NOAA CO-OPS remains the default provider, Canada CHS\u002FDFO is available for early testing, and UKHO Admiralty support is experimental with a user-provided API key.\n\nThe Environment Agency flood-monitoring API can be useful for rivers, flood gauges, and some observed level stations, but it should not be treated as the main UK tide-prediction source for TideWise.\n\nThe National Tidal and Sea Level Facility is a stronger UK research candidate because it documents the UK National Tide Gauge Network and publishes tidal predictions for selected UK and Ireland ports. It still needs licensing, CORS, and data-shape validation before TideWise can depend on it.\n\nLikely future shape:\n\n```yaml\nprovider: noaa_coops\nstation: \"8661070\"\n```\n\nOther providers should get their own station picker and validation rules. For example, Canadian or UK support may need separate station IDs, units, datum notes, and availability checks.\n\n## Contributing\n\nBug reports, confirmed-station reports, and focused feature requests are welcome through GitHub Issues.\n\nFor code changes:\n\n1. Keep TideWise as a dashboard\u002Fcustom card, not an integration.\n2. Preserve existing HACS custom repository install behavior.\n3. Keep changes scoped and update `CHANGELOG.md` when behavior changes.\n4. Run `npm run check`.\n5. Include screenshots for visible UI changes when practical.\n","TideWise 是一个为 Home Assistant（Lovelace）设计的仪表盘卡片，用于展示潮汐预测、当前潮位、下一次高潮\u002F低潮时间以及可选的钓鱼窗口评分。该项目基于 JavaScript 开发，主要使用 NOAA CO-OPS 作为数据提供商，并且初步支持加拿大 CHS\u002FDFO 和实验性支持 UKHO Admiralty 数据源。TideWise 能够集成天气、风速、水温等本地 Home Assistant 实体信息，以提供更全面的海洋活动辅助决策。其界面美观，支持多种主题模式，非常适合需要关注沿海地区潮汐变化或计划进行海上活动如垂钓的用户。请注意，目前 TideWise 仍处于测试阶段，可能会遇到一些布局问题或数据缺失的情况。","2026-06-11 04:08:00","CREATED_QUERY"]