Search results

PAI wiki - MQTT interface

Get your DuckDNS token for your domain. Add the DuckDNS add-on Configure DuckDNS add-on: lets_encrypt: accept_terms: true certfile: fullchain.pem keyfile: privkey.pem token: <your-token> domains: - <your-domain-name>.duckdns.org aliases: [] seconds: 300 It will automatically get a Lets...

The on/off (bypass) you can accomplish by adding the below to your configuration.yaml switch: - platform: mqtt name: "<zone>> Bypass" command_topic: "paradox/control/zones/<zone_name>>" state_topic: "paradox/states/zones/<zone_name>/bypassed" qos: 0 optimistic: true...

You can probably accomplish this by creating custom cards for HA/Lovelace.

Panel Firmware version 7.11 IP module Firmware version 4.40.04 IP boot 2.14

Can log in/view/control via Insite Gold while my HA is running PAI. Got both screens up at the same time.

The PC Password would be the setting: PASSWORD: '0000' Can you connect to your panel via Babyware with the above password?

My zones all appear as switches switch.<zone/sensor_name> and to bypass I would use service turn_on/turn_off or set state on/off Partitions appear as alarm_control_panel.<partition_name> and set state to armed or disarmed. MQTT commands I used to use with my Python scripts were something...

Didn't have to add anything to my config - HA picked everything up automagically. Not very clued up on PAI internals, but from the logs you have supplied it seems PAI can't authenticate to your alarm panel?

For my main alarm control, I have a set of Lovelace cards in one view. A drop-down with a list of pre-defined options that will bypass and arm/disarm certain zones and partitions depending on the selection (driven by a couple of Node-RED flows that also manages the alarm based on...

My setting for that is : MQTT_HOST: core-mosquitto

If you connect via IP150, all you really need to configure is - seems like you left out connection type CONNECTION_TYPE: IP IP_CONNECTION_HOST: <ip150_ip_address> IP_CONNECTION_PORT: Mip150_port> MQTT_ENABLE: true MQTT_USERNAME: <mqtt_uid> MQTT_PASSWORD: <mqtt_password> MQTT_RETAIN: true...

Controlled my IDS X64 via MQTT previously - major problem I had was that it was not local to the alarm - you had to go via the IDS servers, and their servers were more down than up. So essentially they controlled your alarm and you merely requested them to action something on your behalf.

I control my alarm outside the network via Home Assistant or Insight - PAI allows Insight to connect even though PAI is running. So Home Assistant via SSL or I VPN into my home network. Everything I need to do I now do via Home Assistant. Haven't had to use Insight for a while (still have it...

I switched to the EVO 192. 8 partitions and 192 zones.

You can manage your Paradox alarm via PAI from within Home Assistant. This will then allow you to toggle lights, automations, etc. based on zone and partition status.

Done

I got rid of the IDS system - too many issues and excuses/promises from them. The HYYP wasn't a paid service (at that time) or the costs were integrated into my armed response - either way, I didn't see a billable specific to making use of the phone app or their API.

No. But all moot now, as I am a happy Paradox user and have had zero issues so far.

Done