Skip to main content

What's New in Zafron – March 2026 Release

· 2 min read
Zafron
Zafron
zafron.dev

We've shipped a packed release this month with a major UX overhaul, configuration improvements, and a brand-new CLI tool.

A Better Device Experience​

We shipped a major UX overhaul across the Devices section:

  • Simplified device list — Removed the view toggle and made the Data View the default and only list experience. The activity column was dropped in favor of a cleaner, more scannable layout.
  • Device search — You can now search devices by name or serial number directly from the list.
  • Smarter sensor chips — Sensor readings now show a two-line layout with the label above and value below, replacing emoji icons with readable text labels. Long lists of sensors collapse with an expand/collapse toggle.
  • Inline status & health — Device status badges are now inline, with LoRa-aware thresholds for last-seen times. Status cards at the top dynamically tint based on fleet health, with toned-down severity colors.
  • Time range picker — Replaced text links with a segmented pill control for selecting data time ranges.

Configuration Pages Polish​

  • Profiles table — Added an edit button and a device count column so you can see at a glance how many devices use each profile.
  • Rules — Replaced the status badge with an inline toggle switch for enabling/disabling rules.
  • Sources — Added a stale source warning indicator and improved tooltips.

Dashboard Widgets​

  • Widget headers now show an "Edit" label on hover, making discoverability easier.

Zafron CLI​

We're releasing the Zafron CLI — a command-line tool to interact with your Zafron account directly from the terminal. Manage devices, view readings, and streamline your IoT workflows without leaving the command line.

Branding Refresh​

Updated the Zafron logo across all public pages (login, signup, forgot/reset password) and the main navbar to a modern design.

Bug Fixes​

  • Fixed the Add Device modal closing unexpectedly when selecting a LoRaWAN profile.
  • Fixed checkout to use authenticated API calls instead of a form POST.
  • Fixed profile device counts when the profile is returned as a string ID vs. a populated object.

Have ideas or feedback? Reach out to us — we'd love to hear from you.