# Engine integration

**URL:** <https://community.victronenergy.com/t/engine-integration/36065>\
**Category:** DIY\
**Tags:** marine, cerbo\_gx, nmea\_2000\_-\_n2k\
**Created:** [16 June 2025 16:28 UTC](https://community.victronenergy.com/t/engine-integration/36065 "2025-06-16T16:28:20Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![pwfarnell](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/pwfarnell/32/2341_2.png) [@pwfarnell](https://community.victronenergy.com/u/pwfarnell)\
**Post date:** [17 June 2025 06:36 UTC](https://community.victronenergy.com/t/engine-integration/36065/5 "2025-06-17T06:36:38Z")

</div>

There are people who run Node-RED on a separate unit such as a Raspberry Pi and transfer info with the Cerbo rather than on the Cerbo but that is outside my knowledge. There are posts in the Modifications Section on this such as the one below if searched for

> [@Import sensors through internal MQTT](https://community.victronenergy.com/t/import-sensors-through-internal-mqtt/832/2):
>
> After much experimentation I find it the best to setup separate Raspberry PI to run Node Red and talk to Cerbo over DBus TCP and to other things via any other available mechanism, WiFi, Bluetooth, whatever you want… That way you can easily follow all Cerbo updates without much added customization and have your playground elsewhere… See here for my project: [GitHub - mman/node-red-dashboard-ismove: Dashboard for Niesmann Bischoff iSmove](https://github.com/mman/node-red-dashboard-ismove)

---

_[View the full topic](https://community.victronenergy.com/t/engine-integration/36065)._