I’m beautiful and tough like a diamond…or beef jerky in a ball gown.

  • 56 Posts
  • 116 Comments
Joined 7 months ago
cake
Cake day: July 15th, 2025

help-circle


  • In order and in character:

    1. [Chidi]: No, that would be highly unethical
    2. [Eleanor] Of course. How else would you do it?
    3. [Eleanor] Obviously they had it coming so no harm no foul.
    4. [Jason] Nah, Pill-Boi said it was fine.
    5. [Tahani] My heavens, no. I would never want to upset my friend Ray. Charles. Ray Charles was my friend.
    6. [Jason] In Jacksonville we’re legally required to.
    7. [Chidi] Given the ethical implications of restraining user freedom but also providing safety for the majority of people, we have to take into account several factors [ pulls out a blackboard, stomach ache intensifies ]…





  • It’s theoretically possible under ideal conditions but probably not practical.

    There is a maximum hop count of 7 which means there can be, at absolute maximum, seven nodes between the sender and recipient. The default, though, is 3 hops.

    While the radios may, in theory, be able to work at the range of “a few states over” as the crow flies, terrain, structures, and line of sight would likely prohibit them from working in practice at such distances. You’d also need a reliable series of hops to reach from you to them. Again, at those distances, you’d very likely exceed the maximum hop count pretty quickly.

    From what I’ve seen, large meshes are generally regional.

    There’s a way to join meshes over the internet via MQTT but I haven’t messed with setting that up and in some cases it can potentially overwhelm a local mesh.


  • My knowledge is incomplete as to what powers and restrictions you get with an amateur license, but I think the only real reason you’d want to use HAM mode in the US is if you wanted to operate on US 433 or maybe the 868 MHz block. Not sure if HAMs have access to the latter one or not, though. The 915 block is pretty permissive here for unlicensed use, so that’s usually sufficient.

    Also, if a node is operating in HAM mode, it may not be able to mesh with other nodes not in HAM mode due to encryption being disabled. I could be wrong about that as I haven’t read into that specifically, but to my knowledge it tracks.


  • AFAIK, you only need to use it in HAM mode if you want to use licensed frequencies, a higher power transmit (assuming the radio supports it; US 915 can transmit up to 1W/30db unlicensed and many radios can only transmit at 22db max), or to go beyond the airtime limitations (there no limitations on airtime for US 915). HAM mode also disables encryption if I recall. Also AFAIK, you’re not required to use HAM mode just because you are a licensed HAM operator.

    Sources: Have read the docs but am not a licensed HAM.












  • What firmware version are you on?

    I had to switch to the alpha version 2.7.16 because that kept happening on my Heltecs. I never got that message, though. It would just randomly disconnect and not reconnect again until I hit the reset button on the node and force-quit and restarted the app.

    Prior to that, the only thing that changed or was updated was the app. My node was still running the 2.5.0 firmware from last March.


  • You sound like a good candidate for a router role, but just to be safe, I would generally avoid “router” unless coordinating with or organizing a coordinated community mesh. That would allow for the best placement without potentially adversely affecting the wider mesh. Client role will repeat just the same but without “overriding” other, potentially better positioned nodes.

    The top of the mountain location, which would provide coverage for both sides, would be the ideal placement for a node in “router” role without consuming a hop to “jump” to the other side.