Ness Alarm
ness_alarm
The Ness Alarm integration allows Home Assistant users who own a Ness D8x/D16x alarm system to leverage their alarm system and its sensors to provide Home Assistant with information about their homes. Connectivity between Home Assistant and the alarm is accomplished through an IP232 module that must be connected to the alarm.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
alarm_control_panel | Security system | |
binary_sensor | Sensor (motion) |
1 report below say how a device from this integration behaves in the Home app.
What people report
Ness D8x/D16x panels work over IP, but the hard-coded 5 s scan interval in 2026 overloaded the panel; reset to 60 s.
- Works2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Ness D16x alarm panel | Works Local | Arm/disarm commands lost with 5 s polling; default restored to 60 sSaved copyThe problem ### The problem Since the Ness Alarm integration was moved to the UI, `DEFAULT_SCAN_INTERVAL` in `const.py` is hard-coded to 5 seconds, and there is no longer any option to change it (the old YAML `scan_interval` is gone). Each cycle sends four status requests (S00, S20, S14, S18). The D8x/D16x panel answers roughly one request every 1.6 seconds, so requests pile up faster than they are answered. After a few minutes, arm and disarm commands are written to the interface but never acted on by the panel. Reloading the integration clears the backlog temporarily, then the problem … Excerpt saved from GitHub on 2026-10-23. | Issue #183080 · 2026-09 | |
| Ness security panel | Works | Partly in Home Alarm panel not exported after restart until bridge reload | Fixed after report (unavailable state handling)Saved copyThe problem I am using the Ness integration which provides an alarm control panel (interface to a Ness security panel) which is then exported via a HomeKit bridge. However, the error below is observed and the control panel does not get correctly exported whereas it did work fine previously. The alarm control panel works fine within Home Assistant itself. It's unclear to me if the issue is within the HomeKit or Ness integration. [code] ### What version of Home Assistant Core has the issue? core-2024.12.0.dev202411040232 ### What was the last working version of Home Assistant Core? _No … Excerpt saved from GitHub on 2026-10-23. | Issue #129867 · 2024-11 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Details
| Installs (analytics) | 48 (0.01%) |
|---|---|
| Quality scale | Legacy |
| Added in | Home Assistant 0.85 |
| Set up in the UI | Yes |
| Maintainers | @nickw444, @poshy163 |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
