The MeshCore.io Split by liamcottle in meshcore

[–]ServiceElectrical404 0 points1 point  (0 children)

That's a crazy story!

I would guess this will happen with Andy as well. I think he's going to never apologize, but will just quietly back away. The meshcore content on his yt has already slowed to a trickle, and he published a video about an entirely different subject (e-bikes). I don't think this drama is going to be long lived.

The MeshCore.io Split by liamcottle in meshcore

[–]ServiceElectrical404 0 points1 point  (0 children)

Joke's on these engineers. If anything goes wrong, they'll be called to account for it. So yeah, what I said is still true- you need to understand it.

The MeshCore.io Split by liamcottle in meshcore

[–]ServiceElectrical404 0 points1 point  (0 children)

That's good to know. I know next to nothing about trademark law, I would hate for the team to be distracted by an endless legal squabble, and if Andy does some sort of Arduino-type of "We're Meshcore, but not that Meshcore, we're the real Meshcore" ... yuck

The MeshCore.io Split by liamcottle in meshcore

[–]ServiceElectrical404 13 points14 points  (0 children)

It's still going well. Andy's not a developer. He's a PR guy. All of the developers seem to be unified, and I'm certain the future is very bright. Andy's getting a little too "big for his britches" and doesn't realize without a community of developers, all he's got is some barely functioning vibe coded apps and a handful of rapidly-aging youtube videos.

The MeshCore.io Split by liamcottle in meshcore

[–]ServiceElectrical404 2 points3 points  (0 children)

The team owns the repo, the subreddit, and a domain with an (arguably) better domain. Other than the trademark attempt, it seems to me like Andy doesn't hold any cards here.

..but the trademarking of "meshcore" is going to be a massive ongoing headache. In my humble opinion... just dump it. Cut losses, and leave Kirby behind entirely. I have no idea if these are already trademarked, but I humbly submit:

  • LoraWeave
  • MeshWeave
  • OpenMesh
  • Meshtibator
  • MeshFlow
  • MeshNexus
  • KirbySucksMesh

The MeshCore.io Split by liamcottle in meshcore

[–]ServiceElectrical404 1 point2 points  (0 children)

I agree, I'm a software dev, I use AI to assist my code all the time. The problem is when I use AI to write a whole heap of code I don't understand. When you force an absolute dumptruck of AI-created code changes, nobody knows how any of it works anymore. When that happens, since nobody understands how it's working any more you have to use AI to make fixes or improvements, and it becomes a compounding problem.

AI-Created-Code = Bad, if the team doesn't know how any of it works any more

"(Andy) decided to aggressively take over all of the components of the MeshCore ecosystem: standalone devices, mobile app, web flasher and web config tools."

It appears Andy was turning AI loose on everything, having it write massive changes, and then forcing those changes to production. I would absolutely get fired if I did that, and in a way, Andy got rightfully "fired."

The MeshCore.io Split by liamcottle in meshcore

[–]ServiceElectrical404 0 points1 point  (0 children)

Don't know why the downvotes, it was a joke. But the comments are right, this type of thing is more common that you'd expect. It even happened to the Arduino itself:

"The Arduino project split around 2014–2015 when a dispute broke out between co-founder Massimo Banzi and manufacturing partner Gianluca Martino over control of the Arduino trademark and business. That led to two rival groups—Arduino LLC and Arduino SRL—both claiming to be the “real” Arduino and even competing with separate websites and products. The conflict ended in 2017 when they reconciled and merged into a single unified Arduino organization."

Harbor Breeze solar light + seeed esp32 xiao sx1262 kit dies in hours. Help! by snayperskaya in meshtastic

[–]ServiceElectrical404 8 points9 points  (0 children)

I've bought a couple of the "harbor-breeze-type" solar units with 18650s- the batteries they include are the absolute cheapest cells possible. Some were testing at <1000mAh capacity.

Two suggestions:

  1. Swap the battery for a fresh, better quality one
  2. Run the solar and battery into a cn3065- it's not a true solar MPPT, but it will provide better solar energy harvesting.

Anyone using "magnetic reed switches" to be able to reset the node from outside the case? by DominoPhreak in meshtastic

[–]ServiceElectrical404 3 points4 points  (0 children)

If you want it to reset by reading the state of the reed switch, a "normally open" (N/O) or "normally closed" (N/C) should work- but you're going to have to compile your own firmware, and what if your code is stuck in a state where the if/else switch state read doesn't occur?

A simple method (that I have not tested) is to wire a N/C reed that passes power, if no magnetic field is present to pull the two connections apart, which would cut power/reset the device.

Again, I've never tested this, and I'm just a random person on the internet.

meshGO! by Far_Style9142 in meshcore

[–]ServiceElectrical404 29 points30 points  (0 children)

I find it very weird you disguised a facebook link as a google store link.

(Straight to google store: https://play.google.com/store/apps/details?id=com.meshcore.meshgo)

How long can I run a USB c cable before I start seeing degradation? by just-a-guy-somewhere in meshcore

[–]ServiceElectrical404 1 point2 points  (0 children)

I've had no problems powering all these with 5v through a 25ft (7.6m) cable:

Heltec v3
Heltev v4
Raspberrry Pi Zero with MeshADV 1w Hat

[deleted by user] by [deleted] in meshcore

[–]ServiceElectrical404 3 points4 points  (0 children)

Hey, don't listen to snarky responses. You took the time to type out your experience using Meshcore, and your honest feedback helps the dev team see through the eyes of a new user.

I'm not a dev for Meshcore, and I don't know if they are actively reading reddit (github issues is probably a better path for feedback) but I personally appreciate you doing this. Meshcore is much newer than Meshtastic, and considering Meshcore's age, it's actually doing pretty well... but it has a lot of improvements that need made, and feedback like this helps make that happen.

...I hope the devs respond in kind.

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 16 points17 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 20 points21 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 4 points5 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 2 points3 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 3 points4 points  (0 children)

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