# Send Payload from one RPI to another RPI

**URL:** <https://discourse.nodered.org/t/send-payload-from-one-rpi-to-another-rpi/963>\
**Category:** General\
**Created:** [20 June 2018 18:22 UTC](https://discourse.nodered.org/t/send-payload-from-one-rpi-to-another-rpi/963 "2018-06-20T18:22:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pedrofu](https://avatars.discourse-cdn.com/v4/letter/p/35a633/32.png) [@pedrofu](https://discourse.nodered.org/u/pedrofu)\
**Post date:** [20 June 2018 18:22 UTC](https://discourse.nodered.org/t/send-payload-from-one-rpi-to-another-rpi/963/1 "2018-06-20T18:22:47Z")

</div>

Hello,

I’m trying to send out the payload from a sensor reading from one Raspberry pi to another Raspberry Pi . This way I can have multiple readings in one Dashboard. I tried using the TCP output and Input and they connect but the payload msg comes out in Hex instead of the readings from the sensor. Is this the right route I’m taking by using TCP? Or is there any other way to transfer from one system to another. Do I have to format the output prior to using the TCP node? Any guidance would be greatly appreciated.  
Best Regards,

Pedro Fuentes

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [20 June 2018 18:32 UTC](https://discourse.nodered.org/t/send-payload-from-one-rpi-to-another-rpi/963/2 "2018-06-20T18:32:40Z")

</div>

Why not use MQTT to pass the data?

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [20 June 2018 19:04 UTC](https://discourse.nodered.org/t/send-payload-from-one-rpi-to-another-rpi/963/3 "2018-06-20T19:04:57Z")

</div>

I would agree MQTT is probably the easiest method.  
You might need to draw a thumb-nail sketch to see how all the IP and Port numbers are mapped.

---

<div class="post-metadata">

**Author:** ![pedrofu](https://avatars.discourse-cdn.com/v4/letter/p/35a633/32.png) [@pedrofu](https://discourse.nodered.org/u/pedrofu)\
**Post date:** [20 June 2018 19:10 UTC](https://discourse.nodered.org/t/send-payload-from-one-rpi-to-another-rpi/963/4 "2018-06-20T19:10:02Z")

</div>

Thanks, I imagine that I would setup A broker on one node. Right?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [20 June 2018 20:29 UTC](https://discourse.nodered.org/t/send-payload-from-one-rpi-to-another-rpi/963/5 "2018-06-20T20:29:27Z")

</div>

Correct- just put the broker on the central or main PI.  
But for the TCP node - how have you configured its output ? As strings should probably be what you need.
