elvisimprsntr

Now that you are a disciple, spread the good word. If we can save at least one life from a horrible tragedy, our reward will be knowing we helped. [emoji120]

This is one of those examples. Never ever automatically close a garage door, regardless of what stop sensors are installed. There is a documented case where a small child fell, laying under the beam height, was crushed under the weight of the door which failed to reverse direction. The parents sued the Uncle, the manufacturer Sears, and the contractor who installed the garage door. Also take the situation where you park/stop your vehicle half way in the garage, with the beam under the vehicle. Even if the door will reverse direction, I'm sure it will still damage the vehicle. If I leave the garage door open, I send myself a notification. Then I confirm the door is clear with a live camera feed BEFORE manually closing the door. The rolling current date/time superimposed on the camera feed, by the camera itself and not a NVR, confirms the image is not stale. For manufacturers who provide the capability to automatically close a garage door, I suggest you read the fine print in the limited liability section. I also suggest you talk to your insurance company. I'm sure they will use it as an excuse to raise your rates or drop you altogether. My conscience is clear. Is yours?

Finally someone else with common sense! This has been one of my biggest arguments when I see people asking how to automatically close ones garage door, tap into their fire protection system, or people on RPi forums using their Rube Goldberg contraption to control their furnace or high voltage lighting. People will brush it off even after I post articles of fires, deaths, and homeowners getting sued. If nothing else, I have a clear conscience for warning people. Money and common sense doesn't always go together. Just because you can do something, doesn't mean you should.

You need to configure the KPL options to non button toggle on for A and non button toggle off for B.

Based on your symptoms, I suspect you assigned a static IP. Change your new router to use the old subnet, or connect your old router. The other option would be to change the subnet mask in your new router to 255.255.0.0, which will allow you to connect to the ISY. Any network scanner will then find the ISY IP address.

@felickz Did you assign a static IP in the ISY?

One of the other things I discovered is you also should update the GF variable initial value in your programs to the current state to prevent programs from executing when the ISY reboots an your MLHD updates the GF variable. My garage door seemed to open randomly until I did that.

When civil unrest gets to a certain point, I will setup a PIR motion tracking sentry. http://m.instructables.com/id/Autonomous-Paintball-Sentry-Gun/

@ryanmead83 Depends on your specific use of HA. Personally I use it as part of a 4 layered home protection. Deter, detect, delay, defend. Well actually 3 layers. The last layer doesn't require HA.

Personally I have no trouble hearing the buzzer on my W/D. If yours doesn't have one there is amazing device I found may work well. It's called a smartphone with a timer. Sorry I could not resist. Seems like a solution in search of a problem.

For anyone interested in controlling a ZM camera mode based on an ISY event while the ZM API is still a WIP, I figured out how to control the camera mode using ISY network resources with HTTP POST. I have ZM built in authentication enabled, thus needed to generate a cookie I could reuse in the ISY. curl -d "username=username&password=password&action=login&view=console" http://192.168.69.85/zm/index.php -c zm.cookie Then you can examine HTTP headers sent by the curl command to reverse engineer what needs to populated in the ISY. curl -v -d "view=none&action=function&mid=1&newFunction=Modect&newEnabled=1" http://192.168.69.85/zm/index.php -b zm.cookie * Hostname was NOT found in DNS cache * Trying 192.168.69.85... * Connected to 192.168.69.85 (192.168.69.85) port 80 (#0) > POST /zm/index.php HTTP/1.1 > User-Agent: curl/7.38.0 > Host: 192.168.69.85 > Accept: */* > Cookie: zmSkin=classic; ZMSESSID=************************* > Content-Length: 63 > Content-Type: application/x-www-form-urlencoded Below is what the ISY network resource module HTTP looks like. POST /zm/index.php HTTP/1.1 Host: 192.168.69.85:80 Content-Length: 63 User-Agent: curl/7.38.0 Content-Type: application/x-www-form-urlencoded Accept: */* Cookie: zmSkin=classic; ZMSESSID=************************** view=none&action=function&mid=1&newFunction=Modect&newEnabled=1 Let me know if there is a better method. Elvis.

Thanks for the update. If it is anything like the Harmony Link, even though the ISY controller is not added to its own activity screen, you can manually edit one of the other devices activity screens and add an ISY IR code button. The down side is you can't rename the ISY IR code buttons to something useful, even thru the MyHarmony site. I suspect one can add/fix an existing IR code, but that assumes you have an existing remote to TX the ISY IR codes.

And I have a 4 yo Harmony Link which I can one tap touch "Watch Movie" which sets up all my AV equipment and turns down the ISY lights. I ran Cat5 in the walls between my theater and living room to extend the IR blaster between rooms for the added bonus of one Link for two rooms. Link - $99 in 2011 Misc wire and keystone jacks - $20

http://www.insteon.com/support-knowledgebase/2015/7/31/control-insteon-devices-from-your-logitech-harmony-hub Based on my interpretation it appears the Harmony Hub communicates to the Insteon Hub thru SH cloud services. For the ISY to enjoy the same capabilities, UDI would have to lift their no cloud based dependency position and of course work with Logitech to define the API. I do know UDI is working on their own portal, so maybe they are softening. Update: Harmony does not work with all models of the Insteon Hub. Scroll to bottom. https://support.myharmony.com/en/harmony-experience-with-insteon

