Skip to content
View in the app

A better way to browse. Learn more.

Security Installer Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

All Activity

This stream auto-updates

  1. Today

  2. Bonjour
  3. al-yeti started following Long time away
  4. Hi just re found (If thats the correct word lol) Been at ADT for agggggges (Made redundant then went to Chubb and now back for my sins at ADT) just thought id pop in and say Hi
  5. Gary-P joined the community
  6. Yesterday

  7. techmandan1 joined the community
  8. Thats a good idea to be fair, ill make sure I have a look night
  9. Fair challenge al-yeti, I don't know of any for the i-ON. I was talking about addressable detectors in general and should have been clearer, so for virdi it's conventional PIRs on zones. Thanks james for the Risco and HKC examples.
  10. Last week

  11. blue knight joined the community
  12. You don't need to adjust it tho, default will give a long lasting battery unless you want to keep a faulty device going ? Even the ones that are opened allot Just use a decent battery if your not replacing yearly really
  13. On the battery question: real-life life on Ajax kit depends a lot on the detector ping interval set on the hub. Leave it at a sensible default rather than the shortest setting, because a very short ping interval drains the detectors noticeably faster. Devices in cold spots or outdoors, and door contacts that get opened all day, also go quicker than the brochure figure, so it's worth checking battery levels in the app every few months for the first year to see what your own house actually does.
  14. A quick point for anyone still considering this: if a buried cable has been damaged, a basic continuity test can still pass while the pair resistance is too high for stable PoE. Check each pair and test the camera while powered and streaming, not just with a cable tester. If it drops out under load, treat the cable as failed rather than relying on a passive pair-sharing adapter.
  15. DavidJ_75 started following Tat in Habitat
  16. Risco had a485 detetor and hkc do addressle
  17. For a temporary prove-out with power isolated, short only what you can confirm is the alarm loop and leave the tamper pair alone so you do not mask a real tamper. Longer term, buzz each pair with a meter while you operate a replacement contact rather than permanently twisting unknown colours, then fit a proper reed/magnet and retest the whole tamper loop.
  18. It's not what I am asking , I am asking what "bus" detectors did you think Eaton scantronics have ? Generally speaking most panels are using a bus these days for there keypads expanders etc But none of them use bus data pirs except 1 or 2
  19. I cannot think of a single IAS system that allowed detection devices connected directly to a system bus/data line. There have been a few that connect via a single interface such as ID biscuits or Securicor's Genesis system which used MLI's. I am not saying there isn't such a thing but I just cannot recall anything that did this.
  20. By bus detectors I mean PIRs built with the panel's own addressable bus interface, rather than a conventional relay-output PIR. They are enrolled as individual devices and report alarm and tamper over the bus, so the panel has to support that exact detector family. A quick way to identify one is that its manual specifies bus addressing and current draw, not just terminals for alarm and tamper contacts. If you add one, check the panel's permitted bus cable length and total current, then measure voltage at the furthest detector during a walk test, since a marginal supply can cause intermittent device faults.
  21. What bus detectors?
  22. Yes, the AUX Tamper terminals are what shows up as AUX 0 in the log. With a long global tamper chain, a short maintenance-window test of jumpering half the chain at a time should find the faulty leg faster than opening every detector.
  23. Cornish Superstar joined the community
  24. For the Fanvil side you mainly need one dry-contact pair into the gate Start / open input: NO and COM on the i66, matching whatever Common you trace back into A60 terminal 20 as Nice said. Green sounding like the old Verso relay legs fits that job once you confirm continuity to that Common. Orange you already proved is the fob path, so leave that alone unless you are deliberately moving the fob input. Brown being unused by the gate when unplugged usually means it was only feeding the old intercom (status / door-open sense or a second relay), not something the A60 needs to run. If you want to be sure, buzz brown back to the A60 end before you cut it. Photocells stay on their own Common in terminal 20; do not share that with the intercom NO/COM.
  25. zydrius001 joined the community
  26. Oversite joined the community
  27. It also seems the current intercom is not a Control4 branded intercom and is actually a 2N IP Verso (without camera) model
  28. It's possible I only need the green pair that is connected to the relay terminals when connecting the Fanvil i66 The 2N IP Verso I/O Module (Part No. 9155034) expands compatible intercoms with two logical inputs and two relay outputs for sensor integration and external device control.
  29. Hi James I am replacing the Control4 intercom with a Fanvil i66 The issue I am dealing with is understanding which of the 3 pairs in the intercom need to go into the new intercom
  30. Earlier

  31. i dont understnd the question sorry, what you trying to achieve?
  32. I have tested the old control4 intercom and the orange pair are the fob. Unsure what the brown pair are as the gate works when that connector block is unplugged
  33. Message from Nice tech support goes against my green pair theory Hi James, From your picture, none of the greens are from the Common on the A60 control unit, if you reference the diagram below I sent you, you have multiple commons in terminal 20, I would assume for the photocells and the intercom unit. (you will need to verify) So from the picture, green is for a NO of your choice and programming of the Fanvil, and you will have to cable trace which common you have free in terminal 20 of the A60 that lead back to the intercom unit to be wired into the relevant Common.
  34. I am expecting the green pair which was connected to the relay terminals to be connecting into the NO1 and COM1
  35. On the i-ON side, that bus daisy chain is mainly for keypads, expanders and other addressable devices. Ordinary PIRs still go on the zone wiring unless you specifically bought bus detectors that match the panel. Same idea as the O----O----O layout already mentioned, just worth knowing PIRs are not automatically on that bus.
  36. Can you help me with the install of a Fanvil i66 please. I have removed a Control4 PoE intercom and there is 3 pairs out of 4 connected to it O/OW G/GW BR/BW The blue pair at the intercom end was not in use There is a pair of photocells and a remote fob

Who's Online (See full list)

Member Statistics

  • 52,437 Total Members
  • 1,932 Most Online
  • Gary-P Newest Member ·

Forum Statistics

  • Total Topics 33.6k
  • Total Posts 448.7k

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.