ParadoxAlarmInterface / pai

Paradox Magellan, Spectra and EVO, with MQTT, Signal, Pushbullet, Pushover and others
https://gitter.im/paradox-alarm-interface
Eclipse Public License 2.0
347 stars 92 forks source link

intermitted connection issue, PAI to SP6000 #261

Closed n00bster-za closed 3 years ago

n00bster-za commented 3 years ago

Hi peeps. Only recently started with HA have been reading non stop for the past week.

I have my SP6000 working with PAI. Very basic setup at the moment. I was trying to setup some Notifications to my HA app on android. Managed to get 1 Automation working but now I keep getting the Disarmed notification that I created and it seems like it is linked to the connection interruption between PAI and IP150.

The notification comes up each time the connection gets restored. I need help to make sure my PAI config is correct and that my alert automation is correct. I noticed a Keep_alive value at 10 is this the amount of minutes PAI will keep the connection going?

PAI config

LOGGING_LEVEL_CONSOLE: 20
LOGGING_LEVEL_FILE: 40
CONNECTION_TYPE: IP
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 9600
IP_CONNECTION_HOST: 192.168.1.6
IP_CONNECTION_PORT: 10000
IP_CONNECTION_PASSWORD: paradox
KEEP_ALIVE_INTERVAL: 10
LIMITS:
  zone: auto
  user: 1-10
  door: ''
  pgm: 1-5
  partition: auto
  module: ''
  repeater: ''
  keypad: ''
  key-switch: ''
SYNC_TIME: true
SYNC_TIME_MIN_DRIFT: 120
PASSWORD: ''
MQTT_ENABLE: true
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_KEEPALIVE: 60
MQTT_USERNAME: pai
MQTT_PASSWORD: Parad0x
MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true
COMMAND_ALIAS:
  arm: partition all arm
  disarm: partition all disarm
MQTT_COMMAND_ALIAS:
  armed_home: arm_stay
  armed_night: arm_sleep
  armed_away: arm
  disarmed: disarm
HOMEASSISTANT_NOTIFICATIONS_EVENT_FILTERS:
  - live,alarm,-restore
  - live,trouble,-clock
  - live,tamper
PUSHBULLET_CONTACTS: []
PUSHBULLET_EVENT_FILTERS:
  - live,alarm,-restore
  - live,trouble,-clock
  - live,tamper
PUSHOVER_EVENT_FILTERS:
  - live,alarm,-restore
  - live,trouble,-clock
  - live,tamper
PUSHOVER_BROADCAST_KEYS: []
SIGNAL_CONTACTS: []
SIGNAL_EVENT_FILTERS:
  - live,alarm,-restore
  - live,trouble,-clock
  - live,tamper
GSM_CONTACTS: []
GSM_EVENT_FILTERS:
  - live,alarm,-restore
  - live,trouble,-clock
  - live,tamper
IP_INTERFACE_ENABLE: false
IP_INTERFACE_PASSWORD: paradox
DUMMY_EVENT_FILTERS: []

Automation alert config - This is the only alert config that works from about a dozen tried. even if I duplicate this one and try and turn it into a "Armed" alert it does not want to save.

alias: House Alarm Disarmed
description: ''
trigger:
  - platform: device
    device_id: 86db92e3d7c1e39bf527a88b8a92ec17
    domain: alarm_control_panel
    entity_id: alarm_control_panel.house
    type: disarmed
condition: []
action:
  - service: notify.mobile_app_s20_ultra
    data:
      message: Alarm System Disarmed at {{ now().strftime('%H:%M %A %d %B %Y') }}
      title: HA Alarm System
mode: single
yozik04 commented 3 years ago

PAI resends all mqtt topics on restart. If you tell it disconnects from time to time so most probably it restarts and resends all. HA probably thinks it is a new state and resends notification. Try to use state change as a trigger instead of device event in your automation. Make sure you specify From state as well.

Jevgeni

27 авг. 2021 г., в 16:36, n00bster-za @.***> написал(а):

 Hi peeps. Only recently started with HA have been reading non stop for the past week.

