r/Lora

So I have purchased 2 Heltec v4 boards, and some LoRa antennas, I flashed Meshtastic and eventually after trying the latest alpha finally got some good range of about 2 miles. For reference I am the only Meshtastic node in over a 100 mile radius. However today I setup Reticulum using and setup 2 RNODES, however I found my range was less than 1/4th what it was with Meshtastic, to my understanding reticulum will eventually try to fallback to opportunistic mode to send the messages, but I couldn't get anything past the street I was on. Is that normal to see such decreased range in Reticulum? How have your expirences with the Heltec v4 as RNODE's been? I also tried to setup 1 node as an RTNODE to try to backhaul a TCP connection over LoRa, with the goal of setting up 1 node at my office, the other at my house 1.6 miiles away. I have gotten Meshtastic messages to send reliably between my office to my house.

Character (synthetic IG persona, fully-locked identity):

~20yo athletic white European woman, platinum-blonde hair with mint-green tips

2 facial piercings (vertical L-brow barbell + horizontal bridge barbell)

Blackwork tattoos: tree-branch on neck/chest + cracked-pattern full sleeves both arms

5 silver rings (consistent count), matte-black nails

Edgy / punk / skate vibe

Setup that i'm using at the moment:

Qwen-Image (20B) via ai-toolkit (Ostris), uint3 quantized + accuracy-recovery adapter, on a 24GB 3090

87 training images, all generated via ChatGPT Images 2 for cross-image consistency (no real photos exist):

74 bare-arm (tattoos + rings visible)

13 covered-outfit (jackets / sleeves / gloves) with num_repeats: 2 → ~26% effective, to teach conditional coverage so prompting "wearing a leather jacket" actually hides the tattoos

Captions: JoyCaption Beta One → manual cleaning → 2 multi-agent verification rounds (38 corrections total)

Caption strategy: omit invariant identity features (hair color, piercings, eye color) so they bind to the trigger word; caption everything that varies (pose, framing, hair state, coverage status, rings-visible vs no-rings, gloves vs no-gloves)

Hyperparams: rank 32 / alpha 16, LR 1e-4, 3000 steps, adamw8bit, flowmatch, multi-res [512, 768, 1024], grad checkpointing, no TE training, caption dropout 0.05

Mid-training (step 1750 / 3000) results:

✅ Tattoos lock fast and consistently across all prompts

✅ Trigger binding clean: prompts without the trigger generate a random woman, not her

⚠️ Face identity inconsistent — best when the prompt has contextual anchors (jacket + backwards cap); drifts on plain "tank top + grey studio"

❌ Piercings often missing or distorted (the main worry)

⚠️ Mild hair-color leak to non-trigger prompts (cosmetic only — face does NOT leak)

Questions:

Is "leave invariant fine details uncaptioned" actually the wrong call for piercings? Should I caption them explicitly even if it costs the auto-trigger-binding?

Is uint3 quantization the bottleneck on fine details like piercings? Worth retraining at fp8 with CPU offload despite the speed hit?

Is 87 images the floor for a character this feature-loaded — do you really need 150+?

Higher rank (64+) for fine-detail capture, or does that just overfit at this dataset size?

Hard-coupled features (tattoos + rings + piercings always present together) — is one LoRA correct, or would stacked / decomposed LoRAs work better here?

Better captioner than JoyCaption Beta One for this kind of fine detail?

Anything obvious I'm doing wrong?

Thanks in advance guys :)

(all images that im uploading are consistent and come from gpt images 2)

https://preview.redd.it/697181dvg82h1.png?width=1122&format=png&auto=webp&s=d73c3932b0eebf5f23d0bf8dfcc680479d68de45

https://preview.redd.it/bsdie1dvg82h1.png?width=1122&format=png&auto=webp&s=d626161840fd609b21230d1ada8f08d805c282e6

https://preview.redd.it/lfpxv1dvg82h1.png?width=1122&format=png&auto=webp&s=e3f0419c44b62dd75bc4007dda29b80ad6b5191d

