ESP32 firmware to read and control EMS and Heatronic compatible equipment such as boilers, thermostats, solar modules, and heat pumps
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 89%
Response Time: 2d
First Timer Success: 100%
emsesp/EMS-ESP32 has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in emsesp/EMS-ESP32 respond to incoming external pull requests in approximately 42.6 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 65.8 places emsesp/EMS-ESP32 in the A tier.
The external contributor pull request merge rate for emsesp/EMS-ESP32 is 89.4%, based on public PR activity from non-core contributors.
emsesp/EMS-ESP32 currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in emsesp/EMS-ESP32. Prompt code reviews with positive guidance for new contributors.
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/emsesp/EMS-ESP32?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 Monday - Wednesday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~28 hours (96% approval). Large PRs (>500 lines) take ~204 hours (40% approval). Keep your diff compact for rapid review.
DESCRIPTION On my fresh installed hybrid system with HM200.2 and wlw-7 mb ar I don't get valued für compressor output power and compressor speed. They always show zero REQUESTED INFORMATION Provide the System information in the area below, taken from http://<IP>/api/system {"system":{"version":"3.9.0-dev.4","uptime":"000+00:34:51.618","uptimeSec":2091,"resetReason":"Software reset CPU / Software reset CPU","platform":"ESP32","cpuType":"ESP32-D0WD-V3","arduino":"Tasmota Arduino v3.3.8","sdk":"5.5.4.260407","freeMem":173,"maxAlloc":108,"minFree":155,"freeCaps":4146,"usedApp":1973,"freeApp":2699,"partition":"app1","flash_chip_size":16384,"psram":true,"psramSize":4096,"freePsram":4025,"model":"BBQKees Electronics E32V2.2 rev.2.2/2026012","txpause":false,"gpios_allowed":"2, 4, 5, 14, 32, 34, 36, 39","gpios_in_use":"2, 4, 5, 14, 32, 34, 36, 39","gpios_available":""},"network":{"network":"WiFi","hostname":"ems-esp","RSSI":-49,"WIFIReconnects":0,"BSSID":"set","TxPowerSetting":0,"staticIP
I have a problem with the newest 3.9.0 dev3 with MQTT connection to HomeAssistant. I came from 3.8.2 where eversything worked fine. HomeAssistant always shows all entities as Offline/not available. However, when I look at it in MQTT explorer, I see that all data gets updated very well and frequently. I cleared my broker Mosquitto completely (and removed the MQTT integration from HomeAssistant several times) and restarted ems esp several times but somehow I always get "offline" in ems-esp status topic which leads to HomeAssistant seeing everything as not available. It seems like right after start there are a few milliseconds where MQTT explorer reports that an online was sent but right after it there was an offline setting and it stayed like this... Here is the system information: ` system version "3.9.0-dev.3" uptime "000+10:05:48.306" uptimeSec 36348 resetReason "Software reset CPU / Software reset CPU" platform "ESP32" cpuType "ESP32-D0WD-V3" arduino "T
DESCRIPTION Hello, first off, I’m new to the ems-esp project and would like to thank everyone involved. When my heatpump switches to cooling mode, none of the parameters of the room thermostats (from ems-esp UI/ or HA UI) are applied/ send back correctly to the heatpumps room thermostats. On the other hand all changes made on the physical room thermostats and in the bosch app are correctly reflected in the ems-esp data. REQUESTED INFORMATION systembackup/ config { "system":{ "version":"3.8.2", "uptime":"000+00:15:15.610", "uptimeSec":915, "resetReason":"Power on reset / APP CPU reset by PRO CPU", "platform":"ESP32", "cpuType":"ESP32-D0WD-V3", "arduino":"ESP32 Arduino v2.0.17", "sdk":"v4.4.7-dirty", "freeMem":171, "maxAlloc":107, "freeCaps":4160, "usedApp":2378, "freeApp":2294, "partition":"app0", "flash_chip_size":16384, "psram":true, "psramSize":4093, "freePsram":4022,
DESCRIPTION After upgrading firmware of K30RF from v12 to 14.00.01 my HomeCom app has stopped working whenever I connect the EMS-ESP32S3 gateway to my heating system. As soon as the gateway is connected to the EMS bus, the HomeCom app can no longer communicate with the system. Bosch 7800i system also reports about Locking error 1010 - No communication via EMC BUS connection. CR20RF remote module also shows error 1010. If I disconnect the EMS-ESP32S3 and restart the controller, the HomeCom app works again without any issues. I use ESP32S3-16MB+, initially it was version 3.7.0, then upgraded to version 3.8.2. Also tried to switch EMC Tx Mode to EMS+, EMS BUS ID to Gateway 7 (0x4D) - still the same problem. In system log a lot of messages like: 2026-05-24T15:58:33.151 W 61: [telegram] Incomplete Rx: 90 48 F7 00 FF 0A F0 29 2026-05-24T15:58:36.542 W 62: [telegram] Incomplete Rx: 90 48 F7 00 FF 0C EC FF FF 88 00 07 00 09 00 00 00 00 00 00 00 01 00 00 00 00 82 2026-05-24T15:58:39.075 W 63: [
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 emsesp/EMS-ESP32, 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 emsesp/EMS-ESP32 acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 89.4% were successfully merged into the primary branch.
emsesp/EMS-ESP32 has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 65.8 places emsesp/EMS-ESP32 in the Welcoming tier.
The external pull request merge rate is 89.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, emsesp/EMS-ESP32 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 emsesp/EMS-ESP32 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.