Feature: UniFi Drive (UNAS) service widget

[stevenharris-dev]

Proposed change

Adds a new service widget for UniFi Drive (UNAS) devices. This enables Homepage users to monitor storage statistics from their UniFi NAS directly on their dashboard.

Related discussion: #5960

Features

• Storage statistics: Total capacity, used space, available space, and health status

Configuration example

widget:
  type: unifi_drive
  url: https://unifi.host.or.ip
  username: your_username
  password: your_password

API endpoint used

• GET /proxy/drive/api/v1/systems/storage?type=detail — overall storage stats

Example API response

{
  "data": {
    "totalQuota": 2000000000000,
    "usage": {
      "system": 50000000000,
      "myDrives": 300000000000,
      "sharedDrives": 150000000000
    },
    "status": "healthy"
  }
}

AI disclosure

Claude (Anthropic) was used to assist with test writing, proxy handler patterns, and PR preparation. All code was reviewed and tested by the author.

Type of change

• New service widget

Checklist:

• If applicable, I have added corresponding documentation changes.
• If applicable, I have added or updated tests for new features and bug fixes (see testing).
• If applicable, I have reviewed the feature / enhancement and / or service widget guidelines.
• I have checked that all code style checks pass using pre-commit hooks and linting checks.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• In the description above I have disclosed the use of AI tools in the coding of this PR.

[codecov]

Codecov Report

❌ Patch coverage is 97.67442% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 88.55%. Comparing base (ff4eaa2) to head (fcfddf7).
⚠️ Report is 1 commits behind head on dev.

Files with missing lines	Patch %	Lines
src/widgets/unifi_drive/component.jsx	95.65%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #6461      +/-   ##
==========================================
+ Coverage   88.51%   88.55%   +0.04%     
==========================================
  Files         521      524       +3     
  Lines       24861    24947      +86     
  Branches     2160     2170      +10     
==========================================
+ Hits        22005    22093      +88     
+ Misses       2748     2745       -3     
- Partials      108      109       +1     

Flag	Coverage Δ
shard-1	33.20% <46.51%> (+0.07%)	⬆️
shard-2	30.66% <23.25%> (+0.02%)	⬆️
shard-3	38.99% <23.25%> (+0.45%)	⬆️
shard-4	31.01% <74.41%> (-0.43%)	⬇️
vitest	88.53% <97.67%> (+0.04%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/widgets/unifi_drive/proxy.js	100.00% <100.00%> (ø)
src/widgets/unifi_drive/widget.js	100.00% <100.00%> (ø)
src/widgets/unifi_drive/component.jsx	95.65% <95.65%> (ø)

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[shamoon]

Thanks. Before I take a look please simplify the widget options, homepage aims for simplicity

[shamoon]

Specifically the share list needs to be removed or brought in line with homepage widgets. I don’t like letting LLMs just riff like this

[stevenharris-dev]

Massively simplified the implementation. I removed the additional shares as per your request shamoon. I had a feeling it was too much for homepage, but since it wasn't mentioned in the discussion, I left it for the PR, but I understand the need to simplify. Now the widget only shows available space on the entire UNAS, and doesn't have per-share information.

[shamoon]

Sigh, still a massive amount of LLM cleanup to do here.

Also the proxy is now almost entirely a line-for-line copy of the existing unifi proxy, which pretty obviously makes no sense, right?

All due respect, as I have said about 1000x by now, AI PRs have a way of shifting the work onto maintainers that I find pretty frustrating.

[stevenharris-dev]

Dear Shamoon,

I totally get like feeling this difficult to deal with as a maintainer for a large project. So I have made the changes that you requested.

In regards to the proxy however, the reason why there are two nearly identical proxies is because of the hardcoded prefixes in the original unifi network widget as both the Drive and the AP endpoints are different. So a new proxy was made to keep the separation of concerns. This is personally the way that I would have done it in my projects pre-LLM days.

If you want, I will happily create a new PR to have an argument passed from each unifi_console and unifi_drive widgets to use the same proxy.

[shamoon]

This is personally the way that I would have done it in my projects pre-LLM days.

Again, no disrespect meant, but do you have dev experience pre-LLM? I dont see anything in your GH profile to suggest that, and this idea doesnt make a lot of sense to me. This would leave us with two areas to reason about wrt authenticating with unifi devices, two nearly-identical paths for handling errors etc.

Instead I've refactored the unifi proxy to be more generic, merged that in here and made the drive proxy just a thin wrapper.

Also, as a matter of etiquette, I prefer you not force-push every single time you make a change, it makes it much harder to track changes.

[shamoon]

Please test this out, let me know if you have any concerns.

[stevenharris-dev]

I checked out the changes and tested it on my own system, it looks like it is working fine great. Thanks for the refactor on the proxy handler.

In the future I'll use incremental commits going forward instead of force-pushing. Appreciate the patience.

RE. PreLLM -- I've been a "full stack" developer for over 15 years now, primarily in Python and not JS. Which is why I used an LLM approach on this project for my own use. I don't commit to a public GH and use my own private git servers (Gitea at the moment). I develop websites and services for companies and their internal tooling and I don't have a lot of experience with open source projects (though I have some very minor contributions in the past). So I am sorry for any of the inconveniences that I've caused.

[shamoon]

Appreciate that, sorry if I sounded grumpy, I have enjoyed maintaining OSS projects for a long time but LLM-enabled PRs has been a bit of a mixed bag as the tools are not always used thoughtfully. Thanks for being so understanding.