#us - NYC metro
1 messages Β· Page 19 of 1
Lombardis is over rated
So the little 2p3s DC ups battery pack has been awesome n
I'm using it on a spectrum modem at the moment. It works pretty awesome, just plug in the stock adapter into it and the pig tail and it just stays working.
Ideally, this thing could possibly benefit from a balance board for long term. But so far seems to be doing just fine.
I might have to pickup a few of these and just put them on every little router/modem.
I got a spot south of me I wanna check out but it was dough sold out at 7 PM!!! one sec :
check it anyone been
slice place they were super cool but slammed
Haven't tried that place yet. I tried Wizard Hat in Brooklyn.
the Catskills are what I'm referring to when I say upstate
is there a login that allows subscribing on mqtt.nycme.sh? I want to do some data analytics
i promise to not mqtt downlink on the default channel π
You can attempt to write a web scraper for https://meshview.nyme.sh/firehose
i would prefer to not, i just spent hours writing code to decode and decrypt the binary protobufs π
thank you for the pointer though!
One would think... But it's .. not exactly
I might go sling pizza for a week in aug
The water In the Catskills varies dramatically depending on which section of well water you hit
Some can be quite off putting. Some are terrific.
Sure. I can set you up with a read account, check your DMs
o/
woo the app update changed the UI a little
colors all the way across the node list row/cell not just the short name
which app?
About the same weight as my K2 Plus. Things are massive but they print really quick and quiet.
I do have it on a 90lbs slab of concrete. It was very hard to get into the table while also positioning foam layers below it. π
But I love having 350mm cubed volume. The h2d prints really large too.
Overpriced imo but I do sometimes wish I had two tool heads so I could swap support materials.
mesh android
oh, so its like iOS now? I hate how the apps are different
idk I only saw iOS once
about to be in lower Manhattan will see how mesh looks today
@abstract iron packet blast away my fellow junglist
excuse any filter test messages, testing all the filters i have on hand (currently 5: GPIO Labs band pass, NooElec band pass, Airframes Cavity Filter, and I've built 2 of my band pass design to see if there's variance in the filter part/my build)
also some idiot wasted a perfectly cromulent SanDisk Ultra SD card in their VNA (and that idiot was me, swapped for a non-ultra sandisk)
Purely off the VNA the Airframes is the clear winner... until you move off LongFast then you might as well use my design (for 1/10th the cost) and/or go through retuning the Cavity Filter
I'm still planning to move my nodes over on Tuesday
Corey you have that grocery node right
oh! I didn't realize Catalpa was one of yours - always shows up in the Grand & Union pileup
and Corey you're going to medium fast?
huh. Liam Cottle's mesh map has started recommending MeshCore.
OH! was that the station in LIC?
heh not sure, just saw on the AARL field day map there was one in LIC
ohhh yes I didn't know where they were
ohhh nice! I didn't know the name of that park. I see what you mean
how hard is it to recreate your design?
it's trivial and already have a revised version i need to have fabbed but the problem right now is it's way too narrow - basically as useful as not having any filter, ~40 active. right now have the airframes (10x+ the cost, 20x+ the weight) cav filter which is a mere 104 active nodes in just under 2hrs)
i'm gonna try and tune it later, which apparently actually is just removing some of the ceramic material
Uh oh
Aarl had a field day?
yeah, today and tomorrow - so I guess it's more like field weekend day(s) https://www.arrl.org/field-day
I checked pskreporter and didn't see anything with their callsign so I guess they're doing SSB phone?
I can't remember where you find those CW sniffing sites that report seen callsigns
little bit of a problem is that using the filter inline with the external antenna makes it less physically robust. I guess I could rework the inside of the donk to include the filter?
Hah yeah rev2 adds ufl/ipex connectors and waiting on some smt edge ntype connectors to make sure the pads are wide enough for it and sma edge connector - basically make it super flexible
Unfortunately this particular filter sucks for Long Fast (906.875) but should be great for Medium Fast (913.125) - but it stills fees too narrow bandwidth via the gpio labs (because private channels are on diff freqs within the overall 900-930MHz range)
The airframes is also amazing, and similarly narrow bandwidth but perfectly tuned for 906.875 so it works much better on LF out of the box
(And again also 10x+ price and 20x the weight)
wow I didn't know private channels were offset
yeah, they're a random slot
actually maybe slot is derived from the PSK? I forget, it's somewhere in the docs
yeee
While you can have a different PRIMARY channel and communicate over SECONDARY channels with the same Name & PSK, a hash of the PRIMARY channel's name sets the LoRa frequency slot, which determines the actual frequency you are transmitting on in the band. To ensure devices with different PRIMARY channel name transmit on the same frequency, you must explicitly set the LoRa frequency slot.
also I never noticed this lora.ignore_incoming is an array *of nodenums (not !userid) you can set in config.yaml to ignore nodes
Yes hash of primary sets frequency slot for ALL mesh channels. Which is why guides on setting a private primary usually mention setting frequency slot
yeah i wanna tweak the location so it's more accurate. it's actually around lafayette x marcus garvey
yeah, had brainfart - but glad i rechecked docs cause i found lora.ignore_incoming
if you connect via android you can set the precision to more exact, or via remote admin as well. my windownode i set lat/log and 0 precision to get it to be offset
yep i know how to do it. just haven't gotten around to it. i hate that they're all stacked at kellogg diner lol
40.6911 / -73.9397 should be the intersection
or wherever in willimasburg
haha yeah kellogg's is a couple blocks north
Just checked in to update some pocket nodes and noticed 2.6.11. Is this a critical update for the rooftop stuff?
d84c in here?
doubtful since, and since they're running 7hops and messages are coming 5/7 likely not hearing acks/replies
easiest is probably skim the release notes but mostly some cleanup/small fixes, biggest thing from 2.6.10-13 is checking for and alerting on low entropy keys (some devices were being factory flashed with the same firmware/keys, which it'll alert if it detects)
tl:dr; no (because even if you have low entropy key device deployed it's not DMing) and if you have a device with OLED installing 2.7.0 tech preview is well worth it
yah saw their giant hop count via the new UI updates
CT2?? new one
check the first seen time? (does android show that? ios does but meshsense doesn't)
I forgot if I asked this, but if anyone has solar nodes for sale let me know. I have a few rooftops in central Brooklyn and DUMBO I could add them to
there are tons of nodes over by dumbo iirc
theres a distinct lack of coverage by borough park, bensonhurst, and flatlands
very hard to get messages eastward π¦
and to manhattan, I'm very lonely up here
it's not in my nodedb, C2
pizza do you get my pings from Queens etc?
I Was up in Queensbridge park today couldn't figure out which nodes were around me except for Astoria
Negative. Up in this hole called midtown. My 24th floor homie seems to not be around anymore π¦
Sad mesh noises
it's ok, I have othe rSDR projects keeping me busy π
Plane and boat tracking π
Yeah I like doing the planes. do you feed one of the open ones, or, fr24, etc?
I feed all of the account-less aggregators that the sdr-enthusiasts use in the adsb.im image. Pretty sweet....I'm doing ads-b, acars for planes, ais for boats, just fired up radiosonde for weather balloons......have some remote feeders setup at the office and other places, and I am convincing friends to host some....and then I'll sneak in meshtastic nodes later on those raspi's
nice
I usually turn one on around the time of travel to get a business account on FR24
I even have the rtlsdr with built in LNA, and a 1090 MHz filter, for ADSB
yeah, I have two of those adsbx dongles on raspi3's, super portable.
nice
βSo what did you do this weekend?β
Do you hear my Borough Park node? It's called Prospect a031
I can produce these for less than $50
Inside is one 18650 a faketec a bms and a voltage regulatoe
do they get enough sun if they're mounted vertically? or do you usually mount them at an angle?
from the pics i've seen they're mounted vertical but ~35-40 degrees is "ideal"
@brazen spear can i buy a few off of you for $50? or are you just sharing how cheap it would be to make
used to see a031 all the time in Greenwood and at Mama Tried ππ₯³
Yeah we made a how-to guide. I'll re-upload it here. Also can build a bunch but you'll prolly have to wait til August.
Do you not see it anymore? I never could see it consistently.
I'm in that neighborhood every day. Haven't heard it in weeks
not in the window's 606 nodeDB which means hasn't heard it for 6-7 weeks since the db was last reset
Anyone else with a screen on their node update to 2.70? The UI is super nice!
Okay well I reset Prospect a031 and sent a test message... didn't receive it here. Might need to go visit.
Oh it sent a nodeinfo message!
6 hops jeeze. Can't wait for prospect heights to go up.
I guess I should probably have all of these reset every week or two with a cronjob...
smolfox + giant screen π
Wait til you find the clandestine flights.
Apparently part of the aarl field day
It man his website has been the same since 2021
Did anyone get the message from prospect a031?
nope 8(
First and last heard 32 minutes ago. Its back
oh shit, i didn't look back far enough π¬
didnt get the message but def heard it!
I kinda like that as I get a little older and my vision is going TO SHIT
I do have the basic planefence and plane-alert running for funβ¦.i really wanna know when the Goodyear Blimp is around the homies ππ€£
I haven't seen a blimp in ages
I did at the Indy500
I'm not down there anymore
looks like I got nodeinfo 1 h ago but no message. 7 hops π¦
1 hop away. Didn't receive message
I put up a few nodes in NYC east side
Awesome, and welcome!! Which nodes are they?
also the filter tests have concluded and the results are: GPIO Labs is π€, Airframes is amazing but very narrow, NooElec is ok but active/needs power and not as good as GPIO Labs and my design... is as narrow as the Airframes but cuts off harshly right around LongFast/906.875MHz but was about 2/3rds as good as the GPIO Labs for 1/3rd the price, but now i'm gonna get a bunch of different band pass/saw filters with more bandwidth and make up PCBs and see how that goes
Guys hear me out
I had a brainfart
Pwnagotchi nodes and they send the captures over meshtastic to get cracked
not enough bandwidth on LongFast, need bigger solar + battery setups to run
T114 and ESP32
T114 and ESP32 but my collection is growing fast, I also have a car node as I travel between NYC and NJ. Any advice to manage a small fleet of LoRas?
I swear I have to keep blocking Brooklyn Solar Node
is it a router or something
I have a few extra pi zero2ws what should I do with them
Dunno, it is on the list
back up your configs! at minimum the privateKey which can be done by copy/pasting from the mobile apps though they've had some updates recently to make that a little easier, the web-ui if you have an ESP32 before it was removed in latest versions, will have a CTA to backthem up to a file in browser, or via meshtastic python-cli, which will also let you backup the entire device's cfg simply. just be wary about putting them into a git repot that's publically accessible since the privateKey is "secret" and there's also a channel_url which should be also considered "sensitive"
reminder tomorrow is july 1st! for anyone else moving things over medium-fast
What that means?
I know the reasons to change.. is just your message didn't make sense for me I don't know the context.. is july 1st the day all are going to change.. july 1st is the deadline?
i'm not sure who else is doing it but i'm moving my nodes over in central brooklyn
if no one else moves over after a couple weeks, i'll probably move back to long-fast but i hope others join
@mortal wind what firmware version are you on?
@amber edge have you seen https://discord.com/channels/867578229534359593/1389196732587573268 ? related to changing presets
i haven't seen it. but i also don't have access to some of my nodes for a while, so even if that were to merge i won't be able to flash that firmware
I'll change tonight sometime so I'm ready to go
perfect. i'm planning to do it around midnight
I've been rocking that 2.7.0 fw as well for a week or so, I like the UI for small screens
When we cutover, we change to Medium Range - Fast
But, do we need to change our Frequency Slot from 20?
2.6.11
@midnight mural https://meshtastic.org/docs/overview/radio-settings/#frequency-slot-calculator the default frequency slot for medium fast is 45. does that answer your question?
Maximize your Meshtastic device's potential with detailed radio settings instructions, including frequency bands, data rates, and encryption options.
no, I changed my preset on my t1e just now (getting ahead, fuck it) and I changed the preset to Medium Range - Fast, yet my Frequency Slot remains at 20
so I dunno if that will cause a problem, I thought that was what the preset did, but do we need to make 2 two changes instead of 1?
where in the UI are you even seeing the frequency slot? i don't see it on android
sigh, a tale of two apps. iOS app has it in the Lora section
the same way the devs missed naming the presets the same in Android and iOS
yeah, so the iOS app did NOT do that for me
I bet @jaunty harness knew this π (iOS app & Android differences)
there was insufficient entropy in the previous RNG, so the odds were not low
see the caution at the top of https://github.com/meshtastic/firmware/releases/tag/v2.6.11.60ec05e
yeah there were 2 issues, low entropy (not great) but also manufacturer's (re)flashing the same cfg to multiple units at the factory (specifically the
) - and I'm not THAT familiar with the android app, i have it on an old fire tablet that's just the feed for doorcam, and on workphone but don't use either to manage nodes). andoird has been getting a lot of dev work lately so things kinda moving around there
I still have a MF window node up, just a Xiao nRF52840 + WioSX1262 Kit with TE Connectivity Lynx ant and one of my band pass filters since 913.125MHz is in it's "sweet" spot vs LF 906.875MHz being around where SWR >6 and it starts filtering out useful/used parts of the 900-930MHz range
iOS had set slot to 0 which I think is the equiv of manually setting45 (0 in most of the firmware stuff doesn't mean "zero" / "false" as much as "default" value)
I cut over to MF/45 on my two daily drivers. Maybe Iβll see some action Β―_(γ)_/Β―
Bad data
iOS just needs preset changed
"When 0, the slot is automatically calculated based on the primary channel name"
Mine was at 20, not 0
Maybe it moved from 0 the last time I did this
Pizza Pinged from Roosevelt Island on MF, no ack
Maybe this week will be different
Yeah if it was 20 you likely set it at some point / restored it from a cfg
Ahhhh, ok, that makes sense then.
So maybe Iβll set mine to 0 to not have to worry going forward.
Is the Williamsburg Bridge the problem up/down the east river?
was able to reach LF on Manhattan Bridge
on the train
I have an issue with the UI. Certain things like responding are a little clumsy
Itβs moving in the right direction. Works fine on my wismesh pocket
Iβll take that out to the east river tonight and see if I can hit porkβs window on MF
Iβd say the new UI works better than the t1e TX π€£π
I see a e8f6. Maybe flying by
Not me womp womp
I still basically see nobody unless their in an airplane.
Ok serious question I'm going to fly Saturday late evening do we see any value in me sending the flight msg in MF or LF? Using EWR
Thatβs what I was going to do
Just blast with the t1e every few seconds on takeoff
The euro change is EZPZ. I was having fun in Spain and Portugal this spring
yah I'm going to pt
Have fun, chatty bunch!
Wooooo
im liking that you can see replies in the android client
that is nice
MFers what time you cutting over? if I have time/remember I can put a Donk MF up at work but it's typically uptown facing not BK
For me, likely shortly before I fall asleep / go to bed, I guess.
my WRDN is ready
on preset 45
I donβt see anywhere on the nyme.sh site that we are currently on LF 20 or the MF 45 testing we are about to start. Canβt recall who manages the site but can we add this info please?
The website is managed via https://github.com/MeshNY/meshny.github.io/pulls
Idk much about this testing (what the plan is, duration, etc) so not the best person to update the site⦠but this is really good to know. Thanks!
I'll update it after I do the dishes.....why do the dishwashers also not put away the dishes, wtf?
Migrating all my nodes right now
MEDIUM FAST JULY 2025 COORDINATED TEST
We are conducting a full on test to see if Medium Fast(45) is a better fit for NYC than Long Fast(20). If you would like to participate, please do so by joining the Medium Fast LoRa preset in the Meshtastic app of your choice.
Meshtastic App > Settings > LoRa Config > 'Medium Range - Fast' or 'MEDIUM_FAST'
what else should I add, can make more tweaks later, but this is the gist, what did I miss before I submit
Do we know approximately how long we plan to run this test? or is it currently undecided?
I can switch over later tonight.
To not join if your firmware is too outdated, maybe.
I think we mainly want to avoid the issue that happens with one of the AMR nodes in which it aggressively sends NodeInfo in large meshes.
Which firmware version was this fixed in?
MEDIUM FAST JULY 2025 COORDINATED TEST
We are conducting a full on test to see if Medium Fast(45) is a better fit for NYC than Long Fast(20). If you would like to participate, please do so by joining the Medium Fast LoRa preset in the Meshtastic app of your choice. This test will begin July 1, 2025 and will end when the community decides our next step. Check here and our discord channel to stay current and help shape the future of our mesh!
- Backup your keys.
- Firmware version 2.6.x or greater.
- Change your preset:
- Meshtastic App > Settings > LoRa Config > 'Medium Range - Fast' or 'MEDIUM_FAST'
Two weeks sound okay with everyone?
Yeah, I guess we can say we'll decide the next steps at that point.
My range so far is just as good with long fast, if not better?
From ten minutes of anecdotal testing
Very scientific
MEDIUM FAST JULY 2025 COORDINATED TEST
We are conducting a full on test to see if Medium Fast(45) is a better fit for NYC than Long Fast(20). If you would like to participate, please do so by joining the Medium Fast LoRa preset in the Meshtastic app of your choice. This test will begin July 1, 2025 and will end when the community decides our next step in the coming weeks. Check here and our discord channel to stay current and help shape the future of our mesh!
- Backup your keys.
- Firmware version 2.6.x or greater (flasher link below).
- Change your preset:
- Meshtastic App > Settings > LoRa Config > 'Medium Range - Fast' or 'MEDIUM_FAST'
Can you put some wording near the beginning that hints that there's some recommend requirements to look over before making the switch?
backup keys, update firmware and change your preset?
Yeah. I'm assuming some people might not read that far.
lol, it's bulleted so hopping they do
I just closed my pull request, I will add some clearer wording about the steps
but you are right, a little muddy
MEDIUM FAST COORDINATED TEST - JULY 2025
We are conducting a full on test to see if Medium Fast(45) is a better fit for NYC than Long Fast(20). If you would like to participate, please do so by joining the Medium Fast LoRa preset in the Meshtastic app of your choice. This test will begin July 1, 2025 and will end when the community decides our next step in the coming weeks. Check here and our discord channel to stay current and help shape the future of our mesh!
If you are joining us on Medium Fast, please do the following:
- Backup your keys.
- Meshtastic App > Security > Key Backup
- Firmware version 2.6.x or greater (flasher link below).
- Change your preset:
- Meshtastic App > Settings > LoRa > 'Medium Range - Fast' or 'MEDIUM_FAST'
The sentence
If you would like to participate, please do so by joining the Medium Fast LoRa preset in the Meshtastic app of your choice.
should be replaced with
If you would like to participate, please do so by following the steps down below.
ahhh, I like trhat
MEDIUM FAST COORDINATED TEST - JULY 2025
We are conducting a full on test to see if Medium Fast(45) is a better fit for NYC than Long Fast(20). If you would like to participate, please do so by following the steps down below. This test will begin July 1, 2025 and will end when the community decides our next step in the coming weeks. Check here and our discord channel to stay current and help shape the future of our mesh!
If you are joining us on Medium Fast, please do the following:
- Backup your keys.
- Meshtastic App > Security > Key Backup
- Firmware version 2.6.x or greater (flasher link below).
- Change your preset:
- Meshtastic App > Settings > LoRa > 'Medium Range - Fast' or 'MEDIUM_FAST'
"will end when the community decides our next step in the coming weeks"
to give us some wiggle
ok, submitted pull request for real for real.
can make any tweaks the next few days if need be
yes, it's happening
I'll head to the east river in a bit and see if i can hit any of you all in Q & BK on my WisMesh Pocket on MF
Migrated my nodes! Got two more coming next week I'll put on MF in central Brooklyn roofs
My solar is refusing to BT I'll try to get it going
God damnit. I don't want to switch to MF.... Everuthing I have is set up for 906.875. I don't mess around with the 915mhz centered stuff... π
thanks
awww, you know you want to π
Nope, not really. Not even a little bit. I LIVE IN WESTCHESTER! Who am I medFasting... lol
Just sent test MF. have a T1E & solar moved over
oh, yeah, nope LOL
Everything? You don't have a single "normal" node?
"Normal" is a setting on a washing machine lol.
Let me merge thisβ¦
Done!
Oops, someone center-aligned one of the main headings (in green):
And I'm sure I have some antennas in the "crap" bin that i don't bother with because they're tuned too high.
mmmm wanna say late 2.4.x/2.5.0 but really 2.5.x should be upgraded to 2.6.x because of the LFS issues anyway so I'm cool drawing a line at 2.6.0 for the test
so far it's like being somewhere with no nodes laugh. let's see if we start to see some nodeinfo
sending is faster
Should we ping the user behind Harlem Relay?
@abstract iron it's not even july 1st! and yes my messages and traceroutes are quite a bit faster
I have good LOS to Queens and Brooklyn, so I know my Roosevelt Island pings should be somewhat ok
I'm sending test on MF
starting to see some MF nodes in telemetry π
Iβll still be in this hole π
I find it funny some of us canβt wait till tomorrow. But you know, canβt be too prepared π
Annnnnnnnd my two nodes canβt hear/talk to each other so I assume none of you either
I nuked my nodeDB when I switched over to MedFast. I want too see what I can actually see on it
Set your frequency slot from 20 to 0.
long-fast: 20, medium-fast: 45, or you can set it to 0 to pick the correct value for whatever preset you are on
You show on channel 20
a.li3n? or someone else?
Alien. Sorry, my discord updated really slow
all good. just making sure it's not me π
I factory reset and got this!
which firmware version?
2.7.0, rebooted and itβs fine
Tried that, now it's on 902.125mhz lol I'll change it to 45 and see if that makes a difference.
I never nuked it when I updated to 2.7.0β¦..Iβm just starting fresh, whatever :). backups at home
Changing to 45 worked.
Assuming you've followed https://meshtastic.org/docs/configuration/tips/#creating-a-private-primary-with-default-secondary previously, make sure to also rename the LongFast channel to MediumFast.
Tips and Solutions to help you get the most out of your Meshtastic device and network.
Yall want me to switch all my rooftop nodes?
Yes please if possible
If they're 2.6.x or newer and it's convenient to do so, yes please.
Nuked everything, and now my t1e is doing this lol
I believe that's the range test module doing what it does.
Okay but they're all 2.5.20
Do I need to change to 2.6.11?
Will be more work.
Does this update wipe the config like last time?
That should be new enough.
Thank god π
(I have no idea)
What's the LFS issue?
I will investigate
LittleFS filesystem corruption issue, which IIRC was fixed in 2.5.20.
You were correct! Thatβs neat! And on by default, strange but ok
IIUC, that would be a bug.
Yeah right. Okay I'll just switch to medium fast 45
going 2.5 -> 2.6+ IS A CONFIG WIPE!!
Yeah no I'm definitely not doing that then π€£
yeah just go to MF45 and save the updates for another time (as it will take some time)
you get a pass on this one, but also 2.5.20 was when the LFS stuff was sorted IIRC so the "should be upgraded to 2.6.x" isn't exactly right as much as "should be upgraded anyway"
Someone want to save me time and tell me the cli command?
i think it's meshtastic -t --set lora.modemPreset MEDIUM_FAST --set lora.usePreset true but gimme like 30s to try π
Looks right from the meshtastic.org docs
yeah that worked
What's the -t part of that?
the usePreset should be the equiv of setting value of 0 / "default" slot 45 (in this case)
-t = localhost connection, sorry muscle-memory
it tries serial connection by default but if you're doing meshtasticd -t saves you like 5s of it doing the serial check then falling back to localhost
I don't think the -t is needed for me
yeah... unless until you start playing with smolfox or the 1W pihat or the meshstick π
actually gonna put this 1W in the last free window, since 1W and PoE, should be better than the xiao nrf+wio that's been sitting there hearing nothing for months except when zilla was like a block away
and far as firmware... any 2.6.x update will wipe you device so backup + update + restore cfg for each
meshtastic --port /dev/ttyACM0 --ch-medfast
I did that to the solar
and then re-exported the config to keep for swapping around
I wouldn't necessarily know if that automatically fixed the freq preset except that my android configured t1e worked MF with the ZLLS MF so
I just saw GrandSt come up
on MF
i cant seem tp get a good connection to my pony expresses im gonna have to walk close to them
pork let me know when you pop that up
pizza you got link to Grand?
I did grand vernon lilybx and Prospect
I can't tx from pizzadeliverydude to caseyjones, but I can the other way......can there be something fucked up in my radio not letting it tx more than node info or is that not sound?
key or something?
no, just says max retries etc
well, I guess it could be
but it is symptomatic of not sending in the first place
P1NY just showed up for me
Southslope has wifi connectivity issues. Will have to do over remote admin at some point.
Also... realizing I'll have to do remote admin for a few over the air, which needs to happen sequentially or when I'm close to them.
Lol that's why we try stuff. To learn the most obvious things π
Have a T-Echo on 2.7 and MF45 in my window for now. So far, Iβve picked up 703d with incomplete info.
Haqer which way you face in your new spot?
How long are we gonna run this test?
first message went through
pork ultrafox-lyra / π¦Ύ is up in the middle window... precariously... and powered by 3M Blue tape
Iβm facing North from Marsha P Johnson Park now
haqer you're f25a right
Fa5a
yes, thatβs the T-Echo I have on MF now
I got your test
(I think) it's been so long since I built that lol
Nothing set in stone, but likely at least a week or two, then we'll collectively make a decision on what to do next.
Yes! thats the node you built.
that one is still on LF20. Need to update the FW on that before moving to MF.
i didnβt get your reply
we need all those secret nodes that help me out like Metaphor to cut over
Anyone see the himrod solar message?
no
Hi gangβ¦.New to the NYC mesh
S301 and S302β¦.primarily operating out of Forest Hills, Queens
Just in time, we testing out MF.
As in MediumFast, which is not to be confused with the other meaning of MF.
Doom? /s
just remember to use ALL CAPS when you spell the mad name
Yes, MF DOOM.
Saw that!
Whatβs the concept behind that test, MF improving range since are a fairly dense mesh?
lowers message congestion for a slight loss in range (theory).
1/2 the tx time for ~10% loss in range, but also ditching the old firmware/poorly placed nodes running infra roles - and yeah we're dense enough it should be sustainable
Also, many of the older nodes that are on the REPEATER/ROUTER(_CLIENT) roles are intentionally left out.
Just received βHimrod solar2 testβ
But no ack
first message i received on MF
this little T-Echo with stock antenna iβm sure hears better than it transmits
Im in the opposite situation
I don't think vernon is working. Anyone seen it on mf?
Should've gotten an ack from vernon
Perhaps from grand
haven't heard it on LF since 8:18PM
I still have everything being ackβd immediately on MF
Can you traceroute to grand?
351e? i only have node ids, no names
both of my esp32 devices do not like MF
MF might be a stretch for NJ
@brazen spear no response but shows 1 hop away. i donβt live at domino park anymore so no longer have direct LOS to the grand st node π₯Ί
Iβm at Marsha P Johnson Park facing North now
hitting 703d directly there and back
received grand test @brazen spear
Well I don't know why grand worked but vernon didnt
yep i see 351e from bed stuy as well
finally got the nodeinfo for the node i can consistently hit directlyβ¦ itβs P1NY Pony Express Solar
the tape was giving out so swapped back to the xiao nrf + wio MFer
Updated fa5a to 2.7 and have it on MF 45 now. Still havenβt decided on a naming convention for my nodes so might rename this node later.
@brazen spear this node sees Vernon2 4b7b with node info right away
got the vernon test message and replied
This node with its 5.8dBi antenna is already performing better than the T-Echo was on MF
getting the vernon and grand test messages
The issue was Vernon's primary channel was named LongFast. Not sure how to remove it, but can manually adjust depending on what we're on.
First assessments here are that Vernon apparently is not retransmitting from LilyBX or grand or prospect. So, no meshing due to distance I would guess. I'd like to suggest perhaps simply changing the frequency slot instead of the modulation. Has anyone done a survey of the iot band to see which frequencies are least used?
Could the rain/weather have made enough of a difference tonight?
Otherwise, I wonder if Medium Slow (like sf bay) would have enough range to reconnect those nodes.
Glad that one swapped over I didn't get an acknowledgement. I think at this time 1, 4, and 0 should have swapped to MF
biked to work I only got P1NY
Thanks Im still trying to get a response from p2ny while at work to swap it
my other nodeinfo are at least 7h old
bike ride is about 24 mins so I would have had to get lucky for more broadcasts I guess
in that window
In time square and I'm on an island, as usual. No Acks. Nothing.
My main node is on mf now
switched SST briefly to Med Fast and had 0 connections, 0 ACKs, switched back. QMOD2 still on MF.
Nothing of mine has been acked
Updated the meshview code, it does a better job of seeing packets from all presets now. We've got 1 MF node representing thanks to P0NY. https://meshview.nyme.sh/map
Reminder it's day 1/14 and not everyone has switched over
Sure, but if I can't get MF acks between the 2 nodes I have on the same campus I'm not swapping my main infra node full-time yet. Will leave the secondary there as it was always intended to be.
Man I keep reading MF and thinking we are all cursing π€£
just moved pork femtofox / π¦ / 883c over
no real good way to secure the other node so fuck it
i can only see one other node at the moment π₯²
Although I haven't heard from this node since, the following was received at Great Neck, NY on MF:
i mean... it's kinda apt for someone named Uno - but also takes time
no nodes present in this MF
Where are you based?
you can continue to periodically wave at us in the hudson valley
need to change the channel name?
Only if you're following these instructions: https://meshtastic.org/docs/configuration/tips/#creating-a-private-primary-with-default-secondary
Otherwise, switching radio presets does it automatically.
Discovered ZLL1 on MF.
oh nice that's my t1e
I'm just going to launch a ballon tethered above my house with a node on it....
iβm in midtown closer to hudson
changed to MF and clear the node list.. so far nothing yet.. I'm at West Orange
b344 is on MF.
ill put ZLLP near my uptown facing window but usually
it doesn't help
P3NY installed and on MF
got the test message
Wooo
That's great once P2NY is on MF it should help
Thank you for your infra work
MF looks like tx attempts feel so much faster than LF.
i get acks seemingly within a split second whereas it used to take a few seconds on LF
sounds promising
Just got ZLLP on my node list leggooo
Smorgasburg fa5a
~.5s tx vs ~1s tx, and then on other side it's same time to RX, and then again to re-TX the ack
so you're basically benefiting at ever part
Itβs even more apparent that S&F modules would be a necessity as more nodes propagate the mesh network since a lot of nodes have a list limit (200)
(already reached mine on b344).
clearing out old nodes do help
depends on the node - nRF are capped at 80 nodeDB, meshtasticd... I'm at 600 of 1000 max
more appropriate clients for infra roles, indeed. meshtasticd is definitely a necessary library to export the bulk of the work to systems that can handle it (Time to get the LoRa pi Hat I was putting off until now).

haqer I got you over here
That's my mobile node
i see your tapbacks. youβre 4 hops away
ayee
i see BOKN too
turning into off grid discord rn lmao
someone near me must be a strong MF because I'm getting mesh inside the building as I rip between meetings
I got two nodes on the network to push as much tx as possible.
Yay!
Yeah Iβm also seeing you over here
Woooooooo
I'll leave it on MF
Although
.... Yeah my solar ain't so great so it will only work between sunup and 2 hrs after sundown lol
internet with a natural curfew
lol
accidentally sent couple carriage return/new lines in last message, was able to just send it through
instead of max tx attempts,
P2NY reached on MF. so promising 
Wooo that's great
P0NY to P3NY are on MF just n3d to get to P4NY to swap it
same here (the lyra is now tx_disabled so stopped broadcasting)
easy and fast TR to you.
yeah, the squares have heavy interference. I sent a couple of messages between greenley and herald squares
no acks
7-9 aves work away from the squares

Range does seem to be affected quite a bit then. My biggest concern is Gardnerβs nodes not communicating with each other anymore when we were only supposed to lose ~10% range
Itβs obviously still too early to tell for sure
I don't think I have any more easily accessable roofs
I say mother fucker in my head every time π
hrmmm, should we also all be running CLIENT? fdc0 is running CLIENT_MUTE so far less likely to be heard / won't retx to expand coverage of M(other)F(luffer)
Do you see my TMNT nodes, Iβm in your picture π
How is the first half of day 1 going for everyone?
not able to get some messages out in my area, but i also know a few of the nodes close to me haven't migrated yet
I had no nodes until I got P3NY and P2NY up
All my nodes are on MF
heard fcd0 again but they're 1/7 hops so something inbetween is relaying (probably Vernon2)
Able to reach a couple of nodes between @abstract iron and @twin root so far on ground 
was in buildings before.
are we actually moving to medium fast?
Weβre just testing for now but eventually want to evaluate and move to a preset that is not Long Fast
so should i go to my rooftops to change the node modes or no
If youβd like to participate in the testing, yes. The more people who participate, especially high/rooftops nodes, the more realistic this test will be.
is medium fast longer range or faster than the normal one
alrighty
lets see how this goes
You can read about the testing and recommended settings here
Medium Fast has less range but more bandwidth
so far faster tx and rx
makes the BBS system viable imo so far.
According to mesh view, both of my nodes are showing up on MQTT, good sign: https://meshview.nyme.sh/top
is anyone able to see GHFC? just want to make sure someone sees it besides me π
I donβt see your node on meshview atm, π«
I didnβt notice them before I left this morning but most nodes had incomplete nodeinfo so no names
Had my node "Auto" up most of the day - only see one node π©
is the person who manages Steiner Studios Tower active in here?
i just remembered that's a popular node in my area
Yeah, they are here iirc, but they are currently on LF rn.
@fervent nebula currently admin those nodes
thats me.
I've just switched SST to MF, still no contacts on QMO2, but heck it I guess.
Back home for a bit and iβm up to 18 other nodes in my list now
I'm only at 12 nodes but seen 213 times according to meshview
I also run the meshview π
iβm trying to understand the refresh rates on these things just in case if i show someone how this works, i wouldnβt be blind-sighted too much
in IRL demos
the MQTT reports whenever a packet is recieved/sent, SST has default telemetry enabled so it logged that sent packet and shipped it to the mqtt service. meshview database refreshes the data live from the mqtt notification, and the page is rebuilt about once a minute. so if your node is sending mqtt packets it should become visible in less than 3 minutes (or when full nodeinfo is available)
thatβs a good rubric to tell if someone is on the mesh then, since the view refreshes on packet
there are other devices reporting to mqtt, so it'll be updated when any of them see the packet. You can also check the https://meshview.nyme.sh/firehose to see (close to) live packet insertion.
Still getting 0 confirms/contacts on SST. Sad node energy. Gonna go hit some dinner, will check back later.
This is what Iβm seeing so farβ¦ for nodes who are sharing location
mesh usually picks up a bit when the sun goes down, hopefully rain will have passed by then
Also, the modulation of activity/discoverability is much faster than LF. travel Nodes that would report βonlineβ for extended periods of time on LF now update fast on MF.
but names seem to die off after a distance i cant get p1ny to tell me its name from p0ny
less nodes = less exchanging nodeinfo. you can cheese it a bit if you have a pre 2.7.x / BasicUI device (or a T1000E w/2.7.x) you can double-press the user-button to send an ad-hoc ping, otherwise try sending a traceroute
My node map on day 1 of MF
interesting, is βok to MQTTβ enabled on GHFC?
none of my nodes have MQTT enabled. tbh i still don't really know what MQTT is
Discovered P4NY direct on subway.
the best way I can describe it is comparing the ecosystem to torrenting: the trackers/seeders are analogous to the website nyme.sh provides. Itβs a pointer (called a βbrokerβ) to a set of nodes (βclientsβ) under a given topic (location is usually the designation).
i think that created more questions for me than answers π
I can only see pork 883c but not get to that node
does it require nodes to be actively connected to the internet at all times?
not really, it helps for discovery
instead of depending on LoRa completely for nodeinfo, MQTT takes care of that and quickly encrypts contact instead of wating for the handshake to complete
what's the benefit of it? besides showing up on a map. i thought the whole point of meshtastic's routing is that nodes don't need to be discovered in order for them to be relayed
faster discoverability and longer reach depending on whoβs on topic.
how does the longer reach work?
Like a guestbook. If there was any info that you had a presence on nyme.sh with the same public key, any other nodes who are on that topic would auto accept the node because the node was on the same topic at a previous time..
why does it extend the range though?
shouldn't messages be reachable, regardless of whether they have MQTT enabled?
Yes, and the difference is how info is sent over; LoRa only takes a bit of time to get the nodeinfo straight from network, minutes to an hour depending on the quality of connection. MQTT cuts that work out by looking up the node on the broker to see if they are on the same conversation.
and if the node hop count is greater than one, it takes a long time to show up on your node list if going through LoRa only.
gotcha, that helps a bit with my understanding. i'll do some more reading on the website too
what train?
The "OK to MQTT" is actually a flag that gets added to messages sent by your device, indicating that nodes are allowed to forward those packets to an MQTT server. Without that flag, the packets will not appear on any of the nyme.sh tools. In addition to the recording of data, MQTT on some servers (not MQTT.nyme.sh) can be used to bridge two distant nodes via the Internet and pass messages as though they were radio connected. The "Ignore MQTT" setting tells your node that messages that have come from a MQTT server should be ignored instead.
The other MQTT server settings are only applicable to Internet connected nodes, and set the mqtt server and service information.
Iβm going to switch four or five different nodes to MF tomorrow around different parts of Brooklyn
Some tools (MeshSense) don't bother to respect the OkToMqtt flag or use the MQTT service.
You also donβt need MQTT setup to bridge now that thereβs UDP
Sure, that's another good way to do it. I'm just answering the mqtt piece
DNRQ Line
fair, and it's not like MQTT bridging is deprecated but UDP is def way less overhead (if your node can network). i think better example of MQTT use is have a buddy in Cali, one in Texas, one in Boston - we all use a private MQTT broker (server) and can have a shared channel that spans the entire US even though our RF will never reach each other
exciting!
Boston mesh for instance uses MQTT to bridge to parts north of the city because they have a couple rouge repeaters downtown and can't get out otherwise
Yeah that makes sense. since itβs a quick toggle, that means I donβt have to haul the packets back after establishing an encrypted connection on primary channel.
I think MQTT is interesting as a backup plan or for location reporting but it would be nice to stay RF-only if possible, excluding the Boston example. there are analogues elsewhere like ham links that use public IP to link voice systems that have local RF. cheating? or just usable? eh...
Yeah I'm thinking that ~10% was theoretical.
fdc0 is just on my desk at home
Ah-ha! Well I was hearing it earlier but been a few hours, now I'm seeing !124d441a direct but no NODEINFO and even though it seems to be direct no SNR/RSSI to gauge the signal (it's like MeshSense doesn't know how to deal with non-LF?)
Do we need someone to do a survey of the ism band to see which freq slot is most unoccupied?
I'm thinking picking the best frequency would be more beneficial than a modulation change for reliability
I moved my node to Medium Fast, doubt I will get anything in NJ
I think default slot is probably best for now since itβs should be just changing preset vs additional complexity of quantifying the whole band for the optimal slot and explaining how to set that on iOS/android/webui/mui/bui/python-cli
For now I see waaaaaaaaaaaaaaaaay less airtime/channel utilization so while thereβs certainly a more optimal slot we at least ditched sharing 15%+ utilization on 906.875
yeah, I see 0% utilization π
i think either 441a or myself has a channel misconfiguration - I see plenty of their packets but can't decode and always show "encrypted". since I was able to decode gardener's fcd0 node earlier I'm blaming 441a π
after doing some more reading it looks like the UDP is multicasted on the local network, which means both radios would have to be on the same LAN to bridge using UDP instead of mqtt, no?
lan/vlan/vxlan
sure, but setting up a vxlan at a remote site is definitely more work than having mqtt from the device
doesn't have to be separate devices though, traditionally the way presets were bridges is a raspi running mosquitto and multiple radios connected to and bridging via MQTT, now they just send all that traffic over localhost
other thing i've seen is 3 esp32 devices, two with radios, third just runs softap the other two connect to
VXLAN is overkill in this context. According to https://serverfault.com/a/881694, even most unmanaged switches should work, assuming each node has ethernet.
I'm down to no nodes visible
When I switch to Medium Fast, not even a single node is discovered β even though I have a Yagi antenna on the roof!'
is Grand St up? I can't even see that
Unlike Medium Fast, Long Fast worked properly last week β nodes were being discovered without any issues
Up to 20 nodes for me on MF
jeez 1 h to NJ
its on jay stret high enought to see the bridge so i can see it working
I lost everything in mh when I got back to bk
my mobile node π¨ sees 17, 11 online
can you get any TRs on anything?
from my apartment not really, but i never had great connection here even with long fast
I'm very close to A7D4, but it's not showing up for me
can you post your meshtastic lora config?
I'm using both a RAK4631 and a SenseCAP tracker β one connected to an Android device and the other to an iPhone. They are successfully communicating with each other over Medium Fast using default settings.
Region: US
Mode: Medium Fast
Frequency Slot: 45
cool, mainly making sure your slot was set correctly. how long have you been connected?
Iβve switched back to LongFast and Iβm reconfiguring it now. It should be up and running again in a few minutes.
anyone get my test msg?
plz try again
yeah, nothing
need some staten island folks to move onto MF
I'm in Sunset Park, and my yagi antenna is pointed toward Montclair.
hmm, if u can, try pointing it to linden airport kldj
No way I can get up to the roof right now, buddy.
lol no prob, probably best to keep it pointed there anyway
ok
something finally acked my Ping
If only the weather was better, I wouldβve thrown the SenseCAP tracker on a drone and tested it myself! ππ
im basically an island rn in NJ, I dont think anyone else in NJ aisde from VYL0 is on medfast
got an ack from pony express mobile π€―
Sorry was playying overwatch didnt see your origin ping
No MF activity in midtown all day.
Womp womp
i may or may not have had my primary channel misconfigured, but I DEFINITELY screwed it up trying things...
it should be fixed now.. probably - and hey, I see myself!
lol, im all the way at the edge
well i'm done messing with the femtofox for tonight, tomorrow see if its fixed for not
ive got your nodeinfo as of 3 min ago
100 nodes π just need the promicros attached
Woah, thatβs legit
My nodes were low or out of powerβ¦.whoops, they are charging, I wonder if any node info gets down to you all outside of midtown
o/
what are those?
I'm in NJ too.. and I changed mine.. I have a good view from NY skyline. I'm giving a little time to see how goes
Yup, in addition to VYL0, I see BOKN now
100x of something on this list: https://github.com/porkcube/meshtastic-diy-nodes
any documentation about udp? would go through a vpn?
yeah that's works if your VPN allows udp/vxlan, there's also a #1374849766248157246 thread worth looking at and there's also the super useful mudp python app to monitor the traffic
not sure if messing with the channels did anything but 2 new nodes and saw gardener's fdc0 as well over night
New here. In lower Manhattan, device name RED, how do I test to see if itβs connected?
- Read the recommendations posted at https://nyme.sh/
- Send a message such as
Hello from lower Manhattan.and wait for a response.
I set to medium range-fast, and sent a message on the primary channel 0
I'm not familiar with the iOS app that much, but it looks like you accidentally renamed the primary channel from whatever the default value is to 0. Change it back to the default value of blank, and it should automatically rename itself to MediumFast.
the sidekick is my personal favorite DIY node, just super small and easy to build with either smd or through-hole parts
Android is the odd ball actually, 0 is correct for primary channel which is index 0
It seems like I am able to receive messages but it seems like my messages arenβt sending, will keep trying
Are you on the latest firmware version?
I believe so
If you need an idiot to test hardwareβ¦..Iβm your guy! Haz monies for goods π
Iβm in midtown, I am in the Man-Hole πππππ
Nothing goes in our out via RF π€£π€£π€£
Pizza you too close to the UN or something, jamming π
I have two nodes up in Chelsea, at work, that might reach downtown. Or look for Grand St
I have been on MF now for 1 day - only saw 1 node. No one on now. I am in upper east side.
i know there are still people who haven't migrated to MF yet, so stay the course! but if this trajectory stays, i wonder if MediumSlow will be our sweet spot
(reminder the despite the name, mediumslow is faster than longfast)
the range seems to be significantly affected, because even though we have some of the highest or most present nodes switched over, we can't get anywhere
Another possibility is that the number of abandoned REPEATERs is higher than we thought.
I'm assuming people bought a few "for reasons" then lost interest
Yet somehow the nodes still have power.
The only way to find out for sure is switching everyone to a non-default frequency slot on the LongFast radio preset.
I'm quite interested in this. I can run a spectrum analysis from my house, but the more folks that could do this, the better.
Documentation also suggests mediumslow has better range than mediumfast.
but this is just an impression I'm not sure how we could get metrics on this
As long as you're following all of the recommendations listed on https://nyme.sh/, sure.
Medium Slow works really well in the SF Bay. If weβre not getting the range we need with Medium Fast, Iβm down to try MS next.
SST had 100+ nodes in the DB on LF; on MF after almost 24 hours I have 6 nodes and 0 messages or telemetry and all of my sent messages have been marked unheard. I think the range impact of going to MF is not worth. Would be willing to try MS instead.
Weβve only had like 20 nodes switch over so far. I think itβs too early to call it.
I think we should change to medium slow before more people put the work in to switch
I feel like mediumfast failed our initial test.
@brazen spear are your nodes still not talking to each other? thatβs gonna be a good barometer for how things are working
Correct
But they are each functioning and connecting to folks
But they are not linking the boroughs
If Gardenerβs nodes arenβt talking to each other on Medium Fast then Medium Fast probably isnβt gonna be the preset we land on
I believe thatβs also how other metro areas decidedβ¦ test a preset and see if their key infrastructure nodes are still communicating
Is anyone online? Letβs try MediumSlow β Iβm in Sunset Park.
Iβm not home to change my preset but will be later today
SST is now on Medium Slow in Brooklyn Navy Yard.
My node is named βSunset Parkβ with short name π β switching to MediumSlow now for testing.
Shall I switch mine over? I can do it in the evening.
i'm not going to switch any of mine until a week or two after july 1st
Unfortunately I can't easily change southslope which is probably where you connect to.
I'm using a Yagi antenna on the rooftop, so most of my connections are 0-hop.
i'd rather give medium-fast a full-hearted attempt before we write it off completely, even if it's completely quiet. at least we can say we thoroughly tried. i know a couple people who have been busy and haven't had time to switch their nodes from long-fast
On medium-fast, communication range drops dramatically β especially in a high-interference environment like NYC. Without line of sight, even seeing 1 mile between antennas is a miracle.
i'd be open to shortening the trial from 2 weeks to 1 week though
yep, I'd say we give at least a week for medfast
I'm in Manhattan next to P1NY and I can no longer hear P0 and P4
bunch of nodes on staten island were helpful getting the mesh connected to NJ (beside Jersey City), they arent on medfast yet (or I cant hear em)
One week on MF should be the metric. but this looks like unless we get dktower and the few nodes from Staten Island don't think mf is our radio settings
I know other metros had setup a node to send a regular msg on LongFast to move over to the new profile
maybe someone can do that
Im in south bay ridge. I just switched to medium slow. After 24hrs of mediumfast, i only picked up one node with incomplete data.
Jumping presets during testing invalidates the testing
X started with A then swtiches to B means X isnβt testing anything but their ability to switch A->B and by not sticking on A for the duration also skews the results for all because itβs no longer a test of A
1 weeks on MF then 1 week on MS seems like the move since there appears to be some impatience, but the mesh is dynamic and just calling it after 24hrs isnβt good measure - what I see today is already 4x what I saw yesterday for instance
Probably me π
I can only see myself and BRRN
This test is already setup for failure. There has been no prep, no data points on LF that we can compare with MF, and no criteria for what a success or failure looks like.
What we should have done is:
- have a discussion about the trade-offs of potential presets we want to try
- identify key infrastructure nodes
- confirm the key nodes are talking to each other on LF
- define what success looks like (can the key infra nodes still communicate? or are they out of range now?)
- define what failure looks like
Just moving to a random preset and messaging each other to see how things βfeelβ isnβt going to accomplish a whole lot. This should be a data driven decision.
Thankfully, gardener has infra nodes he knows were communicating before and are not now. That alone doesnβt equate to failure but itβs a good data point to have.
what you're describing would be great, but what we lack is folks stepping up and taking initiative on those bulleted points. and until then, i'm personally okay with the vibes-based low-fi timed rollout we're doing.
whether we like it or not, we are learning how medium-fast is (and isn't) working out for us right now, which is the point. it's ironic you're proposing more structure around our testing when yet you advocate for ditching our current approach
Iβm not advocating for ditching our current approach. I was one of the first ones to move to MF when we started this test. Iβve been posting data points and running tests since we started so not sure what youβre on about. I also posted that only about 20 nodes have switched so far so thatβs not enough to call this a failure yet.
Just having worked at software companies most of my career, Iβm giving my input on how this testing could be improved now or in the future.
as someone who has worked at software companies my whole career i have no idea why it's relevant to the conversation here lol
Data driven decision making. Do you not do that at your software companies?
What was the reason behind this change?
Faster communication?
More airtime?
Less interference?
yep! but the kind of data we're talking about here is very anecdotal, hard to analyze, and nobody here (or very few of us) work on our mesh grid full-time to dedicate to that kind of detailed analysis
I wish a notice had been sent through Meshtastic before the change β that way, many people who donβt check Discord would have been informed.
I posted this announcement in the Long Fast channel:
NYC Mesh has begun testing on Medium Fast. We kindly ask anyone who wishes to contribute to this testing process to switch to Medium Fast."
I don't know how many people will get that message with my nodes already on mediumfast
They're supposed to backup the keys and update the firmware first.
We could strike a balance between the type of proper preparation most of us donβt have time for and switching without a plan or proper notification.
Itβs easy for those of us with window nodes to switch presets but people who have rooftop solar nodes in different locations have to spend way more time switching/testing.
The mesh doesnβt work for most of us, hence why we are testing other presets
Great, @normal osprey volunteered to plan out our next test π
Everyone move to Medium Slow now and message each other! π
(jk of course) would be happy to help coordinate the next test π«‘
Thank you!
Iβm not questioning why we are testing a different preset btw. I know weβve outgrown LF. The meshtastic article about different presets also confirms weβve outgrown LF.
Just giving my input on testing methods.
I think we are doing great all things considered.
Nothing wrong with executing this plan, and making improvements for the next step.
I do agree someone with the chops to script it to blast LF hourly we are on MF
Actually, if this node switched to Medium Fast, there would be a significant increase in mesh coverage
false. I was on Medium fast for the last 24 hours and had 0 contacts.
Thatβs @fervent nebula βs node I believe
There's a co-located node named Quasimodo (QMO2) which has been (and remains) on Medium Fast.
Are you sure you were on the right channel?
There was a storm yesterday and I believe it had a big impact. Would it be possible for you to switch now so we can run a test?
SST is on MediumFast again. Hooray, look at that 0% airtime usage.
Next time I'm in the office I'm just going to take all the unused nodes and set them up in the window next to each other, one on every default preset.
Alright, Iβm switching back to MF now β letβs see if it can be seen this time.
Is anyone seeing more than 20 nodes on MF so far? Trying to get an idea of how many nodes have switched.
Maybe next test, weβll have a βsign-upβ sheet where people can list their nodes they will be switching, approximate location, etc
@fervent nebula nothing so far
yup
I'm getting up near 15-20 at work in Chelsea that have node appearance in last 2 h or so
but at home nothing basically
Would love for us to get 60+ and test since thatβs about where the Meshtastic article said LongFast becomes unreliable. Would be interesting to see how MF handles 60+ nodes.
omg someone actually saw my message
I sent that from Chelsea
you gonna be waiting for that MFing acknowledgement for a while ππ«‘
These MFers actually ack faster than LF π
MF definitely leads in shitposting potential
IIRC it was a suggestion for critical mass of 60 in close proximity, 300 is the # usually thrown around for when LF implodes
That makes sense. Thanks for the clarification.
word - considering I easily heard 100 nodes with the airframes cav filter we're probably closer to 200ish already since there's still blackholes
pork I saw you ack becc did you see me?
can someone find all those nodes that bridge us. is Kellogg's running a node or something
i still have yet to see grand or vernon
and get them on MF
kellogg's is way too low vs everything that's been built up around it past 20 years
there was someone on the north/east side of the park on LF like 6months ago but then disappeared
pretty sure it was DPRK (close enough to pork that my brain decided to retain it)
(ultrafox is sitting on my desk hopping through femtofox so still CM)
I had some delays bc of work but Iβm going to bike around changing my nodes at various friends houseβs now. Mostly around wburg
Hehe donβt think Iβve seen anyone >5% on MF
I wonder if someone could put an omni node on wtc
There was one on ~100th flr but died, thereβs since been on thatβs ~85th flr of 1WTC IIRC and one at 4WTC
hehe, needs a filter - the 100th flr one was seeing crazy util #s
That map woudnt be too far off. I used agl of 406m
hrmm, it's assuming perfect 360 coverage which isn't likely to be the case
I want to do a test tomorrow or on Friday. Iβm planning to attach the SenseCAP tracker to a drone, fly it up to 120 meters (legal limit), and keep it airborne for 15β20 minutes. Iβll be testing on Medium Fast. Do you think itβs better to put it in router or repeater mode?
Definitely not REPEATER. Either ROUTER or maybe consider ROUTER_LATE.
But that's exactly my goal β we can't communicate using Medium Fast, and I want to test that
Reconfirming that the ack speeds are cf on mf (crazy fast on medium fast)
it's faster on this MFer
Running a client would rebroadcast the same as repeater or router - router_late is the one that wouldnβt preempt clients and actually serve a beneficial purpose for retransmission. 15-20mins Iβm guessing is a battery life limitation but also not a great window of time for clients that are on much wider windows for sending telemetry so sending out a message indicating the time would be very helpful to maximize the tests utility
I believe we have low channel utilization because the nodes aren't meshing.
If we just leave it in mf and keep pushing on LF for people to switch for a few weeks I bet we can get it going a little
If the best roofs can't talk to eachother with direct los then a citywide network that doesn't require 7 hops isn't possible.
I got this message in cobble hill from Chelsea
With def no LOS
While sitting inside by a window
you know where i live, i'm pretty much middle of vernon<->grand and i've yet to hear either yet i'm still seeing fdc0 at 1 hop so SOMETHING is ninja relaying
Anyone running mf lower Manhattan I can bike by and test ranges
Aye everyone, I heard that there were some weird pockets of interference, espeically in squares. I wanted to do further testing but ahh stomach flu.
Yeah the Squares kill any reach
So far I tested Herald, Greenly, @feeb did some sest msgs on times, I haven't checked washington, mad, or union.
nice! well, on the tests at least - thanks for doing that! we still got few days left on MF and then MS next week so plenty of testing to do once you're over the stomache flu
@fervent nebula what's the retention of stats on nyme.sh? is there a way to export the information for this test?
I got a node near Soho
GHFC just showed up for me @ 1hop
Oops; I just used remote admin to change the preset on a node and then wondered why I couldnβt then change the name of the main channel.
I guess Owl will be out of commission for awhile.
Does anyone have any tips for using remote admin to migrate a node to medium fast?
Is that an ios bug?
I assume I canβt edit it because itβs now on Medium Fast but in a channel named LongFast, so the remote admin interface doesnβt have a channel to it.
Oh! I can just mirror it on my local device canβt I
did you explicitly set the channel name to LongFast or just leave it default/blank?
Set it explicitly I imagine. Is that not required? Didnβt know that.
i'm still not 100% on what the python-cli is doing for --ch-medfast vs --set lora.modemPreset MEDIUM_FAST --set lora.usePreset true
but I also got a little hungup on using it to update the channel name, because it gets really complainy if you try and set it to blank
and yeah, if left blank it should automagically set the name to the preset
Hmm. Iβm mirroring the settings but Channels is staying gray.
huh, and you can actually access LoRa config?
I can. That part is done.
huh... were you using the "legacy" admin channel method or the pubkey remote admin?
ahhh k, yeah that's the channel-less/newer way
i've had ios/macos remote admin be a little weird sometimes where i'll go to a setting and it's like OH NO I HAVEN'T CONFIRMED YOU CAN REMOTE ADMIN and then go back to main settings screen and go back into same setting and it's fine, and had it happen per setting but the grey out channels i just dunno
there's no way without live-logging the mqtt to replay it as far as I know. the 3 different services on nyme.sh each do a different type of data collection and aggregation for their own uses, I would have to look into export. I'm not sure that there's any easy way to export it.
30 nodes and 2.59 channel utilization on π¨
You can set your remote admin device to whatever you believe your node is set to (i.e. mf modulation, freq slot 20) then change the freq slot to 45
So you shouldn't need to change the channel name for it to work with the rest of medium fast
Up to 43 nodes over here, but can only get trace routes to complete for a few
Without a channel configured named appropriately and psk AQ== it wonβt send out metrics/location that others can decode*
So it may rebroadcast but wonβt show up for people other than !userid and encrypted packet
rtl-sdr + usb-c adapter + sdrtouch == SDR on your phone
On the other hand, doing something is more progress than doing nothing. It's not a waste or a failure, it's just an iteration.
hey I'm 1 hop to Hops
well that's a fluke but I took the donk outside and haqer can see me... with a mystery hop in between
well haqer you can hear the donk but I can only hear you with the t1e
so at least that's typical
getting messages from ZLL1 now
So far is medium fast working
I'm asking so that if it's better and the community is going to move to it then I'll go and move the nodes over
Haqer I actually got a direct confirmation of one of the msgs... not sure what path it's taking
TR is zero for me thus far except when I'm at work and Hoboken 1W is easy to hit
I can TR to P1NY 0 hops there and back consistently every timeβ¦ but thatβs to be expected since we are right across the river from each other.
as long as there is a way to log the activity during the current tests, then there is no 'failure' as there are nodes that are able to hop through the network.
I did TR maybe P2NY from Chelsea also..I think
seems generally understood there is less range so far
understood/observed
like there's no way I can get a TR to pork even tho that used to be 75 percent possible
and I'm seeing his nodeinfo
we need SQUONK and Metaphor
anything more than 1 hop i cant seem to trace eithier
i stand corrected
The feds, duh π
Hey, if you're in Hoboken, I should totally be able to reach you. My rooftop Yagi is pointed right at Montclair β back when I was on LongFast, I could easily talk to nodes in Hoboken, Jersey City, even Kearny and Clifton.
USB-C RTL-SDR Blog v4 > USB C to USB C cable to your phone π
I'm attempting to trace every node in my nodeDB right now. Yeah sure, I've gotten an occasional nodeinfo or telemetry from 30 nodes, but so far not a single trace response or message confirmation. For my purposes this aint a mesh.
TR LongFast wasnβt working either, at least on my iPhone.
Some of us live in areas that are nearly impossible to get signal through
when I get home I'll switch everything to MF.
my only issue is that its bad enough in LF where I can barely get out at sea level, 10 percent less is ... deathly!
no man... it's the "vintage" meshtastic experience π
(pretty sure I made the same joke last test)
but who are the hoppers
It appears to be more than a 10% loss based on what weβve seen so far
i think it's less the range than the change in noise floor
(which does affect our already very limited range vs wide open spaces)
Iβm having no luck on MF in Bay Ridge, Boro Park and Midwood. Are we testing until Sunday night?
Iβm in βMidtown Man-Holeβ still
I'm across from Hoboken when I'm at work. from there I can usually see P?NY (I forget which ones but maybe 2) and Hoboken 1W. Since so far the WTC nodes have faced other directions from me they flake in and out
Ok back in midtown today, might go to LES to see if MF is truly reachable
weird one ffff is back? from wb waterfront
is ffff here?
whOs 4032
becc?
that's their default shortname, user id is !b03cbecc
picked up P1NY / P4NY and looks like PYT! also joined the MFers
looks like !b03cbecc is "Central Park" (PARK) https://meshview.nyme.sh/packet_list/2956771020?q=!b03cbecc&portnum=
oh nice thank you. I was starting to see becc from the western side of Roosevelt island
I just did a whole loop over to Bushwick Inlet, into Queens, around Roosevelt Island, and back. mostly I just see P?NY and PYT. other behavior the same. T1E hears what Donk doesn't, donk gets me out
saw this at the top facing N. auto?
if you saw them @10.25db you were reaaaaaaaally close
yeah I was able to message them. no response. didn't seem to be fluctuating (like as if it was a car moving)
wait, repurposed node then...
looks like dkTower is holding an infra space.
im 4032. i saw the messages from earlier but wasnt around to reply
Someone answered in #help on why the ffff with a ? SNR value exists: #help message
Given the context around this, my assumption is that people have been messing around with their channels, such as by doing https://meshtastic.org/docs/configuration/tips/#creating-a-private-primary-with-default-secondary improperly.
Tips and Solutions to help you get the most out of your Meshtastic device and network.
where is "I see 0 nodes" π
I saw a SchrΓΆdinger's node. It only appeared once, and then never again: #1202833898376138752 message
they switched for 2 minutes and switched back
It's one of @gardener2549's nodes.
ohh..
I don't think there's a set deadline. people were suggesting 1 week. we would need to coordinate with gardener and Lordwithpet for the exit day (IMHO)
Just let me know with a day advance and I can swap whenever
Iβm in Halifax Nova Scotia until next Wednesday. Left Smorgasburg fa5a on MF.
I saw your node earlier but kinda cheated because I was just at inlet heh
if that didn't work was going to give up on this MF entirely
Window fox went down, only have 1 phase of electrical at the moment and UPS it and cable modem are on just ran out of juice
Unfortunately itβs the OTHER phase I needed to go offline ensuring the buildings cameras are offline and I can sneak onto roof
You paid off the wrong guy π
I paid coned, no choice!
I got ack, iβm in East village/alphabet city
damn what they doing that you lost a phase?
π€·
fire dept had to rescue someone from elevator in building next door
still only 1 phase but stuck the ikoka stick outside window and messed around in electrical panel to get innernet back up
3h left for the poll above. we can use the results of that to determine next steps for the trial #1202833898376138752 message
I like the poll, great idea
I think this sums up NYC pretty well. This is my ADS-B stuff. I have two, TWO whole feeder setups at home and the office. Visiting friends with a less expensive and less awesome setup sitting in a guest room, and you see the difference.
Howβs the MediumFast switch going? (Select as many as applicable)
14
35
3
I see fewer nodes than before
hello all! I'm just learning about Meshtastic. I ordered a T1000-E - but is there some better recommend hardware?
I carry the t1e around on client mute@4 hops. Does ok sorta on the tx side. Listens really well
The problem with sending on 4 hops is if you get responses at 3, you might never know.
tell that to the 7 hoppers π
I'm also thinking about this one... https://a.co/d/e0OMTAX
Who's "MakerHawk-US"?
t1e is great. easy to carry. nodeinfo blast button, great tx
It's a pretty solid starter. Honestly can't go wrong with it.
It's in my EDC rotation.
Other than a random Amazon seller.
They've been around a while, on Amazon. And I've purchased batteries from them before. TBH I think I got my T114 from them.
Does Heltec ship from China? I'm impatient π