[rcarteraz]

Adds the Heltec V4 R8 (hwModel 132, HELTEC_V4_R8), a revision of the Heltec V4 that needed its own hardware model.

The entry mirrors the Heltec V4 entry, with values taken from the heltec-v4-r8-oled env in meshtastic/firmware variants/esp32s3/heltec_v4_r8/platformio.ini:

Field	Heltec V4	Heltec V4 R8
hwModel	110	132
hwModelSlug	HELTEC_V4	HELTEC_V4_R8
platformioTarget	heltec-v4	heltec-v4-r8-oled
displayName	Heltec V4	Heltec V4 R8
images	heltec_v4.svg	heltec_v4_r8_base.svg

architecture, activelySupported, supportLevel, tags, requiresDfu, hasMui and partitionScheme are the same as the V4.

hasMui is true, as on the V4. The firmware's R8 env does not declare custom_meshtastic_has_mui yet, unlike the V4 env; nothing in this repo reads that field.

The image name follows the variant's base section, [heltec_v4_r8_base]. Firmware's custom_meshtastic_images for this env says heltec_v4_r8.svg, so the two differ; nothing in this repo reads that field.

Depends on meshtastic/web-flasher#453, which adds public/img/devices/heltec_v4_r8_base.svg. Merge that first, or this image reference points at a missing file.

Not included:

• The heltec-v4-r8-tft env. The V4's TFT env has no separate entry here either.
• Purchase links. data/deviceLinks.json is synced hourly from msh.to, so R8 links belong there.

Verification

• pnpm validate: OK, 118 devices (117 before)
• pnpm biome ci src/lib/resource.ts: clean
• pnpm build:data: builds

Summary by CodeRabbit

• New Features
  • Added support for the Heltec V4 R8 device, including its display and device setup options.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: d4dd32c8-9e9b-413c-82dd-5346f42b9600

📥 Commits

Reviewing files that changed from the base of the PR and between ed1b38c and bc6faeb.

📒 Files selected for processing (1)

• src/lib/resource.ts

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The device hardware list now includes HELTEC_V4_R8 metadata for hardware model 132, including its PlatformIO target, support settings, partition scheme, and image.

Changes

HELTEC_V4_R8 Device Support

Layer / File(s)	Summary
Add HELTEC_V4_R8 hardware entry src/lib/resource.ts	Adds the HELTEC_V4_R8 device metadata to the hardware list, including its target, support settings, and image.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: thebentern

Merge Risk: ⚪ Minimal · up to bc6fa

The new hardware metadata has no identified merge-blocking issue.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding support for the Heltec V4 R8 device.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the hardware list
One Heltec entry joins the rest
Its target, screen, and image fit
Sixteen megabytes are set
The bunny hops away to rest}

_{Comment @coderabbitai help to get the list of available commands.}