Another great video, thanks for posting. I have to say I love your comment: "...it (MQTT) may seem defeating the purpose of a mesh network to use the Internet because the whole purpose of Meshtastic is to be able to communicate Off-Grid without any GMS network, without any Internet network..."
According to the documentaiton, Setting this to option to 'true' means the device will ignore any messages it receives via LoRa that came via MQTT somewhere along the path towards the device
I am trying to text from an Raspberry Pi to a Mestastic device. Do you know what is the basic mosquitto_pub line command to send text to your Mestastic unit?
You'll find your answer in details on this post : meshtastic.discourse.group/t/what-is-the-basic-mosquitto-pub-command-to-send-text-to-your-mestastic-unit/11686/8
you create a new channel in the radio configuration/channels sub menu. For others to be able to use your channel, you'll have to share the QR code (the password).
@@PoweredMeshtasticEurope hmmm ok the T-Beam also. Is there no device available that will not crash - very annoying. Maybe with an additional RaspberryPi? Do you have any ideas why the device crashes?
@@JohnDoe-qp3vb The device crashes because of a volume overload (public channel used by everyone at the same time). The best approach I believe is to set up your own private mqtt server/subscription so that only people who received the channel info may communicate on it.
Great video but sometimes we don't need 10 minute videos telling us what something is or additional words. Short 3 minute videos on how to configure something is just as good.
Another great video, thanks for posting. I have to say I love your comment: "...it (MQTT) may seem defeating the purpose of a mesh network to use the Internet because the whole purpose of Meshtastic is to be able to communicate Off-Grid without any GMS network, without any Internet network..."
By connecting to MQTT I have 999 nodes... but it is better than being alone.
True😂😂😂
Hello, what about the ignore MQTT option in Lora settings? Should I enable or disable it?
According to the documentaiton, Setting this to option to 'true' means the device will ignore any messages it receives via LoRa that came via MQTT somewhere along the path towards the device
Merci!
Robinson Nancy Clark Amy Thomas Cynthia
What is the default password for the MQTT server? Thanks
You just need to enable the MQTT in the corresponding radio config menu. The default values are set by default in the app.
tres utile, merci beaucoup!
Thank you. I might check the firewall's port number on my Linux system.
Mine isnt working
diificult to help without more details
Great video, but no mention when someone is using a router/repeater.
thanks for that video that help a lot Aussie Meshtasic user Gmrg
Great tutorial!
merci beau coupe
Yes Sir, thanks!
I am trying to text from an Raspberry Pi to a Mestastic device. Do you know what is the basic mosquitto_pub line command to send text to your Mestastic unit?
You'll find your answer in details on this post : meshtastic.discourse.group/t/what-is-the-basic-mosquitto-pub-command-to-send-text-to-your-mestastic-unit/11686/8
I have a question. If I want to appear on meshmap but not seeing "online" nodes in my node list do I have to enable only uplink, right? Thank you!
I guess so
how do you configure your own private Ch?
you create a new channel in the radio configuration/channels sub menu. For others to be able to use your channel, you'll have to share the QR code (the password).
Hello, is there any module available that doesn't crash if this module is connected to the public channel (LongFast) via MQTT and W-Lan?
I can tell that the Heltec V3 and the RAKWireless 19007+4631 will crash. I did not try any other meshtastic compatible hardware.
@@PoweredMeshtasticEurope hmmm ok the T-Beam also. Is there no device available that will not crash - very annoying. Maybe with an additional RaspberryPi? Do you have any ideas why the device crashes?
@@JohnDoe-qp3vb The device crashes because of a volume overload (public channel used by everyone at the same time). The best approach I believe is to set up your own private mqtt server/subscription so that only people who received the channel info may communicate on it.
Great video but sometimes we don't need 10 minute videos telling us what something is or additional words. Short 3 minute videos on how to configure something is just as good.