Remote access for Paradox panels: Insite Gold, BlueEye, SWAN and local IP150 options

Discuss the Paradox Spectra and Digiplex Range of Alarm Systems
Post Reply
User avatar
ZerOne
Site Admin
Posts: 292
Joined: Sun Dec 13, 2020 8:21 am

What this thread is
A short map of how you actually talk to a Paradox panel from a phone or a PC: the official apps (Insite GOLD and BlueEye), the SWAN cloud service, and the older local IP150 path. The module-by-module compatibility detail sits in the keypads-and-modules thread. Connecting a panel to Home Assistant is already covered in Paradox alarm panels and smart home integration (Oct 2026): PAI, IP150, serial, and the firmware warning and in the PAI + Mosquitto + Home Assistant project thread. This post does not repeat those steps, and it does not recommend exposing an IP module to the internet.

It is not official Paradox advice, not a monitoring-contract guide, and not a product endorsement. App features, SWAN subscription rules and which firmware talks to which app have all changed more than once. Confirm the combination you actually have — panel, IP or PCS module, module firmware, and app — before you promise a customer (or yourself) a particular remote-access method. I have not published prices, and I have not bench-tested these combinations.

Complexity
Reading: beginner. Putting a communicator on a live, monitored panel is installer work — see who needs a licence to install alarms, CCTV or access control.

1. Two official phone apps, not one
Paradox’s official software page currently lists both:
  • Insite GOLD — official iOS and Android app for the classic IP150 / IP150+ generation (and for PCS modules that official pages still describe as supporting Insite GOLD, such as PCS265LTE). Official feature list: arm/disarm, PGM control, access-door control, push notifications, multi-site, video-on-demand features, panic buttons, SWAN configuration, and fixed / direct IP as well as SWAN. The official Insite Gold Complete User Guide (v1.9.2) is the end-user document.
  • BlueEye — official iOS and Android app for the later MQTT generation (officially IP180, IP150 MQTT / IP150+MQ, PCS265V8, and the M25 platform in the September 2026 catalogue). Official IP180 and MQTT-module pages are explicit: when those modules are fitted, Insite GOLD will not connect. The official software page also describes BlueEye as the app for alarm, access control, video and outputs, with an installer section for programming and maintenance.
You cannot assume “the Paradox app” will work. The module generation decides which app is the official path. A site that still has a classic IP150 is an Insite GOLD site; a site that has been moved to an IP180 or to IP150 MQTT firmware 6.0 is a BlueEye site.

2. SWAN, and the older PMH service it replaced
SWAN is Paradox’s current cloud connection service for apps and, depending on the module, for installer software. Official IP150+ documentation describes the module polling SWAN, and lists ports that need to remain open if you are using that path (including the configurable software port, default 10000, and ports 53, 443, 3478 and 5683). Official IP180 documentation talks about SWAN-Q, with its own port list (including MQTT on TCP 8883).

The older public-facing service was paradoxmyhome.com (PMH). Official Insite GOLD documentation includes a migration from a PMH site to SWAN, and older IP configuration software (IP Exploring Tools, last official listing I saw was a 2013 release) was built around that DNS service. If a customer still has a PMH-style site ID, that is a migration conversation with their installer, not something to jury-rig from a phone.

Official Insite GOLD user documentation says a created site can be added to an unlimited number of devices “without the need to pay for a subscription up until it expires,” and that creating a new site is an installer task (the installer setup guide sits behind a paradox.com login). Official MQTT product text for IP150 MQTT firmware 6.0 says that module requires a paid SWAN site. I have not stated a price, a plan name or a renewal fee, because I could not verify a current official public price list that I was confident would still be right tomorrow. Ask the installer or the distributor for the current SWAN terms.

3. Local / direct IP, versus cloud
There is still an official on-LAN path, but it is generation-specific.

Classic IP150 / IP150+ and Insite GOLD. The official Insite GOLD user guide has a section on adding a direct IP connection as well as adding an existing SWAN site. Official IP150+ documentation is also written around local PC software (BabyWare, InField, NEware) talking to the module, with DHCP on by default and a configurable software port (10000 in the MG/SP programming guide). That local IP path is the one the existing PAI integration thread discusses, and it is the one that thread prefers over a cloud/SWAN connection for Home Assistant. Firmware on the IP150 matters a great deal for third-party local access; those ranges and warnings stay in t=161 rather than being copied here.

