lilyoyo1

Since, its Roomie's software, it would be on them to do the testing not UDI. UDI cannot fix their programming for them. You would need to contact Roomie. UDI provides the necessary resources for people to integrate their products should they chose to do so. If they choose not to, then it won't happen. If this is the case, I highly doubt a resolution has happened nor will one be forthcoming. From the looks of it, it seems like a situation where Roomie just isn't interested. Most likely, there simply isnt enough interest to warrant the investment in time and money like they said there would be for them to support it.

It'll be easier to put all of your requirements in 1 post so people can provide answers based on exactly what you're looking for vs general statements one at a time that cuts out all of their recommendations.

I use Yale

Whats your firmware AND UI? Have you recently upgraded your firmware. The isy has nothing to do with lights flickering. That could be your bulbs, switches, bad wiring, or outside wiring.

Your best source of information would be through the manufacturer of the product. I'd use the support link on the page that you linked to.

From the way things look, for his use case, he has it programmed properly. He's not simply trying to turn the light off at 0510; but off should it be on (or turned on) via various methods that control wouldn't capture. As written, if they turned the light on at 8pm it would turn off at 1010 if left on. If he used his voice at 1156 to turn the light on, it would turn off at 1206.... Ditto for any other time as well. If he turned on the light at 0510, it would stay on all day (unless turned off manually) until 1010 at night

Its unfortunate but most systems aren't built that way. They're designed for single home: one time installations. In fact, I dont know of any system (outside of commercial/custom/purpose built) that would allow you to easily accomplish what you're trying to do. Just because the ISY (or any system) may not work as you wish, I wouldnt give up on the idea. As an installer myself, I would actually take a look at what you do at home and simplify things for your customers. Instead of trying to cover everything at once, try to handle a few major things to justify the time and cost- and charge accordingly. Over time, this helps you get in and out faster to handle more homes...but also opens you up to having repeat customers since they'll want to do more over time allowing you to make more for the same work.

With the eisy being new, most probably won't be able to speak definitely on any subject unless it deals with someone jumping fully into migration or starting over with a clean slate. I tried something similar to what you're asking with the 994 many years ago and I must say, it was a complete CF. I spent more time fixing things and cleaning up than I would have had I simply built a system from scratch. I tried different methods to see which one worked best and all had issues (node servers weren't even involved then). For example: using a backup w/devices meant having to keep all the devices separate in the console and swapping each- one at a time. That worked but the process would've been faster had I simply added the devices as new and called it a day. I could never come up with an isy template that was faster than I could recreate things on my own. If anything, I would copy the programs so that you have a template to refer to when rebuilding things.

You may want to take a look at going the node server route. The 2 way communication really comes in handy

Hopefully they'll reach out and work something out with udi

I use node servers for my Sonos which allows for volume to be set (both of them do). I don't use your method so I can't help you with that one.

Just in case you didn't know, the isy994 was officially sunset back in January (maybe December). With the eisy being so new, Roomie may not even be aware of it. I'd reach out to them just in case so they can work with udi to get it supported

Yes..... Just add the set volume you want to your program.

See the tips and tricks post.

https://forum.universal-devices.com/topic/34826-zwave-700-series-tips-and-tricks/

It already does support hue. You can use the hue node server via Polisy or eisy or network resources. If you Google isy hue, you'll see plenty of posts on the matter. Or you can just scroll down on the forum until you see the Node Server

I know. I've had all of them since alpha testing

I love the paddle. It has a really smooth and quiet operation. Guess theyll release the kpl soon.

Right click on the device and choose group device

Anything zwave would work. This post has a link to all available zwave devices. https://forum.universal-devices.com/topic/34826-zwave-700-series-tips-and-tricks/

That's part of the problem which adds to the confusion. You have multiple people asking the same questions in different ways which receives the same information in different ways. This isn't the isy which has been around for 10+ years. Every single person using zmatter and eisy are using it for the first time together. The main ones that tend to help are also the ones who jump feet first into the fire so they're limited in regards to helping those who are hesitant and wanting to take baby steps (I'm sure that applies to udi as well) as they're building things for those who are trying to jump into things wholely or do a completely new install vs piecemeal. Reality is, the system isn't ready for prime time unless you're starting from scratch. You're not getting a plug and play type of system at this moment. Anyone hesitant to break their system or spend time rebuilding things should probably sit this round (or the next few) out. Taking baby steps or needing hand holding will probably cause more headaches and problems than it solves. Especially when you consider the time wasted. For example, look at this question that was asked. We're still on it 5 days later. Even with being busy, udi couldve answered a support call much faster. Hell, depending on skills, the op could've rebuilt his entire system in this time (especially if he took time to take note of his programs and previous setups). I get the hesitation. I completely understand the reasonings behind it. However, if you're not ready to commit, you're probably better off waiting for things to be stable and then proceeding.

I'm not understanding your point. Matter is not just wireless but IP based overall. Doesn't matter if it's wireless or hardwired. There's more than 1 way to skin a cat.

Id clear java cache to make sure your UI and firmware matches. Once done, click on a line, choose update, and then save each program again

I've seen different issues with different setups so your mileage may vary. Many were able to get their systems up and running properly but it took time and effort. The easiest way to keep up with what's good/bad is to check the latest firmware release page as it'll have the latest bug fixes for whatever popped up in earlier releases. Generally the early adopters comment their issues in the first few posts so it's easier to keep up reading the first 1 or 2 pages before things go sideways. From Udi's perspective, it wouldn't make sense to say yay or nay to a release since the latest is suppose to fix what was previously broken. The main broken things I've seen with the latest release deals more with individual node servers than the system overall. Personally, I would hold off if you're looking for a a stress free upgrade. While I'm confident that my system would be fine, I'm waiting for that reason. I don't have the time right now to focus on troubleshooting.

Is this accomplished through scenes or programs?