The Complete Local (Modbus/TCP) SolarEdge Integration for Home Assistant
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 63%
Response Time: 1h
First Timer Success: 50%
WillCodeForCats/solaredge-modbus-multi has a recorded first-timer success rate of 50.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in WillCodeForCats/solaredge-modbus-multi respond to incoming external pull requests in approximately 1.3 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 71.1 places WillCodeForCats/solaredge-modbus-multi in the S tier.
The external contributor pull request merge rate for WillCodeForCats/solaredge-modbus-multi is 63.0%, based on public PR activity from non-core contributors.
WillCodeForCats/solaredge-modbus-multi currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in WillCodeForCats/solaredge-modbus-multi. Prompt code reviews with positive guidance for new contributors.
Discussions in WillCodeForCats/solaredge-modbus-multi focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/WillCodeForCats/solaredge-modbus-multi?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (79% approval). Large PRs (>500 lines) take ~6 hours (28% approval). Keep your diff compact for rapid review.
Evaluate sensors that could or should be moved into the diagnostic category.
Describe the bug After installing solaredge-modbus-multi v4.0.0 via HACS on Home Assistant OS 2026.9.2, the custom integration fails to load. Setup never reaches Modbus/TCP. Home Assistant cannot import IllegalDataAddressError from the modbus_connection.exceptions module that is actually resolved at runtime: Setup failed for custom integration 'solaredge_modbus_multi': Unable to import component: cannot import name 'IllegalDataAddressError' from 'modbus_connection.exceptions' (/usr/local/lib/python3.14/site-packages/modbus_connection/exceptions.py) The same ImportError is then logged when Home Assistant tries to load the integration config flow. Observed sequence: HACS installed v4.0.0. Integration setup failed with the ImportError above (__init__.py line 29 → hub.py line 17). Config-flow load failed with the same ImportError. All integration entities became unavailable. Rolling back to v3.3.9 via HACS, keeping the existing config entry, restored a working integration. v4.0.0 hub.
Describe the feature Hi, would you mind adding a "only positive numbers" check into the "consumption" template sensor as you did with the "production" sensor? I am having all the fluctuations, see screenshot, and i am not proficient enough to mess around with the math in the sensor. Screenshots Home Assistant (please complete the following information): Home Assistant Core Version: current solaredge-modbus-multi Version: current Additional context Add any other context about the request here.
We're adopting Home Assistant's modbus-connection library for our v4.0.0 release. The first release will focus on minimal changes to adopt the library and to remove unsupported features from the integration without substantially altering the core code so we're not doing a full rewrite in one step (which has a higher chance of introducing regressions). The first changes reduce integration code by about 15%. Future releases will explore leveraging more features provided by modbus-connection. Feedback for the v4.0.0 pre-releases can be added to this issue or to the Modernizing Modbus in Home Assistant discussion.
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 WillCodeForCats/solaredge-modbus-multi, 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 WillCodeForCats/solaredge-modbus-multi acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.0% were successfully merged into the primary branch.
WillCodeForCats/solaredge-modbus-multi has a recorded first-timer success rate of 50.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 hours. 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 71.1 places WillCodeForCats/solaredge-modbus-multi in the Elite tier.
The external pull request merge rate is 63.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, WillCodeForCats/solaredge-modbus-multi 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 WillCodeForCats/solaredge-modbus-multi 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.