Announcement

Collapse
No announcement yet.

Primary-Secondary Controller Confusion

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Primary-Secondary Controller Confusion

    When I set up my HS3 network several years ago, I added a second znet controller to reach some distant devices. I intended for it to be a secondary controller on the same network, but because I now have a failing zstick on another network, I have become very interested in controller back ups. In trying to synchronize these znet controllers (what I hope will also serve as a back up), I get this error "Your Main interface for this network must be the SUC, SIS, or primary controller to use this function." As I started digging into this issue, as the screenshot indicates, what I thought was my primary controller seems to be a node of what I thought was the secondary controller; neither can be synchronized. Can anyone explain what I have configured and how I might make it more orderly?
    Attached Files
    HS4Pro on Windows 10
    One install with 2 Ethernet Z-nets
    2nd install with 1 Ethernet Z-net
    300 devices, 250 events, 8 scripts
    6 CT-100 tstats
    Serial IT-100 interface to DSC Panel with 8 wired zones
    18 Fortrezz water sensors & two valve controls

    #2
    It's Saturday, but surely someone is awake
    HS4Pro on Windows 10
    One install with 2 Ethernet Z-nets
    2nd install with 1 Ethernet Z-net
    300 devices, 250 events, 8 scripts
    6 CT-100 tstats
    Serial IT-100 interface to DSC Panel with 8 wired zones
    18 Fortrezz water sensors & two valve controls

    Comment


      #3
      Any help?
      HS4Pro on Windows 10
      One install with 2 Ethernet Z-nets
      2nd install with 1 Ethernet Z-net
      300 devices, 250 events, 8 scripts
      6 CT-100 tstats
      Serial IT-100 interface to DSC Panel with 8 wired zones
      18 Fortrezz water sensors & two valve controls

      Comment

      Working...
      X