Paradox Security Systems DGP/EVO Alarm Plugin

Plugins & Plugin Development General Plugin Discussion
121

[quote=“VictorMSK, post:120, topic:165163”]Thanks a lot for your reply.

The problem is that the LastUser is not a usercode, but the programmed name, and my system is in Russia, therefore, cyrillic characters are not transmitted correctly. Is there a way to get a usercode instead of the username? There is no way to program names in latin, as the whole system is in russian and no latin symbols available.[/quote]
I imagine you could get it to work, but I’d have to see the byte sequences that the Paradox is returning when it’s asking for the User Label strings. Then you’d “build” the Luup comparison string using [tt]String.byte(…)[/tt] using those bytes… but that’s a guess.

To make it a little simpler though, I’ve modified the plugin on code.mios.com (trunk) so that it gives users the option to use either the User “Code” or their associate “Label” in the result [tt]LastUser[/tt] variable.

To do this, I changed the logic somewhat:

[ul][li]a) the Advanced configuration parameter [tt]maxUserCodes[/tt] can now be set to 0.
This means it will no longer load any of the User Label strings from the panel[/li]
[li]b) the “[tt]LastUser[/tt]” variable is populated with either the User-Label (from the Panel) or the User-Code (from the Arming command) if no User-Label exists
[/li][/ul]

The net result is that, for your situation you can set the Advanced configuration parameter maxUserCodes to 0, and then the LastUser will be populated with “001”, “002”, … instead of the label of the users.

This will avoid the translation/i18n issues.

This code is only in trunk, and I don’t currently have a plan to push it to apps.mios.com. Feel free to download it from there and apply it as a one-off patch to your system to try it out.

122

Thank you very much sir. It’s working just as supposed now.
I appreciate your kind help!

123

Hi I am new with vera3. I already have paradox sp6000. I want to upgrade to paradox evo with prt3 module.
Will it be diffiult to install? Will someone be able to help me through a little (is there any tutoriels on youtube?).
When funtional this is a scene I would like to set:
The trigger would be the opening of the garage door (my garage door will be on PGM1)
When I would open the grage door the alarm system would disarm and a couple of lights would open.
Is that easy to accompish
Thanks for the input
Pierre :slight_smile:

124

@DrD,
Generally speaking, if you’re comfortable doing some basic wiring, and a lot of research/reading, then it’s possible to make the change yourself.

For me, I’ve only ever added stuff to an existing system (Zones, COMBUS modules, PRT3 etc), and not installed one from scratch. There are a few video’s here and there, but they’re mostly for simple stuff.

If you’re not comfortable working it out without the Videos, then you may want to contact a local installer to make the cutover for you.

AFAICT the Keypads are different between the EVO Series and the Spectra’s, so they might need to be substituted also.

Functionality wise, for Garage doors, you’ll need both a PGM (output) and a Zone (input). The PGM will control the door, and the Zone will let you know if the door is open or closed. Depending upon local codes (etc), you may not want local control (PGM) over the garage door.

There are a few threads on the board here for general Garage door control, and the scripting/plugins needed, so I won’t re-hash that.

You could also write a Scene that “disarms” your Alarm Panel when the Garage door is open (using the Zone above), but I wouldn’t recommend it. Everything needed is there to do it declaratively, but it’s really insecure and it’ll require you to store your PIN Code (or A PIN code) into Vera (which gets into your Backups, and stored on MiOS Servers)

… and yes, that scene can also turn on a few lights (etc)

NOTE: Paradox is currently Beta testing a newer EVO model, the EVO VHD. It’s not clear how long this will take to cycle through beta, but it might be worth the wait to get the newest panel model… either that, or use it to get a special on one of the EVO 192 boards, as it looks like a number are offering the dealers “packages” on the EVO 192.

125

Thanks for the quick response . I will read attentively your recommandations… if I have any more questions Iwill write back.
Pierre

126

