bdraco · 2026-01-04T22:07:23Z

What does this implement/fix?

Combine consecutive log statements into single calls using multi-line string literals.

Logging is one of the most intensive operations in ESPHome and blocks the event loop longer than most other operations. Each ESP_LOG* call involves formatting, memory allocation, serial output, and network packet transmission. Combining consecutive log statements reduces event loop blocking and the number of network packets sent to connected clients.

Note: The log processor reformats multi-line output so each line gets its own timestamp and log level prefix - the final output format is unchanged. Minor reordering of dump_config output may occur when LOG_PIN or other logging macros cannot be combined with ESP_LOG* calls - this is acceptable as it does not affect functionality.

See https://developers.esphome.io/architecture/logging/ for more details.

Types of changes

Bugfix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Developer breaking change (an API change that could break external components)
Code quality improvements to existing code or addition of tests
Other

Related issue or feature (if applicable):

Pull request in esphome-docs with documentation (if applicable):

Test Environment

Example entry for `config.yaml`:

# N/A - no config changes

Checklist:

The code change is tested and works locally.
Tests have been added to verify that the new code works (under tests/ folder).

If user exposed functionality or configuration variables are added/changed:

Documentation added/updated in esphome-docs.

codecov-commenter · 2026-01-04T22:17:17Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.44%. Comparing base (05695af) to head (e527bce).

Additional details and impacted files

@@           Coverage Diff           @@
##              dev   #12937   +/-   ##
=======================================
  Coverage   73.44%   73.44%           
=======================================
  Files          53       53           
  Lines       11303    11303           
  Branches     1534     1534           
=======================================
  Hits         8302     8302           
  Misses       2602     2602           
  Partials      399      399

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

github-actions · 2026-01-04T22:20:26Z

👋 Hi there! This PR modifies 1 file(s) with codeowners.

@nielsnl68, @numo68 - As codeowner(s) of the affected files, your review would be appreciated! 🙏

Note: Automatic review request may have failed, but you're still welcome to review.

Copilot

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

github-actions · 2026-01-04T22:30:46Z

To use the changes from this PR as an external component, add the following to your ESPHome configuration YAML file:

external_components:
  - source: github://pr#12937
    components: [xpt2046]
    refresh: 1h

(Added by the PR bot)

github-actions · 2026-01-04T22:42:59Z

Memory Impact Analysis

Components: xpt2046
Platform: esp8266-ard

Metric	Target Branch	This PR	Change
RAM	28,484 bytes	28,484 bytes	➡️ +0 bytes (0.00%)
Flash	294,691 bytes	294,671 bytes	📉 ✅ -20 bytes (-0.01%)

📊 Component Memory Breakdown

Component	Target Flash	PR Flash	Change
`[esphome]xpt2046`	1,002 bytes	988 bytes	📉 ✅ -14 bytes (-1.40%)

🔍 Symbol-Level Changes (click to expand)

Changed Symbols

Symbol	Target Size	PR Size	Change
`esphome::xpt2046::XPT2046Component::dump_config()::__pstr__`	109 bytes	12 bytes	📉 -97 bytes (-88.99%)
`esphome::xpt2046::XPT2046Component::dump_config()`	137 bytes	123 bytes	📉 -14 bytes (-10.22%)

Note: This analysis measures static RAM and Flash usage only (compile-time allocation).
Dynamic memory (heap) cannot be measured automatically.
⚠️ You must test this PR on a real device to measure free heap and ensure no runtime memory issues.

This analysis runs automatically when components change. Memory usage is measured from a representative test configuration.

bdraco · 2026-01-04T23:03:20Z

thanks

[xpt2046] Combine log statements to reduce loop blocking

e527bce

Copilot AI review requested due to automatic review settings January 4, 2026 22:07

Copilot AI reviewed Jan 4, 2026

Copilot started reviewing on behalf of bdraco January 4, 2026 22:26 View session

swoboda1337 approved these changes Jan 4, 2026

View reviewed changes

esphome Bot added code-quality component: xpt2046 small-pr PR < 30 lines labels Jan 4, 2026

bdraco merged commit 3ea11d4 into dev Jan 4, 2026
42 checks passed

bdraco deleted the combine-logs-xpt2046 branch January 4, 2026 23:03

github-actions Bot locked and limited conversation to collaborators Jan 6, 2026

Navigation Menu

Uh oh!

Uh oh!

[xpt2046] Combine log statements to reduce loop blocking - #12937