Mashtastic in SA discussion

Howdy All, I been going through a few Youtube's of people range testing Meshcore/Meshtatic devices and seen everyone has a multiple extra nodes.

I missed a sale on Carbonite last Wednesday someone sold a [Heltec WiFi LoRa 32 V3 (433 - 510MHz)] for R300

TLDR: Anyone in CPT with a spare or cheap board for me to play with, once I got the hang of it I would enjoy investing in the solar/battery backup units.

Make sure you get a 868Mhz node if you want to use it for Meshtastic or MeshCore in Cape Town. Smartcasa as mentioned above or Micro Robotics is your best bet to get going for cheap.
 
Evening All, Im now at hour 3-4 trying to get this to work but seem to be failing,

took a drive to Micro Robotics and got:

Went over to flasher.meshtastic.org and selected the V3 option (pictures helped) something about the API cant pull data when trying to select the firmware, managed to get some firmware and started the old laptop (COMS port connections.)
But I still do not get any success?

Any assistance would be great here, thanks!
(added the Firmware I downloaded from Meshtastic too)
 

Attachments

Evening All, Im now at hour 3-4 trying to get this to work but seem to be failing,

took a drive to Micro Robotics and got:

Went over to flasher.meshtastic.org and selected the V3 option (pictures helped) something about the API cant pull data when trying to select the firmware, managed to get some firmware and started the old laptop (COMS port connections.)
But I still do not get any success?

Any assistance would be great here, thanks!
(added the Firmware I downloaded from Meshtastic too)
This is what copilot thinks:
Your ESP32-S3FN8 OLED board isn’t flashing Meshtastic correctly because the web flasher struggles with API pulls and driver/firmware mismatches. The most reliable fix is to bypass the web flasher and use the CLI method with the correct firmware build for ESP32-S3 devices.

Key Steps to Get Success

1. Verify Drivers & COM Port
- USB-to-UART driver: Install the CP210x or CH340 driver depending on your board’s USB chip.
- Check COM port: In Windows Device Manager, confirm the ESP32 shows up under “Ports (COM & LPT).” If not, reinstall drivers.
- Baud rate: Use 115200 for flashing.

2. Use CLI Instead of Web Flasher
The web flasher often fails with ESP32-S3 boards. Instead:
- Install Python 3 + pip.
- Run:
`bash
pip install esptool
`
- Download the correct Meshtastic firmware for ESP32-S3 from Meshtastic releases.
- Flash manually:
`bash
esptool.py --chip esp32s3 --port COM3 erase_flash
esptool.py --chip esp32s3 --port COM3 write_flash -z 0x0 firmware-esp32s3.bin


3. Match Firmware to Hardware
- The ESP32-S3FN8 OLED049 is not a Heltec V3 — it requires the ESP32-S3 build.
- Using Heltec V3 firmware will cause boot loops or blank OLED screens.
- Always select “esp32s3” firmware, not “heltec” or “tbeam.”

4. Common Pitfalls
- No antenna attached: Can damage the LoRa chip. Always connect before powering.
- Wrong firmware file: Double-check the filename includes esp32s3.
- Old laptop COM issues: Some older machines need USB 2.0 ports or powered hubs for stable flashing.

Risks & Troubleshooting
- Critical fault #3 on OLED: Means firmware mismatch with SX1268 radio. Fix by reflashing with the correct ESP32-S3 build.
- API pull errors on flasher.meshtastic.org: Ignore — download firmware manually.
- Blank screen after flash: Usually wrong firmware family (Heltec vs ESP32-S3).

Next Actions
1. Install drivers and confirm COM port.
2. Download the latest ESP32-S3 firmware.
3. Flash using esptool.py.
4. Connect antenna before powering.
5. Verify boot messages via serial monitor.
 
Many Thanks HandyTech, I saw that was an option but never seen a video on it, will push on and send a message when successful :cool:
This is what copilot thinks:
Your ESP32-S3FN8 OLED board isn’t flashing Meshtastic correctly because the web flasher struggles with API pulls and driver/firmware mismatches. The most reliable fix is to bypass the web flasher and use the CLI method with the correct firmware build for ESP32-S3 devices.

Key Steps to Get Success

1. Verify Drivers & COM Port
- USB-to-UART driver: Install the CP210x or CH340 driver depending on your board’s USB chip.
- Check COM port: In Windows Device Manager, confirm the ESP32 shows up under “Ports (COM & LPT).” If not, reinstall drivers.
- Baud rate: Use 115200 for flashing.

2. Use CLI Instead of Web Flasher
The web flasher often fails with ESP32-S3 boards. Instead:
- Install Python 3 + pip.
- Run:
`bash
pip install esptool
`
- Download the correct Meshtastic firmware for ESP32-S3 from Meshtastic releases.
- Flash manually:
`bash
esptool.py --chip esp32s3 --port COM3 erase_flash
esptool.py --chip esp32s3 --port COM3 write_flash -z 0x0 firmware-esp32s3.bin


