lilyoyo1

Is the motion sensor turning the lights on or are you turning the lights on manually?

There's a difference between obsolete and bad. Obsolete implies the ISY no longer works which is far far from the truth. In fact out of all the different DYI controllers out there, the only one more capable than the ISY (and has the pretty interface you desire) would be fibaro's home center which costs twice as much as the ISY. If you don't like the ISY then don't use it. As you've already mentioned, there are other options. The ISY is for programming and forgetting about it. If I had to control something based off it, I'd probably share your same thoughts. You're bashing something that simply no longer fits what you want. The great thing about it is that you have the freedom of choice. While you may have stopped recommending the ISY due to your complaints, many of us still recommend it to others. I have heard the same complaints from them in the beginning. However, those same people also sing the ISY praises now and recommends it themselves. I'm using my system with RTI so I still have a pretty interface on my touchscreens that I never use.

The ISY can do both. A person can make their system as complicated or as simple as they want it. There are just those who wants it simplified for their needs which would take away from it's designed purpose. UDI is between a rock and a hard place. They can fix the UI to make others happy (there's still no guarantee people would like it) and piss off their ardent supporters while doing so.

If making the UI pretty ends up costing us any capabilities, I would rather keep the existing interface.

Automation isn't for everyone. There are those such as yourself that has no desire to invest the time nor effort into taking their home to the next level. Michel readily admits that the ISY isn't for people such as yourself. Some people want simplicity. Me personally, I feel it's more work using those systems which takes the joy out of investing in technology. This is why smartthings (or any of those other cheap controllers) aren't for me. For me, I don't want to take the time to unlock my phone, open an app, wait for it to connect, find my device/scene, and trigger it. It's much simpler to have a remote on my night stand to reach over and hit the button for those times I want/need manual control over my system. Anything else happens automatically. You talking about not using voice control and how your app works since your wife is asleep. I like that if I go to the bathroom in the middle of the night, my underbed lights automatically turns on so I can see. Once I get to the bathroom, the lights automatically turn on to 10% and all turns off once I'm done. Not once having to lift a finger or pull out a phone. Hell, if I fall asleep with stuff on, they automatically shut down. I don't have to tell a speaker or pull out my phone. The fact is, UDI made the ISY for a group of people who are willing to invest the time, money, and effort into achieving what they want. Do they miss out on more market share because of that? Of course. However the same can be said for those simple cloud based systems. We get on those who bag on them for not giving them what they want when reality is, they are giving the people they designed for what they want. Their main consumer base wants automation not a fancy remote. In the end, these topics will never be helpful because those who come here wanting simplicity are using the wrong system as a whole. That's no different than me going to smartthings and complaining that they should be more like the ISY.

Obsolete because of Java yet the ISY can do much more than smartthings! It's not the language that a device uses but what a device is capable of. From my experience (I've used both systems) the ISY is capable of much more. If you're looking for control then smartthings is a great place. If your looking for automation then the ISY is where you would want to be. If you are depending on an app then you're not doing automation. What's even better, if your internet or router goes down, your system still works with the ISY

As Oberkc said, it depends on your platform. While I have RTI, I don't really believe in using apps. What's the purpose of automation if I need to take out my phone! There are ways to add both the best and ecobee3 to the ISY. From my personal experience with the ecobee3, it can do all that you want with it without interference from anything else. The nest to a lesser degree but still extremely good on its own. With that said, (if at home) what little control is needed you can natively do with Alexa or Google home (if you have them). The ISY interface isn't the best. However it works the best if you invest in programming it towards your lifestyle. Taking the time and effort to dial your system in will negate the need for app control for the most part.

Exactly how I would've written it. Great minds think alike.

In addition to what Stusviews wrote, I would add a disable program to the then clause so that it automatically disables itself after the update

Insteon devices can be reprogrammed when awaked. Just write a program that runs once triggered and the ISY will trigger as you go.

Yes, both Insteon and Zwave can coexist together. The 5.0 branch does a better job than the 4.6 firmware but you can accomplish what you are trying to do with either one.

The ISY doesn't work like that if you use programs to control your devices.

Io_guy is correct. Create a program that controls the scene and then add the program to alexa

Yes, under the then clause you will see the options for programs. That's where you will find it.

Does your maid turn on/off the light manually? If so, write the motion program like normal and deactivate the program anytime she physically turns on the light. You can reactivate the program anytime the light is switched off.

I understand what you mean though I do find it ironic in the sense that you still end up using only one manufacturer for your system.

I use them too for sensors and locks. For network repeating I use the outlets (they aren't in use). Need necitates use not desire (outside of sensors)

What's happening? It'll be easier to debug knowing what is going on

That's how I would've written it

Create folder in programs. In folder say: "If status of laundry light is off Then allow programs inside to run You'll follow Larryllix advice afterwards

That's still not ground for a lawsuit. Certification of a device does not mean they have to use everything that the certification offers. A classic device can still receive certification as long as it has"some" of the features. It's unfortunate, but mfg can still do what they want. I want to like zwave. They have some great products. I just can't get behind them until they get rid of this guessing game.

Yes it is. I can buy with confidence knowing what I am getting myself into. I don't have to do alot of programming just to get basic features that comes with every device.

Your argument is so weak that it really doesn't deserve a response. My Zwave issues arent about new features that's added due to development such as your case of I1 vs I2CS. That goes with any technology. In the end, new devices can still be used with older devices for both protocols. What IS messed up is the fact that devices within any single generation will have different capabilities in how they communicate. Even now, with what this posting is about, the poster has a zwave plus device that he expected to have certain capabilities due to the certification and it doesn't. Your dual band/non dual band is weak as well. Unless you want to include discontinued models the only non dual band devices are battery powered (a person would need to be an idiot to think it was dual band) and the IOLINC. Which states clearly on its product webpage that it is Powerline only. If a person buys without reading then that's on them. Same thing with peek and poke. First off, that's a feature for developers and something the avg user would not care nor know about. The fact that it was removed in I2CS also limits your argument unless you are trying to include discontinued devices in your argument.

How about creating a folder that allows your motion program to run only when the light is off.

There's no lawsuit from using a deprecated feature. This is especially true since those devices were out before the feature was dropped. Since the lutron patent ended, it would behoove leviton (and others) to change how their devices work but that does take time and it is still their choice whether or not to embark on that. While smartthings and UDI may not use hail, other controllers do so the products can be used. With all that said, this is my biggest gripe about zwave. It's too fractured. Regardless of what generation, manufacturers still get to pick and choose what they support leading to a confused end user.