Paradox Alarm Panel integration.

Plugins & Plugin Development General Plugin Discussion
1

Hi Guys.

I need assistance selecting an Alarm and Panel.
I am new to home automation and am moving into a new home so am in the market for a new alarm system and looking to integrate into a new Vera Edge.
I cant find an updated list of supported Alarm Panels.

I am looking to go with the Paradox Evo or 5050 [is the 5050 supported?], but want to know if the Paradox TM50 Touch Keypad supports the PRT3 module for home automation.
Or would I need to go for one of the analog panels to integrate.

Appreciate your assistance in this regard.

2

The current Paradox Alarm Plugin was written for the EVO (and DGP) series boards, as supported by the HA interface on the Paradox [APR-]PRT3 interface card.

The Paradox Magellan-series of Panels, like the 5050, don’t support HA functionality via that interface card.

I wrote the Paradox Alarm Plugin back in 2009, and at that time I had a Paradox DGP-848 (with PRT3). I’ve since upgraded to an EVO-192, using the same PRT3 board, and it’s working well under UI5/Vera 3.

It’s in the apps.mios.com store as Plugin Id 46.

Keypads wise, that doesn’t matter, as long as they’re compatible with the core Panel. The Alarm interface board (the PRT3) is performing the COMBUS conversion work that’s required to integrate with the Plugin.

For reference, I have the following parts in my system:

[ul][li]K641 - Keypads[/li]
[li]EVO192 - Alarm Panel[/li]
[li]PRT3 - Home Automation interface board[/li]
[li]ZX8 - Wired expansion modules[/li]
[li]IP150 - Internet module[/li]
[li]RTX3 - Wireless Expansion board[/li]
[li]Some wired Motion ensors (Quad Element DM60’s, Ceiling DG467)[/li]
[li]Some wireless Motion Sensors (Indoor PMD1P, Outdoor PMD85)[/li]
[li]Some wireless Zones (DCT2, DCTXP2)[/li]
[li]A wireless PGM for Garage door monitoring/control (2WPGM)[/li][/ul]

I’ll probably start replacing the K641 Keypads with TM50’s within the next yr.

There are known issues in UI7 that impact the initial configuration of the DSC Alarm Plugin and, since I wrote both, it’s likely these will also impact the Paradox Plugin also. Vera Edge is UI7 only, so it’s likely you’d run into similar issues.

I’ve not done any material testing of the Paradox Alarm Plugin under UI7 since, at the times I’ve tested, there were far too many obvious bugs in that release that need to be addressed.

3

I’m assuming you’re considering Paradox because of where you’re located, otherwise I’d steer you towards the DSC, which has a broader user base here.

They’re not common in the US, but seem more widely used in Europe, Canada and Africa (etc).

4

I am trying to get the EVO192 working for at least 3 days with UI7 platform using the PRT3 and following the initial instructions provided for the UI5.

I have executed all the step many time over the last 3 days and the issue seems to be the new os UI7/ Vera edge .

I have reached this point :

Type the command ZL001 and press
The PRT3 should respond with the Label string for Zone 1

I got the PRT3 Label string for Zone 1 and the next step is supposed to be connect the usb cable to the vera but nothing happens and i get the following error message : ParadoxAlarmPanel : Failure in Request-Area-Label Response, communications error AL001.

and vera serial port setup give this msg : Serial Port configuration
If you connected the USB/serial device and it’s not displayed here, reload Luup.
Not available.

Reloaded many times with no result.

I will try to get an old UI5 Vera lite to test if my alarm setup was ok and if everything work fine with ui5 it will confirm that the issue is the Vera Edge and the actual firmware.

I have been able to set up few DSC using the EVL3 ip card so i will recommend you to get away from paradox for now …

Guessed i know you dont have touched the UI7 yet but if you think to any good idea to get my issu fix i will appreciate.

I will post the result after my test on veraedge.

5

Since my last post i have been able to put the hand on the Vera lite with automatic update flag turned off so the UI5 ver 1.5.622 and it take me about 5 minutes to complete the set up using the initial instructions provided with the Paradox plugin . So it clearly confirm that the main issue is generated by the Vera Edge and the new OS UI7 and again we could only refer to Vera team support and hope they will find a way to fix the issue soon.

The main issue is the fact that the Vera unit do not recognized any devices connected to the USB port so when you following the instructions of the plugin you will block at the step where you should normally set the baud rate in the vera :

