meshing-around BBS/utility BOT

[rare tulip]

Is there a way to connect the Meshtastic Node ( heltec v4) to LAN instead of Wifi ? maybe POE ? ... thinking about a metalcase with antenna which comes on the roof and is only connected via POE ....

[drowsy rock]

I tried without, with, not sure what it means by 'dubious ownership'. I stepped away from this rpi for a couple months, just busy, and sorta forgot what I'm doing. I never did get it to work.

Ok i looked into it. I'll do it correctly next time

[gentle kestrel]

It’s just permissions - you can do what it suggests and clear it

[gentle kestrel]

Yea you can WiFi (can’t enable WiFi and ble same time)

[rare tulip]

I meant NO Wifi ! ... cable ... i like to have things cabled ... and it would be nice to get a POE to the roof Antennas and put the node there powered and connected by LAN

[gentle kestrel]

Set up a pi put meshing around on it

[rare tulip]

Just to unerstand it right ... the SNR should be the higher, the better, right ? An Antenne with SND +5dB ist higher than the noise around, and an Antenna which brings me -20dB is 20dB under Noise and the "bad" one ? but this only shows me RX if i am right ?

Examples, but changed Antenne was on the TX device... and why i am asking, the 5dB is with the "short Heltec" standart Antenna

[drowsy rock]

I think you're in the wrong room.

[rare tulip]

ups...

[gentle kestrel]

And if the SNR is higher it would be a better signal @rare tulip

[heady raven]

Aloha spudgunman and everyone using this awesome tool👀 I been working on an alternative TUI for this with a certain amount of success. GitHub nursedude/meshforge 🤔Been learning a lot and configuring this app in ways I never thought possible ha ha 🙃💯🌋🤙 73 and aloha

[gray igloo]

not sure if im doing something wrong but my bbs keeps breaking idk whats happening to it but it eventually just stops working and i have to restart it

femtofox

[gentle kestrel]

What’s the last logs before death?

I normally don’t go much over 4-6 hours on my fox so ..

[gray igloo]

where were the logs saved

[gentle kestrel]

/opt/meshing-around/logs

[gray igloo]

thats the lates log file before todays

[gentle kestrel]

Well that’s interesting, first glance it looks like someone took you out

I will test a few things

How often and what OS

[gray igloo]

its been down for a while now, been lazy restart it

so not sure

[gentle kestrel]

Is it naguOS or mpwrdOS

[gray igloo]

naguos xd

[gentle kestrel]

There is also a message log, I think on by default (haha I don’t recall) @gray igloo

If you can find out what that node was sending at some point to get blocked by the bot software it’s interesting they are slamming away before the radio was lost

[gray igloo]

lemme see

[gentle kestrel]

You might also add it to the firmware block list they likely sending characters of shenanigans

I only auto blocked real junk - anyone getting blocked, was tying to get in by every way possible

Time stamp the logs against meshtasticD and if you got any valuable data worth passing to JD etc

[gray igloo]

aight xd

[gray igloo]

disabled

how unfortuante

ill enable it

[gentle kestrel]

AQ== always a party

[gray igloo]

haha

[twin dust]

AQ== always a party
great idea for a meshtatic tee

[drowsy rock]

Same but haven't investigated. Started after last update.

It'll work for a couple days then just stops.

[gentle kestrel]

Not much changed lately, what’s logs say

[gray igloo]

Ill check when i get home if kt works still

[gentle kestrel]

That persistent save was added; but I don’t know any other memory changes really went down lately is this all on Fox boards?

[heady raven]

Public channel can get crazy and yet most tourist coming to Hawaii are using that to reach out to us locals and of course trying to send messages from the plane 🌺

By the way 🥔 I do have a TUI version of meshing-around 🙃👀needs work, 🔥but it runs nice

[gentle kestrel]

Dropped some additional safety measures in for malformed and memory

[drowsy rock]

Just a normal pi 4 with whatever the latest OS is. I'll try and update when i feel like getting everything set back up. Running headless and my android ssh app sucks.

[dusky abyss]

juicessh is pretty nice

couple it with mosh ❤️

[drowsy rock]

That's what i have. Constantly crashes mid operation

[gentle kestrel]

I accidentally just rebooted my “uptime testing bot” but it was online when I rebooted it haha

[stone lance]

@gentle kestrel is it possible to make the DM replies to DMs with triggers into actual replies to the specific message?

It would help me work out which of the 5 pings it's actually received and responding to.

[gray igloo]

Yeeee lol

