lilyoyo1

If it works via your console then I would say nothing is wrong with the setup. Most likely it's the syntax you're using. How is your program written just in case?

There was nothing disrespectful about the statement. Early on you mentioned ISY>lutron, the desire for low cost offerings due to the area you're in, and then we started focusing on C4 which already has a driver and is cost prohibitive. Simply making a statement that captured the gist of all that was spoken. I assumed if you were looking for something to integrate with higher end, you would want something that could benefit you most and the clientele in your area.

That is correct. Control4 uses it's own proprietary zigbee implementation. There's already drivers for C4 and insteon. There are shortfalls with it but it exists. You're probably better off focusing on lutron especially the Caseta line as it's much more affordable

As ScottMichaelj said, there's a lot of choices. None in my opinion are perfect. They are have pros and cons. My personal choices are Control4 and ISY. When it comes to the ISY I prefer insteon switches and zwave peripherals such as locks and sensors. Since the isy is for low end stuff I'm not one to integrate it into high end stuff. Personally I try to mix as little as possible to avoid complications. My place is one thing. Doing so in someone else's home is another

After I re-read my post I can see the confusion. My apologies. I'm not a fan of lutron though I think it's a good system. While I personally wouldn't use it at this time, I can see the usefulness of it and can see it being used a lot. Having options is never a bad thing.

In my house, I use insteon/zwave integrated with RTI. Even then it's done more for the theater control and touchscreen than anything else. For high end homes I use control4 which does have conditional logic. Control4 is lts own system. I dont combine high with low.

The downside of lutron caseta over the isy with Insteon and/or zwave is the lack of conditional programming. This is why I choose control 4 over radio ra2

Trust me, more than you and me both

If memory serves correct (it's been about 5 years), getting it connected wasn't that hard. Just designing it was the tedious part

You're pretty much doing the work yourself. They have everything you need though to get it working though. I did one a long time ago. It took a while. However if you're going the path of a touchscreen interface, it's worth it.

I can understand that. However that's more of a static situation such as with my RTI touch panels. With that said, check out command fusion. It'll allow you to design your own

In addition to what I said, voice control is making a control app a waste. Using Google assistant for example, you can still control your system away from home with that. If you wonder if you left a light on, tell Google to turn your lights off and it will. No need to go through the process of finding the app, opening it up, finding the device and clicking a button.

I can't agree with something that I don't agree with. It's been so long since I've touched an app that it's hard for me to justify one. Even on the client side of things, I don't give them an app until they've lived with their system for at least a month. Early on it was to show off for friends. Once that novelty wore off it became an extra app on their phone. Mobilinc x looks really good. However I can't get into it until/unless it supports the UDI portal and a set fee. I just can't see spending more on an app in 3 years than I did on the actual controller over the same amount of time.

I didn't think that. I have a couple and was just confirming that it works with the new firmware

No. It has the switch built in. https://www.homedepot.com/p/GE-Z-Wave-Plus-Wireless-Smart-Lighting-Control-Motion-Switch-26931/303468678?cm_mmc=Shopping|G|Base|All-Products|All|All|PLA|71700000014585962|58700001236285396|92700010802552412&gclsrc=aw.ds&&gclid=Cj0KCQjwrJ7nBRD5ARIsAATMxsvfQlT51fsapQMZDU0Q4j91_peO6Q0ZM0jWjCqckAAGO1Gq0qP5NUwaAtndEALw_wcB

Ge has one. A dimmer and a relay version

I know the new version of the siren works with the 5.0

Post your actual scenes so we can see how they are set up. I suspect since you haven't configured your scenes, there's a conflict somewhere.

Even if UDI created their own app, it doesn't mean others would like it any better since app interfaces are a subjective matter. There are many complaints about the smarthings app. Comparing UDI to smarthings and neocontrol is like comparing apples to oranges. The only thing similar is that they work with smart products. Smarthings is a glorified remote. It needs an app. The ISY is an automation control. Programmed fully, the need for an app diminishes greatly. Compare that to Neo control whose app looks great. However good luck at getting it at the same pricepoint as the isy. I like ISYs model as it doesn't force me into any one system. Choice and control is of the utmost importance to me which UDI gives. I cam use an app or not. I can try different apps to find the best fit vs only 1 app that I may or may not like. Mobilinc does have a new app called Mobilinc X. You also have agave, ekeypad, and others.

Should this happen again, I'd look at the Alexa app to see what phrase Alexa is hearing just in case it's different than what you're saying.

You should never link devices outside of the isy as the isy would not be aware of them which is partly why your set up is not working. The other part is the isy ONLY talks to the device that you are having it talk to. You need to add both devices to the isy, create the scenes properly and then add the scenes to Alexa to control. I would recommend taking the time to read the wiki and different posts on the forum to familiarize yourself with how the isy works.

A backup is exactly what the name implies. A backup of your configured system. It restores your Isy back to what it was at the time of the backup

With fibaro, I found it best to click it's button 3 times to wake up prior to updating parameters. I also turn off automatically put devices to sleep while updating to let the device time out on it's own once done.

I doubt it's the device since it doesn't beep until it's added to the isy via the restore. If it were a bad device it would beep once reset and outside of the isy. If you don't feel like going through re-adding it to the isy and the scenes it's part of, a replacement device would be the easiest fix. The downside is whatever configuration is causing the problem will likely be transferred to the new product as well.

Just to add to what MWester said, this applies to all zwave devices. UDI does not determine their parameters. You'll always have to check with the oem for your parameter settings.