Releases: openhop-dev/openHop-HA-Integration
Release list
v1.1.6 - Faster Updates, Neighbor-Link Diagnostics, and Expanded Repeater Controls
This release improves update responsiveness, adds support for the latest openHop Repeater neighbor-link and CAD APIs, introduces configurable refresh intervals, and includes a completely rebuilt example dashboard.
Highlights
Configurable Integration Refresh
The integration now refreshes Repeater data every 15 seconds by default, replacing the previous fixed refresh interval.
The refresh interval can now be configured from:
Settings → Devices & Services → openHop Repeater → Configure
Supported range:
- Minimum: 5 seconds
- Default: 15 seconds
- Maximum: 300 seconds
Changing the interval automatically reloads the integration.
Note: This controls how often Home Assistant refreshes Repeater API data. External sensor polling schedules configured on the Repeater remain unchanged.
Improved GPS Updates
GPS updates no longer delay the integration's scheduled refresh cycle.
Previously, frequent GPS snapshots could postpone updates for radio, packet, MQTT, system, and sensor data. GPS entities now remain responsive while the rest of the integration continues refreshing at the configured interval.
Neighbor-Link Diagnostics
Added support for the latest openHop Repeater neighbor-link APIs.
New Diagnostic Entities
- Observed Neighbor Links
- Active Neighbor Links
New Home Assistant Actions
- Get Neighbor Links
- Get Neighbor-Link History
Neighbor-link history remains available on demand rather than being downloaded during every refresh.
Manual CAD Diagnostics
Added a new Run Manual CAD Check action.
New capabilities include:
- Known-signal calibration mode
- CAD symbol counts of 1, 2, 4, 8, and 16
- Configurable CAD timeout
- Optional live application of manual CAD parameters
- Validation aligned with the latest Repeater API
Saved CAD settings now also include the configured CAD symbol count.
Metrics Storage Diagnostics
Added a new Metrics Data Source diagnostic sensor.
Attributes include:
- Active metrics backend
- RRD enabled state
- RRD availability
- Active SQLite or RRD storage source
New Example Dashboard
The included example dashboard has been completely redesigned:
dashboards/openhop_repeater_dashboard.yaml
The new dashboard includes sections for:
- Repeater overview
- Radio health and utilization
- Packet flow and trends
- Signal quality
- Listen Before Talk diagnostics
- Neighbor links
- Routing
- Repeater controls
- Advert statistics
- Advert rate limiting
- Clients and identities
- MQTT brokers
- Companion bridges
- GPS position and satellites
- External modem telemetry
- Update management
- Metrics database diagnostics
The template uses a single REPEATER_SLUG placeholder, making it easy to adapt for any installation with a simple find-and-replace.
Existing dashboards are not modified automatically. To use the updated layout, copy the new template into Home Assistant and replace the placeholder with your Repeater entity prefix.
Documentation
Documentation has been expanded with:
- Improved installation instructions
- HACS installation button
- Integration options
- Dashboard setup guide
- Home Assistant action reference
- Authentication and reauthentication guidance
- Persistent token database recommendations
- Security recommendations
- openHop Discord community link
- Updated badges and release information
A new contributor guide has also been added:
docs/AGENTS.md
Compatibility
There are no intentional breaking changes.
Existing:
- Devices
- Entities
- Dashboards
- Automations
- Config entries
remain compatible.
The new diagnostics require a recent openHop Repeater version. Older Repeaters may report those entities as unavailable until upgraded.
Updating
- Update the integration through HACS.
- Restart Home Assistant.
- Review the new integration refresh interval under Configure.
- Check the Repeater device page for the new neighbor-link and metrics entities.
- Optionally import the new example dashboard.
Validation
- ✅ HACS validation passed
- ✅ Hassfest validation passed
- ✅ Python Smoke passed
- ✅ 8 integration contract tests passed
- ✅ Python compilation passed
- ✅ JSON and YAML validation passed
- ✅ Dashboard anonymization verified
- ✅ Release metadata and changelog validation passed
What's Changed
Features
- Prepare openHop integration v1.1.6 and update documentation by @yellowcooln in #13
CI and Maintenance
- ci(deps): bump actions/setup-python from 6 to 7 by @dependabot[bot] in #12
Full Changelog: v1.1.5...v1.1.6
New Diagnostics, Region Controls, and Home Assistant Compatibility
This release updates the integration for the latest openHop Repeater development API, adds new diagnostic entities and region controls, improves compatibility with newer Home Assistant versions, and aligns validation with current Repeater behavior.
Highlights
Latest Repeater API Support
- Added support for the latest openHop Repeater development API additions.
- Updated the integration to expose newly available diagnostic data.
New Diagnostic Entities
Added Home Assistant entities for:
- Packet type statistics
- Listen Before Talk (LBT) diagnostics
- Default region
- Update channel
Default Region Control
- Added support for selecting the Repeater's default region from the available transport key regions.
- Region selection is synchronized with the current Repeater API.
Home Assistant Compatibility
- Fixed the Options Flow crash on newer Home Assistant releases.
- Updated the integration to avoid assigning to the now read-only
OptionsFlow.config_entryproperty. Thank you @wazmac for the issue report.
Validation Improvements
- Updated CAD settings validation to match the Repeater API.
- CAD threshold values are now validated within the supported 0–255 range.
Validation
- ✅ HACS validation passed.
- ✅ Hassfest validation passed.
- ✅ Python smoke tests passed.
- ✅ Verified new diagnostic entities and API coverage.
- ✅ Verified Options Flow compatibility on newer Home Assistant versions.
- ✅ Verified CAD validation matches the current Repeater API.
What's Changed
Features
- chore: release v1.1.5 by @yellowcooln in #11
Full Changelog: v1.1.4...v1.1.5
openHop Repeater Home Assistant Integration v1.1.4
This release completes the user-facing rebrand from pyMC Repeater to openHop Repeater and moves the Home Assistant integration to the openHop GitHub organization.
New Repositories
Home Assistant Integration
https://github.com/openhop-dev/openHop-HA-Integration
openHop Repeater
https://github.com/openhop-dev/openhop_repeater
What's Changed
openHop Rebrand
- Rebranded the Home Assistant integration from pyMC Repeater to openHop Repeater.
- Updated HACS display names, dashboard title, diagnostics, bundled icons, and documentation links.
- Updated repository references to the new openHop GitHub organization.
New Sensor Entities
Added Home Assistant entities for:
- Repeater Sensor Manager summary data
- Configured Repeater sensor plug-ins
Sensor entities are now created dynamically when readings become available, instead of requiring sensor data during the initial integration setup.
Compatibility
Important: The Home Assistant integration domain remains
pymc_repeater.
This is intentional to preserve compatibility with existing Home Assistant installations.
The following identifiers remain unchanged:
- Integration domain
custom_components/pymc_repeater- Config entry IDs
- Service names
- Entity registry references
Do not remove and re-add the integration simply because the branding has changed.
Existing Installations
If you already have the integration installed, update it normally through HACS.
If HACS does not detect updates after the repository move:
-
Do not remove the integration from Devices & Services.
-
Remove the old custom repository from HACS (if present):
-
Add the new custom repository:
-
Select Integration as the repository category.
-
Install or update the integration.
-
Restart Home Assistant.
Your existing configuration should continue to work because the integration domain remains pymc_repeater.
New Installations
Add the following custom repository to HACS:
https://github.com/openhop-dev/openHop-HA-Integration
Then install openHop Repeater and restart Home Assistant.
Notes
- The branding is now openHop Repeater, while the internal integration domain remains
pymc_repeater. - Existing entity IDs, services, and configuration should continue working without migration.
- Do not rename
custom_components/pymc_repeater. - Do not change YAML or automation references from
pymc_repeaterunless a future release provides an official migration path. - Although GitHub redirects the old repository URL, HACS custom repository behavior may vary. If updates stop appearing, follow the repository migration steps above.
What's Changed
Features
- Update actions/checkout to version 7 and rebrand openHop integration by @yellowcooln in #10
CI and Maintenance
- ci(deps): bump actions/checkout from 6 to 7 by @dependabot[bot] in #8
- ci(deps): bump actions/checkout from 6 to 7 by @dependabot[bot] in #9
New Contributors
- @dependabot[bot] made their first contribution in #8
Full Changelog: v1.1.3...v1.1.4
v1.1.3
v1.1.3
This release updates the Home Assistant integration for newer pyMC Repeater API changes and is based on pyMC_Repeater v1.0.10.dev115.
Added
-
New Home Assistant action:
pymc_repeater.get_broker_presets
-
Support for the repeater
broker_presetsAPI endpoint -
Access to bundled MC2MQTT broker template data directly from the repeater API
Included Broker Preset Data
- Preset ID
- Preset display name
- Optional preset website
- Bundled broker configuration entries included with each preset
Notes
-
Primarily an API surface synchronization release
-
Most repeater-side changes in this range focused on:
- Setup wizard updates
- Update/restart messaging improvements
-
The major telemetry fixes remain from
v1.1.2, including:- Corrected per-hour packet counters
Repeater Base
-
Based on:
pyMC_Repeater v1.0.10.dev115
Full Changelog: v1.1.2...v1.1.3
v1.1.2
v1.1.2
This release updates the Home Assistant integration for newer pyMC Repeater API changes and fixes the per-hour packet counters in Home Assistant.
Fixed
-
Packets received per hour no longer tops out around 50
-
Packets forwarded per hour no longer relies on repeater status counters backed by the capped
recent_packetsbuffer -
Both per-hour sensors now use:
/api/packet_stats?hours=1
-
This now tracks real last-hour packet totals much more accurately
Added
- Expanded GPS diagnostics support from newer repeater API updates
- GPS position source metadata
- GPS time sync state
- GPS time sync enabled status
New Home Assistant actions:
get_adverts_by_contact_typeget_adverts_count_by_contact_type
Changed
- Integration version bumped to
1.1.2 - Changelog updated to reflect newer release history
Notes
-
Based on pyMC Repeater API changes through commit:
e03174d
-
Includes the fix for issue #5:
- Home Assistant packet-per-hour values plateauing below repeater dashboard totals
What's Changed
Features
- Add updates for repeater API version 1.1.2 by @yellowcooln in #6
Full Changelog: v1.1.1...v1.1.2
v1.1.1
What changed
- stopped polling GitHub branch data every 60 seconds
- removed update_channels from the normal integration refresh loop
- left update_status in place so Home Assistant still shows the repeater’s local update state
- changed the update channel UI to use a local fallback list instead of repeatedly fetching GitHub branches
What's Changed
Fixes
- v1.1.1 by @yellowcooln in #3
Full Changelog: v1.1.0...v1.1.1
v1.1.0 - Add expanded GPS diagnostics and gps_stream-based live updates
This release improves GPS support in the pyMC Repeater Home Assistant integration.
Based on repeater commit: e4efc80 from pyMC_Repeater dev.
Added
-
Expanded GPS diagnostics support from the newer repeater API
-
New GPS entities for:
- Enabled / running / stale status
- Geoid separation
- Course
- Magnetic variation
- PDOP / VDOP
- GPS UTC time
- Location update state
- Checksum counters
- Last sentence type
-
Richer GPS attributes for:
- NMEA details
- Recent sentences
- Sentence counters
- Raw GPS attributes
- Location update metadata
Changed
- GPS data now uses
/api/gps_streamfor faster live updates - Standard 60-second polling remains unchanged for non-GPS integration data
Result
GPS entities in Home Assistant now:
- Update significantly faster
- Expose more live repeater GPS diagnostics
- Preserve existing behavior for the rest of the integration
v1.0.0 — pyMC Repeater Home Assistant Integration
Added
- Home Assistant config flow for repeater host, port, and admin password
- Automatic pyMC API token creation and token-based polling after setup
- Repeater/device naming sourced from pyMC instead of only host:port
- Sensors for:
- Repeater
- Packet
- Radio
- Hardware
- Database
- Update
- Room
- Companion
- GPS data
- MQTT broker monitoring (one entity per broker)
- Control entities for:
- Repeater mode
- Advert controls
- Duty-cycle controls
- Update actions
- Maintenance actions
- Advanced Home Assistant actions for:
- Room operations
- Companion operations
- Packet/log lookups
- ACL lookups
- Other pyMC admin functions
- Lovelace dashboard template for quick deployment
- GitHub wiki with installation, setup, entities, dashboard, services, and troubleshooting documentation
Included in This Release
- HACS validation workflow
- Home Assistant
hassfestvalidation workflow - Python smoke test workflow
- Dependabot configuration for GitHub Actions
- MIT License
Notes
- First stable baseline release
mainanddevboth currently start from the same v1.0.0 code state- Canonical integration repo: https://github.com/pyMC-dev/pyMC-HA-Integration
- pyMC Repeater upstream repo: https://github.com/rightup/pyMC_Repeater