[home-gitops-bot]

This PR contains the following updates:

Package	Update	Change
ghcr.io/unpoller/unpoller (source)	minor	v5.7.0 → v5.8.3

---

Release Notes

unpoller/unpoller (ghcr.io/unpoller/unpoller)

v5.8.3

Compare Source

Changelog

• eff32b0 fix(datadogunifi): read the upgradable key for switch firmware updates
• f0d8e97 build(deps): bump docker/login-action

v5.8.2

Compare Source

Changelog

• 1da022d fix(otelunifi): record client radio rates in bits per second
• 031c22e fix(otelunifi): record the operating radio channel and tx power

v5.8.1

Compare Source

Changelog

• ad21ac7 fix(otelunifi): record switch port PoE current in amps
• b849720 fix: skip null system temperature sensors

v5.8.0

Compare Source

Changelog

• d0444d4 fix(inputunifi): reuse fetched clients and devices for DHCP lease association
• 81e05ba fix(influxunifi): drop the state field from the UDM access point
• f9c4ad1 fix(datadogunifi): prefix system temperature sensors with temp_

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[home-gitops-konflate]

Tip

Routine: only container-image and chart-version changes; 2 resources across 2 apps

image	from	to	upstream
ghcr.io/unpoller/unpoller	v5.7.0@sha256:5be0ef…	v5.8.3@sha256:6a474f…	✅

_{konflate 0.6.6 · rendered 9786c04 · full diff →}

[home-gitops-bot]

HelmRelease diff

spec.template.spec.containers.app.image  (apps/v1/Deployment/observability/unpoller)
  ± value change
    - ghcr.io/unpoller/unpoller:v5.7.0@sha256:5be0efc124aa58c37b3d66b0e5edf00478670f278b9206e5566c102b64c9c868
    + ghcr.io/unpoller/unpoller:v5.8.3@sha256:6a474f5202d40864affe6be9882492061331d77d474593bb1cd4a8c737dc834f
  

Kustomization diff

spec.values.controllers.unpoller.containers.app.image.tag  (helm.toolkit.fluxcd.io/v2/HelmRelease/observability/unpoller)
  ± value change
    - v5.7.0@sha256:5be0efc124aa58c37b3d66b0e5edf00478670f278b9206e5566c102b64c9c868
    + v5.8.3@sha256:6a474f5202d40864affe6be9882492061331d77d474593bb1cd4a8c737dc834f
  

_{Diff created by flate — Workflow run}

[home-gitops-bot]

Verdict: Safe to merge

Reviewed the only change in this PR: ghcr.io/unpoller/unpoller v5.7.0 → v5.8.0 in kubernetes/apps/observability/unpoller/app/helmrelease.yaml (tag + digest only, no other diff). v5.8.0 is the immediate next release after v5.7.0, so there are no intermediate versions to check.

Full changelog for v5.8.0 (3 commits):

• fix(inputunifi): reuses clients/devices already fetched during polling instead of making a duplicate GetActiveDHCPLeasesWithAssociations call for DHCP lease association. On UniFi OS consoles the duplicate request was doubling the rate of a known device-tags-request memory leak in unifi-core. Applies regardless of output backend — net positive, no config changes needed here.
• fix(influxunifi): drops the state field from the UDM access point point (previously wrote a Go struct stringified as "{1 1}", not usable data). Only affects the InfluxDB output, which this repo explicitly disables (UP_INFLUXDB_DISABLE: true) — not applicable.
• fix(datadogunifi): prefixes temperature sensor fields with temp_ (previously a USG's CPU temperature sensor overwrote the cpu utilization gauge under the same key). Only affects the DataDog output, which this repo's HelmRelease doesn't configure — not applicable.

This repo scrapes unpoller via UP_PROMETHEUS_HTTP_LISTEN + a ServiceMonitor, which none of the three fixes touch. No breaking changes, no deprecations, no action required beyond the version/digest bump.

Sources consulted:

• https://redirect.github.com/unpoller/unpoller/releases/tag/v5.8.0
• https://redirect.github.com/unpoller/unpoller/compare/v5.7.0...v5.8.0
• https://redirect.github.com/unpoller/unpoller/commit/d0444d457294f4fa61e4b3c57428135a9812a9f9
• https://redirect.github.com/unpoller/unpoller/commit/81e05ba95c10cd47cfd4349141beed6ca2b8f8dd
• https://redirect.github.com/unpoller/unpoller/commit/f9c4ad1997343ba7cb3fd40ea63683eda017916b

[home-gitops-bot]

Verdict: Safe to merge

Reviewed the full version range in this PR: ghcr.io/unpoller/unpoller v5.7.0 → v5.8.1 in kubernetes/apps/observability/unpoller/app/helmrelease.yaml (tag + digest only, no other diff). An earlier bot comment already reviewed v5.7.0 → v5.8.0; this PR has since picked up one additional patch release (v5.8.0 → v5.8.1), so I reviewed that delta as well rather than treat this as a plain rebase.

v5.8.1 changelog (2 commits):

• fix(otelunifi): switch port PoE current was recorded in milliamps while the gauge was documented/consumed as amps (1000x too large); now divided by 1000. Only affects the OTel exporter, which this repo doesn't configure (UP_PROMETHEUS_HTTP_LISTEN only) — not applicable.
• fix: skip null system temperature sensors. A UniFi device reporting a null temp sensor (e.g. {"CPU":null}) previously caused a panic in promunifi's exportUSG (recovered by the client library, but that device's scrape was dropped for the cycle) and an unrecovered panic in datadogunifi (process exit). The promunifi path is the one this repo actually uses via its ServiceMonitor/Prometheus scrape — this is a genuine reliability fix for a code path in play here, not just noise. datadogunifi isn't configured, not applicable.

