# Indirect OpcItemPath **URL:** \ **Category:** Ignition\ **Created:** [June 13, 2023, 1:56pm UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957 "2023-06-13T13:56:25Z")\ **Posts on this page:** 1\ **Showing post:** 14
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [June 14, 2023, 12:33am UTC](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957/14 "2023-06-14T00:33:16Z")
Kevin beat me to it, here's a brief description on what to do. Your connection names can obviously be whatever you want. - For communication between primary and secondary devices with different addresses/hostnames, create 3 device connections - Device connection “A” - Device connection “B” - Device connection “Master” - Connections “A” and “B” will only be used for reference to the diagnostics to determine a device connection - Tags used throughout the project will reference the “Master” connection - A Gateway Timer Script will run at a specific delay and will determine the correct hostname for the “Master” based on the connection for “A” and “B” and the pre-determined primary and secondary definitions (typically “A” is the primary and “B” is the secondary) - If a connection to “A” is good, then use the hostname for “A” - If a connection to “A” is not good and the connection to “B” is good, then use the hostname for “B” - If neither connection to “A” nor “B” is good, then leave the hostname as-is - Can have a delay to swap back to “A” --- _[View the full topic](https://forum.inductiveautomation.com/t/indirect-opcitempath/74957)._