3. Match Firmware to Hardware
- The ESP32-S3FN8 OLED049 is not a Heltec V3 — it requires the ESP32-S3 build.
- Using Heltec V3 firmware will cause boot loops or blank OLED screens.
- Always select “esp32s3” firmware, not “heltec” or “tbeam.”

4. Common Pitfalls
- No antenna attached: Can damage the LoRa chip. Always connect before powering.
- Wrong firmware file: Double-check the filename includes esp32s3.
- Old laptop COM issues: Some older machines need USB 2.0 ports or powered hubs for stable flashing.

Risks & Troubleshooting
- Critical fault #3 on OLED: Means firmware mismatch with SX1268 radio. Fix by reflashing with the correct ESP32-S3 build.
- API pull errors on flasher.meshtastic.org: Ignore — download firmware manually.
- Blank screen after flash: Usually wrong firmware family (Heltec vs ESP32-S3).

Next Actions
1. Install drivers and confirm COM port.
2. Download the latest ESP32-S3 firmware.
3. Flash using esptool.py.
4. Connect antenna before powering.
5. Verify boot messages via serial monitor.
 
Okay, after a lot of poking around even using a second laptop (try everything approach) I have success!

Issue though (guess not it). Is the stick v3.1 doesn't have a big enough screen like the other devices.

Appreciated the help All.
 

Attachments

  • Screenshot_20260524_002709_Meshtastic.jpg
    Screenshot_20260524_002709_Meshtastic.jpg
    61.7 KB · Views: 4
  • 20260523_223110.jpg
    20260523_223110.jpg
    298.5 KB · Views: 4
Okay, after a lot of poking around even using a second laptop (try everything approach) I have success!

Issue though (guess not it). Is the stick v3.1 doesn't have a big enough screen like the other devices.

Appreciated the help All.
Ummm, so after all that poking.... What was the last poke that made it work??
 
Okay so that web flasher worked again around 12pm after trying to get the other laptop to work (the other laptop did more with setting up Python and CLI but couldn't install that USB bridge software.

Randomly clicked on the web flasher again calling it a night, and low and behold it populated with a firmware, immediately clicked install and things were happening, tried a different version but seems only the Heltec V3 option works.

The next issue is the screen size so nothing showed up correctly (2nd Pic) then another tutorial showed connecting to the Meshtastic device through a web portal, I pound the Bluetooth pairing settings and changed it from random to static, finally connected and called it a night.

Lesson to the masses: don't buy the boards not in the video tutorials 😅
 
Hate to post so much But I really would like to find out if Anyone is getting the test message
[Based in CPT - Table View]

I also sent test messages for the Meshtastic Monday's but that didnt seem to work either.

f8886848-c0a9-4b1f-aa49-5ab675472844.jpg9d9e9f29-9fee-4afd-9190-7f5f626c5493.jpg
 
Hate to post so much But I really would like to find out if Anyone is getting the test message
[Based in CPT - Table View]

I also sent test messages for the Meshtastic Monday's but that didnt seem to work either.

View attachment 1910631View attachment 1910635
Unfortunately not :( ... in Table View you should be able reach some nodes, maybe try and get a little more height?
 
Hate to post so much But I really would like to find out if Anyone is getting the test message
[Based in CPT - Table View]

I also sent test messages for the Meshtastic Monday's but that didnt seem to work either.
Glad we were able to make contact over RF even if it was Meshcore and not Meshtastic and only from a temporary location. :)
 
Glad we were able to make contact over RF even if it was Meshcore and not Meshtastic and only from a temporary location. :)
Glad so too! I do intend to get a heltec V3 and my V3.1 then I can duel wield both systems.

MeshCore feels more polished Meshtastic seems to be the DIY hands on, custom coding aswell.
 
Top
Sign up to the MyBroadband newsletter
X