---- After the plugin has been installed go to Apps >> Develop Apps >> Serial Port configuration and select the alarm panel device from the Used by device drop-down list.
---- Save.
---- After Luup restarted, reload the UI.

So from my point of view the plug-in remains perfect even after 6 years but the Vera OS have been modify and in a lot of scenario like this one Vera will have to make patch over the new firmware to ensure the old devices that was use to perfectly work will work again.

List of my actual issue with UI7

Aeon Lab 4 in 1 5th generation : Motion no longer working and the setting need a lot of manual modification to partially work.
Leviton Dimmer : error msg always on : Unable to get manufacturer information

The good news is Vera making monthly update over the firmware.

6

[quote=“guessed, post:2, topic:186840”]The current Paradox Alarm Plugin was written for the EVO (and DGP) series boards, as supported by the HA interface on the Paradox [APR-]PRT3 interface card.

The Paradox Magellan-series of Panels, like the 5050, don’t support HA functionality via that interface card.

I wrote the Paradox Alarm Plugin back in 2009, and at that time I had a Paradox DGP-848 (with PRT3). I’ve since upgraded to an EVO-192, using the same PRT3 board, and it’s working well under UI5/Vera 3.

It’s in the apps.mios.com store as Plugin Id 46.

Keypads wise, that doesn’t matter, as long as they’re compatible with the core Panel. The Alarm interface board (the PRT3) is performing the COMBUS conversion work that’s required to integrate with the Plugin.

For reference, I have the following parts in my system:

[ul][li]K641 - Keypads[/li]
[li]EVO192 - Alarm Panel[/li]
[li]PRT3 - Home Automation interface board[/li]
[li]ZX8 - Wired expansion modules[/li]
[li]IP150 - Internet module[/li]
[li]RTX3 - Wireless Expansion board[/li]
[li]Some wired Motion ensors (Quad Element DM60’s, Ceiling DG467)[/li]
[li]Some wireless Motion Sensors (Indoor PMD1P, Outdoor PMD85)[/li]
[li]Some wireless Zones (DCT2, DCTXP2)[/li]
[li]A wireless PGM for Garage door monitoring/control (2WPGM)[/li][/ul]

I’ll probably start replacing the K641 Keypads with TM50’s within the next yr.

There are known issues in UI7 that impact the initial configuration of the DSC Alarm Plugin and, since I wrote both, it’s likely these will also impact the Paradox Plugin also. Vera Edge is UI7 only, so it’s likely you’d run into similar issues.

I’ve not done any material testing of the Paradox Alarm Plugin under UI7 since, at the times I’ve tested, there were far too many obvious bugs in that release that need to be addressed.[/quote]

hello guessed veraite paradox connected with my evo 192, everything works perfectly with your plugin, only problem after 24 hours freezes Veralite and exit this screen:

what could be the problem?
thanks

7

[quote=“luise, post:6, topic:186840”][quote=“guessed, post:2, topic:186840”]The current Paradox Alarm Plugin was written for the EVO (and DGP) series boards, as supported by the HA interface on the Paradox [APR-]PRT3 interface card.

The Paradox Magellan-series of Panels, like the 5050, don’t support HA functionality via that interface card.

I wrote the Paradox Alarm Plugin back in 2009, and at that time I had a Paradox DGP-848 (with PRT3). I’ve since upgraded to an EVO-192, using the same PRT3 board, and it’s working well under UI5/Vera 3.

It’s in the apps.mios.com store as Plugin Id 46.

Keypads wise, that doesn’t matter, as long as they’re compatible with the core Panel. The Alarm interface board (the PRT3) is performing the COMBUS conversion work that’s required to integrate with the Plugin.

For reference, I have the following parts in my system:

[ul][li]K641 - Keypads[/li]
[li]EVO192 - Alarm Panel[/li]
[li]PRT3 - Home Automation interface board[/li]
[li]ZX8 - Wired expansion modules[/li]
[li]IP150 - Internet module[/li]
[li]RTX3 - Wireless Expansion board[/li]
[li]Some wired Motion ensors (Quad Element DM60’s, Ceiling DG467)[/li]
[li]Some wireless Motion Sensors (Indoor PMD1P, Outdoor PMD85)[/li]
[li]Some wireless Zones (DCT2, DCTXP2)[/li]
[li]A wireless PGM for Garage door monitoring/control (2WPGM)[/li][/ul]

