Am I missing something? Elk M1 System

We are about to move into a new house that has been pre-wired for security, cameras, automation...per my specs...wired contact at all int./ext doors, windows, 2 int. sirens, 5 keypad locations(only asked for 4), 28" security can, 2 motions, etc.

My intent here is to install an elk m1 as the backbone for security and automation system, and at some point in the near future adding ISY or RadioRA2. We will not have a landline telephone, just ooma/google voice VoIP.

My current shopping list includes an elk m1 kit with wireless, additional keypads, input expander, ethernet interface, databus hub, and doorbell/telephone detector. I have an uplink 4350 that I plan to take from our current house and repurpose for primary reporting...if possible.

I feel like there is something big missing from my list, and would greatly appreciate any input.

Thanks!!
 
Will you have surge supression on your input power?

While not big items, do you have mounting provisions for all accessory boards? How will you mount the XEP?

The input expander comes with the SWGs. The DBH comes with the SWP3.
 
You have the basics covered - control, keypad, ethernet adapter but you didn't mention any window or door sensors or noise makers like speakers and sirens.
 
Mike.
 
I'm not sure if anyone here can tell you what you are "missing" in your vision.  Besides, that would generally be a question to ask BEFORE you finish the pre-wire.  After the walls go up, the only real question is how to get the wires through for the items you did forget.
 
Thanks for the quick responses y'all!!!!
 
 
drvnbysound said:
Will you have surge supression on your input power? While not big items, do you have mounting provisions for all accessory boards? How will you mount the XEP? The input expander comes with the SWGs. The DBH comes with the SWP3.
ahhh...surge supression...there's one thing I forgot...oh and glides for the XEP.    Guess I'll add a set of SWGs, a 950, and a SWP to the list.  
 
 
mikefamig said:
You have the basics covered - control, keypad, ethernet adapter but you didn't mention any window or door sensors or noise makers like speakers and sirens.
 
Mike.
...and an additional speaker.  
 
 
ano said:
I'm not sure if anyone here can tell you what you are "missing" in your vision.  Besides, that would generally be a question to ask BEFORE you finish the pre-wire.  After the walls go up, the only real question is how to get the wires through for the items you did forget.
 
I think i had them wire for everything...except shades...wifey didn't see the appeal in having shades open and close automatically.  
 
Aside from sensors, sirens and keypads, what else would need to be wired?  
 
Sensors cover a lot of ground, I assume you have doors and window and probably smoke but there are also carbon monoxide and  water and temperature and motion etc etc, Take a look at a GE catalog for a variety of sensors.
 
And you may like door strikes but then that is more automation than security.
 
Mike.
 
You might wire for in wall touchscreen consoles if you are into that sort of thing. 
 
That said if you do go with touch consoles leave one keypad in place or in a place you can get to.
 
Always to have more than less wires.  Wire for everything you will need; then wire for things you may need or want in the future.
 
CCTV is a popular option.  I wired for satellite in one home build because I didn't want to see any wires outside.  I also added coaxial to a centrally located com closest and catxx from the same area to the closet.  This provided me with cable, satellite and telephone from the outside to the central closet.  I have gone from satellite to FIOS in said house.  If you want to automate irrigation then wire for that.  Multimedia room planning stuff can be included.
 
mikefamig said:
Sensors cover a lot of ground, I assume you have doors and window and probably smoke but there are also carbon monoxide and  water and temperature and motion etc etc, Take a look at a GE catalog for a variety of sensors.
 
And you may like door strikes but then that is more automation than security.
 
Mike.
I was hoping the ELK wireless setup would help me cover what i missed as it pertains to sensors, but I am now seeing you've had some issues with it...Hopefully your RMA turns up a defective unit instead of a product design problem.  
 
 
pete_c said:
You might wire for in wall touchscreen consoles if you are into that sort of thing. 
 
That said if you do go with touch consoles leave one keypad in place or in a place you can get to.
 
Always to have more than less wires.  Wire for everything you will need; then wire for things you may need or want in the future.
 
CCTV is a popular option.  I wired for satellite in one home build because I didn't want to see any wires outside.  I also added coaxial to a centrally located com closest and catxx from the same area to the closet.  This provided me with cable, satellite and telephone from the outside to the central closet.  I have gone from satellite to FIOS in said house.  If you want to automate irrigation then wire for that.  Multimedia room planning stuff can be included.
Great minds think alike....I have 2 cat5e and 2 coax run to each of the TV locations, and 1 cat5e and 4-wire run to each keypad location.  
 
I am working out the camera systems, and am hoping for a better solution by the time I can afford it.  I had them wire 4 exterior camera locations with cat 5e and a cctv rg59/power....wanted interior cameras too, but wifey vetoed again.  if I were to stumble across a pile of cash, I'd put up Vivotek fisheye POE cameras, and a Vivotek NVR with HDMI out to a HDMI-to-QAM modulator (VECOAX?).  The hope is this would let me pipe the cameras to all the TV's picture-in-picture via coax, and/or add it to the channels in the Windows Media Center/Ceton setup I have for TV.  
 
Thanks again for all the great input...making me feel better about my "system design".
 
The hope is this would let me pipe the cameras to all the TV's picture-in-picture via coax, and/or add it to the channels in the Windows Media Center/Ceton setup I have for TV.
 
Here over the years have gone from Windows Media Center to XBMC.  You can run XBMC on Wintel, Linux or Android.  Almost all of the themes / plugins for each OS.
 
Just wrote up a quickie methodology to do an overlay of the CCTV cams into XBMC.  Its kind of neat looking as its a sort of translucent overlay that slides over a section of the screen and stays up for whatever time you want.
 
It is here:
 
