Control your Eufy RoboVac from Home Assistant
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 86%
Response Time: 4d
First Timer Success: 71%
damacus/robovac has a recorded first-timer success rate of 71.4%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in damacus/robovac respond to incoming external pull requests in approximately 89.2 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 52.0 places damacus/robovac in the B tier.
The external contributor pull request merge rate for damacus/robovac is 86.4%, based on public PR activity from non-core contributors.
damacus/robovac currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in damacus/robovac. Reviews community pull requests with focus on project quality.
Discussions in damacus/robovac 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/damacus/robovac?utm_source=github&utm_medium=badge)
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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~58 hours (96% approval). Large PRs (>500 lines) take ~428 hours (39% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Python.
Connect any AI copilot or autonomous agent to your enterprise tools — through a single, secure MCP/Agent gateway with built-in identity, access control, and full observability.
Helpful tools and examples for working with flex-attention
A curated collection of resources for 🌌 Azure OpenAI, 🦙 LLMs (+RAG, Agents). Monthly Updates.
RoboVac Model Code Please provide the exact model code for your RoboVac (e.g., T2103, T2250). You can usually find this in the Eufy app or on the device itself. Model Code: T211A RoboVac Series (if known) Based on the Contributing Guide, which series (C, G, L, X) do you believe this model belongs to, or what features does it seem similar to? Estimated Series: C Observed Features What features have you observed working with this model in the Eufy app? (e.g., Edge cleaning, Boost IQ, Mapping, Room cleaning, Consumable tracking) Features: Vacuum and Mopping Room Cleaning AI Automation Clean Intensity Water Level Indicators Suction Levels Connection Details Are you able to retrieve the localKey and devId for this device using methods like the Eufy Security Web API? (This helps confirm Tuya compatibility) Connection Successful: [Unknown] Debug Logs If possible, please enable debug logging for custom_components.robovac in Home Assistant, attempt to add the vacuum (even if it fails or doesn
feat: Add Protocol 3.4 Session Key Negotiation Summary Protocol 3.4 devices require a 3-way session key negotiation before encrypted communication can begin. This is required for some newer Eufy vacuum models. Technical Details Based on tinytuya protocol notes: Session Key Negotiation Flow Client → Device: Send 16-byte nonce Device → Client: Respond with 16-byte device nonce + 32-byte HMAC-SHA256 of client nonce Client → Device: Send 32-byte HMAC-SHA256 of device nonce Session Key Calculation tmp_key = bytes([a^b for (a,b) in zip(device_nonce, client_nonce)]) cipher = AESCipher(real_key) session_key = cipher.encrypt(tmp_key, use_base64=False, pad=False, iv=client_nonce[:12])[12:28] Known quirk: If the first byte of the resulting session key is 0x00, the device considers it invalid and negotiation must restart. Current State ✅ Protocol 3.4 HMAC-SHA256 checksum support added ❌ Session key negotiation not implemented Affected Models (Suspected) Models that may require sessio
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 damacus/robovac, 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 damacus/robovac acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.4% were successfully merged into the primary branch.
damacus/robovac has a recorded first-timer success rate of 71.4%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. 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 52.0 places damacus/robovac in the Solid tier.
The external pull request merge rate is 86.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, damacus/robovac currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for damacus/robovac 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.