Skip to content

Fleet Manager v1.90.0

Latest
Latest

Choose a tag to compare

View all tags
@simeon-marinov simeon-marinov released this 03 Jul 20:21
v1.90.0
be3a90b

Fleet Manager v1.90.0

This release contains the major product work added since v1.80.0.

Upgrade / Breaking-Change Audit

This is a major upgrade from v1.80.0, not a simple app restart. Back up the
Fleet Manager and Zitadel databases before upgrading.

  • Run ./deploy/deploy-public.sh migrate --plan-only first. If it reports
    required work, run ./deploy/deploy-public.sh migrate --yes or
    ./deploy/deploy-public.sh upgrade --migrate-first --yes.
  • Fleet DB changes from TimescaleDB 2.25.2-pg16 to 2.28.1-pg18.
    PostgreSQL 16 data directories cannot be started directly as PostgreSQL 18
    data directories. The migration path must use dump/restore or pg_upgrade;
    the deploy tooling plans this before starting the new database image.
  • Zitadel changes from v2.64.1 on PostgreSQL 16 to v4.15.3 on PostgreSQL
    18. Existing Zitadel v2 installs need the staged path
    v2 -> v3.4.9 -> v4.15.3; the deploy tooling includes that staged hop.
  • Redis is now a required runtime service for streams, cache, coordination, and
    ingest buffering. New Redis credentials are generated into deploy state.
  • The public deploy script now has explicit migrate, upgrade-audit,
    backup-db, backup-state, and guarded upgrade commands. A plain
    upgrade refuses to continue if database/Zitadel migration work is pending.
  • The API surface is much larger and has changed since v1.80.0. Regenerate
    API clients from /api/docs/openapi.json or use docs/generated/api.md.
  • Notification destinations are now channels. New API clients should use the
    Channel.* commands and destinationChannelIds for alert destinations.
  • The backend runtime changes from Node 22 to Node 24. Rebuild and retest any
    custom plugins, local extensions, or source-based deployments.
  • Public docs changed from a small static doc set to full API guides plus a
    generated API reference.

Documentation

  • API reference is included in this release at docs/generated/api.md.
  • Deployment and upgrade guide is included at docs/deployment.md.
  • Runtime OpenAPI document is served by each instance at
    https://<your-host>/api/docs/openapi.json.

New Alerts Module

  • New rule engine for fleet alerts.
  • Rule builder for devices, components, groups, locations, and tags.
  • Alert types for state changes, thresholds, offline devices, heartbeat,
    stuck sensors, rate of change, and energy consumption.
  • Built-in starter rules for common device and sensor alerts.
  • Alert lifecycle states for pending, active, recovering, no data, evaluation
    error, acknowledged, cleared, and resolved.
  • Rule notifications with reusable message templates.

New Energy Module

  • New energy dashboards and long-range energy reporting.
  • 15-minute rollups for faster charts and reports.
  • Logical meters, formula meters, and meter roles.
  • Tariffs for day/night, time-of-use, seasonal, and live-price billing.
  • Power-quality views for voltage bands and reactive/apparent energy.
  • HTML and CSV exports for large energy ranges.

New Redis Ingest Path

  • Redis streams for device ingest, status events, and background writes.
  • Dedicated Redis connections for blocking stream readers.
  • Redis-first device update path to reduce live device latency.
  • EM-sync backfill metrics and safer handling for large history imports.

New Device Onboarding

  • Waiting room for newly connected devices.
  • Approve, deny, and bulk-accept flows.
  • Post-accept device health checks.
  • Better handling for sleeping devices and first-connect data.

New BLU Sensor Support

  • BLU sensors can be promoted as top-level devices.
  • Friendly BLU names are shown in the UI.
  • Door/window sensors show open/closed state instead of raw booleans.
  • Gateway relationships show where the BLU data comes from.

New Locations and Fleet Organization

  • Locations for organizing fleets by site, area, or room.
  • Groups and tags for operating on sets of devices.
  • Scoped views and rule targets based on fleet structure.

New Dashboards and Virtual Devices

  • New dashboard management flow.
  • Dashboard tabs and bulk dashboard actions.
  • Virtual devices built from components of real physical devices.
  • Virtual devices use the same device and component cards as normal devices.
  • Relationship views show how a virtual device is built.

Operations

  • Firmware library.
  • Backup and jobs pages.
  • Device authentication tools for passwords and certificates.
  • Clearer deploy status, upgrade, and rollback output.

Security and Reliability

  • Stronger tenant scoping for reports, firmware, backups, notifications, and
    ingest.
  • Safer plugin execution limits.
  • Better runtime observability for services, Redis/EM-sync lag, and database
    version drift.

Docker

docker pull shellygroup/fleet-management:latest

Install

git clone https://github.com/ALLTERCO/fleet-management.git
cd fleet-management
./deploy/deploy-public.sh up
Assets 2
Loading