Python API and command line tool for Tuya WiFi smart devices using a direct local area network (LAN) connection or the cloud (TuyaCloud API).
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
jasonacox/tinytuya has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jasonacox/tinytuya 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 7.5 places jasonacox/tinytuya in the D tier.
The external contributor pull request merge rate for jasonacox/tinytuya is 0.0%, based on public PR activity from non-core contributors.
jasonacox/tinytuya currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in jasonacox/tinytuya. Reviews community pull requests with focus on project quality.
Discussions in jasonacox/tinytuya 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/jasonacox/tinytuya?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
hi everyone, I ham having an issue with one dehumidifier that is not being seen by tinytuya. I have tried to scan for the IP and I get this: root@5355b5b34b5b:/app# python -m tinytuya scan -force 192.168.20.17 TinyTuya (Tuya device scanner) [1.16.3] [Loaded devices.json - 4 devices] Scanning on UDP ports 6666 and 6667 and 7000 for devices for 18 seconds... Option: Network force scanning requested. Running Scan... New Broadcast from App at 172.17.0.2 - {'from': 'app', 'ip': '172.17.0.2'} Starting Scan for network 192.168.20.17/32 Unknown v?? Device Product ID = ? [Failed to Force-Scan]: Address = 192.168.20.17 Device ID = (len:0) Local Key = Version = ?? Type = default, MAC = Polling 192.168.20.17 Failed: No matching key found Scan completed in 18.0173 seconds Scan Complete! Found 1 devices. Broadcasted: 0 Force-Scanned: 1 - Matched GWID: 0 Matched Key: 0 Unmatched: 1 Versions: 0.0: 1 Unknown Devices
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 jasonacox/tinytuya, 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 jasonacox/tinytuya acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
jasonacox/tinytuya has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 7.5 places jasonacox/tinytuya in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jasonacox/tinytuya 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 jasonacox/tinytuya 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.