I see that entity when I go to Settings > Devices & Services > Entities.
I think the issue is that, I wont be able to create an automation using the UI wizard e.g. Settings > Automations: Triggers, Conditions, Actions.
Looks like it all needs to be done via YAML.
EDIT: I was able to get this to trigger notifications. I have a new issue but not related to NESS.
- alias: 'NEWSend notification when alarm is Arming'
trigger:
- platform: state
entity_id:
- alarm_control_panel.alarm_panel
to: "arming"
action:
- service: notify.notify
data:
message: "ALARM! The alarm is arming {{ states('sensor.date_time') }}"
title: "Alarm is arming"
Does anyone know if there is a way with this integration to only arm specific zones in the house? I was going to use the Arm Home for this as we have our pet sometimes in one part of the house when out, however arming home has a known bug
Yeah I know about that way but I was hoping I could either fix it so that it properly says armed home or at the very least exclude certain sensors via an automation Iād love to try help but I dont even know where to begin
Can confirm the update has fixed up the home/away issues thanks again for all your work on this pluging we use it so much! Plus the sensors come in handy for the lighting automations.
I fixed this (along with a few other panic status related things) in my nessclient fork.
If you want to give it a try, download this directory and put it in your HA custom_components directory, restart and see if youāre still having the issue.
I didnāt submit a PR at the time since while these changes work for my panel version, I wasnāt sure if it would break for other peopleās.
Cheers for that, gave it a go but still canāt get the panic alarm happening. I think mine is a panel version 5.8. If you know of any other fixes or workarounds to try, that would be awesome!
Had to upgrade my D16 to the new DPlus and can confirm that the NESS component still works. Although there is a new network card available for it also now that utilises the serial port which seems interesting.
Hey @aumatt - Iām in a similar situation (existing D16 has crapped it - probably internal power supply related). Was it a swap of the main board, or ācompleteā new system? (Ballpark cost to if possible?)
Thx,
Chris
I got mine replacement from Home Security online, I bought the main board, L16 expander and a new Navigator Touch panel (old one not compatible) for $554aud delivered.
Had to return the original main board because it was defective but got a replacement the following week. Works great.
@nickw444 might have to update the integration to support 32 zones. I asked Ness for an updated doc and they wouldnt provide it and basically said the only difference is the support for 32 zones.
If the D16 boards are failing more than they should there may be a common reason thatās repairable.
If somebody has a dead board I can take a look at Iām happy to do that. Ageing does tend to effect power supply components before most else, and power supply parts are usually quite replaceable.
By nature though, an alarm PCB is the hub of a web of long unshielded cables, which are vulnerable to local lightning or RF events. That sort of damage is often not repairableā¦