Integrating a Ness D8x/D16x with Home Assistant (IP232, ness_alarm and the limits)

Discuss Ness Alarm Systems, Including Smart Home Integrations
Post Reply
User avatar
ZerOne
Site Admin
Posts: 292
Joined: Sun Dec 13, 2020 8:21 am

What this thread is
A practical map of the official Home Assistant Ness Alarm (ness_alarm) integration for Ness D8x/D16x panels, using the panel's ASCII serial protocol and an IP232 serial-to-ethernet bridge. It is a companion to the welcome / panel identification thread in this forum.

It is not official Ness advice and not official Home Assistant support. I have not run this on a live panel. Confirm settings against the manual for your board and firmware, and against the current Home Assistant docs, before you change anything.

Complexity
Intermediate. Fitting an IP232 and enabling serial reporting is low-voltage work on the panel's serial header, but the system is still a security alarm. In Australia, paid installation, maintenance or programming of alarm equipment is licensed work — see who needs a licence. If the system is monitored, tell the monitoring company before you change programming or add a device to the serial port.

1. Safety first
  • The panel must keep working on its own if Home Assistant, the network, or the IP232 fails. A smart-home notification is not a monitoring centre, and it is not a substitute for a qualified back-to-base path. See also alarm IP reporting in 2026.
  • Anyone who can operate the alarm entity in Home Assistant can arm and disarm the system. Do not expose it to voice assistants, guest dashboards or a cloud-exposed instance without extra access control.
  • The official IP232 installation manual states that the IP232 does not support encryption or a secure network, and that the TCP port used for bridged connections should not be routed outside the local network. Put the bridge on a trusted IoT or security VLAN, give it a DHCP reservation or a static address, allow only Home Assistant to connect, and do not port-forward it. Use a VPN if you need remote access to Home Assistant itself.
  • Power the panel down, or have your installer do it, before you plug anything into the serial header. Use the correct Ness serial lead for that board (see section 3).
2. What Home Assistant officially supports
As at 22 November 2026, the Ness Alarm integration docs say:
  • It is for a Ness D8x/D16x alarm system.
  • Connectivity is through an IP232 module connected to the alarm.
  • The module communicates via the Ness D8x/D16x ASCII protocol.
  • You get a binary sensor for each configured zone, and an alarm control panel that reports status and can arm and disarm.
  • It is a local push integration (introduced in Home Assistant 0.85).
  • Actions include ness_alarm.aux (change an aux output) and ness_alarm.panic (trigger a panic alarm).
  • Zones are added in the UI after setup, as zone numbers 1–32, each with a device class.
  • An option, Infer arming state, works around a bug on some panels older than v5.8, which emit an empty status update when they are armed.
  • A further option can show or hide Arm home on the alarm panel card (on by default).
The integration does not program the panel. You still use a keypad or NessComms for programming. It does not claim support for Ness M1 Gold or SmartLiving — those are different platforms (see the identification thread).

3. DPlus and XCEL: likely the same protocol, not named in the HA docs
This is the main caution on model coverage.

The official Home Assistant page names only D8x/D16x. The Python library behind the integration, nessclient, describes itself as an implementation of the Ness D8x/D16x Serial Interface ASCII protocol, and its README also lists D8X_CEL_3G / D8X_CEL_4G, D16X_CEL_3G / D16X_CEL_4G, DPLUS8 and D32X.

Separately, Ness's own manuals say:
  • DPlus, XCEL and later D8x/D16x use a two-way RS232 port at 9600 baud, 8 data bits, no parity, 1 stop bit, with messages in ASCII. The DPlus manual (890-511 Rev 1.12) says the Ness serial protocol is available on request, and that P199E enables those serial outputs — the same option family used for D8x/D16x and for Ness-Bridge.
  • The official IP232 product page says the module includes leads "to connect directly into the Ness DPlus / D8X / D16X / D8XCEL / D16XCEL panels", and can also be used with a Ness-M1 serial port (that M1 path is not the ness_alarm integration).
So DPlus and XCEL 4G look like the same ASCII serial family, and the library authors list them. That is not the same as Home Assistant officially documenting those models. If you try it on DPlus or XCEL, treat it as untested against the HA docs: keep a keypad that still works, do not remove monitoring, and report what firmware you ran. I have not found a current Ness catalogue item called D32X; that name appears in the library list only, so treat it as unverified.

Community posts also report that a generic RS232-to-IP device which accepts a TCP connection (not only the Ness-branded 101-244) can work. That is community experience, not an official Home Assistant or Ness statement. If you use a third-party bridge, it still needs 9600 8N1 and a stable address, and it still must not be exposed to the internet.

