NextAlarm

I understood the sensors used by Nextalarm are Visonics, then check the Visonic receiver at www.rfxcom.com.
The RFXCOM USB Visonic receiver has also a W800 compatible mode where all Visonic sensor and keyfob codes are translated to X10 security format.
 
We really don't have a firm timeframe for the Elk native Internet support, but we also didn't know how much interest there was in it. I can't promise anything, but I'll show this thread around and I'll post when I have more information.
 
We really don't have a firm timeframe for the Elk native Internet support, but we also didn't know how much interest there was in it. I can't promise anything, but I'll show this thread around and I'll post when I have more information

I beleive other manufacturers communicate with the same receiver/line card as the ELK. TCP/IP is also the direction that the industry will go in. I would also think in the long run its more cost effective for the CS to use this format.
 
Dan_NA said:
We really don't have a firm timeframe for the Elk native Internet support, but we also didn't know how much interest there was in it. I can't promise anything, but I'll show this thread around and I'll post when I have more information.
I am also not aware of any other monitoring services that work with the Elk native Internet support. You know what they say about the first kid on block to have something! :lol:
 
toymaster458 said:
You know what they say about the first kid on block to have something! :lol:
Yes, the big kids come over, beat the snot out of him, and take it :D . Kidding aside I'm glad I started this thread. I see nothing but good things coming and it brought Dan out of the woodwork.
 
Dan_NA said:
We really don't have a firm timeframe for the Elk native Internet support, but we also didn't know how much interest there was in it. I can't promise anything, but I'll show this thread around and I'll post when I have more information.
I don't even know what it is, but if everyone else is getting it, i'll be damned if I'm the last one with it.

Count me in!
 
Dan_NA said:
We really don't have a firm timeframe for the Elk native Internet support, but we also didn't know how much interest there was in it.
I had an online chat with one of your support people (for a different reason) several months ago, and was given the impression you guys are actively working on that. I'll be really disappointed if it ends up not coming around soon - I'm limping along in SIA mode waiting for it, since ContactID doesn't work well with my VoIP. I think you may find quite a few new customers if you roll it out, and you may find yourself losing quite a few if someone beats you to the punch.
 
I think you may find quite a few new customers if you roll it out, and you may find yourself losing quite a few if someone beats you to the punch.

I agree.... the first CS that is ready will probably get my business. I know someone from Next Alarm was on this board last year or earlier this year and said they were working on it. I have been dying to get a CS hookup through my ethernet adaptor and would sign up tonight if it was available.

Doesnt the GE ethernet setup also communicate with the same receiver/line card as the ELK? Between the two there should be tons of business.
 
Dan:

When are we going to see NextAlarm take advantage of the two-way talk/listen feature between the ELK M1 and the CS? I'm wiring for it now and SentryNet is trying to woo my customers to them. I have a conference call with SentryNet on Monday to discuss it.
 
Two-way voice for all systems that support it is coming very soon, even over ABN. I would expect to see this within two months.
 
Dan_NA said:
Two-way voice for all systems that support it is coming very soon, even over ABN. I would expect to see this within two months.
Great news. I just signed one of my customers up with NextAlarm on Tuesday. I guess SentryNet will have to wait. Two-way voice is a nice feature.
 
Dan:

We need to see account numbers sent with each email or SMS notification. If you are monitoring multiple accounts you cannot tell which one is sending a periodic test signal, alarm signal, etc. Thanks.
 
Dan:

I have an activated account on NextAlarm that is on permanent test. The central station dispatched anyway, against my instructions and NextAlarm's written confirmation that the system was log only. It appears that the central station is a separate entity from NextAlarm and the blame game is beginning. Can you clarify this confusion between the CS and NextAlarm? Thanks.
 
Hi,

We are very closely tied to our central stations, but we are different entities. We use General Monitoring Services, which is in California, and Amcest Nationwide Monitoring, which is in New Jersey. We also offer service in Canada through BPG, in Montreal.

I can't really address specific accounts in a public forum, but generally speaking, our operators do err on the side of caution in these cases (i.e. they'll tend to dispatch rather than not dispatch if there's any doubt), so I apologize for the inconvenience. If you let us know through the customer service ticket system, we can fix the problem, if it hasn't been already.
 
Dan

I'm currently a customer of NextAlarm, however, this raises a concern regarding local law enforcement being dispatched for "false" alarm. In my jurisdiction if there are two false alarm per year then I'm being force to pay a fine.

If a person were to perform a monthly testing on the system and notify the CS via phone or website and police is still being dispatched then who is going to pay for the fine. Worse yet in my jurisdiction after third false alarm in a year then the system is going to be verified and sign off by an independent dealer. In my case I'm DIY and don't want to pay the dealer to verify.
 
Back
Top