[MacNite]

This brings HivePal's HiveHub integration up to date with HiveHub, covering items 1–6 of the gap analysis. It needs MacNite/HiveHub#199 for hive links, relay status, AP mode, export and range delete. On an older HiveHub those features return 404; everything else works with current HiveHub main.

1. Fixes for things broken today

• Hive names for slots 3–18 were never saved. HivePal sent hives[], which HiveHub silently dropped. It now sends names and hive_ids. Names and links are stored in HiveHub instead of only in the browser, and a slot links to a HivePal hive by id, not by name.
• Swarm alerts could not work. The job sent the user id as a bearer token, read fields that don't exist, and never applied its cooldown. It is replaced by an insight-based email job:
  • It runs every 15 minutes and emails new or escalating HiveHub alerts (swarm, robbing, queenless, winter, …) for all 18 hives.
  • It sends one digest mail per run and tracks what was sent in a new HiveHubAlertNotification table.
  • It is opt-in per user (Setup → Alert emails) with a minimum severity. Users who had swarmAlert on stay on.
• Firmware upload: the hivehub target is accepted, a board is forwarded, and uploads are capped at 16 MB. Relays work for any hive 1..18, with an optional force.
• Wide chart ranges were truncated. HiveHub caps each request at 10k rows, so a "year" chart showed only about the last 35 days. Ranges beyond 7 days now use server-side max_points.
• Request bodies are validated with zod schemas in shared-schemas.

2. Inspection mode

• Start/stop with hive scope and a note, pending and active status, timeout, and history with editable notes.
• The HivePal inspection form suggests starting it for a linked hive. It never starts automatically.
• The hive detail page gets a HiveHub card for linked slots.
• Inspection windows are shaded on the charts.

3. Configuration

• Calibration wizard and temperature compensation for every hive, 1–18.
• HiveTraffic night mode, time zone and emitter banks.
• Inspection timeout setting.
• HiveTraffic relay buttons, and "relay anyway" (force).
• The page uses the insights summary.

4. Visibility

• Health tab: hub status (signal, time source, battery, solar, last check-in) and sensor health, with HiveHub's fault explanations. It names each HiveInside node and HiveTraffic counter.
• Overview: per-hive cards for every hive, with compensated weight, 24 h change and alerts.
• Dashboard: new HiveHeart spectrum and daily max weight widgets, a custom date range, and full i18n.

5. Audio

• Record 1–60 s from a HiveInside, play or download the WAV (streamed through the backend), see quality figures, delete.

6. HiveHub API additions and cleanup

• Per-node relay status, remote setup access point, NDJSON export, and a range delete gated by the claim code.
• SD import refuses a card recorded by another hub unless you confirm.
• The claim form takes the hive 1/2 names again.
• Removed the unused sound and bee-counter panels.
• All nine languages translated; added the missing navigation.hivehub key.
• Docs, README env vars, TODO and v0.20.0 release notes updated.

Testing

• Backend: 150 unit tests pass, including 19 new ones for alert rules, relay slots, SD device detection and the shared schemas.
• Checks: tsc is clean for the frontend and backend, eslint has 0 errors, and the frontend builds.
• The new migration was applied to Postgres and prisma migrate diff against the schema is empty.
• End to end, HivePal backend and frontend were run against the HiveHub mock server (with the mock fixes from Feature Request: Improve the Inspections table — customisable columns, a Notes column, and a meaningful "Actions" column martinhrvn/hive-pal#199):
  • Every new proxy route was exercised.
  • Screenshots of all tabs were checked by hand.
  • This found one more bug, now fixed: an older HiveHub or the mock sends no hives[], so the frontend now rebuilds it from the flat fields.
• Not tested: against a real hub or a real HiveHub server; alert emails with a real mail provider; the audio recording flow (the mock can't record).

Notes for review

• Commits are grouped by layer (backend, frontend, docs, translations) rather than by item, so each commit builds on its own.
• The release-notes entry in v0.20.0.md has no PR number yet.
• Translations were machine-drafted by Claude, not a native speaker; worth a skim, especially ru/sk/sr.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V4BwZGxKox5nD1Nw8fP9NL

---

Generated by Claude Code