Hi again!
My alarm guy will do the installation. (not sure if I will wait for the new Evo or not)

Sorry to ask the question but what are the advantages to use the paradox plugin if it is not suggested to arm or disarm the system
in a scene?
(probably best to use a zone as a trigger to do something else?)

Is it woth it?..I already have Iparadox android app but it is not integrated in Vera.

Thanks again for your precious input

Pierre

127

@DrD,
It’ll depend upon what you want to do. Generally, in scenes, Disarm commands require a PIN to be stored and Arm commands don’t.

For me, I Arm the house using Keypad one-touch before I leave. I then use this as a “secure” means of determining whether I’m at home or not. My Vera has a set of scenes that execute when it detects (via the Plugin) the house transition to this Armed/Not-at-home state:

a) Turn off the [Nest] Thermostats, or set them to “Away” mode to save Power.
b) Turn off all of the lighting
c) Turn off the Hot water pump
d) Turn off the Sonos units, the TV (etc)
e) Completely power down the AV Gear (not even standby mode, completely “off” via a WebSwitch)

Something along the lines of the reverse happens when I Disarm the house, which I also do via a standard Keypad.

For a few yrs now (3-4?), I’ve also had scenes that put the Thermostats into “Away” mode when I open Windows (etc), to avoid heating/cooling the house… again mostly for power savings.

These were done using the original [wired] sensors that were around the house, windows & doors (etc).

More recently I’ve added extra sensors to the house for the sole purpose of automation. These include:
a) battery powered micro-sensors (DCT2) for inner doors, so lights come on
b) ceiling mounted motion sensors (DG467) to turn on walk-in-closet lights
c) weatherproof motion sensors (PMD85) to turn on exterior lighting, and notify me when folks are approaching
d) hallway motion sensors (PMD1P) to turn on inner lighting
e) Garage door contact sensors/PGM (2WPGM) to detect if the garage is open, and notify me

The total power savings are substantial, which is what makes it worthwhile to me. The additional automation, like having house lights come on at night when disarming, also makes it worthwhile as part of a broader set of security measures.

With each thing added to the system, you have to balance off convenience and security. Each person will have different tolerances there.

Moving forward, I will add a [bi-directionally authenticated] mechanism to detect our cars coming home, and to open the Garage door and disarm the house as the cars come up the drive. The tech to do this [securely] is starting to be commercially available at a reasonable price.

I also like to experiment with tech, since it’s what I do for work :wink:

Now, you can always tie your secure system (Alarm Panel) to an insecure one (opening the Garage via traditional remote), it’s just something that I prefer not to do.

Technically, you can do that with the Panel itself, and no other components.

For example, you’d use a [Paradox] Keyfob in the car to disarm the house, and at the same time have it open the garage for you. I haven’t looked closely, but I believe you can do that, but you wouldn’t get the other benefits of the automation. It also means that someone that steals your car, or Keyfob remote left in the car, can get into your house un-noticed.

It would be more secure than using the regular Garage opener, since you’d use the Paradox Keyfob to “disarm” instead of using the regular garage remote (or a sensor on the garage door, which can be tricked with a strong magnet) but it still has it’s weaknesses.

Backup and Access…
I currently have an older Panel (a DGP-848), which I will upgrade to the EVO VHD when it comes out. At that time I’ll add an IP150 module, and have the iParadox app as a backup to this whole setup, since stuff does fail :wink: )

My Vera is not attached, and does not backup, to any of the MiOS Servers. I have a home VPN for any internal access that I need (since it’s secure). This isn’t for everyone, since it requires a lot of configuration.

128

Some clarifications I might offer to help,

The new Paradox EVO VHD system that is currently in development is not meant to replace the EVO192. According to the grapevine from Paradox distributors, it’s meant to replace the poorly selling Paradox Imperial system. As such, it’s not really the same thing at all, and they are leaving the EVO192 unchanged as their default robust system.