https://preview.redd.it/jc4n22dvg82h1.png?width=1122&format=png&auto=webp&s=6853cceab81ac87e1c551d9206fd6deca09a3867

https://preview.redd.it/udseq1dvg82h1.png?width=1122&format=png&auto=webp&s=fdc5b1d1275b4d96067319d2f2e307efd7d13ad9

https://preview.redd.it/mlfsy1dvg82h1.png?width=1122&format=png&auto=webp&s=a08fea65f336f942390a5b2246828b6f4a6193dc

https://preview.redd.it/moe5q2dvg82h1.png?width=1122&format=png&auto=webp&s=878b364380ce19f68978c2c33055ec9863d87aa1

LoRa radios offer incredible long-range, low-bandwidth communication—but only if your antenna is up to the task. A poor antenna can limit you to a few hundred meters, while a well-built DIY design can push past 20 km. The best part? You can build proven, high-performance antennas for just a few dollars.

This guide covers everything you need to build your own LoRa antennas for LoRa and Meshtastic 433 MHz (Europe/Asia/amateur radio), 868 MHz (EU), and 915 MHz (North America/Australia). You’ll find exact dimensions, construction tips, band-specific trade-offs, and real-world performance comparisons.

Stock antennas that ship with LoRa modules, Meshtastic nodes, and Helium Hotspots are typically tuned for minimal cost rather than maximum performance. They’re often mismatched to your specific frequency, use cheap materials, and have poorly characterized radiation patterns.

I've made a few small esp32 and esp8266 sensors in the past, but nothing on this scale, so I'm a little excited and frightened at the same time.

Working on a vehicle presence and telemetry project for my 1976 Land Cruiser. The vehicle is fully analog (no OBD-II, no factory ECU) and I am adding sensors and reporting back to a Home Assistant install at home. I live in Loja Ecuador and my home is on the Eastern ridge of the Loja valley with a clear view of about 2/3 of the city. So I think LoRa is my obvious choice.

Requirements:

- LoRa radio for telemetry back to home. 915 MHz band (Ecuador). I will run a receiver at home, likely an ESP32 with LoRa as a gateway.

- GPS module for position reporting. Periodic position updates while parked (deep sleep with timed wake), continuous position every 30 seconds while the engine is running.

- BME280 for cabin temperature, humidity, and barometric pressure.

- MPU6050 for inclinometer and impact-wake tamper detection.

- Deep sleep with wake sources: ignition on (optocoupler from the HEI distributor), door open (factory door pin circuit), MPU6050 motion interrupt, and a timer for periodic GPS check-ins.

- Powered from the vehicle's 12V battery via a buck converter. Constant 5V so the tamper detection runs while parked.

- Piezo buzzer for status feedback.

My current candidate is the LILYGO T-Beam since it integrates the ESP32, LoRa SX1276, and a NEO-6M GPS on one board. But before I order:

1. Is the T-Beam still the right choice in 2026, or is there a newer board that does this better and is well supported? I have seen the Heltec V3 mentioned for Meshtastic and the RAK4631 for low-power LoRa work.
2. Anyone running a LoRa-based vehicle tracker with deep sleep that wakes on impact? Specifically interested in whether the wake-on-MPU6050 path is reliable when the device has been asleep for hours.
3. For the home-side receiver, what is the cleanest way to get LoRa data into Home Assistant? Raw LoRa to MQTT via a gateway ESP32, Meshtastic, or LoRaWAN through ChirpStack? I was thinking MQTT. I want this fully local (no cloud).

Happy to share more about the project if useful. I'm in the idea/planning phase, so no decisions made yet.

, as a new to thin genere I'm trying to find a cheap receiver easy to build and with a body and an integrated battery.

I'm trying to communicate with my friend.

Also a quick question, how it works precisely, it works even without a Bluetooth and just peer to peer technology?