Conversation

Notices

1. :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Monday, 10-Feb-2025 17:20:42 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

   Due to change of plans this weekend, I got more time over to tinker with #meshtastic .

   I finally understood the basics of MQTT, got my own broker running with ACLs, TLS, logins and all that goodies.
   Connected all my nodes to it and also to my selfhosted Meshmap where my nodes and neighboring nodes are displayed.

   • :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse: (selea@social.linux.pizza)'s status on Monday, 10-Feb-2025 21:05:07 JST :debian: 𝚜𝚎𝚕𝚎𝚊 :opensuse:

     in reply to

     • Christian ♭

     @chrx

     I am wondering the same, because that would be a perfect solution for two nodes with yagi antennas

   • Christian ♭ (chrx@mastodon.nu)'s status on Monday, 10-Feb-2025 21:05:08 JST Christian ♭

     in reply to

     @selea I have questions! Does the MQTT transport impact hop count (guess not)?

     I'm wondering if setting up a local MQTT broker just to pass packages from the "home node" (client mode) to my mobile #meshtastic node (client mute) connected to my cell phone would make any sense.

     As it is now, even when home, I miss packages that are never forwarded from the "home node" to the "mobile node" since they reach the hop threshold. I wonder if private MQTT would solve this.