Yeah that will be an issue, if you are lucky and the version is not too high, from version 4 I hear it auto updates as well so check the version before you let it go online and maybe you can preform this downgrade.
MG5000 fw 4.76 with IP150 v 4.10 - Problem logging in · Issue #22 · Tertiush/ParadoxIP150v2 · GitHub
also check out this thread,
Help build binding for Paradox Alarm Panel with IP150 - Bindings - openHAB Community
I hope it works.
Thanks. I’ll find out in a week or so I guess
Dear JP,
Thank you for the write-up as well. Very useful.
It still does not work for me, but I have a different panel (EVO192), which might be the issue.
regards
I would still have one available if interested (v1.40). I bought it specifying I needed an old formware (they are typically more onerous than those with the current firmware) and the seller sent me a new one. He did not want to send me the correct one before I sent back the other one and therefore I bought another one from another seller as I had to leave on holidays. It is brand new.
Kind regards
I have emailed the supplier I have put the order in with to see what they have. I’m Australia, where abouts are you?
This place seems to sell ones with the old firmware.
https://www.megateh.eu/products/control-panel-modules/paradox-ip150s-internet-module-service-open-version
I see its a different version the IP150s as mentioned on this page.
http://www.paradox.com/Products/default.asp?CATID=3&SUBCATID=38&PRD=563
Europe as well - keep us posted with the version of your supplier
The issue I had was with MQTT - now the Paradox Addon is working for me as well.
I am going to try the arm/disarm based on the information above.
I think you are mistaking Austria with Australia, I’m on the other side of the globe 
Definitely not - but I expressed myself wrongly - I am in Europe as well with regards to the reseller proposed by J-P. I have family in Australia, although haven’t seen them for a long time. Cheers
oh, sorry. I misunderstood
well I just heard back from my local supplier… they have shipped me version 4.3 so I guess I’m screwed unless I want to pay for another one 
@sparkydave I do not wish to hijack this thread, as it is a great module integrated with HA, but if you have problems with recent panels, this project may help you: https://github.com/jpbarraca/pai
Thanks, I’ll check it out once I get my Paradox alarm system up and running. Delivery is today
Hi @alfredo
Thanks for this addon. Everything is working very well.
Is it possible to control Paradox PGM from Home Assistant? I have my blades connected to PGM and would like to create some automations from HA.
Thanks
Hi Alfredo, Xessiv and all.
Thanks again for all your assistance on this project. Xessiv, you mention above that you have 2 areas that you control in Home Assistant and in your setup you simply add another entry under alarm_control_panel and append ‘/2’ onto the state_topic and command_topic.
Do these multiple areas need to be set up somewhere, or should the just work? I have 3 separate areas on my Paradox Evo192 (house, garage and office) and I tried adding ‘/2’ and ‘/3’ to the my alarm_control_panel, but only ‘/1’ (house) area works. The other two area show as ‘unknown’.
alarm_control_panel:
- platform: mqtt
state_topic: "paradox/alarm/state/1"
command_topic: "paradox/alarm/cmnd/1"
payload_disarm: "DISARM"
payload_arm_home: "ARM_HOME"
payload_arm_away: "ARM_AWAY"
qos: 1
name: "House alarm"
- platform: mqtt
state_topic: "paradox/alarm/state/2"
command_topic: "paradox/alarm/cmnd/2"
payload_disarm: "DISARM"
payload_arm_home: "ARM_HOME"
payload_arm_away: "ARM_AWAY"
qos: 1
name: "Office alarm"
- platform: mqtt
state_topic: "paradox/alarm/state/3"
command_topic: "paradox/alarm/cmnd/3"
payload_disarm: "DISARM"
payload_arm_home: "ARM_HOME"
payload_arm_away: "ARM_AWAY"
qos: 1
name: "Garage alarm"
Is there anything else I need to do to get these two other areas working?
Hi Claude, please see below.
My Paradox MQTT connection addon is standard, didn’t change anything on that except for Alarm host IP, and MQTT user/pass
In my configuration.yaml, I have the following:
alarm_control_panel: - platform: mqtt state_topic: "paradox/alarm/state/1" command_topic: "paradox/alarm/cmnd/1" payload_disarm: "DISARM" payload_arm_home: "ARM_HOME" payload_arm_away: "ARM_AWAY" qos: 1 name: "Control State Home" - platform: mqtt state_topic: "paradox/alarm/state/2" command_topic: "paradox/alarm/cmnd/2" payload_disarm: "DISARM" payload_arm_home: "ARM_HOME" payload_arm_away: "ARM_AWAY" qos: 1 name: "Control State Garage"
I’ve just had time to rebuild my HomeAssistant setup, and have encountered an issue where command_topic isn’t allowed to be in sensor format anymore, so I had to remove that.
So for the arm/disarm ‘sensor’, I have this in my sensors.yaml
- platform: mqtt state_topic: "paradox/alarm/state/1" qos: 1 name: "Alarm State Home" - platform: mqtt state_topic: "paradox/alarm/state/2" qos: 1 name: "Alarm State Garage"
And for the actual switch component (arm/disarm separate zones), that just works from the data in configuration.yaml. The command that does the switching is the command_topic line, so when you reference the entity it will bring it up for you.
And this is how I’ve got them referenced in my groups.yaml - cut down version so you can test if it works for you.
default_view: view: yes icon: mdi:home entities: - sensor.alarm_state_home - sensor.alarm_state_garage - group.Alarm Alarm: name: Alarm icon: mdi:alarm-light view: yes entities: - alarm_control_panel.control_state_home - alarm_control_panel.control_state_garage - sensor.alarm_state_home - sensor.alarm_state_garage
Tested and working on Home Assistant 0.87.1 with Paradox addon v5 running on HassOS 2.8 on a RPi 3B
Let me know if you have any more questions 
Hi hybrix, sorry for the delay.
I’ve just written hopefully a more complete post below, with all of my sections documented. Please check it out - Paradox Alarm MQTT Hassio addon
Let me know if you’re still having issues 
Once again Xssesiv, many thanks for your time. Unfortunately, my setup was almost exactly the same as yours, but I still couldn’t get my system to see the other ‘areas’ of my Paradox installation.
My entire system was slowing down on a Raspberry Pi installation so I reinstalled a snapshot of my setup in a Docker container on an Ubuntu laptop and now it can see the other Paradox areas! Maybe just a problem with limited resources.
I can now unset the system using alarm_control_panel and see all motion sensors, door sensors etc. The only problem is that I can’t set the alarm.
I have the following setup for my areas:
- platform: mqtt
state_topic: 'paradox/alarm/state/1'
command_topic: 'paradox/alarm/cmnd/1'
name: alarm_house
payload_disarm: 'DISARM'
payload_arm_home: 'ARM_HOME'
payload_arm_away: 'ARM_AWAY'
qos: 1
- platform: mqtt
state_topic: 'paradox/alarm/state/2'
command_topic: 'paradox/alarm/cmnd/2'
name: alarm_cottage
payload_disarm: 'DISARM'
payload_arm_home: 'ARM_HOME'
payload_arm_away: 'ARM_AWAY'
qos: 1
My Lovelace alarm panels are set up as follows:
- entity: alarm_control_panel.alarm_house
name: House
states:
- arm_home
- arm_away
type: alarm-panel
- entity: alarm_control_panel.alarm_garage
name: Garage
states:
- arm_home
- arm_away
type: alarm-panel
and lastly, my Paradox setup is as follows:
{
"IP150_ADDRESS": "http://192.168.xxx.xxx:xxxx",
"PANEL_CODE": "XXXX",
"PANEL_PASSWORD": "xxxxxxxx",
"MQTT_ADDRESS": "mqtt://core-mosquitto",
"MQTT_USERNAME": "XXXXX",
"MQTT_PASSWORD": "xxxxxxxxxxx",
"ALARM_PUBLISH_TOPIC": "paradox/alarm/state",
"ALARM_SUBSCRIBE_TOPIC": "paradox/alarm/cmnd",
"ZONE_PUBLISH_TOPIC": "paradox/zone/state",
"CTRL_PUBLISH_TOPIC": "paradox/ctrl/state",
"CTRL_SUBSCRIBE_TOPIC": "paradox/ctrl/cmnd"
}
Can anyone see any reason why I can only disarm my alarm and not arm them?
Thanks in advance for your help.
Hi Claude,
I don’t know why you still can’t control more than one area, very strange! Maybe try to remove the single new line between the first and second areas under your alarm_control_panel: code?
For the arm/disarm though, maybe you’ve got too much information on the Lovelace alarm panel section?
Maybe just try having the entity and name lines, and remove the states/type because it may work without them?
The code I put up for my groups.yaml has displayed this for Lovelace. Circle highlighted are the sensors and then 1/2 are the 2 areas, which can be controlled separately, and can arm/disarm:
And in Pending state when Arm Away is selected:
Hope this helps you/anyone out further.