# Flowfuse and Opto/22 deployment

**URL:** <https://discourse.nodered.org/t/flowfuse-and-opto-22-deployment/91053>\
**Category:** FlowFuse\
**Created:** [17 September 2024 18:44 UTC](https://discourse.nodered.org/t/flowfuse-and-opto-22-deployment/91053 "2024-09-17T18:44:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wz2b](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/wz2b/32/55839_2.png) [@wz2b](https://discourse.nodered.org/u/wz2b)\
**Post date:** [17 September 2024 18:44 UTC](https://discourse.nodered.org/t/flowfuse-and-opto-22-deployment/91053/1 "2024-09-17T18:44:55Z")

</div>

I found [Opto 22 Embraces Node-RED to Drive Customer Innovation • FlowFuse](https://flowfuse.com/customer-stories/opto22-embraces-node-red/) and it got me curious: part of what FlowFuse does above N-R is gives you a way to deploy from a central Flowfuse N-R out to your edge devices, where each edge device can have its own set of flows specific to that device.

For this to work with an Opto/22 device like a Groov wouldn't the Groov have to be running the FlowFuse device agent? Does it do that?

---

<div class="post-metadata">

**Author:** ![butteronadonut](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/butteronadonut/32/41374_2.png) [@butteronadonut](https://discourse.nodered.org/u/butteronadonut)\
**Post date:** [14 November 2024 14:36 UTC](https://discourse.nodered.org/t/flowfuse-and-opto-22-deployment/91053/2 "2024-11-14T14:36:44Z")

</div>

+1 on interest on Opto22 and FlowFuse divide agent integration.

cross-post:

> **[FlowFuse device-agent](https://forums.opto22.com/t/flowfuse-device-agent/6139)**
>
> Is anyone running the FlowFuse device-agent on EPIC or RIO in lieu of the Node-RED environment available natively on these devices?