lilyoyo1

Insteon and UDI are 2 different companies. They are no more aware of their plans as UDI is of theirs. That's like asking Michel what new products insteon will be coming out with.

And what I said still stands. You would need to be exact or limit your scenes to very basic functions. At that point, just to keep track of 1 detail you lose out on many other things you can accomplish This is especially so in a large install with multiple users. You could have 2 different scenes with the same exact devices that still meet the base requirements of your program.

Even with your flag idea, defining a scene being on would be hard (very well impossible depending on setup). The problem (even with a flag) is that it is possible to have a multitude of different devices in many different scenes (especially in large installs). Just because 1 particular light is on doesn't mean a possible scene itself is on.

You're welcome. I was like that too when I first started with the ISY. I had a million programs just to do one thing. In time, it'll become second nature.

Both devices simply needs to be in the same scene as controllers. Make sure you update both devices on what state the other should be in (both should be on)

I'm the exact opposite. I use scenes for almost everything. Anything larger than 10-15 devices, I will create a scene with everything set to be a responder and write a program based on the trigger (whatever button I want to push)

One thing I want to add is that the newest versions add glass break to it. Can't say how well it works but I have it programmed as a backup to my other alarm sensors. If my alarm is disabled/off for whatever reason and someone broke a window, I'd still be alerted

To be honest I can't speak on range. I have about 10 of the Cooper zwave outlets installed around my house so range has never been an issue for me. Battery life has been great for me. The very first one I bought lasted about a year before needing to change. The couple of door sensors I've had, I haven't had to change at all. My leak sensors haven't needed changing yet either

I prefer zwave sensors over insteon sensors personally. I specifically use the fibaro ones and love them. The 5 series firmware works with mine without issue

I use the built in stuff from the ISY. Much less programming involved. Since all of my alerts have subject lines, I simply have my email forward them to the proper folders for logging.

There are so many different things that happen when someone adds devices from an older system that it's almost impossible to write something to cover everything. This is why everyone recommends a factory reset. Even the most advanced users will factory reset as they k ow it's not.ally easier,faster, and cleaner to start over than deal with all the issues that may arise. With the complexity of automation systems such as the ISY, it would take to many resources to cover each and every detail of how to fix something. This is especially true when an issue may have multiple fixes. The forums really are the best place to go for most fixes.

Trickery or not, it works really great. Even with my edison bulbs, I never go down to 1%. All of my bulbs are on a 2 second fade. These are the only ones that I have found that allows me to fade on and off properly. They don't have that instant on affect like other leds that i've come across

Philips warm glow LED bulbs work great for me. I have the br30's and standard bulbs in that line

Thats a lot of programs for such a simple task. You could simplify it by simply stating if the status of the light is off and the fan is on, wait x amount of time then turn the fan off.

The 6 button keypad shows up as 5 buttons since the on and off buttons are tied together. Outside of changing it to 8 button configuration, there are technically only 5 programmable buttons

I'd create a single scene with all devices that you want on as a responder. That way you lessen the chance of something potentially getting missed when each scene is activated

My concern is that it's for the independent user not a company like UDI. If they develop for it, how many problems would that cause them. I wouldn't want to see them tied up in litigation trying to help a few and the company suffers on the whole

Apple Fanboys will jump all over it. Then blame every other company when its not supported.

I've done the Alexa already which works well playing around with it. I like the critter idea. I may do that in the back yard. Put a motion sensor out there that turns it on

Thanks for that info. I'm going to have to look into that since half the work is done now. Lol. It would be a good way integrate into my RTI I've been trying to think of reasons to add it to the ISY but since I've gotten it, I've never felt the need to interfere with it. The only reason I could think of was if I needed to go into the yard. With summer approaching, I may add a program that stops it the day of planned events/yard useage

I went with the rain machine for my irrigation needs. While I cant control it from the ISY, it took much less programming and hopefully (time will tell) last longer than the ez flora. It does have a rest API so if ever needed, I could technically control it with the ISY as well. At this time however, its interface does all that I need it to do.

If control motion is switched off and control motion is not switched on then Wait x minutes Set light off

The information RAF posted is incorrect. While I am unable to say how I know I would take his information with a grain of salt

Plug them in close to the ISY to link. Also make sure the firmware and UI are the same on the ISY prior to trying to link

That's not possible. The ISY will always be able to issue commands just like the switch will always be able to work locally. With that said, if you're trying to keep programs from running if you manually turn a switch on (such as an auto timer), you could disable a program if a switch is manually turned on