MWareman

Thanks @Xathros - if you do find out I'd appreciate knowing. I really don't feel like hacking thru all of my programs without being able to devote a few hours to the experiment!

@Xathros, when you do the reset (parameter 255 I assume), does it clear the zwave network membership as well - or just reset the config parameters and metering totals?

Unless something changed, this is not the case. ISY does not proxy access to the cameras.

Important to note, there are workarounds needed for many MyQ compatible openers.... If that is the type of opener you have.

If a switched load turns on but not off, its usual that the load is generating noise that causes the off to fail. With no load, that's probably not the case here.

You are correct. I do this a lot.

I had a cable box and hdpvr prior to the home runs, and the component out was shut off. I had to use a device that pulled from HDMI, told the box there was a protected content path then sent the content out a component link (an HDFury). It was designed to be 'permanently affixed' to the receiving device to be license compliant, but it served me well prior to the prime devices. http://www.hdfury.com/hdmihdcp/

I think there was also a device that could detect an audio or video signal that could be used in this application as well. Personally, I gave up on the cable box to feed my MythTV by using two HDHomerun Prime boxes and cable cards. I haven't looked back! (cheaper too - Comcast give a credit for not using their cable box that's more than the monthly cost of two cable cards).

Messy, but cannot ISY (thru the network module) call its own rest interface under program control to accomplish this?

You control a KPL led by having the led be the responder of a scene, and then you call the scene. Scene members do not acknowledge commands. This is an Insteon scene limitation though - not an ISY or program limitation. If the light is more reliable from another device, it could indicate noise causing unreliable comms between your main PLM and the KPL with unreliable lights.

I use a reverse SSL proxy based on Apache running on a Linux system. Its 'free', but there is a fairly steep learning curve and you need a running (Linux, probably) system. Commercial solutions like Blue Iris may be able to help, but also need a running (Windows, in this case) system. Alternatively, hardware like Swann NVRs can receive the can data on your LAN and make it available to your mobile device with encryption. Cameras with SSL built into them can also be used securely without needing an external system to provide the security, but they tend to be much more expensive than the Foscams and clones.

I use Tinycam monitor on Android with good results (9 Foscams here). Just be aware of the lack of security if you port forward the camera for remote access, unless you invest in some other solution for secure remote access.

The foscams (and smarthome variants) don't do SSL, to if you port forward you are sending your password across the internet without encryption. Personally, I setup an SSL reverse proxy behind a wildcard certificate (with SNI enabled) to securely access my cameras.

My take is the request is valid and useful in the context requested, but detrimental to the way most of us currently use scenes. Not taking a side here, its just how I see it. In general, if there is a way to the solution that doesn't involve breaking the way others use the feature, then the change isn't likely to be accepted.

Try putting all KPL buttons in each scene, and setting the scene responder levels to what you want.

Thanks! I'll probably take a look and give their free 1 cam option a try.

This.

Exactly the thermostat I have, after having 4 failed warranty replacements of the Insteon one.

Is anyone using Sighthound? It claims to be able to locate and alert on people in camera streams rather than simply motion. I'm considering it....

Here is a link to the Word template: http://cache-m2.smarthome.com/manuals/12063_template.doc

Take your mini remote out of the scenes - but otherwise setup everything LeeG detailed. Then - you need programs triggered with the control function of the MiniRemote like this (psudo-code): If Control Mini B 'On' and Fan Off Then SceneFanLow On If Control Mini B 'On' and Fan Low Then SceneFanMedium On If Control Mini B 'On' and Fan Medium Then SceneFanHigh On If Control Mini B 'Off' and Fan High Then SceneFanMedium On If Control Mini B 'Off' and Fan Medium Then SceneFanLow On If Control Mini B 'Off' and Fan Low Then SceneFanOff On After this - your B button 'On' will increase your fan speed - and 'Off' will decrease - in both cases by turning the appropriate scene on. As each scene is turned ON, it will set the KPL buttons to be correct for the state.

Upgrade to 4.2.23. There is a fix for non-pro and MobiLinc SSL.

What version is your ISY? Is it a PRO or non-PRO? Google removed SSLv3 from Android 5.x, and older non-PRO ISY firmware only supports SSLv3.

@QuietMinded, please only use those parameters if that is the correct device! There are other Aeon devices with energy monitor capabilities, and (at least he clamp meter) uses very different parameters for things. For instance, parameter 1 sets the input voltage for the wattage calculation. The Pepper1 site should detail what you need though. Michael.

Got my Echo invite (finally) yesterday. Ordered right away, and they then tell me there is a 3 month delay until shipping. Hopefully, there will be an api figured out by the time I receive mine!