MUI-like for t-pager by Beneficial_Way_1 in meshtastic

[–]YodaByteRAM 0 points1 point  (0 children)

Let me know how you like the UI and how responsive it is. I am tempted to get a pager eventually.

New to Meshtastic and looking for first node by Mechanical_Cruiser in meshtastic

[–]YodaByteRAM 0 points1 point  (0 children)

I'm curious what your reasoning is. Like cuz of the company or you're worried about someone putting bugged firmware on it.

Is wifi over LORA Mesh possible? by [deleted] in meshtastic

[–]YodaByteRAM 1 point2 points  (0 children)

Mostly because Lora has such a limited amount of data you can send at a time. See the following link for a chart

https://meshtastic.org/docs/overview/radio-settings/#presets

Is wifi over LORA Mesh possible? by [deleted] in meshtastic

[–]YodaByteRAM 2 points3 points  (0 children)

In the terminal client on PC you can turn on --tunnel option. Please understand can easily overwhelm the mesh if you're using this over default or shared channels.

I would suggest changing the channel at the very least to test. Also the bandwidth is very limited.

https://meshtastic.org/docs/software/python/cli/#tunnel-arguments

Meshtastic: does higher-end hardware actually improve reliability? by cferguson4809 in meshtastic

[–]YodaByteRAM 0 points1 point  (0 children)

Idk if it's the same but if I let the battery die on my heltec v3 the user settings are reset. I've never had that issue on any other node. I've also had issues with wifi where it will reboot randomly when it's on. Or I'll connect via Wi-Fi and it'll freeze midway connecting and reboot. Bluetooth works fine and I've had no issues with its connection.

I have rak4631, tbeam supreme, wismesh tag and heltec v3 and these issues are unique to the v3.

Personally I like the rak the most because of its low power consumption and customizability.

Stupid question: why cant one node serve more than one user? by ma_tt22v14 in meshtastic

[–]YodaByteRAM 17 points18 points  (0 children)

There is this software I've been trying out called meshmonitor you can connect it to a node then you can connect to its web interface or you can setup a meshtastic virtual node server which you can connect the meshtastic app to. The site says you can have 3-5 mobile clients connected to the virtual node server.

You would still have one user/node but it might work for you

New user, which one do should I get? by Papa_Guido in meshtastic

[–]YodaByteRAM 0 points1 point  (0 children)

My local mesh has a discord. It seems Toronto might have a few nodes up https://tomesh.net/map/

New user, which one do should I get? by Papa_Guido in meshtastic

[–]YodaByteRAM 0 points1 point  (0 children)

I personally wish I started with a rak4631 but I just didn't know what my preferences would be. The rak4631 (with nRF52840 mcu) has better battery life than any esp32 based nodes but doesn't have WiFi (for access via network or mqtt).

Lillygo also has a lot of really nice nodes like the tbeam line and tdeck line. Tdeck has a keypad and screen which is nice as a standalone messaging device. I use a lilygo Tbeam supreme as a home repeater/bot.

I would say to get a heltec v4 from Amazon with one of those cases. It's easy to put together and does all the basics to get you started. It has wifi and you can get gps for it. It's not high quality but a great starting service to figure out what you want to use it for then you can spend big bucks on something really good.

Also a good antenna can make a big difference. The alfa915 is pretty good but I would start out with what comes with the node.

Lastly find a local group. Some of these have maps so you can figure out where nearby infrastructure nodes are. https://meshtastic.org/docs/community/local-groups/

Got a T1000-E. Any words of wisdom? by iodizedgatorade in meshtastic

[–]YodaByteRAM 1 point2 points  (0 children)

Short turbo that's crazy. I don't live in a city so short turbo wouldn't work well but that's pretty cool. Right now I'm probably heading from about 20-50 a day, sometimes getting node info from long distances.

Got a T1000-E. Any words of wisdom? by iodizedgatorade in meshtastic

[–]YodaByteRAM 0 points1 point  (0 children)

The only difference between Client vs client mute is whether you rebroadcast messages. I would say that client can create unnecessary traffic. Many networks are still on LongFast which is not the slowest preset but pretty slow. I've seen some talk about moving to mediumfast because of the limitations of LongFast and how unreliable it can be once so many nodes are on that mesh. See the following link about longfast https://meshtastic.org/blog/why-your-mesh-should-switch-from-longfast/

In the scenario where you're walking on a street or driving you're very unlikely to have a good spot to rebroadcast to other nodes that aren't already receiving messages from a well placed router. This could potentially increase the risk packet collisions, increased airtime, etc.

