PAI cannot find the config file
PAI cannot find the config file
PAI searches for a configuration file in the following order:Fix: Create The Docker image sets
- Path passed via the
--configCLI argument - Path in the
PAI_CONFIG_FILEenvironment variable - The following locations, in order, for each of
pai.conf,pai.json, andpai.yaml:- Current working directory
~/.local/etc//etc/pai//usr/local/etc/pai/
/etc/pai/pai.conf (copy from config/pai.conf.example), or set the PAI_CONFIG_FILE environment variable to your config file’s absolute path.When running in Docker, mount your config directory:PAI_CONFIG_FILE=/etc/pai/pai.conf by default.Cannot connect to serial port
Cannot connect to serial port
Check the port pathThe default in Update your config to match:Check permissionsThe user running PAI must be in the Log out and back in for the group change to take effect. When running Docker, pass the device through:Verify the baud rateThe baud rate must match your panel type:
Raspberry Pi GPIO serial portParadox panels use TTL 5V logic. Connecting a 3.3 V GPIO pin directly to the panel will damage the Raspberry Pi or cause unreliable communication. Use a level shifter between the panel’s serial port and the Pi’s GPIO.
pai.conf is /dev/ttyS1. USB serial adapters (CP2102, PL2303, CH340) typically appear as /dev/ttyUSB0. Verify the device exists:pai.conf
dialout group to access serial ports:| Panel | Baud rate |
|---|---|
| SP / MG (Spectra, Magellan) | 9600 |
| EVO (default) | 38400 |
| EVO (alternate) | 57600 |
pai.conf
Cannot connect to IP150
Cannot connect to IP150
Check host and portVerify the IP150 is reachable from the PAI host:Check the module passwordThe default IP module password is Firmware version mattersPAI supports direct connection to IP150 when the module firmware is below 4.0 or at 4.40.004 and above. Firmware versions between 4.0 and 4.40.004 require connecting through the Paradox SWAN cloud service via
pai.conf
paradox. If you changed it in the IP150 configuration, update:pai.conf
IP_CONNECTION_SITEID and IP_CONNECTION_EMAIL.MQTT not receiving messages
MQTT not receiving messages
Verify MQTT is enabledMQTT is disabled by default. Check your config:Check host and portVerify the broker is runningAuthenticationIf your broker requires credentials, set them in the config:Both default to
pai.conf
pai.conf
pai.conf
None (no authentication).Verify the base topicPAI publishes to paradox/# by default (MQTT_BASE_TOPIC = 'paradox'). Subscribe to the wildcard to see all messages:Events not triggering notifications
Events not triggering notifications
Check the interface is enabledEach interface is disabled by default:Review event filter settingsThe default tag filters for most interfaces are:If the event you expect does not carry all the tags in at least one filter entry, it will be silently dropped. Enable Lower the level temporarily to
pai.conf
pai.conf
LOGGING_DUMP_EVENTS = True to log every event and its tags, then cross-check against your filter.Check MIN_EVENT_LEVELEvents below the configured level are dropped before the filters run:pai.conf
DEBUG to confirm events are reaching the interface.Enable debug logging
Enable debug logging
Set the console log level to For deeper diagnostics, enable one or more dump flags:To write logs to a file, set:
DEBUG in your config:pai.conf
pai.conf
pai.conf
EVO panel not communicating after firmware upgrade
EVO panel not communicating after firmware upgrade
EVO firmware version 7.50.000 and above introduced serial communication encryption. PAI cannot decrypt this communication, so the serial connection stops working after upgrading to an affected firmware.Options if you have already upgraded:
- Purchase a Paradox unlock code. Paradox sells a code that re-enables the unencrypted serial port. Contact your Paradox dealer.
- Use an IP150 module. The IP150 connection is not affected by serial encryption. Switch
CONNECTION_TYPEtoIPand configure the module.
pai.conf