Elk and multiple Areas

[drvnbysound]

I do know that OUT1 is univeral to ALL Areas. So any/all voice announcements would be made via OUT1.
 
It was because of this that I specifically installed the TWA in the application, because the home owner did not want Area 2 announcements at Area 1 keypads and vice versa... except for in the MBR (where they wanted all announcements). Thus I connected the MBR speaker to OUT1, and all other keypads to the TWA and I selectively turn the associated outputs on/off to mute the appropriate zone based on the message.
 
Having said all of that, it's definitely odd that an Area 1 voice announcement is made alerting of zone status as soon as the Area 2 exit delay ends. I can verify this does not occur on the system mentioned above, but it will likely be Friday or Saturday before I am over there again.

 

[mikefamig]

I do know that OUT1 is univeral to ALL Areas. So any/all voice announcements would be made via OUT1.
 
It was because of this that I specifically installed the TWA in the application, because the home owner did not want Area 2 announcements at Area 1 keypads and vice versa... except for in the MBR (where they wanted all announcements). Thus I connected the MBR speaker to OUT1, and all other keypads to the TWA and I selectively turn the associated outputs on/off to mute the appropriate zone based on the message.
 
Having said all of that, it's definitely odd that an Area 1 voice announcement is made alerting of zone status as soon as the Area 2 exit delay ends. I can verify this does not occur on the system mentioned above, but it will likely be Friday or Saturday before I am over there again.

You needn't go to the trouble but I appreciate the offer.
 
My system has had zero data bus errors in the last five hours or so since I disconnected the wireless adapter and the errant chime has disappeared. I am pretty sure that there is a problem with the wireless adapter whether it be it's wiring or the adapter itself. The symptom comes and goes with the adapter.
 
If I still have zero data bus errors in the morning and the chime is still working correctly I will put a new rj-45 on the ethernet cable to the wireless and re-test.
 
Mike.

 

[Del91574]

Sounds like a bug.
 
I have voice announcements running on my system with multiple areas and the second area doesn't annunciate within the main house. I don't use voice chime however....it may be necessary to use the TWA to drive the audio instead and then use rules to turn the matrix on for chime operation and only specific events.

 

[mikefamig]

The system ran all night with zero errors on the data bus and no errant chimes so far. Today I'll make a new wire to connect the wireless adapter to the control as it is only a few feet long and easy to replace. If the wireless adapter still causes errors and troubles after that then I'm all done with the 2way wireless until Elk can supply a solution.
 
Mike.
 
EDIT:
 
I'm a little embarrassed but I was wrong to say that the errant chime has disappeared. Yes the system has run all night with zero errors but the system still chimes a violated zone in area1 when I arm area2 if there is indeed a a zone violated. It was cool outside last night and my wife closed all of the windows so there were no violated zones for the system to chime which caused my confusion. Elk tech support tells me that is it true that the system will do this and they are aware of it.
 
So why is it that drvnbysound here reports to me that his system does not do this? Do we maybe have different firmware versions?
 
My control is version 5.3.0.

 

[mikefamig]

Would one of yo guys be willing to do me a service with a quick test at your house?
 
Could you
1 enable voice chime at each of the keyapds in two areas
2 leave a chime-enabled zone violated in area 1
3 arm area2 away
 
In my system I get the armed away voice chime and then at the ten second mark I get the message that the delay is about to expire and then after the delay expires it tells me that the zone that the zone that I left violated in area1 is violated.
 
Elk tells me that this is what the system does. They don't call it an error and they don't say that it makes sense to do this but they say that it is just the way the system behaves right now. If this is true then your systems should do the same, no? And if this is true then why am I the first and only one to notice it?
 
Now all of the above aside I still have the problem that my system would sometimes just call out a violated zone at random and it did this just a couple of days ago when I had the wireless adapter enabled.It has not done this since I removed the wireless adapter. but it has only been a short while and due to cool weather the windows and doors have been closed overnight.
 
If you could do this for me it would give me at least one known entity and I can accept the chime as a constant but right now I am lost in a butt-load of unknowns which makes it impossible to go forward. Elk telling me that this is the way the system behaves and you guys telling me the opposite just adds to my confusion. My control version is 5.3.0 which may be relevant.
 
Mike.

 

[mikefamig]

I do know that OUT1 is univeral to ALL Areas. So any/all voice announcements would be made via OUT1.
 
It was because of this that I specifically installed the TWA in the application, because the home owner did not want Area 2 announcements at Area 1 keypads and vice versa... except for in the MBR (where they wanted all announcements). Thus I connected the MBR speaker to OUT1, and all other keypads to the TWA and I selectively turn the associated outputs on/off to mute the appropriate zone based on the message.
 
Having said all of that, it's definitely odd that an Area 1 voice announcement is made alerting of zone status as soon as the Area 2 exit delay ends. I can verify this does not occur on the system mentioned above, but it will likely be Friday or Saturday before I am over there again.

 
Your statement above that this does not happen on your system makes me think that we had some settig in the system adjusted differently. Do you have voice chime turned on at both keypads and are voice chimes enabled on all zones involved??
 
Mike.

 

[drvnbysound]

Voice chime is enabled for all zones except motion detectors. I don't think the Chime function was enabled at either keypad during the times I was testing the arming function, but the system still reports the standard ARMED/DISARMED messages. By default, they don't use the voice chime function during the day - sometimes the tone. They generally only enable the voice chime (sometimes) at night.

 

[mikefamig]

Voice chime is enabled for all zones except motion detectors. I don't think the Chime function was enabled at either keypad during the times I was testing the arming function, but the system still reports the standard ARMED/DISARMED messages. By default, they don't use the voice chime function during the day - sometimes the tone. They generally only enable the voice chime (sometimes) at night.

I believe that that would make the difference.
 
Mike.