lilyoyo1

Try a restore plm and once done restore devices

Whether it works or not, most of us here used the isy prior to the portal. While your method may work, most people here go by the proper procedures to lessen the chance of something going wrong. Clearing java cache has been such a tried and true method that avoids so many potential issues, it's hard to let go of for some of us

There's no right or wrong way. Everyone has their own way of programming things for various reasons. Some people prefer the cleanliness and efficiency of scenes while others may be ok with drawing things out with programs (and the perceived effectiveness of it) despite the experience. Neither is wrong. It's whatever works for you.

You're overly complicating simple programs. The benefits of insteon scenes have been covered countless times in the insteon white pages, thousands of posts, the wiki, and isy cookbook. Scenes was mentioned because they're infinitely better than what you're doing with programs. Programs can't make up for poor techniques and issues. Using band-aid solutions such as programs to fix issues only serves to create more issues long term. It's a rabbit hole you don't want to go down which is why Geddy said something about fixing the actual issue. This is what contributes to making programming hard to understand. In a sense you're turning simple math into an algebra equation.

Where would you suggest they put it? UDI like most businesses will do things based on the majority of their users. Many many more people will leave their units on a shelf than those who will mount their units in hard to reach undesirable locations.....This is especially so considering the need to scan a code is something that may be needed once or twice while in use

As with anything like that do a restore. Sounds like plm shot

Isy994 is discontinued and will no longer receive updates so it will not work with the new devices

The best thing for you to do is buy a few different dimmers and try them. There are thousands of mfg out there and countless different models (not including changes made to their same models).

All scenes need to be created by the isy for it to be aware of them. If you did this manually or with some other software, the isy wouldn't know about it and you would need to set them up via the isy.

The information on needing an ELV dimmer was pertinent to the conversation. Eaton and levitation are the only 2 zwave companies that I know of which makes ELV dimmers. There may be others but I'm not aware. Lutron caseta dimmers are also ELV

All of them including insteon. https://forum.universal-devices.com/topic/34826-zwave-700-series-tips-and-tricks/

I don't use solar edge so I can't comment specifically on that one. Noderservers allows you to use 3rd party devices with the isy that are not natively supported. What people do with them depends on the node server. For example, you can use the Sonos Node Server to control the volume of your Sonos devices are start/stop them.

You're on your own with this question. Most (if not all) here werent in your position when they upgraded to speak on all the what ifs. You can downgrade if you need to but we can't say how any would effect your system.

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