lilyoyo1

When I built my house that's why I went with the Moen over Kohler. The way it looked, I figured if one were to ever be supported it would be them. Enough time has passed that I highly doubt either is working to expand either product. I will say, if someone ever releases a product that is more open, I'd rip the Moen out in a heartbeat. The important part is that the infrastructure is in place

Its a great system. I just wish they would open it up a lot more. Im not a big fan of using apps.

Each technology has its own pros and cons. Personally, I feel insteon is better than zwave with the ISY. However I do use a combination of the 2 protocols. I prefer Insteon switches over zwave and zwave (fibaro) sensors over insteon sensors. For repeating zwave signals, I use the Cooper aspire outlets. Due to being recessed, you may need more than you want to invest for range but I have not issues. Many people will get the aetec Siren/chime to repeat zwave signals. Both work really well, but I'm simply not a fan of wall worts. It's Paramount that you have a full mesh network regardless of protocol to ensure reliable communication.

I'd go with Oberkc suggestion. Add all of the devices you want controlled to a single scene (as responders) and simply write a program that turns the scene off at 10 like you want.

Not yet. I've heard rumors that say they are working on it with Alexa but I have yet to see anything geared towards that as of yet. They won't even release the api so people can code their own systems

I have the ecobee3 thermostats. While mine are not controlled by my ISY they can be. For my use, it does all that I need for it to do on it's on. They also work with Google home and Alexa so regardless of which one you use you would be ok.

I factory reset, test, and add my devices to the ISY prior to installing them. That way I know the switch is good prior to the installation so that if something doesnt work afterwards, Im not troubleshooting a bad device. Once everything is in there, I run a backup of that configuration so that if I ever want to start fresh, I can run that backup instead of having to re-add all of the devices back into the ISY.

I understand that. Most of my outlets are smart outlets too whether it be zwave or insteon. I didn't want to have to pick and choose locations to control things from. The insteon outlets are too tight like Teken said. I actually prefer the Cooper zwave outlets (except for places I need the dual outlets). They aren't nearly as tight.

Never had that happen but why plug it into an outlet that already does the same thing?

Any program that I have disabled automatically re-enables itself. For example, my entertainment button will disable my flood light motion programs. Turning that button off will re-enable the program as well as a timed program just in case the outside lights were left on for some reason.

There are features even the hub doesn't take advantage of.

Newer devices have this capability for some time. What firmware/UI are you running? If you click on your device and go to it's options, it can be found there

I wouldn't call Alexa or home AI. Especially based off of how the companies themselves talk up AI and machine learning. Neither device does either one. IMO they are simply responding to user input. For me, AI is akin to a computer learning a persons playing style to beat them at chess. In the automation world, it would be it learning my actions and acting accordingly without me asking. For example, it would learn that I enter my bedroom at certain times and automatically set it up to go to bed. Other times it would know I'm just passing through and do the actions for that. Alexa nor home does those things on it's on. You have to tell it to run a program that you have pre-written (less capable with other systems). In the end, they are no more than glorified remotes.

What is happening today is nothing compared to where the industry can/will be in 15 years let alone 25. It's all new for Mass consumption and adoption (for those that need things said specifically). 20 years ago we couldn't imagine having mini computers in our pockets. The same with what's happening now. In time we will get to the point of a proactive rather than reactive system

In answer to your question im 41. I grew up with computers and X10 as my dad was a programmer from the main frame days. As far back as I can remember, all I have known are computers. Yes the technology has been around for decades. However it was not useable for the majority of people. If you want to be technical about things yes it's been around for decades but the reality of what what systems are capable of doing today is in it's early stages. Back in the early days, what we are doing now was not available to the masses. We are now at a point where consumers can adopt automation technology with ease and yes that part is in it's early stages. We're all intelligent people here. We don't have to try to make ourselves feel more intelligent by correcting a point that the avg person can comprehend.

Both devices need to be controllers in your scene. That way if either is turned on the other responds accordingly and keeps its status in place

Based off certain situations I am able to turn my flood lights on or off without worrying about the motion sensor triggering them when I don't want it to. For example, my entertainment scene will set all the lights on so the outside of the house is completely lit up. That way if people walk through the yard, driveway, etc. they can see and I dont have to worry about any motion sensors timing out afterwards which would then turn off the light. We also get strong storms out here. Since I have a lot of trees around my property, when the wind kicks up, they can sway enough to trigger my lights. A quick double tap temporarily disables my programs from running so the light isnt constantly being triggered

I have standard flood lights wired to an insteon inlinelinc module and motion sensors mounted under it. I found I have many more options this way than by using standard light with a motion sensor built into it.

My method is only for you to control via the app. It is in addition to not a replacement for your current approach

I would write a program based on the control of the 2635 pretty much the same way you wrote it for the kpl. Instead of using the scene you would simply control the device from the app. You could then write a program that turns on the kpl button based on the status of the 2635 changing

The group allows you to simply say turn your lights on/off without having to say what room you are in. The old way you had to specify which room. How else would the system know what room you are specifically talking about? Keep in mind this is still the early stages of automation. Things will take time before our systems know exactly what we are referring to. Note, you can still use spoken commands if you want to turn off another set of light. For example. If you're in the livingroom and want to turn off those lights, simply say turn off the lights. If you want to turn off the kitchen. Lights while in your livingroom, then you would say, turn off the kitchen lights

Sounds cool but I found receiving a text message much simpler since I don't have to ask. Should any battery powered device need new batteries, I will receive an alert stating exactly which device needs changing, what type of battery, and how many. This way I can always go back to the message for reference instead of hoping to remember based off a query

Yes. In programs you would simply say: If Button A is fast on

If I single tap my family room goodnight button, it will set the downstairs lights on timers, turn on the hallway and step lights leading to the bedrooms, and lock the doors etc. Double tapping the same button will do the same as well as set my bedroom up the way I like when I am going to bed.

Add all of your devices to a scene at the levels you want them to be (in your case off). Add the lamp to the scene at the level you want it to turn on. Create another scene and put the kpl button in as a responder. The next part is how I do mine but can be done differently. I have a program written that turns on my scene (which turns out off) then another line that turns off the button. You could add your button to the scene as a controller should you choose. I use a program because I have different scenes run based off a single tap vs double tap. If control A is turned on Set all off scene ON WAIT 2 seconds Set Scene Button A off