Home battery prediction and charging automation for Home Assistant, supporting many inverter types
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 66%
Response Time: -
First Timer Success: 67%
springfall2008/batpred has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in springfall2008/batpred respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 67.2 places springfall2008/batpred in the A tier.
The external contributor pull request merge rate for springfall2008/batpred is 65.8%, based on public PR activity from non-core contributors.
springfall2008/batpred currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in springfall2008/batpred. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/springfall2008/batpred?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (82% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
Describe the bug The rolling debug log feature introduced with #4417 is not accessible if you use the HA companion app. Only works with a web browser. Clicking on the 'download all (.tgz) results in the TGZ being rendered in the companion app, not downloaded anywhere: Similar behaviour if clicking on a snapshot in the debug plan view: Expected behaviour To be able to use the HA companion app to download debug log files. I think the problem is that the debug download capability assumes that when a file is clicked, it will be downloaded as a separate file and stored on the users file system (where it can then be attached to a github issue). This isn't the behaviour of the HA companion app. Same problem exists with 'create predbat_debug.yaml', for which the workaround has been to turn on debug mode and then download the file from the debug directory. The idea behind the rolling debug is to regularly capture debug logs so that you have one available to attach to a github issue. The wa
Background I am running Predbat with a Huawei SUN2000 inverter and a ~10 kWh home battery. Predbat detects the inverter as: Inverter 0: Type HU Huawei Solar The inverter is working correctly for charging/discharging and Predbat is able to control the relevant Huawei services. However, Predbat repeatedly reports: Note: Inverter does not support reserve - disabling reserve functions For example: 2026-08-17 18:27:43.126573: Note: Inverter does not support reserve - disabling reserve functions 2026-08-17 18:27:43.126554: Inverter 0 idle time is 08-17 14:30:00-08-17 23:59:00 2026-08-17 18:27:43.126478: Inverter 0 sensor.predbat_HU_0_scheduled_discharge_enable set to False The same message occurs earlier in the run: 2026-08-17 18:25:42.875684: Note: Inverter does not support reserve - disabling reserve functions and: 2026-08-17 18:25:03.018810: Note: Inverter does not support reserve - disabling reserve functions What I find confusing Predbat clearly knows about a reserve value in the planni
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to springfall2008/batpred, 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 springfall2008/batpred acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 65.8% were successfully merged into the primary branch.
springfall2008/batpred has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 67.2 places springfall2008/batpred in the Welcoming tier.
The external pull request merge rate is 65.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, springfall2008/batpred currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for springfall2008/batpred 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.