Skip to content

[Feature request] Hardware support: Inhero MR-2 (CE-certified BQ25798/RAK4630 based solar repeater board) #3130

Description

@liekmarflow

The Inhero MR-2 is a purpose-built solar repeater board that went on sale this
week (https://shop.inhero.de/en/products/inhero-mr-2-solar-mesh-repeater-board-rak4630-sx1262-mppt-red-ce-gepruft)
I am the hardware manufacturer and would like to contribute first-class
MeshCore support for it.

Hardware:

  • RAK4630 core module (nRF52840 + SX1262), 45 x 40 mm, CE-certified
    (RED 2014/53/EU, tested by an accredited lab)
  • BQ25798 buck/boost charger: universal solar input 3.6-24 V with MPPT,
    JEITA temperature-controlled charging
  • INA228 coulomb counter: real SOC tracking and 7-day energy statistics
  • Supported chemistries: Li-Ion, LiFePO4, LTO, Na-Ion
  • RV-3028 RTC: low-voltage system sleep (<500 uA) with autonomous recovery
  • BME280 environment sensor

The MeshCore variant is complete and has been running in the field for months
on my own installations. Production boards ship with only the bootloader
preinstalled — users flash the MeshCore firmware themselves (prebuilt images
are available from my fork's releases until this is merged). I plan to submit
it as two pull requests:

  1. A minimal set of board hooks in the core (four no-op virtual methods on mesh::MainBoard plus a board.* CLI namespace in CommonCLI), so a board can expose its own telemetry and configuration commands without touching core code. Defaults are no-ops; existing boards are unaffected.

  2. The variant itself (variants/inhero_mr2/ + board JSON + docs), which uses those hooks. Self-contained.

As the manufacturer I can test changes on real hardware — feel free to tag me on anything affecting this variant.

Transparency note: the firmware for this variant was developed with AI
assistance under my continuous engineering direction and review; it has been
through a full pre-submission review pass and months of field operation.
I am stating this upfront in line with this project's position on code
provenance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions