# Controlling remote devices from within FarmOS

**URL:** <https://farmos.discourse.group/t/controlling-remote-devices-from-within-farmos/29>\
**Category:** Development\
**Created:** [June 21, 2019, 6:44am UTC](https://farmos.discourse.group/t/controlling-remote-devices-from-within-farmos/29 "2019-06-21T06:44:45Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![MBConsultingUK](https://avatars.discourse-cdn.com/v4/letter/m/ed655f/32.png) [@MBConsultingUK](https://farmos.discourse.group/u/MBConsultingUK)\
**Post date:** [November 27, 2019, 7:39pm UTC](https://farmos.discourse.group/t/controlling-remote-devices-from-within-farmos/29/13 "2019-11-27T19:39:33Z")

</div>

Absolutely!

I’ve nothing against NodeRed as such, I just have concerns about it’s scalability.

If you’re dealing with a few dozen messages an hour, then it’s perfect for drag-and-drop “glue” to link components together, but once you start to get above a few hundred messages a minute then I’d be concerned about the performance.

Admittedly, I’ve not tried it in a while and it may have improved, but both the IBM-hosted version and a self-hosted version felt a lot slower compared with a 100-line python script when I used them.

As @mstenta says though, there’s no reason we can’t have both, and if we were to “standardise” on something like MQTT as the protocol, then it makes it easy to swap either option in as necessary.

---

_[View the full topic](https://farmos.discourse.group/t/controlling-remote-devices-from-within-farmos/29)._