Ness DX8/DX16 Alarm

aumatt · July 9, 2022, 5:34am

Anyone updated to 2022.7.2? Im currently on 2022.6.7 and the NESS addon works fine, updated to 2022.7.2 and it is broken. I rolled back to 2022.6.7 and all is functional again. I didnt note down the errors in the logs but I think it might have to do with the update to Python

Matt

OzGav · July 9, 2022, 5:54am

Yes I have. Here are the errors:

2022-07-09 12:21:57 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved

Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/nessclient/client.py", line 158, in keepalive
await asyncio.gather(
File "/usr/local/lib/python3.10/site-packages/nessclient/client.py", line 116, in _recv_loop
await self._connect()
File "/usr/local/lib/python3.10/site-packages/nessclient/client.py", line 92, in _connect
await self._connection.connect()
File "/usr/local/lib/python3.10/site-packages/nessclient/connection.py", line 52, in connect
self._reader, self._writer = await asyncio.open_connection(
File "/usr/local/lib/python3.10/asyncio/streams.py", line 47, in open_connection
transport, _ = await loop.create_connection(
TypeError: BaseEventLoop.create_connection() got an unexpected keyword argument 'loop'

2022-07-09 12:21:57 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved

Traceback (most recent call last):

File "/usr/local/lib/python3.10/site-packages/nessclient/client.py", line 76, in update
await asyncio.gather(
File "/usr/local/lib/python3.10/site-packages/nessclient/client.py", line 109, in send_command
await self._connect()
File "/usr/local/lib/python3.10/site-packages/nessclient/client.py", line 92, in _connect
await self._connection.connect()
File "/usr/local/lib/python3.10/site-packages/nessclient/connection.py", line 52, in connect
self._reader, self._writer = await asyncio.open_connection(
File "/usr/local/lib/python3.10/asyncio/streams.py", line 47, in open_connection
transport, _ = await loop.create_connection(
TypeError: BaseEventLoop.create_connection() got an unexpected keyword argument 'loop'

flatstrap · July 12, 2022, 2:00am

Hi, I have the same issue with Ness DX16 not working after updating the core, I tried 2022.7.2 and the latest 2022.7.3 and the issue still persists. I’ve rolled back to 2022.6.7 and it’s working fine.
Unfortunately I’m heading away for a couple of weeks so I won’t be able to help with fixes/testing.
Cheers Flatstrap

OzGav · July 12, 2022, 3:04am

I believe I know what the problem is but I don’t know where the libraries are installed now. They used to be in /config/deps/lib/python3.x But I am thinking I might need to SSH into the OS now…?

nickw444 · July 12, 2022, 5:46pm

Hey all, can see there’s an issue in the latest release. I’m currently overseas so won’t have access to debug this myself until early August. If anyone does find the root cause, and can provide code change to fix the issue and can confirm the fix themselves, I can push a new release as necessary to nessclient or make changes to Home Assistant core to support.

OzGav · July 12, 2022, 6:58pm

As soon as I find where the library is now I will!!

OzGav · July 14, 2022, 11:20am

OK PR submitted https://github.com/nickw444/nessclient/pull/43

For those wanting to fix it now you should have a nessclient directory under /config/deps/lib/python3.x/site-packages Copy the python3.x directory and name it python3.10. Then go into site-packages/nessclient directory and edit connection.py Remove the line (about line 56) loop=self._loop,. Reboot and test.

nickw444 · July 16, 2022, 8:33am

I’ve raised a PR to core with a fix if anyone is game on testing it: https://github.com/home-assistant/core/pull/75298

nickw444 · July 22, 2022, 6:03pm

Hi all, the latest release (2022.7.6) includes the code to fix this bug.

aumatt · July 22, 2022, 10:23pm

Thanks Nick, installed yesterday and can confirm it works great.

matt2468 · July 23, 2022, 1:23am

Yeah can also confirm working on my side too thanks for the quick fix guys!

OzGav · September 13, 2022, 1:15am

Sharing my solution for a panel that won’t accept commands. I wanted to be able to arm and disarm the panel and trigger the alarm. After going through a few ideas on another forum I was pointed to this:

So if like me you have zone 8 spare then you can use this to achieve what i wanted. I constructed this:

I 3D printed a simple box with external dimensions of 94x54x29mm (I used 2mm wall thickness and also a 2mm thick lid made the total height 31mm) to house it and that fits perfectly to the left of the battery. Running ESPHOME on the D1 mini with this config:

esphome:
  name: ness-alarm-control-d1
  platform: ESP8266
  board: d1_mini

# Enable logging
logger:

# Enable Home Assistant API
api:

ota:
  password: "12345678901234567890123456789012"

wifi:
  ssid: "your_ssid"
  password: "your_password"

  manual_ip:
    static_ip: 192.168.1.97
    gateway: 192.168.1.254
    dns1: 192.168.1.206
    dns2: 192.168.1.165
    subnet: 255.255.255.0

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Ness-Alarm-Control-D1"
    password: "some_password"

captive_portal:

switch:
  - platform: gpio
    pin: D5
    id: momentary_keyswitch
  - platform: gpio
    pin: D7
    id: panic_button
  - platform: template
    name: "Ness Momentary Keyswitch"
    icon: "mdi:shield-key"
    turn_on_action:
    - switch.turn_on: momentary_keyswitch
    - delay: 1000ms
    - switch.turn_off: momentary_keyswitch
  - platform: template
    name: "Ness Panic Button"
    icon: "mdi:alarm-bell"
    turn_on_action:
    - switch.turn_on: panic_button
    - delay: 1000ms
    - switch.turn_off: panic_button
    
sensor:
  - platform: wifi_signal
    name: "Ness Alarm Control WiFi Signal Strength"
    update_interval: 60s

text_sensor:
  - platform: template
    name: "Ness Alarm Control Wifi Channel"
    lambda: |-
      std::string out;
      char buffer[64];
      sprintf(buffer, "%u", wifi_get_channel());
      out.append(buffer);
      return out;
    update_interval: 60s

I have two switches which I can use to dis/arm the panel and trigger the alarm. I am using ha-floorplan to build my own alarm control panel. This is where I am currently at (The disarmed on the left is the NESS panel and on the right is the HA automations):

StrickenAza34 · January 16, 2023, 1:56am

Hi all,

I’ve just set up HA Blue and want to integrate my NESS D8XD. Looking at the pics, everyone has been able to connect via serial, but, not sure if it’s because I have an RJ45 plug, my serial pins have a sort of cover over them to prevent a plug being inserted?

Images attached.

Can anyone point me in the right direction for Australian’s to be able to get this working?
I have an Ethernet plug to HA right next to the panel, so would prefer that, as the nearest PC is light years away.

Oh yeah, for anyone opening their box in the future…
THE ALARM BOX HAS A TAMPER SWITCH WHICH WILL SOUND THE SIREN!
Have someone ready to disarm the alarm, and don’t keep your head next to the siren.

aumatt · January 16, 2023, 2:50am

Get yourself one of these

Remove the cover from the serial port of your alarm board, plug the appropriate cable supplied with the above into it, then plug this into the IP232, connect this to your network and configure to suit.

Hope that helps

Matt

StrickenAza34 · January 16, 2023, 8:18am

Perfect, thank you!

I thought they were blocking it out for a reason, guess that reason was to stop me messing with it

kangaroosinaustria · February 18, 2023, 5:42am

I haven’t had an opportunity to have a good look at the serial output from the panel, but from reading through the ASCII protocol document, it seems as though the packets indicate which user has disarmed the panel.

Is there any possibility of expanding on this integration to report the user code that has disarmed to HA?

I imagine it could be an attribute that retains the last identified user code seen in a packet that includes the user code.

I’m good with serial comms but I wouldn’t know where to start with contributing code to HA.

The envisioned application is along the lines of implementing contractor codes, eg: provide a specific code to a cleaner, and when they use their code to disarm the panel, HA identifies the user code and can do things like open roller blinds and turn on lights, etc.

nickw444 · February 18, 2023, 12:23pm

The serial comms abstraction is handled by my client library “nessclient”.

The code for handling the area events is here:

github.com

nickw444/nessclient/blob/a6536a9dadb25dafb9be47a3213fb6d0ad21184b/nessclient/event.py#L83

    
      
              ENTRY_DELAY_START = 0x20
              ENTRY_DELAY_END = 0x21
              EXIT_DELAY_START = 0x22
              EXIT_DELAY_END = 0x23
              ARMED_AWAY = 0x24
              ARMED_HOME = 0x25
              ARMED_DAY = 0x26
              ARMED_NIGHT = 0x27
              ARMED_VACATION = 0x28
              ARMED_HIGHEST = 0x2e
              DISARMED = 0x2f
              ARMING_DELAYED = 0x30
          
          
    # Result Events
              OUTPUT_ON = 0x31
              OUTPUT_OFF = 0x32
          
          
def __init__(self, type: 'SystemStatusEvent.EventType', zone: int, area: int,
                       address: Optional[int], timestamp: Optional[datetime.datetime]) -> None:
              super(SystemStatusEvent, self).__init__(address=address, timestamp=timestamp)
              self.type = type

Currently it handles them in a generic way that doesn’t actually pull any additional information (like user ID) out of them, so some additional tweaks would first be required in the library to support it.

Once there is support, more work would need to be done in Home Assistant core to handle and provide that information to make use of it for automations, etc.

nickw444 · February 18, 2023, 12:25pm

Although looking further (sorry am on mobile), looks like the second part of the payload (user ID) might already be coerced into the “zone” field for the event class instance:

github.com

nickw444/nessclient/blob/a6536a9dadb25dafb9be47a3213fb6d0ad21184b/nessclient/event.py#L100

    
      
          def __init__(self, type: 'SystemStatusEvent.EventType', zone: int, area: int,
                       address: Optional[int], timestamp: Optional[datetime.datetime]) -> None:
              super(SystemStatusEvent, self).__init__(address=address, timestamp=timestamp)
              self.type = type
              self.zone = zone
              self.area = area
          
          
@classmethod
          def decode(cls, packet: Packet) -> 'SystemStatusEvent':
              event_type = int(packet.data[0:2], 16)
              zone = int(packet.data[2:4])
              area = int(packet.data[4:6], 16)
              return SystemStatusEvent(
                  type=SystemStatusEvent.EventType(event_type),
                  zone=zone,
                  area=area,
                  timestamp=packet.timestamp,
                  address=packet.address,
              )
          
          
def encode(self) -> Packet:

(Please forgive my lack of knowledge - I wrote this library 5 years ago and have rarely needed to make changes since then!)

geetron · March 1, 2023, 2:40am

Hi All,

Firstly, thank you to those involved in getting this to work, in particual Nick for writing the library. It was nice to find out I can somewhat make my dumb alarm smarter.

My question is, what is the method to see when the alarm is going off so that I can get HA to notify me? From looking at the library Nick wrote, it appears the library is aware of different events and the Ness integration page states it reports on alarm status. I just can’t figure out where to find the alarm status in the list of triggers when creating an automation via the UI.

e.g. I know how to create an automation where the trigger is a state, and it is for when a motion sensor that changes state, then the action is to send a notification.

Thanks,
Adrian

OzGav · March 1, 2023, 3:15am

Do you have the alarm_control_panel.alarm_panel entity? That shows the alarm state