# Modbus TCP and process.env.NODE\_RED\_HOME

**URL:** <https://discourse.nodered.org/t/modbus-tcp-and-process-env-node-red-home/9643>\
**Category:** General\
**Created:** [1 April 2019 03:12 UTC](https://discourse.nodered.org/t/modbus-tcp-and-process-env-node-red-home/9643 "2019-04-01T03:12:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [1 April 2019 07:21 UTC](https://discourse.nodered.org/t/modbus-tcp-and-process-env-node-red-home/9643/2 "2019-04-01T07:21:04Z")

</div>

Hi @CaptClaude

it looks like that node is still using a way of accessing the Node-RED runtime that has been long deprecated and should have been updated years ago.

The 0.20 release of Node-RED changed the internal layout of the code, so the assumptions that node made about how to access the core of the runtime no longer hold true.

I see you've already raised an issue on the node - that's the right first place to start in resolving this.

---

_[View the full topic](https://discourse.nodered.org/t/modbus-tcp-and-process-env-node-red-home/9643)._