lilyoyo1

The fact that you're on 4.5.4 along with what you're looking for, I would say you don't need to upgrade to 5.anything at all outside of wanting to stayup to date (which is probably irrelevant since your firmware was released over 4 years ago). I don't see the upgrade process getting any easier. If anything, the larger the gap between where you are now vs where the isy can/will be in the future will most likely only make things worse.

Programming is mostly the name. Some things may be tweaked such as changing device levels but it's not something you'll have to truly re-learn. There are some additional capabilities to programs which can be found in the wiki, but those are on a case by case basis as those are generally advanced things that the avg user wouldn't do to fine tune their system. The type of programming that most people do doesn't change however. Programming for the devices you have is exactly the same as if they were Insteon devices.

If they are for the isy then they are in the polyglot store unless it's still under development and not ready to be released. All you have to do is go to the store, find it, and hit install. You're driving 20 miles out the way just to go across the street. Makes no sense

Where did you read (within context of the whole sales page) load whatever is in github? Stuff has to be configured to run with polyglot and isy. Michel has already stated you're more than welcome to sign up to be a developer and then you'll be able to do all that you want. Unless you choose to do that and until then, you will have limitations. If that doesn't work for you, return it. You can always use an Rpi for what you want. UDI prides itself on customer service so if you're not happy with Polisy or it doesn't do what you want....return it

What's over your head? What specific nodeserver are you having issues with? For the most part, you go to the polyglot store, hit install and the nodeserver downloads to your Polisy. You'll then choose a slot that you want it in (1-25), go to your dashboard, choose configure (something like that). Give it a minute. Depending on nodeserver, a message will pop up saying to log into your account. Once you input your credentials in, it'll start finding your stuff. Log into the isy admin console (or restart it) and it should show up.

If you want to do things properly, add the scene and not the device to Amazon. Simply label it a light in the portal.

It's also been discontinued for a year or more

Yes to all. Depending on how old your isy is, it may be under warranty. You can put a ticket in with udi for help as well prior

What steps did you take from start to finish when you upgraded? What was your starting firmware

It's not reading it. Try unplugging the isy and rebooting. If it's still not reading then most likely the serial port is no longer working

I was asking what (if any) plm is showing as connected to the isy. Go to Tools>diagnostics>Plm info.

No since there's no way for the isy to know what you want things to be. If you have the pro version, you could turn off write updates which will make the process a little faster since the write will not happen at that moment. You could also add all responders first (and configure) then the controllers. The scene attributes for each device will automatically be copied to the controller vs needing to write each on 1 at a time

They'll get warm. With you having the same issue with 2 different devices, I would start looking past it being the plm. Does the plm your isy show have the same ID as the new plm

What exactly are you trying to understand? It would be easier to answer that vs going over in detail the exact differences between the 2 as there are many smaller changes vs. major changes (even though the major differences are huge and greatly overshadow the minor). The main differences are in nodeservers and tighter zwave integration. A quick perusal of the forums you can see what people are doing now vs what you are capable of doing. Nodeservers allow 3rd party devices such as hue to be used in scenes and programs as if they were native devices. Now you can integrate those, zwave, and Insteon all together in scenes and programs.

Its not nonsense. Its you not taking the time to research and understand exactly what you were purchasing. NOWHERE does it say download stuff from github or anywhere you want. The product webpage even goes so far to show a partial picture of the store as well as mentioning the store. Polisy was designed for use with UDI's nodeserver store. UDI didnt advertise it as a do as you please device (Thats what an Rpi is for). They advertised it as a way to integrate 3rd party devices with the ISY via their polyglot store which offers plenty of free nodeservers (for now). By downloading it from their store vs direct from Github, they can ensure compatibility with the ISY and some modicum of quality control. After-all, its them that people will be calling when something doesnt work....Not github. No different than with Apple and their app store. Besides that, its the same nodeserver. Why are you making such a big deal about literally hitting a button. Even if you could do it straight from github, most likely it would take more work than a single button click. You're complaining about a mundane task. Thats like complaining about not being able to sideload an app that you can readily get from any app store. If you're looking for something you can do your own thing with the Rpi is the way to go. UDI does offer a no questions asked money back guarantee. You're more than welcome to return yours if you please. Keep in mind, Rpi will no longer be able to access the polyglot store in the near future so it will be up to you to figure out how to make it work.

Not that I've ever seen. Only insteon makes a dual outlet. There are plug in modules with multiple controls

What steps did you take to hook up your plm? What ports are the cables going to?

Not at this time. Currently it's still manual since there are potential migration issues

Are you sure that you put the card in proper slot

When you go to help>about, what does it say your firmware AND UI are?

No. It was removed

There is no right or wrong way to program the isy to control your gear. The best way to program is based on what suits you best. There are those on here who use programs mainly while others such as myself use mostly scenes and allow the programs to control the scenes Ive created. The best way to figure out what suits you best is to experiment with a few things and see what comes about. Everything you did with x10 you can do with insteon (and much more). It all comes down to how you design your system. Before starting, plan out what you are trying to accomplish and what matters most to you. That is what will determine the path for you to take. If you want to control stuff with remotes and rely less on automation (and the isy) then scenes will be your best bet overall. If you just want the ISY to do everything for you and work towards true automation, then programs will become much more important. I use a high combination of both. I set my scenes first. This way I know everything that I want to do will work outside of the ISY. My 2nd reason is uniformity. I like everything being in sync which you do not get with programs. Its hard to answer exactly on how to do something that has different variables to them. The best method is determined by exactly what you want to happen, the devices you have and expertise as some of the best methods are more complex. The way I set my away program utilizes both scenes and programs. When I hit my away button, it starts a program that turns off each room 1 at a time. I could do it a different way (such as a separate scene) but since I already have those set up, I simply use those. Once it gets dark enough in the house (where we want more light) our lights will automatically turn on (depending on different conditions) When we are not home, they turn on at a lower level for the dog in certain areas. If we hit our away button after sunset, the lights that are supposed to come on in our absence will automatically turn on at that time while everything else turns off. There are other programs, systems, and devices in place that allow me to accomplish what I am doing. This is why I said the best method is determined by other variables. An open question like yours can elicit 20 different responses and styles because of what other people have or do which can make things even more confusing for someone not yet versed in how to set up their system.

The 2474 has been around since 2011 as far as I know. Its.not designed to work with LEDs however

You'll need to create variables to create a timer function. I think you're making this much more complicated than it has to be as well as mostly likely going overboard with the fan or not enough. It's your fan's cfm rating and room size that should determine how long the fan stays on vs the light itself being on. The fan is on and moving air while your in there. Depending on how much air it moves, should determine the length of time it stays on afterwards. What I'm saying is that being in the bathroom for 5 minutes or 55 minutes is irrelevant once you exit. It's moving air while you're in there. Whatever is left once you leave will continue to be moved. Due to the room size, if your fan needs 10 minutes, running it an extra 45 minutes is a waste. Same thing with being in there for 5 minutes. Running it for an extra 5 when it needs 10 leaves you short. This is a simplistic view of things but I'm using to help you understand what I'm getting at.

Reboot your isy and restore them