Connection methods
Currently we allow next connection methods:
All wire connections you do at your own risk. It is very easy to burn your board if you plug something wrong.
Panel's serial port should be vacant to use this method.
For serial connection you will need a USB-TTL module or a level shifter if you want to connect to RPI directly. Do not power you RPI from the Serial's AUX+.
┌───────┐
│ Rx ┌╵
│ Tx │
│ GND │
│ AUX+ └╷
└───────┘
If you want a pretty connection then you can buy some of these (a clamper tool required):
Do not connect AUX+. It is 12V.
RX/TX are 5V.
For serial connection usually you will need to use TX/RX/GND. If you use optocouplers, probably TX/RX will be sufficient.
# Connection Type
CONNECTION_TYPE: Serial # Serial or IP
# Serial Connection Details
SERIAL_PORT: '/dev/ttyS1' # Pathname of the Serial Port
SERIAL_BAUD: 9600 # 9600 for SP/MG. For EVO: Use 38400(default setting) or 57600EVO192 supports 38400(default setting for panel) or 57600. See panel's manual how to select a faster speed. This is main performance bottleneck, we do not want to fly slow :).
Got this log line?
PAI.paradox.paradox - Failed to connect: Panel did not replied to InitiateCommunication
It is possible that you have baud rate mismatch between PAI config and Panel settings.
Your Hass.io instance Supervisor -> System -> Host system -> Hardware button -> serial block
PAI can communicate with the panel using IP100, IP150, IP150+, IP150S connection locally or via Paradox Cloud(SWAN).
SWAN connection is possible but is not recommended. Do not abuse it with PAI or Paradox can become angry some day.
Connection process is reverse engineered from Babyware connection process. Unfortunately no public documentation available about this process.
Firmwares supported:
- version < 4.x - Local connection
- 4.x <= version < 4.40.004 - Only SWAN (Paradox cloud) connection. Consider updating your IP150 module's firmware to use local connection.
- version >= 4.40.004 - Local connection, SWAN (Paradox cloud) connection
It is recommended to configure your panel to highest possible baud rate for better performance. See your panel's user manual for available settings.
For IP150 firmware versions: < 4.x and >= 4.40.004
WARNING: When PAI will be connected to your IP150 module you will not be able to use Insite Gold. Only one connection at a time is supported by IP150 modules. There are some exceptions from this rule but details are unknown.
# Connection Type
CONNECTION_TYPE: IP # Serial or IP
# IP Connection Details
IP_CONNECTION_HOST: '192.168.1.10' # IP Module address when using direct IP Connection
IP_CONNECTION_PORT: 10000 # IP Module port when using direct IP Connection
IP_CONNECTION_PASSWORD: paradox # IP Module password. "paradox" is factory default.Make sure IP_CONNECTION_SITEID and IP_CONNECTION_EMAIL is NOT set. Otherwise PAI will work via Cloud (SWAN)
Notice: It was reported that IP module will start rebooting periodically if you fully disable all outbound connections for it.
One of the options how to disable all outbound connections:
- Log in to the web interface and disable SWAN.
- Set your IP150 to a static IP and set gateway to 0.0.0.0
This is to disable any future automatic updates as IP150 checks for updates on boot and updates itself. Once you get a stable connection you do not need new firmware versions.
If you want to install new firmware check Compatibility page to make sure latest version works with PAI.
For IP150 firmware versions: > 4.x
Reason for (not recommended):
- https://github.com/CriticalSecurity/paradox
- Periodic dropouts/restarts
- Possible banning (PAI keeps connection 24/7/365)
- Hard to debug reconnection problems
# Connection Type
CONNECTION_TYPE: IP. # Serial or IP
IP_CONNECTION_SITEID: '<siteid>'. # SITE ID. IF defined, connection will be made through this method.
IP_CONNECTION_EMAIL: '[email protected]' # Email registered in the site
IP_CONNECTION_PANEL_SERIAL: # Use a specific panel. Set it to empty to use the firstIP_CONNECTION_HOST and IP_CONNECTION_PORT will be ignored.
You can damage your hardware if you are not careful, aka the usual disclaimer.
I have tested a few MCU's and have found the ESP32 DOit Wrooom32 DEVKITv1 Very Reliable due to the hardware Serial Port. I do not use protection on mine, but if you feel like you want to OPTO isolate or use logic level converters you should and it most likely recommended. Mine works fine for the TX and RX with no issues. My Wemos D1 Mini that I ran without protection only worked for a while, I think it's mainly due to the the 5v connecting directly to the header. (if you "need" ethernet you can investigate a MCU with ethernet) I personally took on this for my Alarm as Lightning damaged my IP150 several times, and with Wireless and a single source of power I sleep easier.
- You will need basic electronic skills and an understanding of the Arduino Framework.
I will update the design in more detail if needed
Equipment Used
*ESP32
*LM2956 Breakout board (set to 5.0V )
*USB Cable for ESP32 (that can be cut) [to connect between Lm and ESP]
*Pin connector XH2.54 (4-Pin PWM Fan Female Connector (White)) [to connect to panel]
*Connection for pinout below (I modified my existing IP150 Cable)
The Pinout is as per the serial pinout above
Serial on Panel LM2956 ESP32
┌───────┐
│ Rx ┌╵ == > == > == > == > == > == > TX2
│ Tx │ == > == > == > == > == > == > RX2
│ GND │ == > IN(-) -> OUT(-) == > USB GND
│ AUX+ └╷ == > IN(+) -> OUT(+) == > USB 5V
└───────┘
The LM needs to be set to 5v before connecting the Node the USB cable needs to be connected to the 5v output and then to the ESP32 to power the ESP
- It is possible to connect the 5v directly to pin GND and 5v but this bypasses the protection afforded by the USB
You can follow the instructions edit and load the following: https://github.com/espressif/arduino-esp32/blob/master/libraries/WiFi/examples/WiFiTelnetToSerial/WiFiTelnetToSerial.ino once done and available on your network you can connect it to your wifi and test it/locate the IP.
Updated code: https://github.com/cybertza/PAI-ESP32
- added ESPhome example as well (its not tested with pannel, but on the bench it works, it then leverages off the ESPHome stack to keep the device alive, can also add a relay to add to an Panic input if you wanted to do something to that effect).
The following settings needs to be set in your config
# Connection Type
CONNECTION_TYPE: IP # Serial or IP
# IP Connection Details
IP_CONNECTION_HOST: '192.168.1.10' # Address of the ESP32
IP_CONNECTION_PORT: 23 # Port of the ESP32
IP_CONNECTION_PASSWORD: 'paradox' # IP Module password. "paradox" is factory default.
IP_CONNECTION_BARE: true # Used this for base Serial over TCP tunnelsThe following settings needs to be set in your config
# Connection Type
CONNECTION_TYPE = IP # Serial or IP
# IP Connection Details
IP_CONNECTION_HOST = '192.168.1.10' # Address of the ESP32
IP_CONNECTION_PORT = 23 # Port of the ESP32
IP_CONNECTION_PASSWORD = 'paradox' # IP Module password. "paradox" is factory default.
IP_CONNECTION_BARE = True # Used this for base Serial over TCP tunnels
**And on any other command you try to activate then use "=" instead of ":" for example **
LOGGING_LEVEL_CONSOLE = 20
LOGGING_LEVEL_FILE = 40
CONNECTION_TYPE = IP # Serial or IP
# IP Connection Details
IP_CONNECTION_HOST = '192.168.1.10' # Address of the ESP32
IP_CONNECTION_PORT = 23 # Port of the ESP32
IP_CONNECTION_PASSWORD = 'paradox' # IP Module password. "paradox" is factory default.
IP_CONNECTION_BARE = True # Used this for base Serial over TCP tunnels
PASSWORD = '0000' # default password, if you are using any other password please change it here
MQTT_ENABLE = True # Activate the MQTT
MQTT_HOST = '192.168.1.xxx' # MQTT server ip
MQTT_PORT = 1883 # MQTT server port
MQTT_USERNAME = 'user' # MQTT server user
MQTT_PASSWORD = 'pass' # MQTT server pass
MQTT_BASE_TOPIC = 'paradox'
MQTT_KEEPALIVE = 60
KEEP_ALIVE_INTERVAL = 10
Create a folder on docker, pai then inside on pai create a folder config and there add the pai.conf
and the code for this (Don't forget to change SSID and Password and IP and subnet and gateway)
Credits to @CyberTza
Some more info in this ticket: https://github.com/ParadoxAlarmInterface/pai/issues/198#issuecomment-771388699