As I mentioned in a previous post, the SECU16I that I've been using to provide motion and contact closure inputs to HomeSeer has been extremely reliable and fast.
This has caused me to wonder if I shouldn't try to implement the Leopard and adjunct SECU16Is as the home alarm system I've been dragging my feet on implementing.
Oh, sure, I've heard the arguements "I'd rather have a dedicated system..." but this is a firm-ware based product that seems pretty consistent as long as it has power to it - which I can pretty easily assure with appropriate DC batteries.
Does anyone have any feedback on making this implementation? Have you tried it? Have you considered it? Have you (or have seen any) code to do it?
Final question, on a different - but somewhat related - issue: is there a way to ensure that an appropriate piece of code is loaded in a Leopard/Ocelot even if power is lost then restored? Obviously, this could become important in the above case.
Thanks, all.
-Gregory
This has caused me to wonder if I shouldn't try to implement the Leopard and adjunct SECU16Is as the home alarm system I've been dragging my feet on implementing.
Oh, sure, I've heard the arguements "I'd rather have a dedicated system..." but this is a firm-ware based product that seems pretty consistent as long as it has power to it - which I can pretty easily assure with appropriate DC batteries.
Does anyone have any feedback on making this implementation? Have you tried it? Have you considered it? Have you (or have seen any) code to do it?
Final question, on a different - but somewhat related - issue: is there a way to ensure that an appropriate piece of code is loaded in a Leopard/Ocelot even if power is lost then restored? Obviously, this could become important in the above case.
Thanks, all.
-Gregory
Comment