IP180 and MQTT modules and BlueEye. The official IP180 installation manual (V1.00.003, 2024) is blunt: the IP180 “cannot support local closed networks,” “Paradox will offer future local solutions for closed networks,” and although you can configure a static IP in the BlueEye installer menu, “BlueEye does not support static IP connection and IP180 must have internet connection.” Official MQTT product pages retrieved on the same day I wrote this also said static IP connection was not supported “for now” on IP180 / IP150+MQ / IP150 MQTT 6.0, and that IP150 MQTT 6.0 cannot be downgraded to v5.xx.

There is a conflict with a later official line: the current Paradox software page now advertises that BlueEye “NEW! Now Supports Fixed IP.” I have not been able to reconcile that headline with the IP180 manual from a single official technical document, so I am leaving it as an open point. If fixed-IP / closed-network access matters on a BlueEye site, confirm it against the current BlueEye release notes and the manual for the exact module firmware, and do not assume the 2024 IP180 manual has been silently updated.

4. What to use for which job
  • End-user phone control of a classic IP150 / IP150+ site: Insite GOLD, set up by the installer, either on SWAN or (where the firmware still allows it) as a direct IP connection on a trusted network.
  • End-user phone control of an IP180, IP150 MQTT or PCS265V8 site, or of an M25: BlueEye. Official documents say Insite GOLD will not connect to those MQTT modules.
  • Installer programming: BabyWare (and InField for firmware), locally on a 307USB / CONV4USB or remotely through a supported IP/PCS path. EVO end users who need a PC interface officially have NEware. Plus and MQTT-era panels may need a current BabyWare build — see the installer-basics thread.
  • Home Assistant or other MQTT home-automation: start at t=161 and t=162. The short version, already in those threads, is: prefer a local IP150 connection or serial, do not enable the cloud/SWAN option in PAI, do not port-forward the module, and check the PAI compatibility page for the exact panel and IP150 firmware before anyone upgrades anything.
  • Central-station monitoring: classic modules officially report to IPR512 / IPRS-7 (and similar). MQTT modules officially report only to IPC10 / VIPC20. That is a monitoring-centre conversation, not an app setting the end user can “just switch.” Official IP180 text also says reporting is Contact ID only to the IPC10.
5. Network hygiene that does not change with the app name
The same advice the rest of this forum repeats still applies:
  • Change the published default installer and master codes, the Panel ID, the PC password, and the IP module password. The installer-basics thread lists the official published defaults.
  • Do not port-forward the module’s software port (10000 or otherwise) to the public internet.
  • Prefer a local connection, on an IoT VLAN with a DHCP reservation, when the official module firmware still allows one.
  • IP modules typically allow one PC session at a time — disconnect BabyWare before you start anything else that uses the same port.
  • If the alarm is monitored, tell the monitoring company before you change the communicator, the reporting path or the app.
  • Do not upgrade an IP or PCS module “to see if the new app works” without reading the official downgrade warning for that exact firmware. Some official pages, including IP150 MQTT 6.0 and PCS265LTE, warn that particular upgrades cannot be undone.
If you post a remote-access question, the useful details are the panel model and firmware, the exact IP or PCS module and its firmware, whether you are trying to use Insite GOLD, BlueEye, BabyWare or PAI, and whether the module currently has a SWAN site, a direct IP, or both.

Official starting points
Paradox: software and apps (BlueEye, Insite GOLD, BabyWare, InField, NEware)
Insite Gold Complete User Guide v1.9.2 (PDF)
IP150+ Installation Manual (PDF)
IP180 Installation Manual V1.00.003 (PDF)
Paradox: MQTT communication devices
Paradox product catalogue, updated September 2026 (PDF)
Just Smart Homes t=161: PAI, IP150, serial and the firmware warning
Just Smart Homes t=162: PAI with Mosquitto and Home Assistant
Just Smart Homes t=251: security licensing in Australia

This is not official Paradox advice, not a monitoring quote, and not a claim that every app feature listed is available on every firmware. Insite GOLD and BlueEye are not interchangeable, some MQTT modules officially require a paid SWAN site, and official documents currently disagree about BlueEye fixed-IP support. Check the current official manual and app release notes for your exact module, or ask a licensed installer, before you change a communicator or a remote-access path. Researched from official documentation on 22 November 2026 (Australia/Sydney). Please correct anything that has moved on.
Post Reply

Return to “Paradox Alarm System Discussion”