I have my SP6000 working with PAI. Very basic setup at the moment. I was trying to setup some Notifications to my HA app on android. Managed to get 1 Automation working but now I keep getting the Disarmed notification that I created and it seems like it is linked to the connection interruption between PAI and IP150.

The notification comes up each time the connection gets restored. I need help to make sure my PAI config is correct and that my alert automation is correct. I noticed a Keep_alive value at 10 is this the amount of minutes PAI will keep the connection going?

PAI config

LOGGING_LEVEL_CONSOLE: 20 LOGGING_LEVEL_FILE: 40 CONNECTION_TYPE: IP SERIAL_PORT: /dev/ttyUSB0 SERIAL_BAUD: 9600 IP_CONNECTION_HOST: 192.168.1.6 IP_CONNECTION_PORT: 10000 IP_CONNECTION_PASSWORD: paradox KEEP_ALIVE_INTERVAL: 10 LIMITS: zone: auto user: 1-10 door: '' pgm: 1-5 partition: auto module: '' repeater: '' keypad: '' key-switch: '' SYNC_TIME: true SYNC_TIME_MIN_DRIFT: 120 PASSWORD: '' MQTT_ENABLE: true MQTT_HOST: core-mosquitto MQTT_PORT: 1883 MQTT_KEEPALIVE: 60 MQTT_USERNAME: pai MQTT_PASSWORD: Parad0x MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true COMMAND_ALIAS: arm: partition all arm disarm: partition all disarm MQTT_COMMAND_ALIAS: armed_home: arm_stay armed_night: arm_sleep armed_away: arm disarmed: disarm HOMEASSISTANT_NOTIFICATIONS_EVENT_FILTERS:

  • live,alarm,-restore
  • live,trouble,-clock
  • live,tamper PUSHBULLET_CONTACTS: [] PUSHBULLET_EVENT_FILTERS:
  • live,alarm,-restore
  • live,trouble,-clock
  • live,tamper PUSHOVER_EVENT_FILTERS:
  • live,alarm,-restore
  • live,trouble,-clock
  • live,tamper PUSHOVER_BROADCAST_KEYS: [] SIGNAL_CONTACTS: [] SIGNAL_EVENT_FILTERS:
  • live,alarm,-restore
  • live,trouble,-clock
  • live,tamper GSM_CONTACTS: [] GSM_EVENT_FILTERS:
  • live,alarm,-restore
  • live,trouble,-clock
  • live,tamper IP_INTERFACE_ENABLE: false IP_INTERFACE_PASSWORD: paradox DUMMY_EVENT_FILTERS: [] Automation alert config - This is the only alert config that works from about a dozen tried. even if I duplicate this one and try and turn it into a "Armed" alert it does not want to save.

alias: House Alarm Disarmed description: '' trigger:

  • platform: device device_id: 86db92e3d7c1e39bf527a88b8a92ec17 domain: alarm_control_panel entity_id: alarm_control_panel.house type: disarmed condition: [] action:
  • service: notify.mobile_app_s20_ultra data: message: Alarm System Disarmed at {{ now().strftime('%H:%M %A %d %B %Y') }} title: HA Alarm System mode: single — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
n00bster-za commented 3 years ago

yes this is what I thought as well. in the IP150 event log it says the cable unplugged then it restores again. The it says SWAN supervision lost. This I think is because I removed the Default Gateway from the IP config. is there anything else that can cause this disconnect other then physical cable issue? Can HA be asking sending to much info to the IP150 then it stops the connection?

yozik04 commented 3 years ago

SWAN uses paradox cloud they can drop connection periodically. At least I would do that for sure.

n00bster-za commented 3 years ago

I have already done it that is why the error comes up. Can you help me with a notification setup to show time and then person that activated it .The config above was copied. I have created a STATE change alert but not sure how to add the person and date.

alias: Home Armed
description: ''
trigger:
  - platform: state
    entity_id: alarm_control_panel.house
    from: disarmed
    to: armed_night
condition: []
action:
  - service: notify.mobile_app_s20_ultra
    data:
      title: House Armed
      message: "\_"
mode: single
n00bster-za commented 3 years ago

after updating to latest IP150 firmware the connection issues are gone. Version 5.2