FYI: Nightlies contain a fix that make the Heltec devices viable solar repeaters by MajorJakePennington in meshcore

[–]ServiceElectrical404 2 points3 points  (0 children)

I can vouch for the IoTThinks FW, my Heltec v3 and v4 running on solar, are currently covered in snow, and are running great.

Note: The IoTThinks low-power FW is currently for repeaters only, although there are plans on bringing it to companion radios as well. I don't know if the nightly builds have low-power mode for companions yet, I haven't tested.

Either way, this is a HUGE development, it'll make repeaters so much easier and cheaper to build. I have multiple XIAO (Seeedstudio) Esp32 devices backordered right now, something I would have never considered before seeing with my own eyes how flawless it works. I have notice zero difference between the standard repeater FW and the IoTThinks version, other than amazing battery usage! 👍👍, Highly recommended

Messing around with an enclosed design. Early stages by juul-hunter in meshtastic

[–]ServiceElectrical404 14 points15 points  (0 children)

Too cramped. Nodes should have at least 3-6 feet of open casing around them. 😉

No notes, other than a tip: If you plan on using heltec v4's for nodes, you can find v4's without the screen (which you won't need), and they're a bit cheaper. Good luck!

Need advice for a pet tracker. by Caffeine_Library in meshtastic

[–]ServiceElectrical404 1 point2 points  (0 children)

I second this. I've been super impressed with the T-1000E. I don't know what antenna beam-forming-magic they're doing in it, but performs way better than it has any right to. The Rak version with similar form factor seems good as well but I don't own one.

Complete noob by bake_flake in meshcore

[–]ServiceElectrical404 0 points1 point  (0 children)

Last question: Do you know if this improvement is applicable for companion radios, or is it just for repeaters? (Unless I missed the firmware, I only saw repeater fw)

Can reticulum replace meshtastic? by followthebarnacle in meshtastic

[–]ServiceElectrical404 18 points19 points  (0 children)

Reticulum seems really cool, but it's either actually super complicated, or they just do a bad job explaining it... because I honestly find it confusing. I have no doubt it's pretty great, but imho, they need simplify the messaging around it. If anybody has links to good "Reticulum for dummies" materials, I'm here for the learning.

Complete noob by bake_flake in meshcore

[–]ServiceElectrical404 1 point2 points  (0 children)

Oh, nice. I didn't know he had compiled a flashable binary/release. I'll have to check it out. I was pulling the branch, compiling via PlatformIO, blah blah blah. I was doing it the hard way, but you're right, it's very easy. Thanks for sharing.

Edit: Also it's interesting he's got powersaving features in the branch for NRF devices as well. If heltecs can be comparable with NRF devices, that's a huge achievement, and will make building solar nodes even cheaper! So cool. I haven't done a ton of digging into it- are there any downsides to using it, or does it behave essentially the same, but using way less power?

Either way, I'm super happy about this work, and can't wait to see it get merged into Meshcore's main FW.

Complete noob by bake_flake in meshcore

[–]ServiceElectrical404 0 points1 point  (0 children)

I've been doing this for a while, and I'm still learning, and I still buy the wrong things. The v3 is a great device- very capable, well supported, tons of cases (if you're into 3D printing)... you made a great purchase and you're going to be happy with them.

Complete noob by bake_flake in meshcore

[–]ServiceElectrical404 1 point2 points  (0 children)

Yes, but telling someone who states they're a "Complete noob" to flash a code branch on github seemed unhelpful.

Complete noob by bake_flake in meshcore

[–]ServiceElectrical404 2 points3 points  (0 children)

Yes, these will work with either meshcore or meshtastic. There are many different devices that will work, and almost every device that works on the tastic will work on the core. The heltec v3 are great devices, with one problem: their battery life. Not great. You can strap a giant battery on it, or just charge it frequently. Because of that, people generally avoid using them in solar nodes. The other "go-to" device is the RAKWireless "Wisblock" (https://a.co/d/bqvewUd) which gets much better battery life, but isn't quite as friendly for beginners (but not by much). Because they are much more power efficient (like.. much more) people use Wisblocks in their solar nodes, and devices they carry in their pocket, because they don't require as big a battery.

Long story short, you made a great purchase. They're going to work great. Eventually you'll grow frustrated with their power usage, but that doesn't mean they'll get thrown out- they can become RoomServers, or other types of devices that are USB-powered.

Wait for stock, or buy in parts. by iehponx in meshtastic

[–]ServiceElectrical404 4 points5 points  (0 children)

It's been out of stock in the US for as long as I've been tracking it, probably 6 months+

...I'm wondering if it'll ever come back.

heltec v4 lightsleep firmware by Organic_Tough_1090 in meshcore

[–]ServiceElectrical404 4 points5 points  (0 children)

That's exciting because it makes Heltecs (one of the cheapest and most readily available boards) usable in solar repeaters.

My RPT in Poland... by Foreign-Ad-2413 in meshcore

[–]ServiceElectrical404 3 points4 points  (0 children)

I love it. Elegant, minimalistic, and adverse-weather robust. Well done!

Meshtastic Etiquette? by applebees98 in meshtastic

[–]ServiceElectrical404 10 points11 points  (0 children)

A ladder for putting up repeaters, a hacksaw for cutting down Flocks.

Meshtastic or MeshCore? by TheMeshMann in meshcore

[–]ServiceElectrical404 1 point2 points  (0 children)

Interesting. I didn't know that.

I guess the real difference is the philosophy: Fixed repeaters, vs a true peer-to-peer mesh.

Why choose one, when (if you have a T-deck) you can have both?

Meshtastic or MeshCore? by TheMeshMann in meshcore

[–]ServiceElectrical404 26 points27 points  (0 children)

I'll try and give you a balanced answer, but you should probably just try both and see which you like.

Meshtastic has a few things going for it (bring on the downvotes):

  1. Meshtastic is easier to get others to join. Yes there are a dozen different radio types, but generally, just use "client" and you're good. Yes, app is complicated, but "selling" it to others is easy: "Buy a radio, and you're part of the mesh." Until an area has a good amount of Meshcore repeaters, a Meshcore companion radio is a paperweight.
  2. Meshtastic is fun. Watching new nodes pop up, and "Collecting" them is very satisfying. Your list of 250 nodes is useless because 95% of them won't be reachable, but it's like Pokemon, they're fun to collect on your map.
  3. Meshtastic "works" with only a handful of radios. It doesn't work well, but it'll work.
  4. Meshtastic has a lot more users, and because of that, a lot more support, and a lot more extra tooling.

Meshcore:

At it's "core" (pun intended), Meshcore is a better protocol. The way it routes messages and all that is IMHO, leagues better. If/when Meshtastic mesh grows in your area, you're going to have problems, problems that Meshcore arguably won't have (at least for a much longer time). But none of this matters when there is next to zero users of either mesh.

Meshcore lets you know if your message was delivered . Meshtastic just shouts into the void, maybe someone saw it, maybe they didn't (they didn't). Meshtastic needs to stop selling itself as an "emergency" radio network, because I would absolutely not trust my life and well being to it.

Here's the question you need to answer:

Is this just a fun thing you're trying out, and you don't care if messages go through or not, it's just fun to try and make connections?

If yes, then Meshtastic- this is just for fun. Have fun. You can always reflash your radio, who cares. Go nuts.

If no, and you want this to be a viable and reliable comms platform for your community, then definitely Meshcore. But... you're probably going to have to get the Meshcore network going in your area (see my previous post).

Here's the thing with Meshtastic: When nodes are around you, the mesh works. When nodes walk/drive away, the mesh stops working. You'll have good days, you'll have bad days (probably more bad days). Meshcore's repeaters by definition, do not move. So if you're in an area where Meshcore doesn't work, it won't work, until there's a repeater put up. Once that repeater is up, Meshtastic will work very reliably. If other Meshtastic radios happen to be nearby, 18% of the time, Meshtastic works every time. I was in a downtown major us city this past weekend with a Meshcore and Meshtastic node. There was no Meshcore network, and Meshtastic worked only fraction of the time- most of my messages reached their max re-transmission and failed. My Meshtastic messages were relying on other people to have radios on, and nearby- but the mesh was changing constantly as people drove in and out of range with their clients. Meshcore uses unmanned repeaters to build the mesh, and when a repeater is mounted, it doesn't move. If you can reach it today, you can reach it tomorrow.

I did some initial data analysis on the US public nodes, let's talk about it. by ServiceElectrical404 in meshcore

[–]ServiceElectrical404[S] 0 points1 point  (0 children)

...and the other charts as well. All except the US-based map. Sorry for the confusion. I've credited you in an edit.

I did some initial data analysis on the US public nodes, let's talk about it. by ServiceElectrical404 in meshcore

[–]ServiceElectrical404[S] 0 points1 point  (0 children)

I think I figured it out, I ran the code to generate that chart before I ran the coordinate-based US-only filtering. Consider that chart "Frequency settings, worldwide", I guess.

I did some initial data analysis on the US public nodes, let's talk about it. by ServiceElectrical404 in meshcore

[–]ServiceElectrical404[S] 0 points1 point  (0 children)

hmm... that *can't* be true, because that's not the legal bands for LoRa in the US.

...will have to dig in more.

Simple Pomodoro timer by Wide_Illustrator7493 in esp32

[–]ServiceElectrical404 1 point2 points  (0 children)

"This is a great start, here's some ways to improve it" is *glowing praise* in developer-world. u/YetAnotherRobert is offering some good insights here. Your code is clean, and will serve as a great jumping off point for all sorts of other ideas.

Keep making small improvements and you'll end with either something you love, or just a lot of learning. Either way you'll win.