http://cocoontech.com/forums/blog/29/entry-436-xbmc-security-cam-overlay-script/
 
The little FAQ states that they are redoing all of their documentation to remove the older XBMC logo to go to the Kodi logo.
 
kodi-splash-600x336.png

 

 
We are excited to announce that the media center software we’ve all loved for so many years will have a new name, starting with version 14. Instead of XBMC 14, we’d like to introduce you to Kodi 14.
 
Since 2002, the software known as XBMC has gone through three namings. First, it was called Xbox Media Player. Upon realizing that it did a bit more than your traditional media player, in 2004 the development team elected to rename it Xbox Media Center. A mere 4 years later in 2008, the team once again elected to rename the software to simply XBMC, given that it had moved on from its original roots on the Xbox. Support for the Xbox was dropped shortly thereafter. Today it’s all happening one last time.
 
Real World Problems
 
Six years have passed since the Xbox Media Center became XBMC, and simply put, “XBMC” fits less now than it did even in 2008. The software only barely runs on the original Xbox, and then only because some clever developers are still hacking on that platform. It has never run on the Xbox 360 or Xbox One.
Furthermore, while the software still acts as a media center, it also hosts addons, loads games, streams content to and from numerous devices, and can ultimately act as a complete replacement for whatever platform it is hosted on. Indeed, XBMC today is far more an Entertainment Center than a simple Media Center.
In essence both the “XB” and “MC” simply don’t make a whole lot of sense any more.
 
Legal Problems
 
Beyond the nonsensical nature of the software’s name, there is a secondary issue. Because “XBMC” was originally based on the name Xbox, the developers of the software (that’s us) have never had any sort of legal control over the use of its name, which has resulted in a whole slew of problems.
In the past few years, we have seen the mass confusion that resulted from this lack of control first hand. Users have been fooled into wasting money buying boxes running hacked and typically broken versions of XBMC. News sites and blogs have gotten caught in confusing language numerous times. Unrelated fan communities, often founded under the best of intentions, have found themselves under attack, simply because no guidelines existed to simplify the process of clearly distinguishing themselves from the XBMC Foundation. What’s more, the Foundation itself and all of its developers have always operated under a potential legal threat from other companies that did have a legal trademark in a similar name. And that legal threat has actually gotten more problematic in recent years.
Because all these problems have been getting more and more pronounced, the Foundation decided to review its options with the help of the legal team at the Software Freedom Law Center. In the end, it was decided renaming the software that we all love so much was the most realistic solution. We’ve done it twice before. We believe this time Kodi will be the name we can keep forever.
 
Results of the new name Kodi
 
The average user will see little difference with the new Kodi. The software will remain the same. Users will get to keep using the software however they like. The code will remain licensed under the GPL 2.0. We even intend to stick with our current numbering scheme. Our next release will be titled Kodi 14. Indeed, the most significant difference for most people will be a slightly altered splash screen on boot up.
For companies, fan sites, and add-on developer sites, this name change should actually make work substantially easier. The XBMC Foundation has elected to wholesale adopt the policies of the Mozilla Foundation with regards to distribution and trademark licensing. For more information for web hosts and hardware vendors, see our Trademark Use FAQ (currently a work in progress). Simply put we are happy to remain incredibly permissive with the 3rd Party use of the Kodi name, so long as that use doesn’t confuse other users and the community. The FAQ and Trademark Policy should help you navigate exactly what “confusing” means to us.
 
The Last XBMC Shirt Ever
 
Because of your generosity in t-shirt sales, straight-up donations, and word-of-mouth evangelizing, this project has lasted for 12 years and through four different names, and with your help, we all believe it can last twice that long again. So we figured we’d offer a t-shirt to commemorate the name change.
 
There’s only one thing. The image at the top of this article is not the final logo. We are working with doghousemedia to truly realize an awesome logo, and we aren’t quite there yet.
 
So instead of offering a bit of swag with the new name, we figured we’d offer the exact opposite. This is it.
 
The last XBMC shirt or related piece of merchandise we’re ever going to sell.
 
Conclusion
 
There’s still a long ways to go in the renaming process. A ton of code has to be changed to reflect the new name. So many websites, webpages, social networks, and other things have to be updated. Much of the trademark legalese needs to be reviewed by the lawyers and government officials. The logo has to be finished. Needless to say, the upcoming Kodi developers conference this year is certainly going to be intense as we work through these issues. But we believe that with your support and the support of the whole community, Kodi, the media center or entertainment platform or whatever you choose to call it that we’ve all come to love will be even stronger than it was before.
 
Thank you all for your support, now and in the future. In the comments below, we’d love to hear your thoughts, whether they be about how you first discovered XBMC/Xbox Media Center/Xbox Media Player, or about what you think of the new name.
 
Kodi
 
Here settled on the little Aopen Digital Engines connected via Gb with HD outputs running XBMC / Ubuntu 14.04. 
 
I have recently converted them all to small SSD drives and they are doing fine.  Historically did utilize MS Media Center and still have a few devices around the house that were used for Media Center.  They are all off these days. 
 
You do not need to know Linux to use XBMC as most of the management pieces are in the Kodi/XBMC GUI.
 
I would still like to try an ARM based CPU approach set up using a wired / POE configuration sometime in the near future. 
 
It is most amazing to me that these guys replaced the original Android OS (unnecessary fluff) in those little sticks with Linux and turned the sticks into XBMC only Linux devices with better and faster graphics than the Android base on them.
 
I looked into using XBMC a couple years ago, and it seemed like I couldn't get a PVR backend to work with copy-once content.  I am about to retire an old WMC PC and will have to  use it for testing XBMC/Kodi in order to verify stability and wifeproofness.  
 
Back
Top