Being that you have an SP6000 system, you can not integrate to Vera or other home automation systems. The reason is they never implemented the two way communication via the PRT3 integration module for this panel. It’s sad, and foolish, and all things disappointing. You will most definitely have to switch your keypads as well as the main board. Other peripherals such as the PRT3, the RTX3 wireless transceiver, and the IP100/IP150 IP systems will work with either platform. My advice is to see if you can get a good price on the TM50 keypads, as the standard keypads for the EVO are less user friendly IMO than the standard ones for the SP6000. The TM50 is also a cross platform module as well, so makes it a good choice, if the price is right.

Also, stay away from the IP100. Don’t let a dealer try to sell you one, as they are trying to offload old stock. The IP150 is what you want, if you want this component at all. The IP100 had no SSL/TLS to the SMTP client, making the notifications useless. The IP150 fixed this issue. These notifications are a duplication of what the Vera can do, but it’s a great way to go for simple, robust, and reliable notifications.

Now for my own request for aid;

I have to plan a system for a very elderly gentleman. He’s moving in with family, and they want to set him up with a wrist band style panic button. I’d like to be able to help, as having a system in place can make a real difference in their lives. I can handle all of the alarm work, but they don’t necessarily want the default that panels do. (monitoring station response is a bit too dire in this case) They want multiple parties notified via electronic notifications. I can do this with the IP150, but the Vera would give me many more options, given the hardware that the family uses. I will be using a panic button that is configured to trigger a PGM.

In the docs for the Paradox plugin, it says; “Virtual PGM a special type of Zone defined within the Alarm Panel. The Alarm Panel can be configured to establish the conditions under which a Virtual PGM [Zone] is triggered and/or reset. Virtual PGMs events are supported in the code, but are disabled by default to make the UI simpler.”

My question is, are these Virtual PGMs what I’m looking for? If so, how do I enable these in the UI, so that I can expose the PGM of the alarm board as a trigger for scene control?

Thanks in advance!

129
Now for my own request for aid;
@Pestus, Ok, so I wrote that PGM code ~4yrs ago, and it's never been tested. I walked through the logic this morning, and it looks correct, but again... it's never been tested so it probably won't work out of the gate.

To enable it, do the following things:

[ul][li]1. Set the parameter [tt]enableVirtualInputs[/tt] to “[tt]true[/tt]”
This will turn on the functionality. The variable needs to be set in the Advanced tab in the ServiceId [tt]urn:demo-paradox-com:serviceId:ParadoxSecurityEVO1[/tt]
[/li]
[li]2. Set the parameter [tt]maxVirtualInputs[/tt] to the number of inputs you want enabled (default: 5)
This variable needs to be set in the Advanced tab, in the ServiceId [tt]urn:demo-paradox-com:serviceId:ParadoxSecurityEVO1[/tt][/li]
[li]3. Restart.
After the restart, you should see a number of additional Zones created by the Plugin. Each will have a label of the form “Virtual PGM Sensor ” and be of Device Type “[tt]…:device:MotionSensor:1[/tt]” so they’ll have the “regular” icon[/li][/ul]

At this point, they should follow the internal state of the Virtual PGM, as defined/mapped by the PRT3 ↔ Panel mapping.

Again, have never tried it so the road will probably be a little bumpy.

130

Okay.

I had stumbled upon how to enable the device as you’ve explained;

1. Set the parameter enableVirtualInputs to "true" This will turn on the functionality. The variable needs to be set in the Advanced tab in the ServiceId urn:demo-paradox-com:serviceId:ParadoxSecurityEVO1 2. Set the parameter maxVirtualInputs to the number of inputs you want enabled (default: 5) This variable needs to be set in the Advanced tab, in the ServiceId urn:demo-paradox-com:serviceId:ParadoxSecurityEVO1 3. Restart. After the restart, you should see a number of additional Zones created by the Plugin. Each will have a label of the form "Virtual PGM Sensor " and be of Device Type "...:device:MotionSensor:1" so they'll have the "regular" icon