4. Hardware and serial wiring
The official path in both the HA docs (which cite the iComms manual) and the Ness IP232 listing is:
  • Ness IP232, part 101-244 — an ethernet-to-RS232 bridge that acts as a network server (it accepts connections; it does not originate them). The IP232 manual's default TCP port is 2401. Factory default is DHCP; if no DHCP server is present it falls back to 192.168.0.251. Give it a static address or a DHCP reservation so Home Assistant is not chasing a changing IP.
  • The correct serial lead for the board: 450-185 (3-pin) for older D8x/D16x; 450-246 (4-pin) for DPlus, XCEL, and D8x/D16x V8 and later. The current 101-244 kit listing says it includes both. The iComms manual also references a "D8x-D16x SERIAL LEAD 3 WAY - PANEL TO DB9".
  • Set the IP232 baud rate to 9600, matching the panel. The iComms manual says to use at least version 1.1.0 of the IP232 Config Utility, from the Ness download page, to find the device on the LAN and send settings.
Ness-Bridge / Ness-Bridge Plus is a different ethernet product. It is the official path for the Mezzo app, not the path documented for ness_alarm. Do not assume one brick can do both jobs at once. The IP232 manual also says the bridge can accept multiple TCP connections and that data from any of them is sent to the single serial port — if Home Assistant and another client (iComms, aComms, NessComms, a second integration) share that port, the ASCII stream can be interleaved. Prefer one client on the IP232 while you commission it.

5. Panel programming the integration needs
The HA docs, following the iComms manual, say that serial control on a D8x/D16x is enabled at P199E, with options 1E to 6E ON:
  • 1E Send Address
  • 2E Send Time Stamp
  • 3E Send Alarms (zone alarms and area open/close)
  • 4E Send Warnings
  • 5E Send Access Events
  • 6E Send Zone Seal State — D8x/D16x V6 and later only, and required if you want zone open/close (sealed/unsealed) updates
If P199E is left at the factory default (those options off), the integration will not see events. Enabling these options is installer-level programming. On a D-series panel that is entered from a disarmed state: P + master code + E (user program mode, PROG on), then P + installer code + E (installer program mode, PROG flashing), then P199E and the options, then P + E to exit. The factory-default codes and the reasons you must change them are in the installer-basics thread; do not leave defaults on a live system.

The DPlus and XCEL manuals document the same P199E option set (DPlus also has 7E, "Send test ASCII data", which the HA docs do not require).

6. Adding it in Home Assistant
  • Settings → Devices & services → Add Integration → Ness Alarm.
  • Host: the IP address or hostname of the IP232.
  • Port: the TCP port the IP232 is listening on (2401 if you left the default).
  • Enable Infer arming state if the panel firmware is older than v5.8 and the armed state looks wrong.
  • Then Configure → Add zone for each zone number you actually use (1–32), with an appropriate device class.
Older examples used a configuration.yaml block; current docs describe UI setup. Follow the current page, not a 2019 screenshot.

7. Limits to be clear about
  • Official HA documentation names D8x/D16x only. DPlus and XCEL are protocol-family cousins, not a documented HA support statement.
  • M1 Gold and SmartLiving are out of scope for this integration.
  • The integration cannot program the panel, cannot replace a keypad, and cannot replace a central-station communicator.
  • Home Assistant zone items are numbered 1–32, which matches the D-series zone map, including DPlus wireless zones that share those numbers. Label them to match the panel, not to match a wish list of 64 separate zone IDs.
  • Two-area partitioning is a D-series panel feature. The official HA page describes an alarm control panel — I have not seen a documented, supported mapping for two independent HA alarm panels on one Ness. Treat multi-area behaviour as unverified.
  • ness_alarm.panic triggers a panic alarm. Only add it to a dashboard if you actually want that control, and know who can press it.
  • Aux output control from apps on older D8x/D16x needed PCB version 7.8 or later (iComms manual). Confirm your firmware before you rely on ness_alarm.aux.
Official starting points
Home Assistant: Ness Alarm integration
nessclient library (ASCII protocol client used by the integration)
Ness IP232 module (101-244)
Ness IP232 installation manual (PDF)
Ness iComms install manual (PDF) — source of the P199E and IP232 setup steps cited by HA
Ness DPlus installer manual, 890-511 Rev 1.12 (PDF) — serial port and P199E
Home Assistant community thread: Ness DX8/DX16 alarm
Just Smart Homes t=251: security licensing
Just Smart Homes t=247: alarm IP reporting

This is not official Ness or Home Assistant advice, and it is not a claim that a particular panel, firmware and IP232 combination was assembled and tested on a live site. The official HA documentation names D8x/D16x; DPlus and XCEL compatibility is inferred from Ness serial documentation and the nessclient model list, and should be confirmed before you rely on it. Researched from official documentation on 22 November 2026 (Australia/Sydney). Please correct anything that has moved on.
Post Reply

Return to “Ness Alarm System Discussion”