Hi everyone,
I created a Node-RED node that integrates Meshtastic.js functionality.
It allows Node-RED to connect to a device using HTTP and then send and receive messages, packets or whatever Meshtastic.js supports.
This is the first version, bugs are expected. Anyway, I believe it is good enough for text messages and getting data out from the mesh.
This is the GitHub repository: GitHub - danpeig/node-red-meshtastic-msg: Node-RED Meshtastic Messages Node
And the NPM package name is: @danpeig/node-red-meshtastic-msg
Very nice project indeed. Fab use case. Thanks for sharing this and the code. A lovely programing tool. Can you provide a step by step start guide from zero up on how to make it work using your git hub links for people like me who are completely new to node-red and git hub ? I know there is an installation guide but it assumes the user knows about or had node-red. If I am just too dumb and demanding, no worries! Just seems like a tool for total beginners that might be a hit if one knew how to start. Cheers!
(https://nodered.org/ . Node-RED is a programming tool for wiring together hardware devices, APIs and online services in new and interesting ways. It provides a browser-based editor that makes it easy to wire together flows using the wide range of nodes in the palette that can be deployed to its runtime in a single-click.)
Hi,
I will see if I can do a quick video.
Overall Node-RED is quite easy to use. You can build automations just by connecting nodes. No programming skills required.
Regards
Hi danpieg. Great work on the library, I have been playing with it this evening.
Not managed to get it to send/receive to a node running v2.5.4 yet, but this may be optimistic. I’ll try going back a few versions and see if that helps. Any recommendation on known working FW versions? Or am I missing something obvious?
Currently the log shows ping failures in your v. helpful example flow, so I’m guessing I don’t have a working HTTP connection to the node.
At this point I’m just trying to implement a simple
Auto responder on a private channel to use for drive testing. Implementing this via the python CLI is a bit tricky as I don’t have a direct serial connection (node in the loft…)
[Doh! Just realised that the CLI does support TCP connections, so I could use it, but I’d much rather use node-red]
Hi,
The default connection in the example flow uses a standard meshtastic hostname (meshtastic.local). Depending on how your network is configured, the hostname will not work.
I recommend trying to use the IP address of the device instead of meshtastic.local.
To test of the device is reachable from your computer, just type the IP address in the browser and see if it pops the client interface.
Regards
1 Like
Hi danpeig,
Sorry, feeling dumb! Due to a routing mistake (entirely my fault…) the server running node-red couldn’t see the Meshtastic node, although I could see both from my laptop.
A quick traceroute and http request in node-red (no GUI, so no browser) from the server made this clear. Also didn’t help that the node had been allocated a different IP at some point in the testing 
Now on a fixed IP.
All working beautifully now. Many thanks for both the support and the library. Now I can implement my echo service and get coverage mapping.
1 Like