lilyoyo1

A timer isn't needed and is the wrong way to fix this. You could use variables to track a second press to accomplish what you want. Personally, i feel this is a training issue. When you get into automation, it's much different than what people are accustomed to. If people are turning things off/on improperly then you're better served teaching them the proper way of doing things so that is done right the first and every time. Yes programming can help alleviate mistakes but it can also have unforseen consequences which can cause other problems down the road. Keep your setup consistent so that memorizing things are kept to a minimum and you'll find things will work much much smoother.

I'm not following. Is the issue with the kpl or swl? A second press (not double tap) on a lol should result in an off command turning everything off. Hitting a swl on a second time will result in another on command turning everything on (if at a dim level). You can capture double tap, dim down and dim up because those are commands insteon sees and has. A second press is a second press. Still an individual tap. The isy cannot discern what your intentions are. Was it inadvertent, intentional, etc. It just knows the button was pressed resulting in the corresponding command to be sent.

Directly linked devices will always respond in that way since the command comes directly from the device. There's no way to override that with a program. You can remove the controller from the scene and then use Control to trigger the responders when it's pressed. That would do away with devices changing when double tapped

Nope. Not at this time. I used to when Nest had the "works with nest" program. Unfortunately that ended once google cut it off. It may come back in the future but at this time it's non existent

Post your programs.

What were your exact steps to set your parameters?

A device going offline can be Multiple things. 1) could be your mesh. While you may feel it's decent it may not be. 2) are you properly waking up your device and is your Isy set to keep devices awake? If not, it could be timing out before it finishes updating. 3) your device was setup in 1 location(or healed in a location) but you are trying to update in another. If so, you just changed your network so that could be it. 4) verify that you're using the proper parameters. Zwave does have ghost nodes. Those are typically nodes that have no bearing on the device such as a door sensor having a glass break sensor node (yet has no microphone or parameters for it). If you're getting the data you want but your program is not working properly, then most likely your program is the problem.

You can't have mobilinc connect and the Isy portal. You must decide which you want to use. Once you do that, you'll need to connect the other to cancel and switch over

I'm confused in this in regards to use case. If you're opening up the app to turn something on or off, you want to verify if it's on or off prior to doing said action? Just trying to understand the logic.

This is correct

Not wrong at all. The best simple explanation. One caveat is with zwave. Many zwave devices do not use control. I'm those cases, status will have to be used as the trigger

Michel has already stated they will support what they currently support. They will not add support (reverse engineering the code) for newer devices (such as the new line) unless they are given the proper documentation for it.

This all depends on what you value most from insteon. In terms of scalability, usability, and experience, none of the diy systems come to being a viable alternative. If you don't care about uniformity, redundancy, and overall system performance, then zwave would be the best alternative for the isy. The reason I say these things is that wifi devices aren't completely scalable in a full automation setting for the reasons you listed and more. In addition, you have the work involved with flashing all of your devices, maintenance, as well as network impact (can be mitigated if you know what you're doing). For me, the amount of work that goes into using them is not worth the cost savings. In regards to zwave, you're still dependant on the Isy in order to work. Should the Isy fail for any reason, your system no longer works. At least with insteon, you can design it to work outside of the Isy so that your most important stuff still work. This can be somewhat mitigated in zwave IF you have the right devices (emphasis on IF). However the ability to have direct links with zwave devices is extremely limited in the amount of devices you can have control of as well as how it could potentially affect Isy programming. IF (there's that word again) you have the proper zwave devices, the ISY can allow you to recreate some of the things you can do with insteon. However, zwave is not nearly as dynamic in regards to making changes so it doesn't allow for as robust of programming that you'll find with insteon. Finally, (the biggest issue for me) is the popcorn effect. Zwave devices respond 1 at a time not in sync the way insteon does. That's something I could never live with. If that doesn't matter to you then zwave will be fine (though it's response is slower than insteons) If you can afford it, and didn't want to stick with insteon, I would recommend using Radio ra2. There's a nodeserver for it written by @simplextechso that you can use the isy to give it the additional logic control that radio ra2 is lacking.

Did you attempt to do anything in the admin console? The dashboard is typically used for viewing your system and the admin console is for configuring your system

Firmware and UI? Restore your devices by right clicking on the device and choosing restore

No. Your best bet is to upgrade your board since it's the newer firmware that supports what you need. I know it's not what you want to hear but it's really the only option

See post directly below yours

It has not been discontinued though it will be a while before they get more in

If this a real post, your situation has nothing to do with the original post. What is your UI? I suspect that you may need to clear your Java cache.

https://forum.universal-devices.com/topic/27379-context-aware-alexa-with-an-isy/page/3/#comments

Nice install. I'm glad that you got it working. Welcome to the world of zwave. I'd temper your expectations when comparing it to insteon in regards to what you once we're able to do. They are worlds apart in that regards

same advice given previously (post directly above yours) which was ignored.

You must use the scene in order to keep things in sync and not the device

This isn't necessarily true for a lot of people. Outside of basic multi-way setups, most of my controllers actually do different things based on the location. For example, what I need to happen when hitting my away button from the kitchen is different than me doing the same from the front door or garage. If one wants every controller to be the same, they could make it easier by adding responders to the scene first and configuring them. Once done, add the controllers and they will take on the scene attributes automatically