# Modbus tcp IP HOST from msg

**URL:** <https://discourse.nodered.org/t/modbus-tcp-ip-host-from-msg/53436>\
**Category:** General\
**Created:** [9 November 2021 08:23 UTC](https://discourse.nodered.org/t/modbus-tcp-ip-host-from-msg/53436 "2021-11-09T08:23:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)\
**Post date:** [9 November 2021 13:27 UTC](https://discourse.nodered.org/t/modbus-tcp-ip-host-from-msg/53436/2 "2021-11-09T13:27:44Z")

</div>

short answer. The Modbus nodes dont support that.

There is a recent discussion [here](https://discourse.nodered.org/t/ip-address-as-a-variable/53225/3) regarding using environment variables but thats not truly dynamic configuration since (from what i understand) `env` variables update on system restart?

you could open a feature request on the developer's [Github page](https://github.com/BiancoRoyal/node-red-contrib-modbus)

may i ask why you want to do this and how many modbus devices do you have?  
the best solution now is to create multiple modbus-client nodes and Flex-getters

the only use i cant think of is trying to dynamically loop through an array of ips and connect to a list of modbus devices.

---

_[View the full topic](https://discourse.nodered.org/t/modbus-tcp-ip-host-from-msg/53436)._