ua1zbe/meshcore-simple-sensor
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Initial commit: Simple Sensor firmware for Heltec T114 with BME280
Some checks failed
Build and deploy Docs site to GitHub Pages / github-pages (push) Has been cancelled
Details
PR Build Check / build (Heltec_v3_companion_radio_ble) (push) Has been cancelled
Details
PR Build Check / build (Heltec_v3_repeater) (push) Has been cancelled
Details
PR Build Check / build (Heltec_v3_room_server) (push) Has been cancelled
Details
PR Build Check / build (LilyGo_Tlora_C6_repeater_) (push) Has been cancelled
Details
PR Build Check / build (PicoW_repeater) (push) Has been cancelled
Details
PR Build Check / build (RAK_4631_companion_radio_ble) (push) Has been cancelled
Details
PR Build Check / build (RAK_4631_repeater) (push) Has been cancelled
Details
PR Build Check / build (RAK_4631_room_server) (push) Has been cancelled
Details
PR Build Check / build (wio-e5-mini_repeater) (push) Has been cancelled
Details

Browse Source 
- MeshCore-based Simple Sensor firmware
- Heltec T114 without display
- BME280 sensor support (temp/humidity/pressure)
- Radio: 868.856018 MHz, SF7, BW62.5 kHz, CR4/7
- 2-byte path hash
- PlatformIO project
This commit is contained in:
UA1ZBE
2026-06-01 16:19:09 +03:00
commit 42f55e12ae
725 changed files with 98374 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/number_allocations.md Normal file
View File

@@ -0,0 +1,20 @@
# Number Allocations
This document lists unique numbers/identifiers used in various MeshCore protcol payloads.
# Group Data Types
The `PAYLOAD_TYPE_GRP_DATA` payloads have a 16-bit data-type field, which identifies which application the packet is for.
To make sure multiple applications can function without interfering with each other, the table below is for reserving various ranges of data-type values. Just modify this table, adding a row, then submit a PR to have it authorised/merged.
NOTE: the range FF00 - FFFF is for use while you're developing, doing POC, and for these you don't need to request to use/allocate.
Once you have a working app/project, you need to be able to demonstrate it exists/works, and THEN request type IDs. So, just use the testing/dev range while developing, then request IDs before you transition to publishing your project.
| Data-Type range | App name | Contact |
|-----------------|-----------------------------|------------------------------------------------------|
| 0000 - 00FF | -reserved for internal use- | |
| FF00 - FFFF | -reserved for testing/dev- | |
(add rows, inside the range 0100 - FEFF for custom apps)