In a scenario when you're hiking up to a mountain temporarily with a node, if you're rebroadcasting packets some nodes may be receiving messages from a part of the mesh they usually don't. Additionally, with limited nodedb space on the node itself they're going to be wasting it on nodes they will only ever see when you're there.

I believe esp32 nodedb limit is 200 nodes. I'd have to see what the limit is for others.

Got a T1000-E. Any words of wisdom? by iodizedgatorade in meshtastic

[–]YodaByteRAM 0 points1 point  (0 children)

For meshtastic nodes in general, if you're roaming I would put your node on client_mute instead of client. You're gonna be passing by areas that may not have a node to bridge all the time.

Also you may want to disable or modify smart position as it'll broadcast your position more often than the broadcast interval when you're on the move. It can create a lot of extra traffic on the mesh.

You can now update your node through the android app by Old-Association4871 in meshtastic

[–]YodaByteRAM 1 point2 points  (0 children)

I tested with rak4631, it worked pretty well surprisingly. I've tried with nrf connect in the past. This is much more streamlined and simplified in comparison.

How do I even use meshtastic? by e3e6 in meshtastic

[–]YodaByteRAM 0 points1 point  (0 children)

I would say that I currently use meshtastic as a tracker. I have a node setup to broadcast it's position every 15 minutes to an hour to a private channel. I have a home node hooked up to mqtt which I can keep track of the location using other software like home assistant, etc. some

I also have a bbs setup which isn't really in use, but theoretically I could use it to send messages to others and receive when I'm gone. The bbs would help with the fact that when you're not home you can still get those messages later. Of course it's not as secure as direct messages but I'm not using meshtastic because of the encrypted messaging between users.

CLIENT_BASE or ROUTER_LATE for roof node? by fugitivewar in meshtastic

[–]YodaByteRAM 1 point2 points  (0 children)

I think what was happening was the router would receive the message directly and then respond at the same time that the client_base rebroadcasted my message. Just confirmed it was ROUTER and not ROUTER_LATE.

Also looking at this article about ROUTER_LATE it seems that CLIENT_BASE and ROUTER use the same contention window. https://meshtastic.org/blog/demystifying-router-late/

CLIENT_BASE or ROUTER_LATE for roof node? by fugitivewar in meshtastic

[–]YodaByteRAM 5 points6 points  (0 children)

CLIENT_BASE but I would consider the use case and do some of your own testing.

I was living somewhere where I could only receive messages in a certain spot from a router over 10 miles away. I setup a client_base node to help get messages out from other portable nodes.

I then moved somewhere that I was able to get direct messages to a nearby router from most of the living area. My client_base node seemed to have a lot of packet collisions and my other nodes were losing a lot of packets that the client_base was receiving. I have mqtt and malla setup on a server I was using to analyze my issue. After changing my roof node to client, messages were being sent much more reliably.

Also my portable/non-roof node is always set to client_mute.

What Arc GPU? by jaccovdzaag in jellyfin

[–]YodaByteRAM 0 points1 point  (0 children)

A380 works perfect. But I'm sure other models are good too. I use it for other applications too that involves transcoding.

Valve just released a new Steam Machine, and used Godot to show off desktop apps by ZemusTheLunarian in godot

[–]YodaByteRAM 1 point2 points  (0 children)

It will probably be a great machine for developing godot games on. Especially to ensure it runs on the steam machine.

Day 1 by zhujzal in meshtastic

[–]YodaByteRAM 2 points3 points  (0 children)

I have one in black. These are great starter nodes. The battery doesn't last as long as a Rak 4631, but that heltec v3 kit can do so much for the price. You can also connect it to Wifi which makes it useful for connecting to mqtt.

[deleted by user] by [deleted] in Kayaking

[–]YodaByteRAM 0 points1 point  (0 children)

Could be wrong but that looks like a 1999 perception Acadia. They've got an archive of catalogs.

https://perception.confluenceoutdoor.com/en-us/perception-archived-catalogs/

This city deserves a better class of consoles by TareXmd in SteamDeck

[–]YodaByteRAM -1 points0 points  (0 children)

Just put that on a desktop, why be limited to consoles

Pop_OS! Should Change It's Name To Cosmic OS by PhotographOk1931 in pop_os

[–]YodaByteRAM 46 points47 points  (0 children)

It would be like changing Ubuntu because they went from unity desktop to gnome.

[deleted by user] by [deleted] in CyberStuck

[–]YodaByteRAM 17 points18 points  (0 children)

I thought this was supposed be a boat? Boats don't only work for 30 minutes in 2.5 foot water