[yellowcooln]

Summary

Prepare openHop Repeater Integration for Home Assistant v1.3.1 by promoting dev to main.

Release notes

MQTT monitoring

• Added session messages-sent and payload-bytes-sent sensors for each named MQTT broker, alongside combined totals for each Repeater
• Used the existing cached status poll, with no additional HTTP requests
• Added dynamic broker discovery and unavailable handling for missing, invalid, or ambiguous broker data while preserving existing entity identities
• Kept session measurements distinct from lifetime counters, broker acknowledgments, and network/carrier usage
• Updated the comprehensive dashboard template with combined counters and per-broker examples, including corrected name-based entity references

Marketplace installation

• Put the Add to Home Assistant button first in the installation guide
• Added Marketplace installation instructions for Home Assistant 2026.11+, retaining older HACS and manual installation instructions
• Documented restart-free first-install behavior versus integration updates that still require a restart
• Added supported Routers & network and Monitoring manifest categories

Compatibility and maintenance

• Reviewed the latest Repeater development API and documented additional capabilities for future work
• Audited CI dependencies and Home Assistant-owned runtime libraries; existing action references are current and no conflicting standalone runtime pins were added
• Confirmed the existing weekly Dependabot policy targets dev
• Preserved the pymc_repeater compatibility domain, existing config entries, and aggregate sensor unique IDs

Verification

• 174 local source/behavior contract tests passed
• Compilation, JSON/YAML validation, and whitespace checks passed
• Python Smoke, HACS, and Hassfest passed on head 229974c40f251285d5d4b73884c70d55afd30154
• Manually deployed and tested as an upgrade on Home Assistant 2026.11.0
• All four configured Repeaters loaded and continued successful polling
• Individual MQTT broker values matched combined totals for all three MQTT-active Repeaters
• Existing entity registry IDs were retained, with no newly unavailable existing entities at the final check
• Read-only response actions succeeded for all four entries, with no integration errors logged

Fresh Marketplace installation has not been exercised. The live test verified an existing-installation upgrade. MQTT-inactive Repeaters correctly retain unknown combined counters and do not create individual usage sensors. Dashboard examples require installation-specific broker entity IDs; existing live dashboards are not automatically rewritten.

Release handoff

Manifest and changelog are prepared for 1.3.1. This PR does not create a tag or publish a release; release publication remains a manual maintainer step after merge.