I’ll probably start replacing the K641 Keypads with TM50’s within the next yr.

There are known issues in UI7 that impact the initial configuration of the DSC Alarm Plugin and, since I wrote both, it’s likely these will also impact the Paradox Plugin also. Vera Edge is UI7 only, so it’s likely you’d run into similar issues.

I’ve not done any material testing of the Paradox Alarm Plugin under UI7 since, at the times I’ve tested, there were far too many obvious bugs in that release that need to be addressed.[/quote]

hello guessed veraite paradox connected with my evo 192, everything works perfectly with your plugin, only problem after 24 hours freezes Veralite and exit this screen:

what could be the problem?
thanks[/quote][quote=“luise, post:6, topic:186840”][quote=“guessed, post:2, topic:186840”]The current Paradox Alarm Plugin was written for the EVO (and DGP) series boards, as supported by the HA interface on the Paradox [APR-]PRT3 interface card.

The Paradox Magellan-series of Panels, like the 5050, don’t support HA functionality via that interface card.

I wrote the Paradox Alarm Plugin back in 2009, and at that time I had a Paradox DGP-848 (with PRT3). I’ve since upgraded to an EVO-192, using the same PRT3 board, and it’s working well under UI5/Vera 3.

It’s in the apps.mios.com store as Plugin Id 46.

Keypads wise, that doesn’t matter, as long as they’re compatible with the core Panel. The Alarm interface board (the PRT3) is performing the COMBUS conversion work that’s required to integrate with the Plugin.

For reference, I have the following parts in my system:

[ul][li]K641 - Keypads[/li]
[li]EVO192 - Alarm Panel[/li]
[li]PRT3 - Home Automation interface board[/li]
[li]ZX8 - Wired expansion modules[/li]
[li]IP150 - Internet module[/li]
[li]RTX3 - Wireless Expansion board[/li]
[li]Some wired Motion ensors (Quad Element DM60’s, Ceiling DG467)[/li]
[li]Some wireless Motion Sensors (Indoor PMD1P, Outdoor PMD85)[/li]
[li]Some wireless Zones (DCT2, DCTXP2)[/li]
[li]A wireless PGM for Garage door monitoring/control (2WPGM)[/li][/ul]

I’ll probably start replacing the K641 Keypads with TM50’s within the next yr.

There are known issues in UI7 that impact the initial configuration of the DSC Alarm Plugin and, since I wrote both, it’s likely these will also impact the Paradox Plugin also. Vera Edge is UI7 only, so it’s likely you’d run into similar issues.

I’ve not done any material testing of the Paradox Alarm Plugin under UI7 since, at the times I’ve tested, there were far too many obvious bugs in that release that need to be addressed.[/quote]

hello guessed veraite paradox connected with my evo 192, everything works perfectly with your plugin, only problem after 24 hours freezes Veralite and exit this screen:

what could be the problem?
thanks[/quote]

8

[quote=“luise, post:6, topic:186840”]hello guessed veraite paradox connected with my evo 192, everything works perfectly with your plugin, only problem after 24 hours freezes Veralite and exit this screen:

what could be the problem?
thanks[/quote]
There are a large number of problems in Vera/MiOS that result in that type of error being presented to the user.

If you’re used to working with SSH and Log files, then you can enable Verbose logging (in Vera) and look over those first to narrow down the list of potential causes. If you’re not familiar with this, then I’d recommend you contact the MiOS Support organization (during the weekday) to diagnose the cause.

9

ok thank’s guessed today i have enable verbose logging.
you tell me where i can seek the file log.

my configuration serial:

10

ok guessed this any file log, but do you want the file when veralite is locked??

11

these are screenshot log of Veralite while running smoothly, you need the log files when Veralite freezes?

12

hello. is there any update for this ?
does the plugin workable on UI7 ?

13

Hi, someone has already tried or know if Vera can integrate into the control panel Paradox Magellan MG5050?

Thank you

14

guessed - has UI7 stablised enough for you to consider modifying this plugin to work with UI7?

I have a Vera3 (UI7) that I’d like to integrate with my Paradox EVO192 (with IP150 and PRT3 modules).

If my reading of the Paradox-related threads is correct I have two options:

Is that correct?