Bruno PY2TOZApr 6

Thread with notes on my #meshcore experiment 🧵

Given the most recent issues with #meshtastic (uncollaborative MQTT chatters, limited number of hops, difficulty in convincing others to change device roles), I decided to give MC a try. I'll document the journey here as I go.

Show threadBruno PY2TOZ

Flashing the #meshcore companion now and... I must choose the firmware that has either USB connectivity or BLE, but not both.

That's unexpected. Anyone knows the reason for this limitation?

Apr 6 at 11:22pmWeb
Show threadAlec PerkinsApr 6
@py2toz keeps the firmware size lower, I think that’s the only reason
Show threadLitchraleeApr 6

@py2toz From an earlier, cursory examination of the #meshcore repo, it looked like the structure of the companion app was to await upon commands from only one source. So either it's compiled to look at the BLE interface, or from the USB UART.

It's a very single-threaded way of doing things, but it kinda makes sense since this application is meant to accompany the mobile app or a desktop app. But not necessarily both simultaneously.