:house_with_garden: Open source home automation that puts local control and privacy first.
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 72%
Response Time: -
First Timer Success: 58%
home-assistant/core has a recorded first-timer success rate of 58.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in home-assistant/core 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 68.0 places home-assistant/core in the A tier.
The external contributor pull request merge rate for home-assistant/core is 71.6%, based on public PR activity from non-core contributors.
home-assistant/core currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in home-assistant/core. Ensure PR scope matches issue requirements closely before requesting review.
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/home-assistant/core?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (90% approval). Large PRs (>500 lines) take ~115 hours (32% approval). Keep your diff compact for rapid review.
The problem Home Assistant MCP intent tools expose name, area, and floor as optional string properties. MCP clients are expected to omit selectors that are not used, but some LLM/MCP clients materialize every optional string property as an empty or whitespace-only string. For example, this succeeds: { "name": "Kitchen Light" } The semantically equivalent call fails: { "name": "Kitchen Light", "area": "", "floor": " " } The MCP server currently forwards those arguments unchanged. The selected Home Assistant IntentTool then validates every supplied target slot as a non-empty string, so the otherwise valid call is rejected because of the unrelated empty area or floor value. These values are empty strings, not JSON null. Expected behavior: When at least one usable target remains, empty or whitespace-only name, area, and floor values should be treated as omitted at the MCP boundary. A call where every supplied target is empty must remain invalid, so it cannot become an untargeted
The problem After any reboot of Home Assistant I get the following log messages: Logger: roborock.data.code_mappings Source: runner.py:289 First occurred: 7:17:10 AM (2 occurrences) Last logged: 7:17:10 AM 112 is not a valid code for B01_Q10_DP 113 is not a valid code for B01_Q10_DP Everything appears to work fine with the robots but not sure if these log messages need to be cleaned up What version of Home Assistant Core has the issue? core-2026.6.3 What was the last working version of Home Assistant Core? No response What type of installation are you running? Home Assistant OS Integration causing the issue Roborock Link to integration documentation on our website https://www.home-assistant.io/integrations/roborock/ Diagnostics information config_entry-roborock-01KGA44BZ29738QGCY5HF7P6RP.json Example YAML snippet Anything in the logs that might be useful for us? Additional information No response
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 home-assistant/core, 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 home-assistant/core acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.6% were successfully merged into the primary branch.
home-assistant/core has a recorded first-timer success rate of 58.4%. 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 68.0 places home-assistant/core in the Welcoming tier.
The external pull request merge rate is 71.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, home-assistant/core 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 home-assistant/core 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.