Skipping the #TBeamSupreme for this test: two bare #RaspberryPiZero2W boards running #microReticulum with my BLE interface, each sending poetry to the other over their built-in Bluetooth radios.

Two $17 SBCs, 8.8 MB builds, fully secure Reticulum link, and ambidextrous roles: start both, and they decide who is client/server.

#Bluetooth #BLE #Reticulum #RaspberryPi #MeshNetworking

The voyage of discovery expands: I've compiled the microReticulum + BLE interface for my Intel workstation (binary is 8.8M -- ouch!) and have succeeded in having my Intel workstation sends poetry to a T-Beam over Bluetooth and vice-versa. Using a KIVO low quality bluetooth on the Intel. I'm having each unit have its own poem so it's clear where the source is coming from. Next: compile for ARM64 (Rpi4 & then RpiZero2w) and AMD64 (System76 Pangolin)

#TBeamSupreme #Reticulum

Epiphany: I entered the #TBeamSupreme arena to field-test #LoRa and #Reticulum mesh behavior. That led to building a Bluetooth interface.

The surprise: Bluetooth may let me shrink the test range. Instead of sending people blocks away to force LoRa gaps, I can use walls, houses, and barriers on my own property to create repeatable mesh-resiliency tests.

I stress tested the unit for distance and found they remained paired between basement and 2nd floor of a house. Once the unit in the basement went outside the connection broke.

Had the units sending simultaneous and continuous text of: If by Rudyard Kipling.

Now have to consider the logic for resiliency, queuing, heartbeats, and other complicated stuff to make Bluetooth pairing for real world scenarios. I was impressed with T-Beams Bluetooth distance.

#Reticulum #TbeamSupreme