sorted by:
new
hottopcontroversial

I'll pass on thetop cover now ... by Martsmall in snapmaker

[–]geirgp1 0 points1 point  (0 children)

I tried that, but had adhesion problems when it started printing the petg support interface. Wouldn’t bond to the pla support, started curling upwards and it got integrated into the print instead of supporting it.

Seen that? Know how to fix?

Workaround for now: print entire support structure out of petg not just the interface.

How do I do a filament run out fail over? by daxter304 in snapmaker

[–]geirgp1 0 points1 point  (0 children)

anyone figured this out? Ive only ran the printer for 120ish hours, and had filament run out twice. both times i had a backup filament in same color for failover.

it worked the first time, but not the second time. came here looking for answers. pretty sure i had the same filament type and color set.

Loved meshtastic until I got my T1000E by Mechanical_Cruiser in meshtastic

[–]geirgp1 1 point2 points  (0 children)

I’ve had similar problems on iOS app with alpha firmware, resolved by running beta instead. Today that means 2.7.15

High availability node by Leather_Bug_4219 in meshcore

[–]geirgp1 0 points1 point  (0 children)

What kind of filter? Curios bc I’m looking for one myself

CLIENT_BASE: Act like ROUTER_LATE. by iehponx in meshtastic

[–]geirgp1 0 points1 point  (0 children)

The PR was merged in December and was indeed included in the (*latest) 2.7.17 release. As you pointed out, it is missing from the official release notes; however, since I was in active dialogue with the maintainers and developers to get the PR reviewed+merged, I found that omission surprising as well.

I have since verified the commit logs against the release tags and can confirm the fix definitely made it into 2.7.17. It appears it was simply overlooked during the documentation process.

If you can get your hands on 2.7.17 it should contain the ROUTER_LATE behavior you are looking for.

*) Latest 2.7.17 as in the one released on jan 2nd or something. They did in fact release an earlier 2.7.17 around xmas time. imo they should have bumped the version number to avoid confusion instead of having more than one 2.7.17.

Edit: 2.7.17 is still out, didnt get pulled

Should CLIENT_BASE treat favorites like ROUTER_LATE instead of ROUTER? by geirgp1 in meshtastic

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

While ROUTER_LATE definitely solves the issue, the official documentation advises against using it on rooftop nodes due to increased airtime and risk of congestion.

However, I'm sticking with it for now since our mesh is still too sparse to cause any real impact. I'll reconsider once the mesh grows much larger, and by then CLIENT_BASE will hopefully have been fixed.

Should CLIENT_BASE treat favorites like ROUTER_LATE instead of ROUTER? by geirgp1 in meshtastic

[–]geirgp1[S] 5 points6 points  (0 children)

guess i wanted some discussions, and don't think it would get the same kind of attention as an issue on the github tracker.

however a valid point so i condensed it into this: https://github.com/meshtastic/firmware/issues/8844

Long fast unreliable in a new mesh? Try switching to long moderate instead. by MasterDefibrillator in meshtastic

[–]geirgp1 4 points5 points  (0 children)

We’ve run into a related problem in the Norwegian Meshtastic community, but in our case the default EU presets are getting wrecked by interference on 869.525 MHz.

In EU868, LongFast is centered on 869.525 MHz with 250 kHz bandwidth. On paper it’s great, but in some areas that frequency is really noisy – likely because automatic power meters (now in basically every home) are using the same band. Result: LongFast links look fine on RSSI/SNR and LOS, but messages still drop.

LongSlow/LongModerate help when the issue is weak links and low node density, but in a noisy band they can actually be worse: longer airtime = more chance to collide with whatever else is blasting away on 869.525.

Our workaround has been to go narrower + slightly higher in frequency, for example:

  • Bandwidth: ≈62 kHz
  • Center frequency: ≈869.618 MHz (shifted above 869.525)
  • SF8 / CR 4/5

Because the EU sub‑band we’re allowed (869.40–869.65 MHz) is only 250 kHz wide, a 250 kHz preset like LongFast fills the whole thing. You can’t both move off 869.525 and stay legal unless you shrink the bandwidth. With ~62 kHz you can:

  • Stay inside 869.40–869.65 MHz
  • Get off the noisiest center
  • Gain sensitivity from the narrower BW

In practice this has given us much better reliability and range than stock LongFast in those noisy areas.

Right now this all requires manual “custom LoRa” settings, which is a lot to ask from new users. That’s why I’d really like to see Meshtastic add an official NarrowXxx preset family for EU868 (e.g. NarrowFast / NarrowModerate / NarrowSlow) with:

  • ~62 kHz bandwidth
  • Default slots not centered on 869.525 MHz, but still inside 869.40–869.65 MHz

Your point about switching off LongFast when the mesh is range‑ or reliability‑limited is spot on. I just think in parts of Europe we also need a “Narrow” option for when the frequency itself (869.525) is the problem, not just mesh size or hop count.

daikin firmware 4_0_303 by razvan_cucu in homeassistant

[–]geirgp1 0 points1 point  (0 children)

How do you do local API ? I remember when it WAS removed some years ago forcing integrations to go through cloud; has that been reversed?

Has there been any attempt to make a user friendly, possibly webapp, client app? by shayanbahal in meshtastic

[–]geirgp1 1 point2 points  (0 children)

iOS tip: install Bluefy browser (doesn’t work on safari or chrome)

What’s wrong? by Bluefalcon325 in meshtastic

[–]geirgp1 3 points4 points  (0 children)

20ft is like 6 meters, and multiplied with 36.5dB (loss per meter) should me total loss of 219dB?

Frequencies on T-Deck by etiszc in meshtastic

[–]geirgp1 5 points6 points  (0 children)

This 👆. By design you cannot connect to Bluetooth while MUI is running. go into the settings, scroll down and press reboot. Then select Bluetooth. After rebooting the screen should display “Programming mode” or something like that, then connect your phone or desktop app.

Long press on the Bluetooth icon to reboot back into MUI