Yeah, you’d have thought. I can’t remember the last time I bought a non-rechargable battery except for 9V for my smoke detectors, and none of them were Duracell or Energizer.

I was surprised by that, too. When I went looking for a way to decode them with RTL-SDR, I assumed it wouldn’t be parsing the audio but a narrowband data stream. TIL also.

Edit: It does kind of make sense with it being AFSK encoded in-band, though, or maybe I’m just so used to it being that way. I always thought the screeches were there to demand attention (and also be something that headend equipment can pick up and respond to). So it’s interesting they’re doing double duty as both an unmistakable audio cue to pay attention as well as containing the actual alert data.

Plus there are NOAA stations all over the country rather than centralized like the time signal transmitters. It was probably cheaper to do it in band at that scale.

I don’t use MQTT currently, but there’s several things you can do with it:

• Pass some messages as plaintext for use in, say, HomeAssistant
• Bridge meshes over the internet
• Send/receive ProtoBuf messages from an MQTT client to the Meshtastic node and the mesh
• Plugging in some of the mesh mapping programs to visualize the mesh

I tried setting up MQTT with HomeAssistant but couldn’t get messages to come in correctly. Most likely my own fault but I just never got back to it as I didn’t have a specific need in mind when I was setting it up.

Most of what I’ve dealt with were ESP32-based devices like the Heltec V3 (now V4) that have integrated LoRa radios. It should be possible to add on a SX1262 LoRa radio via SPI and flash Meshtastic firmware, but most people just start with a pre-built kit since they’re pretty inexpensive and have battery charging circuitry and everything already onboard (which you’d otherwise have to handle yourself with a vanilla ESP32).

I started with the Heltec V3, and the V4 improves several gripes I had with it. They’re easy to get started with, lots of case designs available, and generally good entry points.

SeeedStudio has a lot of pre-built options as well. My new daily driver is the SenseCap T1000e which is about the size of a few credit cards stacked together. Posted about it here: https://startrek.website/post/34105873

There’s two main flavors of Meshtastic devices: ESP32-based and nRF-based. The former are generally a little less expensive and have WiFi but are a lot more power hungry.

The nRF-based ones are more power efficient and can run longer from smaller batteries. The tradeoff is those only have Bluetooth and lack WiFi. I don’t really use WiFi with these, but it can be useful if you want to connect a node to MQTT.

Check out Seeed to see some of their pre-made options: https://www.seeedstudio.com/LoRa-and-Meshtastic-and-4G-c-2423.html

Definitely one of the “throw it on the pile” projects for me, too, but I’m for sure throwing it on the top of the pile. Have had quite a few severe storm warnings this year already and this could be pretty useful. I was originally just looking for a way to forward NWS/EAS alerts to Meshtastic from the internet, but getting them direct over-the-air is even better.

Only complicating factor is I have to fashion or buy an antenna for ~150 Mhz since I don’t have any adapters that will fit the RTL-SDR (I’ve just used the little stock UHF TV antenna that came with it for ADS-B and other playing around).

AFAIK, yes, memory. There are a lot more packets than just text messages. Telemetry, node info, positions/waypoints, etc.

This is from memory and anecdotal, so take it with a grain of salt.

On firmwares below 2.7, I think it only stored the last-received message on the node itself. 2.7+ may store the latest message from up to a few different contacts, but not more than that (if even that). Either way, it’s not really meant to operate as a “mailbox” where you can retrieve the messages later; they basically need to go somewhere as they’re received.

There’s a store-and-forward mode that can be enabled, but it stores all messages for everyone and is more of an infrastructure node role. It also requires hardware that has PSRAM which the Heltec V3’s don’t have.

True, but I’ve had two grid-tie inverters, and both have had anti islanding protection and would not function when there is no utility power. Pretty much all grie-tie inverters have that protection.

I’m specifically referring to the interconnect agreement, though, which is where you have to jump through a bunch of hoops, fill out a bunch of forms, pay a fee, wait for the power company to come and inspect it, and get the utility provider’s blessing before you can hook in a grie-tie inverter and export even a fraction of a watt.

And you have to go through that process every time there’s a change to your system. e.g. If I start out with a 400 watt balcony solar kit, get that approved, and want to add another 400w kit, I would have to file new paperwork, pay another fee, wait for inspection, etc.

I’m all for reasonable safety measures, but the power company in my area is clearly doing all it can to pay lip service to “yes, we support balcony solar” while also making it as painful as possible for homeowners to actually implement it.

I’ve had to plan on a PV+battery+load sharing solution because my utility provider will fine the absolute crap out of you if you export any power without an interconnect agreement in place. I used to be able to stealth grid-tie with the old analog meters (I never produced more in a month than I used), but these new digital tattle-tale meters will rat you out instantly.

Yeah, I was just hoping for something a little more granular than KWh per year.

Nice!

Any idea the running wattage? I’ve been looking to add a mini fridge to my basement but would want to run it from the solar system I’m putting together. My big kitchen fridge is 100-400 watts depending on the cycle, so I’d guess maybe 50-100 watts for a fridge that size?

That’s what I’ve done for years. Makes managing things much easier, and I run multiple APs (all with the same SSID/PSK) and you can just roam to the best one. One upstairs, one downstairs, one in the weird dead zone in my office, and one on the back patio (it’s not hardwired and uses the mesh connection for uplink).

These are all old Aruba APs running OpenWRT but that’s the plan for this Cudy Model. I may pick up a few more and just replace all of my trusty but very old Arubas.

I bought this one last month when it was on sale for $39: https://www.amazon.com/dp/B0BRK3CYY3

Haven’t deployed it yet, but it’s fully supported by OpenWRT. I would only be using it as an access point, though. My router is a USFF Optiplex with an extra NIC and runs OpenWRT.

Only if the USB Implementation Forum doesn’t get a chance to name it. Otherwise, it’d be something like DNA 3 2.0 Super Speed

Truth.

I just see those devices as mesh extenders waiting to happen lol.

I don’t even remember how I learned about Meshtastic. It was just one day I’d never heard of it and the next day I was obsessed and had multiple radios to play with. How I got there? Total mystery.

:sigh: (high five) ✋

I have that same broom, but it’s to unevenly worn to stand up.

Yep, that’s the one.

I’ll reserve a phone but not a truck, lol. Looks like those are scheduled to be out late 2026, so probably at least next year before I can even think about getting my hands on one.

At least it’s still a thing.

I used to drive a 2004 Ranger and loved it. Would absolutely love an EV version even if the range isn’t super great. Mostly need a truck occasionally and for hauling stuff from the home improvement store or if I find furniture at a garage sale or something.

Need to check and see if that $20,000 no-frills EV truck is making any progress.