Your last bit here is instructive;

At this point, they should follow the internal state of the Virtual PGM, as defined/mapped by the PRT3 <-> Panel mapping.

So the main panel has regular PGMs. The RTX3 (Wireless transceiver) also has PGMs. Lastly, the PRT3 has Virtual PGMs solely for exposure to printers and automation. I was trying to program the regular board PGM, and was about to admit defeat and wire that PGM into a zone input as a keyswitch, when you replied. Once I copied the same layout to the PRT3’s Virtual PGM, it worked instantly.

Consider your code effective. While we are at it, is there anything else you’d like tested?

131

Hi guessed and Pestus!
Thanks for all the info…there is a lot in there.
I already have the ip150 and it works perfect with iparadox.

Is it possible to have some pictures or other documentation ( because I am visual ) to see physically how vera works with scenes from the moment the paradox evo192 ?prt3 plugin is integrated.
I know I am asking more than I should :stuck_out_tongue:

132

Hi guessed, if you get a free moment, can you private message me? I wanted to start a separate dialogue with you regarding the Paradox plugin. I only have 12 posts, so I am too newbie to private message myself. Thanks!

133

[quote=“93732, post:132, topic:165163”]Hi guessed, if you get a free moment, can you private message me? I wanted to start a separate dialogue with you regarding the Paradox plugin. I only have 12 posts, so I am too newbie to private message myself. Thanks![/quote]I can PM you, but you still won’t be able to PM back until you have the requisite # of posts (basically, 25). Post your questions here, and I’ll generally respond in a few days.

134

guessed, Sure no problem. What is the Arm and Bypass switch do for the “Alarm Communication” module? What

135

The Alarm Communication device I build was [originally] intended to represent a failure of the communications to the Panel. There were various error codes, and connectivity indicators, that were intended to “trigger” the Alarm Communication device into a “Tripped” state?.

This particular entity was built using the standard Motion Sensor device, so it gets the [default] rendition (including stuff like Arm/Bypass that are largely useless). The system doesn’t use it, so you’re free to use that “state” for other purposes.

Side-note: This plugin has been around a long time, and there are better ways to do this now, but I can’t [readily] change this without causing compat problems (ones I don’t want to deal with)

136

Anyone have been able to have the plugin working with a Spectra 1738 ?

137

[quote=“goldriver, post:136, topic:165163”]Anyone have been able to have the plugin working with a Spectra 1738 ?[/quote]Some time back, there was an indication that the Spectra Panels didn’t support the necessary functions (over the PRT3) for Home automation integration.

138

Guessed is correct. Unfortunately only the Digiplex or EVO lines of Paradox panels allow for automation systems.

Whats worse, is the Spectra 1738 is a discontinued line. Only the newer Spectra line (4000, 5050, 6000, 7000 etc) will support the IP150 module. That would at least give you standalone access to the alarm with notifications.

Sadly, the Spectra 1738 leaves you with no upgrade paths in this regard. Great alarm, irritating company decisions. This is causing me immense grief with my client base at the moment.

139

Hi,

I have an Evo 192 and an IP150, does this plugin support the IP150?
If not any plans to adapt the plugin to support it?

Regards

140

[quote=“Jpcolin, post:139, topic:165163”]Hi,

I have an Evo 192 and an IP150, does this plugin support the IP150?
If not any plans to adapt the plugin to support it?

Regards[/quote]

No sir. The IP150 is a standalone IP communicator meant for alarm transmission to the monitoring station. It also will allow a stand-alone app for remote access for the end user, and for technician maintenance of the alarm programming. Lastly it allows email notifications for system events. It is an entirely closed system and can not be used in this manner.

The device you need is a PRT3. It’s got an LPT1, an RS232, and a USB. For integration, the EVO192 is the board you want. Guessed wrote a stellar plugin for integration, but this is the only combo that can ever work, barring any major design changes from Paradox.