thomluther/ha-anker-solix - Open Source PR Review Scorecard

Home Assistant integration for Anker Solix Power devices

C-Rank Grade: A (Welcoming) - 69/100

External PR Merge Rate: 84%

Response Time: 2h

First Timer Success: 100%

Frequently Asked Questions

Is thomluther/ha-anker-solix welcoming to first-time open-source contributors?

thomluther/ha-anker-solix has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in thomluther/ha-anker-solix respond to incoming external pull requests in approximately 2.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 69.0 C-Rank™ score (A Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 69.0 places thomluther/ha-anker-solix in the A tier.

What is the external contributor pull request merge rate for thomluther/ha-anker-solix?

The external contributor pull request merge rate for thomluther/ha-anker-solix is 83.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in thomluther/ha-anker-solix?

thomluther/ha-anker-solix currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

thomluther
thomluther/ha-anker-solixA•Welcoming1.1k
GitHub
Back to Explorer
thomluther

thomluther/ha-anker-solix

1,101
Active (30d)A•Welcoming(69/100)Python

Home Assistant integration for Anker Solix Power devices

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
7.2/10
Patience Score
8.0/10
Nitpick Rate
25%

Strict review standards in thomluther/ha-anker-solix. Ensure PR scope matches issue requirements closely before requesting review.

What Contributors Actually Say

Discussions in thomluther/ha-anker-solix focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Link the issue and include reproduction context in the PR
  • •Call out API, migration, or compatibility impact clearly
  • •Add or update tests for changed behavior before requesting review

Top PR Friction Pitfalls (Don'ts)

  • •Do not open context-free PRs
  • •Do not hide breaking changes in implementation details
  • •Do not leave requested test coverage unresolved
Response Velocity
1 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
83.7%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
83.7%
Merge Gauge
100.0%
1st-Timer
Community Vibe92/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for thomluther/ha-anker-solix
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/thomluther/ha-anker-solix)](https://getmerged.abhishekco.de/thomluther/ha-anker-solix?utm_source=github&utm_medium=badge)

Active Good First Issues (3)

View on GitHub

System Health details System Information version core-2026.2.0.dev202601060246 installation_type Home Assistant Container dev true hassio false docker true container_arch amd64 user root virtualenv false python_version 3.13.11 os_name Linux os_version 5.10.60-qnap arch x86_64 timezone America/New_York config_dir /config Home Assistant Community Store GitHub API ok GitHub Content ok GitHub Web ok HACS Data ok GitHub API Calls Remaining 5000 Installed Version 2.0.5 Stage running Available Repositories 3931 Downloaded Repositories 5 Audi Connect logged_in true vehicles 3 region US api_level 0 Home Assistant Cloud logged_in false can_reach_cert_server ok can_reach_cloud_auth ok can_reach_cloud ok Dashboards dashboards 3 resources 0 views 1 mode storage Network Configuration adapters lo (disabled), eth0 (enabled, default, auto) ipv4_addresses lo (127.0.0.1/8), eth0 (192.168.1.96/24

📅 Opened Aug 9, 2026💬 2 comments
Quality: 55/100Contribute

Checklist I have filled out the template to the best of my ability. This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request). This issue is not a duplicate feature request of previous feature requests. Is your feature request related to a problem? Please describe. Hi, I wanted to integrate my Anker Solix Solarbank Max AC into the ha system. Sensor and data is showing now, but I can't send requests to change stuff. It's not responding if you want to set/replace a schedule and it also isn't working when you want to change the charge/discharge power. Describe the solution you'd like A change or further integration so Home assistant can communicate with the Solarbank max and is able to set the power Describe alternatives you've considered Maybe change the setup so it has to send the power value and the Mode(charge/discharge) in one data string Additional context The dada is showing but not sending/updating properl

📅 Opened Jul 18, 2026💬 1 comment
Quality: 80/100Contribute

Checklist I have filled out the template to the best of my ability. This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request). This issue is not a duplicate feature request of previous feature requests. Is your feature request related to a problem? Please describe. No entities to add as list is empty. action: anker_solix.modify_solix_backup_charge target: entity_id: switch.solix_home_power_panel_mqtt_overlay data: enable_backup: true backup_duration: hours: 1 minutes: 0 seconds: 0 Describe the solution you'd like a list of entities to select the proper one Describe alternatives you've considered Tried using many combinations Anker Solix 'Modify backup charge settings' Executed: March 20, 2026 at 5:43:22 PM Error: must contain at least one of entity_id, device_id, area_id, floor_id, label_id. Result: params: domain: anker_solix service: modify_solix_backup_charge service_data: backup_duration: hours: 1 minutes: 0

📅 Opened Mar 21, 2026💬 3 comments
Quality: 70/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for thomluther/ha-anker-solix

When evaluating whether to contribute to thomluther/ha-anker-solix, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of thomluther/ha-anker-solix acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to thomluther/ha-anker-solix

01

Is thomluther/ha-anker-solix welcoming to first-time open-source contributors?

thomluther/ha-anker-solix has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~1 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 69.0 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 69.0 places thomluther/ha-anker-solix in the Welcoming tier.

04

What is the external contributor pull request merge rate for thomluther/ha-anker-solix?

The external pull request merge rate is 83.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in thomluther/ha-anker-solix?

Yes, thomluther/ha-anker-solix currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for thomluther/ha-anker-solix are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.