search

meshtastic / firmware

Meshtastic device firmware
https://meshtastic.org
GNU General Public License v3.0
3.49k stars 863 forks source link

Represent HTTP only features in protobufs so they can be accessed by other connection methods. #787

Closed mc-hamster closed 1 year ago

mc-hamster commented 3 years ago

This was suggested by @sachaw during the Meshtastic Dev Conference.

garthvh commented 2 years ago

@sachaw I still don't totally understand this one

sachaw commented 2 years ago

Yeah, it's not named very clearly. What it's inferring is that http exclusive features. Range test CSV, file system browsing etc should be represented with protobufs so they can be accessed over any connection method.

garthvh commented 2 years ago

https://github.com/meshtastic/Meshtastic-device/issues/1389#issue-1207732505

add range test export over serial interface

triggered by a radioconfig enum, writes over serial using a delimited format with a defined header and footer.

caveman99 commented 2 years ago

I vote for a generic file send/receive over protobufs so we can provision devices by putting proto files into the flash filesystem. One use would be the oem.proto used for a secondary bootlogo and text.

garthvh commented 1 year ago

Is this complete @caveman99?

caveman99 commented 1 year ago

The implementation is done, but there's room for improvement. I think we can close this.