Client ids must be unique for every device.
PAI <---> MQTT Broker <---> MQTT Dash
Both pai and MQTT Dash are clients to MQTT broker. They can have different credentials, but must not share same client ids. If you won’t specify client ids they should be auto generated.
I can not help you debug MQTT Dash because I never used it.
No worries Roland. Thanks for replying.
Thanks Jevgeni. I have now tried a different Client ID on MQTT dash but it is still not working.
I am only using MQTT dash as this is mentioned in the wiki so i thought this is the supported MQTT app on the phone.
What MQTT app do you use on the Android that works?
Just set this up, few teething problems but nothing I didn’t find either in this thread or the wiki. Great thanks.
One question, is it possible to increase the number of users that can access the panel, at the moment I need to stop the Pai add-on to use either babyware or web access. I’m on an evo192 with an ip150.
Hi Roland
I am trying a similar thing: did you ever resolve this issue you were having?
Thanks!
Pretty much yes, it was the way I had set up the MQTT switch in my config.
- platform: mqtt
name: "Front Beam Bypass"
command_topic: "paradox/control/zones/FRONT_BEAM"
state_topic: "paradox/states/zones/FRONT_BEAM/bypassed"
qos: 0
optimistic: true
state_on: "True"
state_off: "False"
payload_on: "bypass"
payload_off: "clear_bypass"
payload_available: "Online"
payload_not_available: "Offline"
This is what I am using currently.
Hello,
Am I the only one to not be able to start PAI Addon since Supervisor 249 upgrade (I think) ?
I got the following error when starting 
Attempting to load configuration from /data/options.json
Traceback (most recent call last):
File “/usr/local/bin/pai-service”, line 8, in
sys.exit(main())
File “/usr/local/lib/python3.7/site-packages/paradox/console_scripts/pai_run.py”, line 36, in main
main(args)
File “/usr/local/lib/python3.7/site-packages/paradox/main.py”, line 118, in main
cfg.load()
File “/usr/local/lib/python3.7/site-packages/paradox/config.py”, line 314, in load
with open(self.CONFIG_FILE_LOCATION) as f:
PermissionError: [Errno 13] Permission denied: ‘/data/options.json’
It has been working flawlessly for weeks.
I tried to reinstall PAI twice : same problem 
Also tried the beta version, same issue.
I don’t understand… I’ve tried everything : restore from 3 different HA snapshots, and then restore the 3 last backups from the past 3 days of the virtual machine hosting Home Assistant : still the same !
I’m 100% positive that PAI was working fine yesterday.
The alarm is OK, I’ve restarted it and I can connect fine from babyWare.
I’ve tested a few times to deinstall and reinstall PAI, use the default configuration without any change, start the addon and same error.
Any idea ?
Couple issues were created regarding that.
PAI version 2.2.3 solved the issue !
Thx
Well done 
Recently the number of entities created by the PAI add-on went over 500 for me. I see there is a “limits” configuration option and there is even some documentation on how to do it in the pai.conf file.
Example:
LIMITS = {
'zone': list(range(1, 18)) + list(range(30,33)) + [40], # Zones to monitor and control (1-17,30-32,40)
'user': range(1, 7), # Users to consider (1-6)
'door': [], # Doors to consider (none)
'pgm': range(1, 6), # Outputs to monitor and control (1-5)
'partition': [1,2,4,7,8], # Partitions to monitor and control (1,2,4,7,8)
'bus-module': [], # Buses to monitor (none)
'key-switch': [] (none)
}
I’m using the config interface from the add-on (configuration tab) that offers settings in this format:
LOGGING_FILE: null
LOGGING_LEVEL_CONSOLE: 20
LOGGING_LEVEL_FILE: 40
LOGGING_DUMP_PACKETS: false
LOGGING_DUMP_MESSAGES: false
LOGGING_DUMP_STATUS: false
LOGGING_DUMP_EVENTS: false
CONNECTION_TYPE: IP #set this to "IP" if using IP
SERIAL_PORT: /dev/ttyUSB0
SERIAL_BAUD: 9600
IP_CONNECTION_HOST: 192.168.X.X #set this to your IP150 IP address if using IP
IP_CONNECTION_PORT: 10000
IP_CONNECTION_PASSWORD: paradox
IP_CONNECTION_SITEID: null
IP_CONNECTION_EMAIL: null
IP_CONNECTION_PANEL_SERIAL: null
IP_CONNECTION_BARE: false
LIMITS: {}
SYNC_TIME: true
PASSWORD: '0000'
MQTT_ENABLE: true
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_USERNAME: pai
MQTT_PASSWORD: #password
MQTT_RETAIN: true
MQTT_BIND_ADDRESS: 127.0.0.1
MQTT_BIND_PORT: 0
MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true
Can anyone suggest how to set the limits in this format?
My configuration for instance :
LIMITS:
user:
- 1
- 2
- 3
- 4
- 5
- 6
pgm:
- 1
door:
- null
module:
- null
repeater:
- null
partition:
- 1
- 2
- 3
Thanks, this worked as expected.
Is it possible to trigger the alarm from home assistant, or is my only option to fit a WiFi relay to one of the zones, on my evo192??
Hook a PGM to a zone. Control PGM from PAI. Profit.
Nice, didn’t think of that.
Hello, I need some help. I can see in logs that there is an established connection with the IP150+, but after a while this connections closes.
2020-10-31 16:09:40,153 - ERROR - PAI.paradox.paradox - Timeout while connecting to panel. Is an other connection active?
Do you know what’s the problem?
Hi there, I’m using PAI with an EVO192 panel and IP150 with the latest hass.io (117.2), and everything seems to work mostly fine. I’m having two issues though. If there is a shorter movement, the PIRs catch it, but I do not see it in lovelace, it just goes unnoticed. And also, when I check the history of the sensors in lovelace, I see quite a number of “became unavailable” entries. I’m not sure the two things are related. Could you please give me some hints, or point me in a direction how to debug this or which configs to review?
When you say ‘PIR catch it’ : what does it mean exactly ? that you see the red LED blinking ? or that you actually see an ‘on’ status on babyware for instance ?
Did you check how Paradox PIR modules work ? All of them have a sleep timer but this timer is not the same for all modules.
For Paradox PMD75, PM2DP and PMD85 for instance : you get an ‘on’ status on the first confirmed detection, then you’ll get a second one for the next confirmed detection in the 3 or 4 next minutes. And that’s it ! It means that’s after these 2 detections, it goes to sleep until the end of the 3 or 4 minutes period after the first detection.
But for NV75MR you’ll the get a notification on the first detection and then you won’t get anything as long as the detector detects motion ! I don’t know its internal reset timer value or if it has one but it is long, at least 10 minutes.
This timer can be changed using a jumper on some of the modules.
Maybe you’re aware of these mecanisms and you can forget my answer, but that’s an important point to keep in mind when you try to use alarm modules for home automation purpose. You have constraints.
Tthanks for your answer. By “catching” I mean the red LED blinking indeed. What concerns the sleep timer, your examples referred to wireless PIRs, but in my case I’m totally wired up, no use of wireless. From what I know there is no sleep timer in the wired ones, but correct me if I’m wrong.
If you have double detection sensor (IR and Microwave) then you can set it to trigger even when only one of the types triggered. There should be a jumper in it.
In Babyware it is recommended to check System Options -> Communication -> “Transmit zone status on serial port” . This way events will be received instantly.