Hi,
I recently upgraded my vista 20p to a vista 128BPT. the EV3 was working great with the 20p.
Reading through the forum and sending support tickets in I am told that the vista 128 testing was stopped and currently not supported, however there are people who have successfully programmed their 128 to use the EV3.
My question is there anyone who has heard of someone who has the EV3 working with a vista 128BPT?
I have it setup as a device in the programming as a keypad number 17. I am able to monitor the zones and can log in on my iphone and send an arm command and it works. However the LRR setup eludes me and I am not getting notifications of the alarms. I have set *57 to 1 and *58 to 111111.
Any ideas or input would be great.
Thanks.
EV3 honeywell vista 128
Moderators: EyezOnRich, GrandWizard
-
- Posts: 1
- Joined: Thu May 23, 2013 11:42 am
Re: EV3 honeywell vista 128
i am in the same boat. I am seeing network outages in the events and some zone opens and closes but can't set or clear the alarm.
-
- Posts: 2375
- Joined: Tue Nov 16, 2010 4:08 pm
Re: EV3 honeywell vista 128
No, that would be a completely different boat. Submit a tech support request from your eyezon account.
sergi182:
I pulled out a t Vista 128 manual and I see that the major difference in LRR programming is that there is no *29 anymore (well there is, it just does other things). You have to get at the LRR through Menu Mode Programming (Section 4-2).
Enter *93 to go into menu mode programming and hit 0 until you get to the devices menu.
"Device Prog?"
Hit 1 to enter device programming. The LRR is always on address 3 so select address 3. You will then be prompted for a device type. In another "cryptic" programming manual it lists a bunch of different types of devices. Device type 6 is reserved for LRR so put that in.
Leave menu programming and then most of all the other options are the same.
I don't have a 128 in our lab so I can't verify all of this, but that is what I see in the manual.
sergi182:
I pulled out a t Vista 128 manual and I see that the major difference in LRR programming is that there is no *29 anymore (well there is, it just does other things). You have to get at the LRR through Menu Mode Programming (Section 4-2).
Enter *93 to go into menu mode programming and hit 0 until you get to the devices menu.
"Device Prog?"
Hit 1 to enter device programming. The LRR is always on address 3 so select address 3. You will then be prompted for a device type. In another "cryptic" programming manual it lists a bunch of different types of devices. Device type 6 is reserved for LRR so put that in.
Leave menu programming and then most of all the other options are the same.
I don't have a 128 in our lab so I can't verify all of this, but that is what I see in the manual.
Re: EV3 honeywell vista 128
In device programming:
Select device 03.
Then enter device type as 06 (LRR)
Make sure you also have the following:
Make sure all zones have a report code set.
*32 1111 or any account number
*45 1 (Contact ID)
*52 111111 (expanded reporting)
*56 00 (dynamic signal delay)
*57 1 (dynamic signaling priority)
*58 111111 (LRR category enable)
*88 0 (com delay)
I have yet to get my unit to send anything other than zone status and troubles to the webpage. My email and SMS is still not receiving any emails other than module supervision alerts...
Hopefully someone can help us out and tell us what is missing.
Select device 03.
Then enter device type as 06 (LRR)
Make sure you also have the following:
Make sure all zones have a report code set.
*32 1111 or any account number
*45 1 (Contact ID)
*52 111111 (expanded reporting)
*56 00 (dynamic signal delay)
*57 1 (dynamic signaling priority)
*58 111111 (LRR category enable)
*88 0 (com delay)
I have yet to get my unit to send anything other than zone status and troubles to the webpage. My email and SMS is still not receiving any emails other than module supervision alerts...
Hopefully someone can help us out and tell us what is missing.
Re: EV3 honeywell vista 128
I fought my way through this and finally got my Honeywell Ademco Vista 128BPT working great with the EVL3.
I followed the great advice from Jim in the prior post but had to do a few things more. So here is the synopsis:
Go to #93 Report Code Programming. For every zone make sure the first digit is nonzero.
Report Code Prog: 1
Alarm, ID Digit: 1
Enter Zone No: 001
001 Report Code 1st: 01 * (or anything non-zero)
001 Report Code 2nd: 00 *
Do the above for all your zones.
Now you want to turn on reports for all the interesting events. This will generate the events that show up in your EyezON web portal. After a bit of playing around, I decided the only events I cared about (for now) are:
Closing (arm AWAY)
Opening (disarm)
Arm STAY
So in #93 Report Code Programming, go into System Group #1 (to enable arm away and disarm events)
System Group #1: 1
Close 1st: 01 *
Close 2nd: 00 *
Open 1st: 01 *
Open 2nd: 00 *
I left the rest of System Group #1 at 00 00
Then I went into System Group #2 (to enable arm stay events)
System Group #2: 1
STAY 1st: 01 *
Stay 2nd: 00 *
That's it for the Report Code Programming.
Now for us folks that don't live and breathe Ademco alarms, the EVL3 is faking the 128BPT into thinking that a Long Range Radio (LRR) is attached to the system. The LRR is also called the communicator in the 128BPT manual. The 128BPT also has a phone dialer which we want to make sure is completely disabled (since the EVL3 is handling everything).
So remember: EVL3 = LRR = communicator
According to the 128BPT manual, the 128BPT will NOT use the LRR unless there is a Primary Subscriber Acct # for each partition. I verified this is the case: if the *32 is cleared, no events get sent to the EVL3/LRR.
So you need to go through each of your partitions and enter a non-zero value for the *32.
I had four partitions in my system, so I just entered the partition number as the *32 value for each partition. While we're in each partition, set the burglar alarm delay to zero too:
*91 1
*32 01 *
*88 0 *
*91 2
*32 02 *
*88 0 *
*91 3
*32 03 *
*88 0 *
*91 4
*32 04 *
*88 0 *
Disable dual reporting. We just want our events communicated to the EVL3:
*51 0 *
Make sure the dialer has no phone numbers lurking by clearing out the phone numbers. Also no reason for download numbers so I cleared them too:
*33 *
*34 *
*35 *
*36 *
*37 *
Use 4 Digit Style ContactID Format:
*45 1
Set the LRR delay to zero:
*56 0
Set the LRR as the primary communicator (instead of the built-in dialer):
*57 1
Set the LRR to enable all categories of reports:
*58 111111
Write it all out:
*99
That did it for me. One more step: even though I had enabled emails in the EyezON web portal (well hidden under Manage Contacts in the EyezON web portal IMHO), I was not getting any emails. The gmail spam filter was tossing them. So I had to go convince gmail they were not spam.
Now its all working. Hope this helps someone else.
The 128BPT is a real nice alarm panel. I have been very happy with it. I installed a Tuxedo touchscreen to tie in my bluetooth thermostats. Works slick.
And now I have my email notifications working through eyezON. THIS IS COOL!!!
I followed the great advice from Jim in the prior post but had to do a few things more. So here is the synopsis:
Go to #93 Report Code Programming. For every zone make sure the first digit is nonzero.
Report Code Prog: 1
Alarm, ID Digit: 1
Enter Zone No: 001
001 Report Code 1st: 01 * (or anything non-zero)
001 Report Code 2nd: 00 *
Do the above for all your zones.
Now you want to turn on reports for all the interesting events. This will generate the events that show up in your EyezON web portal. After a bit of playing around, I decided the only events I cared about (for now) are:
Closing (arm AWAY)
Opening (disarm)
Arm STAY
So in #93 Report Code Programming, go into System Group #1 (to enable arm away and disarm events)
System Group #1: 1
Close 1st: 01 *
Close 2nd: 00 *
Open 1st: 01 *
Open 2nd: 00 *
I left the rest of System Group #1 at 00 00
Then I went into System Group #2 (to enable arm stay events)
System Group #2: 1
STAY 1st: 01 *
Stay 2nd: 00 *
That's it for the Report Code Programming.
Now for us folks that don't live and breathe Ademco alarms, the EVL3 is faking the 128BPT into thinking that a Long Range Radio (LRR) is attached to the system. The LRR is also called the communicator in the 128BPT manual. The 128BPT also has a phone dialer which we want to make sure is completely disabled (since the EVL3 is handling everything).
So remember: EVL3 = LRR = communicator
According to the 128BPT manual, the 128BPT will NOT use the LRR unless there is a Primary Subscriber Acct # for each partition. I verified this is the case: if the *32 is cleared, no events get sent to the EVL3/LRR.
So you need to go through each of your partitions and enter a non-zero value for the *32.
I had four partitions in my system, so I just entered the partition number as the *32 value for each partition. While we're in each partition, set the burglar alarm delay to zero too:
*91 1
*32 01 *
*88 0 *
*91 2
*32 02 *
*88 0 *
*91 3
*32 03 *
*88 0 *
*91 4
*32 04 *
*88 0 *
Disable dual reporting. We just want our events communicated to the EVL3:
*51 0 *
Make sure the dialer has no phone numbers lurking by clearing out the phone numbers. Also no reason for download numbers so I cleared them too:
*33 *
*34 *
*35 *
*36 *
*37 *
Use 4 Digit Style ContactID Format:
*45 1
Set the LRR delay to zero:
*56 0
Set the LRR as the primary communicator (instead of the built-in dialer):
*57 1
Set the LRR to enable all categories of reports:
*58 111111
Write it all out:
*99
That did it for me. One more step: even though I had enabled emails in the EyezON web portal (well hidden under Manage Contacts in the EyezON web portal IMHO), I was not getting any emails. The gmail spam filter was tossing them. So I had to go convince gmail they were not spam.
Now its all working. Hope this helps someone else.
The 128BPT is a real nice alarm panel. I have been very happy with it. I installed a Tuxedo touchscreen to tie in my bluetooth thermostats. Works slick.
And now I have my email notifications working through eyezON. THIS IS COOL!!!
-
- Posts: 3
- Joined: Mon Jul 07, 2014 2:31 pm
Re: EV3 honeywell vista 128
I just wanted to add to this thread that the configuration here works well. I followed it pretty closely and have my panel working both with a Vera as well as the Eyez-On portal. The 128BPT is really quite a good panel. It's unfortunate that nearly all interfaces us only the keypad bus for interface because it has a lot of limitations. The serial port interface on the 128BPT offers many advantages since it was actually designed to support HA.
Anyhow, thanks to nwboson for documenting his setup because even though I'm very familiar with the Honeywell configurations it would have taken me a while to work all the details out.
One suggestion for the Eyez-On folks, it would be great to have a wiki setup or at least a "file" section where we could upload how-to docs and other information useful to uses. Searching through a forum and then getting chastised if one somehow doesn't find a bit of info that happens to be buried there is not user friendly. Such a tool would help your business. Oh, and thank you for publishing the TPI - without which none of this would be possible!
Cheers,
Ron
Anyhow, thanks to nwboson for documenting his setup because even though I'm very familiar with the Honeywell configurations it would have taken me a while to work all the details out.
One suggestion for the Eyez-On folks, it would be great to have a wiki setup or at least a "file" section where we could upload how-to docs and other information useful to uses. Searching through a forum and then getting chastised if one somehow doesn't find a bit of info that happens to be buried there is not user friendly. Such a tool would help your business. Oh, and thank you for publishing the TPI - without which none of this would be possible!
Cheers,
Ron
Re: EV3 honeywell vista 128
My question is there anyone who has heard of someone who has the EV3 working with a vista 128BPT??????