Feature: Add Homebox widget

[cadeluca]

Proposed change

Adds a Homebox service widget. Returns statistics (options are number of items, items with a warranty, locations, labels, users, and total value of items) for the user's group. Default values are set as ["items", "locations", "totalValue"]. Available fields, defaults, and config are noted in the added documentation.

Example:

This widget required implementation of a custom proxy to login, which it does by hitting the /users/login API endpoint. Then the /groups/statistics endpoint is used for the actual data and the /groups endpoint is used to retrieve the currency the user has configued in Homebox. This currency value is used for formatting the totalValue field.

Example API responses:

Closes #1389

Type of change

• New service widget
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation only
• Other (please explain)

Checklist:

• If applicable, I have added corresponding documentation changes.
• If applicable, I have reviewed the feature and / or service widget guidelines.
  • As noted above, Homebox's API requires logging in to get a token for auth on requests, so it was necessary to add a custom proxy. I understand if the preference to avoid more custom proxies causes this to be rejected.
• 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.

[shamoon]

Instead of having a custom proxy (that needs to be maintained) couldn’t we just use the token directly, ie ask users to supply that

[shamoon]

I’m going to go ahead and request that the above change be made to accept this PR. It seems trivial to get the token with the bundled swagger ui and I think that’s all this proxy does.

Let us know if you need info/help

[cadeluca]

We cannot use the token directly, Homebox does not currently support long-lived API tokens. The auth token that gets retrieved expires in a week after fetch.

[shamoon]

Oh gotcha, I see that by testing it out (their docs are a bit slim). Thats certainly not your fault, so in that case what I meant to say instead was "Thanks" 😊

I added the token expiration for the cache, as you may have noticed.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.