Combined with the already-reviewed v5.7.0 → v5.8.0 changes (dedup of a duplicate DHCP-lease-association API call, an InfluxDB-only fix, a DataDog-only fix — none applicable or all already covered), nothing in this range requires action beyond the version/digest bump. No breaking changes, deprecations, or configuration changes needed.

Sources consulted:

• https://redirect.github.com/unpoller/unpoller/releases/tag/v5.8.1
• https://redirect.github.com/unpoller/unpoller/compare/v5.8.0...v5.8.1
• https://redirect.github.com/unpoller/unpoller/commit/ad21ac730b69928f803faf64617d46d26f8bb1dc
• https://redirect.github.com/unpoller/unpoller/commit/b849720477c730edeb89b5e6593525b0c1a3eaf2

[home-gitops-bot]

Verdict: Safe to merge

Reviewed the remaining delta in this PR: ghcr.io/unpoller/unpoller v5.8.1 → v5.8.2 in kubernetes/apps/observability/unpoller/app/helmrelease.yaml (tag + digest only, no other diff). Earlier bot comments already covered v5.7.0 → v5.8.0 and v5.8.0 → v5.8.1.

v5.8.2 changelog (2 commits):

• fix(otelunifi): record client radio rates in bits per second (previously wrong unit/scale).
• fix(otelunifi): record the operating radio channel and tx power.

Both changes are scoped entirely to the otelunifi OTel exporter. This repo's HelmRelease only sets UP_PROMETHEUS_HTTP_LISTEN (and UP_INFLUXDB_DISABLE: true) — no OTel exporter env vars are configured, so neither fix is applicable to this deployment. Combined with the previously-reviewed v5.7.0→v5.8.1 range (promunifi/influxunifi/datadogunifi fixes, already assessed as not applicable or already-covered), nothing in the full v5.7.0→v5.8.2 range requires action beyond the version/digest bump.

Sources consulted:

• https://redirect.github.com/unpoller/unpoller/releases/tag/v5.8.2
• https://redirect.github.com/unpoller/unpoller/compare/v5.8.1...v5.8.2

[home-gitops-bot]

Verdict: Safe to merge

Reviewed the remaining delta in this PR: ghcr.io/unpoller/unpoller v5.8.2 → v5.8.3 in kubernetes/apps/observability/unpoller/app/helmrelease.yaml (tag + digest only, no other diff). Earlier bot comments already covered v5.7.0 → v5.8.0 → v5.8.1 → v5.8.2.

v5.8.3 changelog (2 commits):

• fix(datadogunifi): reads the "upgradable" key for switch firmware updates. Scoped to the DataDog output, which this repo's HelmRelease doesn't configure (only UP_PROMETHEUS_HTTP_LISTEN + UP_INFLUXDB_DISABLE) — not applicable.
• build(deps): bumps docker/login-action in unpoller's own CI. Upstream build tooling only, no effect on the published image or this deployment.

Combined with the previously-reviewed v5.7.0→v5.8.2 range (promunifi/influxunifi/datadogunifi/otelunifi fixes, all already assessed as not applicable or already-covered), nothing in the full v5.7.0→v5.8.3 range requires action beyond the version/digest bump.

Sources consulted:

• https://redirect.github.com/unpoller/unpoller/releases/tag/v5.8.3
• https://redirect.github.com/unpoller/unpoller/compare/v5.8.2...v5.8.3