feat(myuplink): improve NIBE F750 telemetry

[segran2]

Summary

Improve NIBE F750 telemetry using parameter data observed on real F750 hardware through MyUplink Cloud API v2.

The change:

• corrects parameter 40013 documentation to BT7 hot-water top temperature
• exposes parameter 40940 as canonical hp_degree_minutes
• ignores NIBE's -32768 unavailable-value sentinel instead of emitting bogus telemetry
• removes embedded U+00AD soft hyphens from generated metric names
• adds an F750 regression test based on hardware-observed parameter data

No F750 electrical compressor-power mapping is added. Parameter 10012 was not present in the hardware capture, so the driver does not infer electrical power from unrelated parameters.

Driver evidence

• Driver id: myuplink
• Device make/model: NIBE F750
• Firmware tested: hardware-tested F750 via MyUplink Cloud API v2
• Protocol/register source: MyUplink Cloud API v2 /v2/devices/{deviceId}/points
• Hardware test performed: Yes — live F750 telemetry captured and used to build the regression fixture
• Known limits: No verified F750 electrical compressor-power parameter was observed; no hp_power_w mapping is claimed for F750

Observed parameters include:

• 40004 — BT1 outdoor temperature
• 40013 — BT7 hot-water top temperature
• 40033 — BT50 room temperature
• 40940 — current degree-minute value (DM)
• 41778 — current compressor frequency
• 43084 — internal additional-heat power
• -32768 — unavailable-value sentinel observed on multiple points

Safety

• The driver starts read-only, or this is a separately reviewed control change.
• Vendor signs are converted at the driver boundary.
• Cached telemetry becomes stale instead of being re-emitted as fresh.
• No credentials, serial numbers, private addresses or site data are included.

The driver remains read-only. This PR adds no control/write path.

Control evidence

Not applicable — read-only telemetry change.

• HIL evidence or required: not applicable
• Control changes: not applicable; no control path changes.

Checks

• Commits include Signed-off-by.
• make test-driver ID=myuplink
• make check

Full make check: 4810 passed, 923 skipped.

All 91 drivers passed the sandbox safety check. Manifest, index, devices and support-status generation are clean. FTW baseline and host API checks also passed.

[miravoss26]

Mira's read (pr-steward sweep). 2-line summary: MyUplink F750 telemetry. BT7 relabel, degree-minutes as a canonical metric, the -32768 sentinel is ignored, and soft hyphens are stripped from metric names. The driver stays read-only (control: false unchanged).

Checks: the size (18431) and sha256 pinned in index.yaml and manifests/myuplink.yaml match the driver file at this head. The new harness test covers the F750 payload, including the sentinel and soft-hyphen cases.

Findings:

• [low] decode_temp used to emit 0 for a missing value and now emits nothing. That's the intent, but it changes what dashboards see for an absent point. Worth one changelog line.

Security screen: no secrets, no new hosts or endpoints.

Safe to merge from my read. Not auto-merge eligible (repo not on the POLICY allowlist), so a human merges.

[miravoss26]

Review: myuplink 1.2.3 → 1.2.4, NIBE F750 telemetry fix from hardware-captured data.

Correctness:

• 40013 relabeled BT6 → BT7 is comment-only (register id unchanged) — matches the hardware capture in the new test fixture ("Hot water top BT7").
• Real bug fixed: the three canonical temp metrics used decode_temp(...) or 0, so an unavailable NIBE point (-32768 sentinel) was emitted as a false 0 °C reading — exactly the invented-number pattern no_invented_numbers.lua exists to catch. New valid_raw() filters the sentinel before decode, and the metrics are now omitted (not zeroed) when unavailable. Same fix applied to the generic "everything else" loop, so it isn't just the three canonical ones.
• New hp_degree_minutes (param 40940) is additive and follows the existing canonical-metric pattern.
• Soft-hyphen (U+00AD) strip in sanitize_metric_name is a real fix too — the test fixture shows it live in vendor parameter names ("com­pressor fre­quency").
• No F750 electrical compressor-power mapping added, as the description says — param 10012 untouched, correctly left out given it wasn't in the hardware capture.

Tests: new Lua harness test against a real hardware-captured response fixture, verifying both the emitted canonical metrics and that the three sentinel-valued points (hp_reference_air_speed_sensor, hp_current_temperature_system_1, hp_set_point_temp_system_1_heat) are correctly absent. Python wrapper runs it via make check's lua harness. Good coverage for exactly the bug being fixed.

Security: no secrets, no new network destinations, read-only (control: false unchanged) — matches the PR's own safety checklist.

All 5 CI checks green (signed channel, public-boundary, drivers, dco, history-secret-scan). One thing for a human: GitHub shows this PR as conflicting with main right now — needs a rebase, not a content concern. Safe to merge from my read once that's resolved.