build: bump version to 1.0.2

[dewet22]

Patch release shipping the BMS diagnostics work from #56 and a sync to givenergy-modbus v2.0.3.

Changes since v1.0.1

Features

• feat(sensor): expose additional BMS diagnostics on battery devices (feat(sensor): expose additional BMS diagnostics on battery devices #56) — per-index BMS status (status_1 … status_7) and warning (warning_1, warning_2) sensors rendered as fixed-width hex strings, exposes the alt-source cap_design2 field as "Design Capacity Alt", adds a "BMS Diagnostics" card to the auto-generated dashboard. Dashboard schema bumped to v2 so existing installs are prompted via Repairs to regenerate.

Library sync (givenergy-modbus 2.0.0 → 2.0.3)

• Bounds enforcement (modbus#82, in 2.0.1) — out-of-bounds register values now suppress to None instead of passing through. The IR(100)/IR(59) SOC corruption events that previously surfaced as raw out-of-range values (~5710, ~44820, etc.) will now show as unknown for one tick before recovering on the next poll. Cleaner UX, no more spurious "SOC > 100" automation triggers from this class of corruption.
• Pattern A frame-level discard (modbus#78, in 2.0.1) — corrupted IR(0,60) frames are now discarded at the framer level, before they reach the cache.
• work_time_total documented and bounded upstream (modbus#84, in 2.0.1) — confirms our existing hass-side value_fn passthrough is right. Drops the inline tracking comment in sensor.py.
• PlantCapabilities.from_dict() compat (in 2.0.2) — backward-compat fixes for serialised v2.0.0 payloads.
• Framer DoS hardening (modbus#88, in 2.0.3) — defence-in-depth against malformed-frame inputs.

No code changes needed for the library sync beyond the comment cleanup — the API surface is unchanged across 2.0.0 → 2.0.3.

Test plan

• All 83 tests pass on the BMS diagnostics work (feat(sensor): expose additional BMS diagnostics on battery devices #56)
• All 83 tests pass against givenergy-modbus 2.0.3 after the bump
• CI green on feat(sensor): expose additional BMS diagnostics on battery devices #56
• After release: confirm BMS sensors populate, dashboard Repairs prompt fires, and SOC sensors briefly show unknown instead of out-of-range values during the next corruption event

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Bumped integration version to 1.0.2 and raised the minimum required underlying library version.

• Documentation

  • Removed an outdated inline comment about a sensor register’s units to keep internal notes accurate.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9bc539e3-ddbc-4b04-b824-972e90557a76

📥 Commits

Reviewing files that changed from the base of the PR and between d39689a and 5dc451f.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• custom_components/givenergy_local/manifest.json
• custom_components/givenergy_local/sensor.py

💤 Files with no reviewable changes (1)

• custom_components/givenergy_local/sensor.py

🚧 Files skipped from review as they are similar to previous changes (1)

• custom_components/givenergy_local/manifest.json

---

📝 Walkthrough

Walkthrough

Manifest requirement for givenergy-modbus is raised to >=2.0.3,<3.0.0 and the integration version is bumped to 1.0.2; an outdated inline comment in sensor.py related to work_time_total was removed.

Changes

Manifest and sensor cleanup

Layer / File(s)	Summary
Manifest requirement & version update custom_components/givenergy_local/manifest.json	givenergy-modbus requirement changed to >=2.0.3,<3.0.0; version updated from 1.0.1 to 1.0.2.
Sensor inline comment removal custom_components/givenergy_local/sensor.py	Deleted an outdated inline comment about the work_time_total sensor's unit interpretation; no code behavior changed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• dewet22/givenergy-hass#53: Also updates custom_components/givenergy_local/manifest.json to bump the integration version (previous bump from 1.0.0 → 1.0.1).

Poem

🐰 I hopped through JSON, small and spry,
Pushed versions up toward the sky,
A comment pruned, tidy and neat,
The manifest now skips a beat,
Hooray — the release is light on its feet! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: bumping the integration version from 1.0.1 to 1.0.2, which is the primary action described in the file-level changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v1.0.2

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the version of the givenergy_local custom component from 1.0.1 to 1.0.2 in the manifest.json file. I have no feedback to provide as there are no review comments.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	givenergy-modbus@​2.0.0 ⏵ 2.0.3	+1

View full report