You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,3 +10,21 @@
10
10
11
11
-[ ] All top level messages commented
12
12
-[ ] All enum members have unique descriptions
13
+
14
+
15
+
### New Hardware Model Acceptance Policy
16
+
17
+
Due to limited availability and ongoing support, new Hardware Models will only be accepted from [Meshtastic Backers and Partners](https://meshtastic.com/). The Meshtastic team reserves the right to make exceptions to this policy.
18
+
19
+
#### Alternative for Community Contributors
20
+
21
+
You are welcome to use one of the existing DIY hardware models in your PlatformIO environment and create a pull request in the firmware project. Please note the following conditions:
22
+
23
+
- The device will **not** be officially supported by the core Meshtastic team.
24
+
- The device will **not** appear in the [Web Flasher](https://flasher.meshtastic.org/) or Github release assets.
25
+
- You will be responsible for ongoing maintenance and support.
26
+
- Community-contributed / DIY hardware models are considered experimental and will likely have limited or no testing.
27
+
28
+
#### Getting Official Support
29
+
30
+
To have your hardware model officially supported and included in the Meshtastic ecosystem, consider becoming a Meshtastic Backer or Partner. Visit [meshtastic.com](https://meshtastic.com/) for more information about partnership opportunities.
Copy file name to clipboardExpand all lines: meshtastic/admin.proto
+107-1Lines changed: 107 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ message AdminMessage {
74
74
SECURITY_CONFIG=7;
75
75
76
76
/*
77
-
*
77
+
* Session key config
78
78
*/
79
79
SESSIONKEY_CONFIG=8;
80
80
@@ -166,6 +166,28 @@ message AdminMessage {
166
166
SD=1;
167
167
}
168
168
169
+
/*
170
+
* Input event message to be sent to the node.
171
+
*/
172
+
messageInputEvent {
173
+
/*
174
+
* The input event code
175
+
*/
176
+
uint32event_code=1;
177
+
/*
178
+
* Keyboard character code
179
+
*/
180
+
uint32kb_char=2;
181
+
/*
182
+
* The touch X coordinate
183
+
*/
184
+
uint32touch_x=3;
185
+
/*
186
+
* The touch Y coordinate
187
+
*/
188
+
uint32touch_y=4;
189
+
}
190
+
169
191
/*
170
192
* TODO: REPLACE
171
193
*/
@@ -296,6 +318,13 @@ message AdminMessage {
296
318
* Remove backups of the node's preferences
297
319
*/
298
320
BackupLocationremove_backup_preferences=26;
321
+
322
+
/*
323
+
* Send an input event to the node.
324
+
* This is used to trigger physical input events like button presses, touch events, etc.
325
+
*/
326
+
InputEventsend_input_event=27;
327
+
299
328
/*
300
329
* Set the owner for this node
301
330
*/
@@ -397,6 +426,16 @@ message AdminMessage {
397
426
*/
398
427
boolcommit_edit_settings=65;
399
428
429
+
/*
430
+
* Add a contact (User) to the nodedb
431
+
*/
432
+
SharedContactadd_contact=66;
433
+
434
+
/*
435
+
* Initiate or respond to a key verification request
436
+
*/
437
+
KeyVerificationAdminkey_verification=67;
438
+
400
439
/*
401
440
* Tell the node to factory reset config everything; all device state and configuration will be returned to factory defaults and BLE bonds will be cleared.
0 commit comments