TrojanHorse

Yes to Stu [emoji106] Sorry for double post Sent from my iPhone using Tapatalk

Sent from my iPhone using Tapatalk

Typically smartphone access is from an app, not directly into the admin console. Enabling the ISY option for internet access is not required if you either use port forwarding or a VPN to communicate with the ISY when off your LAN. I believe you need to go this port forwarding or VPN route to use an app. If I recall, some consider that option to not be the best way to access ISY remotely? So you use the console to configure the system, then use an app to drive it. You can control scenes, devices, programs etc from an app. I use mobilinc, and it's pretty good for iOS. But for me they need to enable a way to backup the settings before I can fully recommend. Sent from my iPhone using Tapatalk

As long as you get the visor clip you should be okay Just 'cause this can be done, should it? Seems to me my GD opener has better range than insteon. I use my Elk to confirm GD status and soldered a standard Home Depot transmitter to a wired relay for "remote access" (I need battery backup here for the transmitter (cordless phone battery?) but I can start another thread) Are you planning to use iolinc to control? Sent from my iPhone using Tapatalk

Are you using parentheses in the IF statement? Seems like you would want parentheses around the motion statements. Find them on the Right hand side of admin console when editing program if memory serves Sent from my iPhone using Tapatalk

What about this as a cheap option? https://www.amazon.com/Liquid-Flow-Meter-Plastic-Threaded/dp/B00K0TFZN8#productDescription_secondary_view_div_1475601113732 I can't vouch for it but stumbled upon this. Sent from my iPhone using Tapatalk

Thanks Teken. I've read many of your posts here over the past couple years and I agree completely on the use of scenes. The FanLincs might be the sole exception I have at my house. It adds some complication, but (assuming ISY is working...so far so good) it works as expected, regardless of the length or number of button presses. I've enjoyed setting up my Insteon, ISY, ELK etc. and feel that it's a very solid system now. But candidly, this is one spot where Insteon sort of "fell down" for me was when controlling their FanLincs. Especially since Smarthome suggests this combination (and sells packages of custom buttons for this application) but doesn't address this underlying issue. Fast ON / Fast Off (FOFO) to me is a lighting concept and doesn't make as much sense for fans or other devices. In my view, using programs kept me closer to the principle of "works as expected". OT, but the "FOFO" makes me scared to try the garage door IOLinc setup - I'll stick with the Elk relay / soldered transmitter combo. What happens when the door is dimmed or turned Fast OFF? Just kidding, but if Insteon is going to design new devices, I would like to see a way to disable FOFO somehow in the hardware.

Thanks for the reminder - that will be helpful to keep in mind as I continue to tweak my setup (I believe you're referring to button definitions of toggle-on, toggle-off, always on, always off) But I think the problem I describe would still exist if for example I have a KPL button labeled "Fan low" that's linked via scene to the FanLinc. Let's say I define that button as Always On (that's maybe the best choice referencing page 9 in the manual: http://cache.insteon.com/pdf/2486D.pdf ?), a double-tap on this button would still turn the Fanlinc to "fast" / "high". Is there a way to avoid this without using programs? I'd love to be told that I'm wrong here or missing something since the simple scene setup has its benefits. Now, one could say "just don't double-tap the button", but I think I was also getting unexpected behavior if the button was held rather than quickly pressed. (I can't recall exactly; it's been a year since I made the change from scenes to programs). I really am hoping to be told I'm wrong here, but if not, for me the programs prevent questions like - "you spent how much on this system and the "Fan Low" button sometimes makes it go full speed?

Hopefully this doesn't steer too far from the OP. I only do this for the FanLinc. I am using scenes for the previous 3-way switches and for all living room or all outdoor, etc which works well for the lighting (no delay is key here IMHO) I only did this for the FanLinc and KPLs since I have custom buttons that say "fan off" for instance, and I don't want that to turn the fan on high if that button is double tapped. I couldn't accept that nor did I want to explain to my wife or guests for instance that pressing the off button twice would actually turn it on full blast. The programmatic approach seemed to be the only way to prevent that behavior. Similarly, if for example I had a button that was intended to turn off all the lights I would probably do that with a program rather than linking that button to a scene, so that double tapping the "all lights off" button would never do the exact opposite of what I expected. I would have the program turn off the scene probably (rather than have the program turn off individual lights) but I wouldn't link this scene to the keypad. The keypad would instead trigger a program. I wish there was a way to disable the fast on / fast off functionality for a particular switch but I don't believe that's possible so for me this was an acceptable workaround. The half-second delay doesn't bother me when we're talking about the fan speed. Sent from my iPhone using Tapatalk

I have 3 fanlincs with kpl's here using the 4 middle buttons for high medium low and off. All good advice here. Others might have better ideas, but I might suggest that you consider running the fan using an ISY program rather than insteon scene linking*. Reason for me was that to my knowledge the FAST ON / FAST OFF commands are inherent to insteon switches. If they can't be disabled, a double click on the off button would turn the fan on high. So a double tap on any linked KPL button would always toggle the fan from high to off. Not ideal, especially for guests so I went with programs instead. The cons I've noticed to this programmatic approach are: 1, a small delay for the fan to respond and 2, in the event of power outage you will need these fanlinc programs to restart the fan. *I still set up a scene so that only a single fan mode is illuminated on the KPL, if that makes sense. Sent from my iPhone using Tapatalk

Curious, why would you leave the ISY without insteon? Leaving security system? Sent from my iPhone using Tapatalk

Same here. Use them for automation and convenience. These are NOT security devices but they work well for a custom motion light and to receive notifications of motion outside. Best thing is they are quick to deploy and can be moved easily to find the best location. Survived 2 years in MN winters. Replacing batteries now and will see how long those last, but the units have survived thus far. Sent from my iPhone using Tapatalk

Here in MN cold winters with wind and snow I use the insteon outdoor on/off modules for Christmas lights and other things. No problems. I might suggest you try using this same outdoor linc if you can weatherproof the connection to the deck lighting transformer. Sent from my iPhone using Tapatalk