Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Update / New Observation:

未关闭
#3,581 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
c
领域
embedded-iot

调研方向

Start by locating the T-Beam V1.2 target’s sensor and I2C initialization, then trace where the displayed temperature value comes from. Compare the external BME280 readings with any onboard temperature sources and verify which device is selected. Done means the T-Beam reads environmental temperature from the external sensor and reports its humidity and pressure when connected.

由索引模型根据 Issue 内容生成。

描述

I just completely disconnected the BME280 sensor board from the T-Beam. Surprisingly, the MeshCore app still displays the exact same temperature (~52°C), while humidity and pressure are now missing as expected.
This proves that MeshCore is not communicating with the external I2C sensor at all. Instead, the firmware is reading the internal die temperature of either the ESP32 CPU or the AXP2101 PMU and mistakenly displaying it as the environment temperature.
Since these onboard chips naturally run at around 50–55°C during LoRa/Bluetooth operation, this completely explains the ghost readings. The external I2C bus needs to be properly prioritized for external sensors on the T-Beam V1.2 target.

主要语言
C
星标
3.9k
派生
1.5k
平均合并
19 小时 9 分钟
30 天内合并 PR
27

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

meshcore-dev/MeshCore 的其他 Issue

查看 meshcore-dev/MeshCore 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。