Oh ye

Its crashed again

Ill have to check later

Maybe the whole node went offline this time

[gentle kestrel]

It did last time, the bot crashed because the meshD had gone away

[gentle kestrel]

Like the message ID would be handy to know in a pong or just the fancy

I’m currently mulling about if it’s better to mark each chunk or only the first

[stone lance]

anything that its technically able to reply to, really

I think they can reply to themselves?

[gentle kestrel]

That part done ✅ have a working bit in lab to reply threaded or tap-back on all responses each chunk would look like ^^^

Or should I only tap-back the first in the chunk?

Should I add a config value to enable or disable it?

Or just push it and get feedback later

[stone lance]

have it reply to its own messages - that way you can see any missing ones

[gentle kestrel]

Try the latest code let me know if this is what you wanted

[stone lance]

It'll be a couple of days - the loft node is in the loft...

[gentle kestrel]

rrr

[gentle kestrel]

Got a fix on the basic schedule routine as well

[sleek salmon]

for satpass, i have the API key in the config.ini, i am sending the satpass command to the bot but it keeps just sending back the example text .. what am i doing wrong?

[gentle kestrel]

Any interesting log? 🪵
I can’t replicate this.

Assume it’s a bad key?

[sleek salmon]

let me double check my key, maybe its bad

[gentle kestrel]

Or like a parse error when it’s in config it’s just key=AB12C

No””

Also try just “satpass” it should be using the defaults when you don’t specify a ID (I just tested both ways and it works on the main branch)

Defaults to like ISS and Oscar7

[sleek salmon]

my API key might be no longer valid, i am checking that.. i think that is the problem

yep that was it... i copied it wrong

[gentle kestrel]

Happy sat hunting 🙂

[sleek salmon]

thanks!

[celest oracle]

i seem to be having an issue with the replies from the bot if i'm sending commands directly via dm to the bot.
i'm using a virtual node via meshtsaticd with the bot connected via tcp (4403). everything else seems to be working fine and sending commands via public (longfast) and private channels i'm receiving the replies via dm from the bot. sending commands directly via dm to the bot node i can see in the meshing around logs that it's sending replies to my node (via dm) but i'm not receiving it. checking the logs of my node i'm seeing that the bot is replying to the dm but it's sending it on channel 0 (longfast) instead of via dm.

[gentle kestrel]

Sounds like the PKC DM crypto is not properly exchanged yet

You can try generating new keys on the bot and wipe the node elsewhere

I was debating adding a debug log to help identity this situation I may revisit this

If you use web UI you should be able to also just chat and DM with the node being used for a bot

Watch the logs of the meshtasticD also will have some of the errors of PKC

You can turn on the packet debug and get some data about it but it could be too much to follow it will flow fast

Another route entirely is
respond_by_dm_only = False
And let the bot respond on channels only

Further showing if it was only a DM-Key issue

[celest oracle]

DMs between the bot node and my nodes are working. Commands sent to the bot through channels (non-DM) also works and I'm able to receive the bot reply via DM. It's only when I'm sending commands directly to the bot where I'm unable to receive the reply.

[gentle kestrel]

I’m gonna bet DM keys still - let me see about that idea I had a bit ago for a log for this

*slacking and hacking

[gentle kestrel]

Ok I got around to this - I wanted to add this for like 6m thanks @celest oracle for the pressure on it!

Git pull and it has a new warning when PKI goes nuts 🥜 ⚠️

[celest oracle]

I updated to the latest commits and it's showing this error with my DM issue with the bot:

[celest oracle]

I tested a bit more. It looks like the DM issue only happens between the bot and my software nodes (the software nodes are inside docker under the same network with different ports assigned to each node). Everything works okay with real nodes. It's no big deal. Thanks for the help.

BTW regarding the store and forward function, how does the bot determine the last message that a node received? Is it based on when the bot last heard anything from a node?

[gentle kestrel]

Every software node will need the private key generated unique if you are cloning machines it will recycle keys and make a mess

[gentle kestrel]

Just says take the last X messages in time

[gentle kestrel]

I didn’t test this but - kinda handy? - just saying no ACK

[celest oracle]

So for S&F there's no time limit, only the last x number of messages which is configured via StoreLimit in config?

[gentle kestrel]

Should be yes

[heady raven]

i like satpas...

[craggy rampart]

any way to get the network map to populate?

[gentle kestrel]

On the webhtml? It scrapes the log and only shows nodes using the bot (not all nodes in mesh like a mesh map would)