A map of the current official and officially mentioned ways to operate a Ness D-series panel from a phone, and to send events to a monitoring centre. It covers Ness Mezzo with Ness-Bridge / Ness-Bridge Plus, the older IP232 + iComms/aComms path, SMS on 4G-equipped panels, and ArmorIP / Contact ID / CSV-IP reporting. Companion threads cover panel identification, Home Assistant, and installer programming.
It is not official Ness advice, not a monitoring-centre contract, and not a recommendation of any particular central station. I have not commissioned these paths on a live site. App features, subscription prices and which SKUs are stocked change — confirm against the current Ness product page and with the monitoring company that will actually receive the signals.
Complexity
Reading: beginner to intermediate. Changing a reporting format on a monitored panel is work you do with the monitoring centre, and in Australia it often sits under a security licence — see who needs a licence. A phone app is not a substitute for a qualified back-to-base path. A Home Assistant notification is not one either; see alarm IP reporting in 2026.
1. The current official app: Ness Mezzo, with Ness-Bridge
As at 22 November 2026, Ness's current official consumer app for D-series remote operation is Mezzo by Ness Corporation, on the Apple App Store and Google Play. It is not called "Ness Connect" — I could not find a current official Ness product by that name.
Mezzo talks to the panel through a Ness-Bridge ethernet interface, not through the IP232:
- Ness-Bridge (106-014) — the original ethernet interface. The product page now points readers to Ness-Bridge Plus, but it remains the documented Gen1 hardware. Compatible, per that page, with DPlus, D8XD / D16XD Rev 6 and later, and D8XCEL 4G / D16XCEL 4G. Used with the Mezzo app for arm/disarm, Home Mode, zone and panel status, push notifications, and output control (outputs need optional 106-013 relay board/s).
- Ness-Bridge Plus (106-018, Gen2) — the current interface. Ethernet and Wi-Fi 6 (2.4 / 5 GHz, ethernet preferred when both are present), IP monitoring over ethernet and Wi-Fi, dual-path monitoring (internet plus optional 4G or a third-party path), ArmorIP and CSV-IP, and configurable over-the-air firmware updates.
Mezzo free vs subscription, as published on the Ness-Bridge Plus page on 22 November 2026 (confirm the live page; this can change):
- With Ness-Bridge Gen1, Ness says Mezzo currently keeps its existing feature set at no charge, with no subscription required, for as long as Ness continues to operate those cloud services. Enhanced features may require a paid subscription in the future.
- With Ness-Bridge Plus, Ness describes a 3-month introductory period with all features enabled from activation, after which a $5 per month subscription is the path to the full feature set (event history, alarm push notifications, output control, and further features as they are added). Remote arming and disarming remains available in the free version after that period.
- Arm/disarm is listed as available in the free app; Home Mode, output control, push notifications and zone/status viewing are listed as subscription features on the Plus hardware.
2. The older local-IP path: IP232, iComms and aComms
Ness IP232 (101-244) is an ethernet-to-RS232 bridge. It is the hardware the official Home Assistant integration documents, and it is also the hardware Ness lists for two third-party phone apps:
- iComms — iOS, third-party, paid
- aComms — Android, third-party, paid
The IP232 manual is blunt about security: the device does not support encryption, and the bridged TCP port should not be routed outside the local network. Do not port-forward 2401 (or whatever port you chose) to the internet "so the app works when you are out". If you need the official supported remote path, that is now Mezzo via Ness-Bridge, which is a different product. If you need access to a local integration, put a VPN in front of Home Assistant, not in front of a raw serial bridge.
The IP232 can also accept more than one TCP client and will merge their traffic onto one serial port. Running iComms, aComms, Home Assistant and NessComms at the same time on one IP232 is a good way to get a corrupted ASCII stream. One client at a time is the safe assumption.
3. SMS on 4G-equipped panels, and the retired XCEL SMS app
D8XCEL / D16XCEL 4G panels have an onboard 4G communicator. DPlus uses an optional 106-985 4G module. Official manuals and the XCEL ArmorIP bulletin describe operation and programming by SMS to the panel's SIM (master and installer codes in the message, in the published format), as well as SMS self-monitoring.
The XCEL installer manual (Rev 1.14, February 2024) still mentions the free NessXCEL SMS app. Current Ness product pages for those panels, as at 22 November 2026, state: the Ness XCEL SMS app is no longer available or supported. Plan around sending SMS to the SIM, or around Mezzo / a monitoring centre, not around that app coming back.
SIMs can be a Ness plan or bring-your-own; activation and SIM help are pointed at activate.ness.com.au and the contacts on Ness's contact page.
4. Back-to-base monitoring: Contact ID, ArmorIP and CSV-IP
This is the part that has actually changed in the last few years, and it is the one to get right with the monitoring centre rather than from a forum post.
D8x/D16x Deluxe still has a conventional landline dialler. Contact ID (and audible formats) are selected in the P86E family, with telephone numbers and account numbers in the P70E / P72E group. Whether a given site still has a usable PSTN or analogue-leased path is a conversation with the carrier and the monitoring centre, not something this thread can promise.
D8XCEL / D16XCEL 4G can report by ArmorIP or Contact ID, and can also self-monitor by SMS. Ness has published a product notice (Rev 1.1, 1 November 2024) and a technical briefing (Rev 1.0, 16 July 2024) that you should read in full if the panel still reports Contact ID. In summary, those documents say:
- XCEL 4G panels use an analogue voice channel to send Contact ID. After the 3G shutdown, Ness says the panel will no longer be able to report using Contact ID, because CID continues to use the 3G voice path even when the device is "on 4G". Current product pages also warn that analogue-to-digital conversion on VoIP can distort CID tones, and that CID is not recommended.
- If you only use SMS self-monitoring (no back-to-base), Ness says you are not affected.
- If you already report by ArmorIP, Ness says you are not affected.
- If you still report CID to a central station, Ness says you must reprogram the panel to ArmorIP, after talking to the monitoring company (they supply the ArmorIP IP address or URL, port, and account number). Programming can be done on the keypad or by SMS. The briefing's installer checklist includes firmware V11.5 or later, an active SIM, and a test call to the centre's procedure.
- ArmorIP is described as using the same familiar message content as Contact ID, carried as IP on the 4G data network. P86E 3E enables it on XCEL; P170E (and optional P171E) hold the address and port.
Ness's ArmorIP briefing lists a short, non-endorsed sample of ASIAL-graded rooms known to support ArmorIP. It is not a recommended shortlist, and it is from July 2024 — ask your existing centre, or a centre you actually intend to contract, whether they will take ArmorIP or CSV-IP from your exact communicator.
5. What to choose, in practice
- Occupier remote arm/disarm and status on a current DPlus, late D8x/D16x or XCEL: Mezzo + Ness-Bridge Plus is the path Ness is selling now. Budget for the published Plus subscription if you want notifications and history, and confirm the live price.
- Local automation (Home Assistant): IP232 + ness_alarm, on a trusted LAN, no port forward — see the Home Assistant thread. This does not replace monitoring.
- A monitored site: agree the protocol with the centre first. On XCEL 4G, treat ArmorIP as the supported IP format and treat remaining CID-over-4G-voice paths as something to retire. On DPlus or Bridge Plus, ask the centre about ArmorIP and/or CSV-IP. Keep a tested backup path if the contract requires one.
- Do not mix "the app works when I port-forward the IP232" with a security system. That is the opposite of what the IP232 manual says to do.
Ness-Bridge Plus (106-018) product page, including current Mezzo subscription wording
Ness-Bridge (106-014) product page
Ness-Bridge installation & operation manual Rev 1.6 (PDF)
Ness-Bridge Plus Gen2 manual (PDF)
Mezzo on Google Play
Mezzo on the App Store
Ness IP232 (101-244)
Ness IP232 installation manual (PDF)
iComms install manual (PDF)
aComms install & user manual (PDF)
Ness product notice: D8/D16XCEL 4G Contact ID / ArmorIP, Rev 1.1 (PDF)
Ness technical briefing: IP monitoring / ArmorIP, Rev 1.0 (PDF)
Ness D16XCEL 4G panel page (includes the current app notes and CID advisory)
Ness SIM activation
Ness contacts, including monitoring and SIM help
Just Smart Homes t=247: alarm IP reporting (SIA DC-09)
Just Smart Homes t=251: security licensing
This is not official Ness advice, not a monitoring contract, and not a claim that a particular communicator, app version or central-station receiver was tested together on a live site. Mezzo subscription wording and communicator stock change; the Contact ID advisory on XCEL 4G is a Ness notice you should read in the original. Confirm the current official pages and your monitoring company's requirements before you rely on any point in this thread. Researched from official documentation on 22 November 2026 (Australia/Sydney). Please correct anything that has moved on.