Open-source IoT Gateway - integrates devices connected to legacy and third-party systems with ThingsBoard IoT Platform using Modbus, CAN bus, BACnet, BLE, OPC-UA, MQTT, ODBC and REST protocols.
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 79%
Response Time: 5d
First Timer Success: 80%
thingsboard/thingsboard-gateway has a recorded first-timer success rate of 80.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in thingsboard/thingsboard-gateway respond to incoming external pull requests in approximately 115.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 54.2 places thingsboard/thingsboard-gateway in the B tier.
The external contributor pull request merge rate for thingsboard/thingsboard-gateway is 78.6%, based on public PR activity from non-core contributors.
thingsboard/thingsboard-gateway currently has 7 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in thingsboard/thingsboard-gateway.
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/thingsboard/thingsboard-gateway?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 12:00 to 16:00 UTC (12:00 - 16: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 ~75 hours (96% approval). Large PRs (>500 lines) take ~552 hours (35% 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.
Tool for robust segmentation of >100 important anatomical structures in CT and MR images
A Flexible Service Locator for Python.
Efficiently computes derivatives of NumPy code.
When I deployed a thingsboard node and an edge, added a gateway connected to the edge, I wanted to manage remote configuration on thingsboard, but it's not working. I can only update configuration on the edge but not tb. However, telemetries are able to upload to tb. Is there any way to manage a gateway connected to an edge on the tb, that I can manage all the gateways connected to different edge?
Describe the issue There is need to change attributes and telemetry in the broker configuration based of customer needs. However a MQTT broker is hardcoded currently for sending a few standard data samples. It needs attention to customize the broker to allow data keys and values as per customer needs. A set of easy instructions like in other documentation is proposed. Configuration (Attach your configuration file) Notate: Remove Access token from file if you want to attach a tb_gateway.json Configuration file attached. mqtt configuration.txt Connector name (If you need help with some connector/converter): [e.g. MQTT Connector] "MQTT" Error traceback (If it was raised): Missing data as in additional information below. Versions (please complete the following information): OS: As in ThingsBoard Cloud Thingsboard IoT Gateway version: Latest as in ThingsBoard Cloud Python version: As in ThingsBoard Cloud Additional context We set up broker as per 'docker run -it -p 1884:1884 thingsboard/
issue I am running the ThingsBoard Gateway in a Docker environment. Despite successfully mounting my custom tb_gateway.yaml and setting the TB_GATEWAY_CONFIG_FILE environment variable, the gateway ignores the local configuration and attempts to connect to thingsboard.cloud. Environment Gateway Version: 3.8.3 Deployment: Docker Compose Platform: Windows Diagnostics (Proof of Configuration): I have verified that the configuration file is present and the environment variable is correctly configured inside the container: File Existence (docker exec ... ls -l): -rwxrwxrwx 1 root root 197 Jun 29 09:20 /thingsboard_gateway/config/tb_gateway.yaml File Content (docker exec ... cat): YAML thingsboard: host: "thingsboard-ce" port: 1883 security: accessToken: "token" connectors: name: BACnet Connector type: bacnet configuration: bacnet.json Environment Variable (docker exec ... printenv): TB_GATEWAY_CONFIG_FILE=/thingsboard_gateway/config/tb_gateway.yaml Observed Logs: Despite the
Hi, We are currently using the offline gateway installer with Python 3.11. Is there an updated version available that supports Python 3.12?
Hi guys, In the dashboard, I want to press a button and read 25 Modbus attributes in the rule chain (from gateway). How can I do that? I have a bus with 25 controllers and I read a total of 30 parameters/device. Normally, I only need to monitor 2–3 parameters, but if there’s an error I need to set 10 and then confirm that they were written (I read them in Client Attributes). Thank you!
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 thingsboard/thingsboard-gateway, 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 thingsboard/thingsboard-gateway acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.6% were successfully merged into the primary branch.
thingsboard/thingsboard-gateway has a recorded first-timer success rate of 80.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 54.2 places thingsboard/thingsboard-gateway in the Solid tier.
The external pull request merge rate is 78.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, thingsboard/thingsboard-gateway currently has 7 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for thingsboard/thingsboard-gateway 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.