lilyoyo1

Sounds like communication issues. Lots of noise present.

Like that yes. However you did it on a separate post. Depending on how many posts come here before he looks he may not see the exact post that you made. Never mind someone else made the post so you can't edit it.

Edit your post and add his name so he sees the exact post

Respond to commands?

If you're already up and running with your system then you can wait to see what happens with polisy. At this point it's obviously for those who want a simply way of setting up and integrating with Polyglot. Looking at UDIs history, a timeline will not be given regardless of who asks and how much they are asked. They simply won't be pressured into something they don't want to do. Outside of using polisy for Polyglot, there really is not reason to purchase it for future capabilities when it most likely won't happen within the time you would want it to happen. Buy it today for what it can do today not for what it may do tomorrow. When it has what you're looking for then that's the time to purchase.

You may want to direct your message at udi by adding @ and the name of someone who works there as they are the only ones who can answer these questions. With they said, I highly doubt they would give any sort of a timeline for the isy to be ported over. The way their release read, the current versions will be able to run the isy software at some point. Looking at UDIs history, I think it's safe to assume Elk or any other ISY add on would not change. If anything it would get better. Personally, I don't see a port happening for 1 to 2 years. When it does, I would assume it would be once they move on from java. All of this is assumption on my part. I'm sure when udi Is ready they will share more information

If there is a current nodeserver for them then yes, as current nodeservers are supposed to be supported. Add @ and whoever from UDI you want to see your post as they would be the ones with the answer.

Polisy combines everything you have to do now to get polyglot and nodes servers up and running into one easy to use package. Instead of you having to configure your own system it comes ready to go. From the sound of it, at some point in the future, the isy will be ported to it. Hopefully @Michel Kohanim will be able to chime in whether that is true or not. If it is true, I'm assuming it comes with the zwave board included or allows you to take your existing board and put inside when that time comes. If you go into the polyglot subforum, you will see plenty of examples of what current users are currently doing as well as some of the different devices it'll allow you to integrate with the isy.

Naming things are tricky. What's clear for 1 may not be clear for another person. The wiki does cover this type of info

I have one and mine shows on my TVs via my matrix system. No issues at all. I haven't felt let down at all by the image. Most times as already mentioned, I'm viewing something on a tiny screen so it doesn't matter

Any app will do what you're asking. It really comes down to personal preferences in regards to interface. Agave seems to be the popular choice for Android users

What's your UI?

What's the plm you're currently using?

How did you have it set up prior? Were you using an emulator before or the ISY Portal? Unless you use an emulator you would need to use either UDI's portal (V3 connects to) which is cloud based and a subscription or mobilinc's which is cloud based and a subscription. Either way with Alexa being cloud based you'll still have your stuff going through the cloud. We need to know how you handled things prior as that would be the way to get you up and running again.

As long as you have enough devices to build a strong mesh network then you'll be fine with zwave devices. While performance varies (as with anything) it comes down to expectations and what you are trying to accomplish

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.