Skip to content

nRF54L15: fix SHT4x sensor libdep (arduino-sht, not Adafruit_SHT4X)#10515

Merged
thebentern merged 3 commits into
meshtastic:developfrom
cvaldess:fix/nrf54l15-sht4x-libdep
May 21, 2026
Merged

nRF54L15: fix SHT4x sensor libdep (arduino-sht, not Adafruit_SHT4X)#10515
thebentern merged 3 commits into
meshtastic:developfrom
cvaldess:fix/nrf54l15-sht4x-libdep

Conversation

@cvaldess

@cvaldess cvaldess commented May 20, 2026

Copy link
Copy Markdown
Contributor

What

The nRF54L15-DK variant (added in #10193) lists Adafruit_SHT4X in lib_deps, but the SHT4x driver SHTXXSensor includes <SHTSensor.h> and is gated behind __has_include(<SHTSensor.h>).

<SHTSensor.h> is shipped by Sensirion/arduino-sht. Adafruit_SHT4X ships Adafruit_SHT4X.h instead and has no consumer anywhere in src/, so the __has_include gate evaluates false and the SHT4x driver is silently excluded from the build — the variant cannot read an SHT4x sensor.

Fix

Replace the dead Adafruit_SHT4X libdep with arduino-sht v1.2.6.

Testing

Validated on an nRF54L15-DK with an SHT40-AD1B on TWIM30 (addr 0x44): 24h soak, temperature + humidity telemetry stable end-to-end.

🤖 Generated with Claude Code

SHTXXSensor (the SHT4x driver) includes <SHTSensor.h>, gated by
__has_include(<SHTSensor.h>). That header ships in Sensirion/arduino-sht.
Adafruit_SHT4X ships Adafruit_SHT4X.h and has no consumer anywhere in
src/, so the SHT40 driver was silently excluded from the build -- the
nRF54L15 variant could not read an SHT4x sensor as committed in meshtastic#10193.

Replace the dead Adafruit_SHT4X libdep with arduino-sht v1.2.6.
Validated on nRF54L15-DK: SHT40-AD1B @0x44, 24.3h soak, 0 reboots,
temperature/humidity telemetry stable end-to-end.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added needs-review Needs human review bugfix Pull request that fixes bugs labels May 20, 2026
@cvaldess

Copy link
Copy Markdown
Contributor Author

The check-label check is red, but this is a race condition — not a missing label:

  • check-label ran at 15:47:05Z
  • the triage bot applied the bugfix label at 15:47:15Z (~10s later)

The PR now carries the bugfix label, which satisfies the requirement. Could a maintainer please re-run the check-label job (or approve the pending workflow run from the latest event)? As a fork contributor I can't re-run it or change labels myself. Thanks!

@thebentern thebentern merged commit e10e132 into meshtastic:develop May 21, 2026
68 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Pull request that fixes bugs needs-review Needs human review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants