opensense
opensense

Changelog

Notable changes

This page is auto-extracted from the top-level git tags on the OpenSense monorepo. Patch versions are folded into the nearest minor. We follow Semantic Versioning for API surface (v1).

Unreleased

Docs site (2026-05-17)

  • Docs site launched at docs.opensense.murzin.digital. Built with Nuxt 3 + @nuxt/content; SSG; same Cold Storage Panel design language as the marketing site. ~80 pages covering Getting started, Hardware, API, Verticals, Troubleshooting, Security, Integrations and About.
  • Search via minisearch — offline, runs in the browser, no third-party JS.
  • /sitemap.xml, /llms.txt, /feed.xml for crawler-friendliness.

Backend

  • MQTT bridge: per-account topic enforcement via mTLS subject CN.
  • TTN webhook: device-by-DevEUI auto-assignment improved; uplinks from unregistered DevEUIs land in the per-site unassigned tray rather than 404-ing.

v0.1.0-alpha — 2026-05 (Slovakia pilot)

The first version we let real customers use.

Verticals

  • HACCP cold-chain report template (haccp_monthly, haccp_annual).
  • Legionella vertical templates with the 50/60/50 rule defaults.
  • Server-room uptime template against ASHRAE TC 9.9.
  • Indoor climate vertical for CO₂ / RH (offices, schools, museums).
  • Energy vertical with baseline drift detection.

Hardware

  • Shelly H&T Gen1 / Plus / Gen3 supported.
  • Aqara TH via Zigbee2MQTT bridge.
  • Efento NS-T / NX-T via TTN webhook.
  • Generic LoRaWAN with the generic decoder shape.
  • DIY ESP32 + ESPHome with the documented YAML.

API

  • POST /v1/ingest general-purpose endpoint.
  • GET /v1/ingest/shelly legacy GET path.
  • Webhook ingest from TTN.
  • Magic-link auth, session cookies, bearer tokens.
  • Idempotent ingest by content key (no Idempotency-Key required).
  • Rate-limit headers per route family.

Compliance

  • GDPR DPA template (SCC 2021 derived).
  • eu-central data residency (Hetzner Falkenstein).
  • Audit trail with daily-published hash-chain head.

Reading this page

The dates above are best-effort. The audit trail in your account is the authoritative log of what changed in your data; this page is about what changed in the product.

For breaking API changes we will publish:

  • An entry here.
  • An email to all account holders 30 days in advance.
  • A Deprecation HTTP response header on the affected endpoint for the deprecation window.