Threads configuration?

[briandinsmore]

I right clicked my channel, created a webhook, placed that in the webhooks.bash file. When running the script I'm seeing the messages being decoded correctly, but nothing coming through to Discord. Do I need to change something else in the config.yaml? The threads lines doesn't appear to have any information as to what that is setting or if it needs to be changed.

Let me know if I need to provide any other information.

Thanks

[afourney]

@briandinsmore it has been a while since I last looked at this -- and it's configure for our Puget Mesh instance near Seattle. You will need to update the config.yaml.

Probably the minimal config might look like this:

# MQTT Settings
mqtt:
  address: mqtt.davekeogh.com
  port: 1883
  user: meshdev
  password: large4cats
  subscription: msh/US/2/e/#
  map_url_prefix: https://meshtastic.davekeogh.com/?node_id= # Node ID will be appended

# Channel settings
channels:
  - name: LongFast
    key: AQ==
    webhook: ${DISCORD_WEBHOOK}

# Catch all settings
catch_all:
  key: AQ==
  webhook: ${DISCORD_WEBHOOK}

# Blocked senders
blocked_senders: []

Changing the map mqtt details of course

[briandinsmore]

Yep I adjusted the mqtt correctly and seeing both of and mqtt messages. Just missing something on the discord side. Am I supposed to do something different than a channel webhook?

…

-------- Original Message --------

On Monday, 10/13/25 at 19:50 afourney ***@***.***> wrote: afourney left a comment [(afourney/discord_mesh_bot#6)](#6 (comment)) ***@***.***(https://github.com/briandinsmore) it has been a while since I last looked at this -- and it's configure for our Puget Mesh instance near Seattle. You will need to update the config.yaml. Probably the minimal config might look like this: # MQTT Settings mqtt : address : mqtt.davekeogh.com port : 1883 user : meshdev password : large4cats subscription : msh/US/2/e/# map_url_prefix : https://meshtastic.davekeogh.com/?node_id= # Node ID will be appended # Channel settings channels : - name : LongFast key : AQ== webhook : ${DISCORD_WEBHOOK} # Catch all settings catch_all : key : AQ== webhook : ${DISCORD_WEBHOOK} # Blocked senders blocked_senders : [] Changing the map mqtt details of course — Reply to this email directly, [view it on GitHub](#6 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABX55UGOJW7M7FR4RL2ARPT3XQ3DFAVCNFSM6AAAAACI7WXVTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJZGQZTANRWGE). You are receiving this because you were mentioned.Message ID: ***@***.***>

[afourney]

Hmm, I'm not sure. Maybe something with your environment variables.

Try replacing "${DISCORD_WEBHOOK}" with your webhook URL directly.

[briandinsmore]

channels: - name: LongFast key: AQ== webhook: ${DISCORD_WEBHOOK} thread: 1427023267578908794 The "thread" part of that is what I'm questioning, and included in your config.yaml

…

On Monday, October 13th, 2025 at 8:16 PM, afourney ***@***.***> wrote: afourney left a comment [(afourney/discord_mesh_bot#6)](#6 (comment)) Hmm, I'm not sure. Maybe something with your environment variables. Try replacing "${DISCORD_WEBHOOK}" with your webhook URL directly. — Reply to this email directly, [view it on GitHub](#6 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABX55UCCCDWELGTKCLFFF2T3XQ6E5AVCNFSM6AAAAACI7WXVTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJZGQ4DCMJRGU). You are receiving this because you were mentioned.Message ID: ***@***.***>

[afourney]

channels:

• name: LongFast
  key: AQ==
  webhook: ${DISCORD_WEBHOOK} thread: 1427023267578908794

The "thread" part of that is what I'm questioning, and included in your config.yaml
…

So the thread part is because our Discord admin set up different threads under one channel to use. It's not required.
If you have set up threads, you can copy the number from the URL when accessing the thread in Discord via a web browser.

If you don't use threads, simply remove that key from the config file. and it should just write to the channel directly.

[briandinsmore]

Commenting out the thread line appeared to work. Is this how you sent different channels in meshtastic to different Discord channels?

…

-------- Original Message --------

On Monday, 10/13/25 at 20:52 Brian ***@***.***> wrote: channels: - name: LongFast key: AQ== webhook: ${DISCORD_WEBHOOK} thread: 1427023267578908794 The "thread" part of that is what I'm questioning, and included in your config.yaml On Monday, October 13th, 2025 at 8:16 PM, afourney ***@***.***> wrote: > afourney left a comment [(afourney/discord_mesh_bot#6)](#6 (comment)) > > Hmm, I'm not sure. Maybe something with your environment variables. > > Try replacing "${DISCORD_WEBHOOK}" with your webhook URL directly. > > — > Reply to this email directly, [view it on GitHub](#6 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABX55UCCCDWELGTKCLFFF2T3XQ6E5AVCNFSM6AAAAACI7WXVTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJZGQ4DCMJRGU). > You are receiving this because you were mentioned.Message ID: ***@***.***>

[briandinsmore]

Just caught this. I was hoping the threads directive was for channels. Are there any other parameters or flags that aren't documented in the readme? It's a bit verbose and I was looking for slightly more compact (irc style) output.

…

-------- Original Message --------

On Tuesday, 10/14/25 at 14:37 afourney ***@***.***> wrote: afourney left a comment [(afourney/discord_mesh_bot#6)](#6 (comment)) > channels: > > - name: LongFast > key: AQ== > webhook: ${DISCORD_WEBHOOK} thread: 1427023267578908794 > > The "thread" part of that is what I'm questioning, and included in your config.yaml > … So the thread part is because our Discord admin set up different threads under one channel to use. It's not required. If you have set up threads, you can copy the number from the URL when accessing the thread in Discord via a web browser. If you don't use threads, simply remove that key from the config file. and it should just write to the channel directly. — Reply to this email directly, [view it on GitHub](#6 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABX55UD7LDMULMRRYZIZVN33XU7EXAVCNFSM6AAAAACI7WXVTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMBTGEZTGOJSGI). You are receiving this because you were mentioned.Message ID: ***@***.***>

[afourney]

Yes, you can provide the name and key are for the Meshtastic channel and the webhook url is for Discord. You can presumably set up different webhooks as-needed. Mix and match. The thread is to direct messages to different threaded conversations within a Discord channel.

As for verbosity.. there are no other flags. It should be relatively straightforward to edit though -- even just vibe code if needed. If there's a suggested format, I can maybe provide a patch for you.