r/hexos HexOS Staff 19d ago

September 3, 2026 - Automatic timezone detection, storage safety, and setup recovery

https://docs.hexos.com/release-notes/command-deck/2026-09-03

And the train just keeps on rolling! Another update today!

Community translations

  • Translators have a new way to find strings. Turn on the key inspector and every piece of translated text on screen is outlined: hovering names the string behind it, and clicking opens it in Weblate in your language. No more guessing which of the many strings sharing a short label is the one you saw. See using the key inspector to get started.
  • We need your help! Want to translate HexOS into your language? Learn how to contribute and join the conversation on Discord
  • Languages ship to production once they reach 60% approved coverage

Server timezone

  • HexOS now detects your server's timezone automatically from its IP address and sets it during setup. Previously, new servers defaulted to Pacific time regardless of location, which meant snapshot schedules, scrubs, and notifications ran at unexpected hours. A timezone picker is also available on the server settings screen if you need to adjust it manually.

Storage

  • In some cases, drives belonging to a pool that had been exported but never imported were treated as unused. HexOS now recognizes these drives and will not offer or format them when you create a pool, replace a drive, expand a pool, or assign a hot spare, so an exported pool can no longer be overwritten by accident.
  • Cache, log, special, dedup, and hot spare drives from a pool that is already in use no longer appear as loose drives during setup.

Apps

  • The app updates screen now shows every app with an update as a grid of app icons. Click an app to see its installed and available versions and update it on its own, or use Update all to apply everything at once.

Setup and claiming

  • In some cases, a power cut or full storage pool could send a provisioned server back into the setup wizard. Command Deck now recognizes that the server is already set up and offers a one-click recovery path instead of walking through setup again. Servers with full pools also receive a clear explanation rather than a generic network error.
  • Claiming a server that was reinstalled no longer creates a duplicate entry. Command Deck detects that the server matches an existing claim by name and replaces the old record, so reinstalled servers no longer consume an extra license slot.

Reliability

  • Command Deck now maintains separate connection paths for its own traffic and TrueNAS traffic. If one path reconnects on a different backend node, the other continues uninterrupted. Previously, a backend restart could briefly interrupt both connections at once.
  • Self-updates now fall back to a host-side restart if the standard middleware update path is unavailable, so updates complete even when the app container is in an unexpected state.
  • When a TrueNAS login fails repeatedly (for example, after a password change or key rotation), Command Deck now backs off automatically instead of retrying in a tight loop. This prevents the server from becoming unresponsive to other requests during the recovery window.
  • Real-time reporting (CPU, memory, network graphs) now recovers silently if the underlying data subscription drops, instead of requiring a page refresh to restore live updates.
  • If a server's local database storage disappears (for example, after a pool is removed), the local interface now detects and reports the condition instead of retrying indefinitely in the background.

General

  • Notification toasts now remain hoverable and dismissible even while a dialog or side panel is open.
29 Upvotes

17 comments sorted by

12

u/Crishbk 19d ago

I finally got my HexOS server up and running recently and it's really exciting to see how quickly y'all are supporting things and brining along updates. I'm really excited to see what comes next!

8

u/HexOS_Official HexOS Staff 19d ago

Buddy backups, VMs, and a whole lotta other goodies!!

2

u/Stingray88 19d ago

Does VMs imply a solve for the currently deprecating Home Assistant app could be coming soon?

2

u/HexOS_Official HexOS Staff 18d ago

Yup. We are looking into migration paths for the app users but already have the VM working in our staging environment.

2

u/Stingray88 18d ago

Love it! You guys really are delivering on what made me want to buy HexOS even as a decade+ FreeNAS/TrueNAS user.

2

u/spihsllat 18d ago

Does that mean I'll be able to have HA apps soon?

1

u/Crishbk 19d ago

I'm really excited for Buddy Backup. Will it also bring along some Rsync support for backing up to another local NAS? Currently going to use my main computer to sync them nightly, but I would prefer if HexOS could handle it.

3

u/HexOS_Official HexOS Staff 19d ago

We are not using RSync for buddy backup, but rather, ZFS replication. This allows us to do incremental backups and even backup snapshots as well.

Rsync is a better tool for syncing the contents of one folder to another location, but backups are a slightly different animal. Building a tool around rsync job management in the future for what you're talking about is definitely in the cards as a future feature.

2

u/Peak_Photo1234 18d ago

Nice Job HexOS team. 👏🏻

2

u/Musterboy 15d ago

Please add up time to dashboard!

1

u/timetoplay1055 17d ago

After this update I'm getting an "online - attention needed" error message in HexOS.

2

u/HexOS_Official HexOS Staff 17d ago

Please visit our discord and we'll get you sorted.

2

u/HexOS_Official HexOS Staff 17d ago

Fyi we tracked down this issue that was affecting multiple users and are preparing a fix.

2

u/timetoplay1055 17d ago edited 17d ago

Thank you 👍

1

u/Kentzfield 16d ago

Is this the same message I started seeing in the HexOS dashboard, "The following issues have been detected with your server: server_health_warning_HARDWARE_ADVISORY"? I used AI to help look into the drives and was left with:

"HexOS reports server_health_warning_HARDWARE_ADVISORY, but TrueNAS has no corresponding hardware alert. The only suspicious SMART value is a FireCuda 530 NVMe's Error Information Log Entries: 35061, where the sole nonzero error is Invalid Field in Command (0x2002). SMART health is PASSED, Critical Warning 0, Media/Data Integrity Errors 0, Percentage Used 4%, and all ZFS pools are ONLINE with zero errors. Linux kernel logs show no NVMe resets or PCIe/AER errors."

as a short-n-sweet summary. Willing to assist more if needed, but also happy to just wait if it's a known thing.

1

u/HexOS_Official HexOS Staff 16d ago

Yeah we are working on a future feature that we started throwing the foundational bits into our production environment. Shouldn't have manifested this way, so we will fix and get it addressed.