I think I figured it out with some help. Unfortunately ZM 1.26.5 I have installed from packages does not support the API. It's still a WIP even in 1.28.1, although I read someone was successful getting the API install by installing ZM from source. Ugh! POST /zm/api/monitors/1.json HTTP/1.1Host: 192.168.69.85:80 User-Agent: curl/7.37.1 Content-Type: application/x-www-form-urlencoded Content-Length: 47 Accept: */* Authorization: Basic *************************** Monitor[Function]=Monitor&Monitor[Enabled]:true

Sorry to revive a stale thread, but I have a ZoneMinder related question. BACKGROUND I recently looked at NVR solutions compatible with my existing infrastructure and IP cameras. Since I can't run new wires to all my locations coupled with the fact I did not want to scrap my existing IP cameras for P2P PoE cameras, I ended up repurposing a 5 year old Core 2 Quad machine as a ZM NVR and upgraded my router to a dual core AC1900 to handle the additional traffic. I got everything up and running fairly quickly and even purchased the ZmView native iOS app. Works like charm! I have three cameras, 2 exterior and 1 interior. I have set up ZM to MODECT (motion record only) mode to limit abuse on the hard drives. Now I find that I want to further limit the recoding to only when my Elk is armed. For example enable recording of all cameras in AWAY mode, but only exterior cameras in STAY mode. The ZM API documentation allows one to use CURL and JSON to change the state of each camera individually. https://github.com/ZoneMinder/ZoneMinder/blob/master/docs/api.rst#change-state-of-monitor-1 curl -XPOST http://server/zm/api/monitors/1.json -d "Monitor[Function]=Modect&Monitor[Enabled]:true" QUESTION Using the ISY Network Resources, how do I emulate the CURL command? I also have ZM authentication enabled, so I assume I would need to pass the ID/PW in. Thanks in advance Elvis UPDATE ZM apparently supports XML if that makes a difference. https://github.com/ZoneMinder/ZoneMinder/blob/master/docs/api.rst#examples Here be a list of examples. Some results may be truncated. You will see each URL ending in either .xml or .json. This is the format of the request, and it determines the format that any data returned to you will be in. I like json, however you can use xml if you'd like. (In all examples, replace 'server' with IP or hostname & port where ZoneMinder is running)

Sounds like FA going after a cash grab in the HA market with new products, which have backward compatibility issues. And another ill fated SmartHome product when FA removed onelink support from existing products. SH completely disconnected from FA product plans, leaving customers holding the bag. I'm liking my Kidde RemoteLync decision even more.

I don't own any FA smokes, but my interpretation is wireless interconnect is for homes which don't have the extra hardwired interconnect wire. Typically older homes before code required a hardwired interconnect. That might not be the same as onelink communication protocol. The SmokeBridge specifically says onelink alarms only.

I don't think wireless interconnect is same as onelink.

No battery backup built in, but nothing preventing you from connecting to a UPS When you enroll the device, you place it in a learning mode, at which point you are prompted to press the test button on one of your smokes furthest (all my smokes are hardwired interconnected) from the unit, then press the test button on a co alarm. I assume the device samples the signal to account for slight manufacturing variability or installation effects. Hopefully the sampled signal is used to reject false positives.

The Kidde RemoteLync is compatible with most smokes from any manufacturer after 1978. It monitors the audible alert from the smoke or co alarm. It does not use a proprietary RF signal like the First Alert and SmokeBridge. Yes it connects to your wifi, and uses cloud to send email and SMS messages. Not exactly sure how else you would propose any form of remote notification and control. No different than a Nest Protect, except that I don't have to spend $900 (9x100) to replace all my smokes/co alarms every 10 years as required by FPA/NEC. I can replace them with less expensive units for $90 (9x10). What I like about the Kidde RemoteLync is: 1. No need to tap into the hardwired interconnect signal 2. Works with any smoke or co manufactured after 1978 3. Does not require a home owner or tenant replace existing smokes/co The Kidde RemoteLync should not be used for primary detection and alert. If you read the ToU for the device it clearly states that. If you need a prime reliable notification with failover capability then this product clearly is not for you. I was offering the Kidde device as an alternative to the proprietary SafeAlert and SmokeBridge which some seem to have problems finding compatible smokes. Personally I would not use the SmokeBridge or any Insteon product to protect life or property. That is what I have an Elk for which has a commercial smoke detector connected to one zone.

Received my Kidde RemoteLync today. Took 2 minutes to set up. Works great! You do need either the iOS or Android app to enroll the device, but it can be set up to send email and/or SMS messages. Received a response from the support team, unfortunately there is no third party API. I'm sure some enterprising individual could reverse engineer it.

Another reason I don't use Insteon for security, or protect life or property. Lighting and convenience only.

The video claims it can send a notification to a PC which I assume is an email. I've got an inquiry into the product support team about a public or third party API.

I just ordered one. I am sure the Kiddie unit can be configured to send SMS messages which would be device independent. The app would only be for push notifications or to check manually check status. I'll update once my unit arrives.