lilyoyo1

What steps did you take to add them to alexa

Polisy is for multiple types of people. Those with certain knowledge can and do the more advanced stuff. Ease of use is relative. As a developer (or person with knowledge) going outside the store and configuring things for personal use is much easier. If you don't understand the commands, then someone will be on here telling you each step of the way what to do. When something doesn't work, it's them having to take the time to figure out what's wrong and walk you through it. For everyone else there is the store. People (including myself) push towards there because anything else means being your own person tech support person afterwards. While you may not like it or want something different than what the store offers; that's the level you seem to be on which is why you're pointed to there. If something goes wrong when using the store you have 50 people that can help. Something goes wrong by bypassing the store, you have 5 (not literally) available. Mostly likely only 1 will be available and then he's stuck with you. That means time away from doing stuff with family/friends or whatever else they want to do. Same with UDI. They recommend the developer and store based on knowledge. There is a minimal expectation of knowledge and skill when it comes to developers. If they have to take time to walk you through every step, they've lost time and money. This affects their business. The store on the other hand is much easier. Unfortunately It's the nature of the beast.

When you come across the way you did, you'll automatically have people gunning for you. It's just like arguing with someone. If someone comes taking jabs at you from the start, you'll do the same back. In this case you took jabs at UDI in your approach so those who know different automatically took UDIs side. I know I help people based off the knowledge that they show they have and how something was designed. If you don't know how to SSH into something, run the commands, etc. why reinvent the wheel, with having you do something when there are much easier alternatives. Maybe you have the knowledge but how are we to know? Those that do already take advantage of that without coming on to forums carrying on as you did. Because of that, our approach is to point you to the method that polisy is actually sold for and that is the avg consumer. Coders and developers are not avg or even above avg. They're in a league of their own. They already know there's limited help outside of specific people which is why they have their own place for stuff. Instead of bashing, simply asking for help would've gotten a much better response

People push you towards the store because that is the easiest way to accomplish what you are trying to do. Those well versed with using SSH, sudo, etc. are able to do things that normal users are unable to do. If you understand SSH, sudo, coding, etc. well enough, you probably wouldn't be on here carrying on the way that you are. Most aren't going to take the time to walk you through what's needed when there are much easier and direct ways to accomplish the same task that your going around robinhood barnyard to do. After all these days going back and forth (based off the 1 nodeserver you mentioned) you could've already had it on your Polisy and using it. Just send it it back if it's so much garbage. At this point, the likelihood of anyone wanting to help you even with my same stuff is probably nill (except UDI since they have to).

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 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

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

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

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

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

I use both insteon and zwave. Insteon for lights and zwave for sensors. Zwave is far from being close to insteon for lighting while sensors is Insteon's weakness. I use zwave outlets for repeaters (have insteon outlets as well). I'm not going to get into the nitty gritty details of the insteon vs zwave argument as this question has been posted many times on the zwave subforum. @asbrilanswered the questions you had but I will add a few things. Zwave is still in its infancy with the isy compared to insteon so there was/will be more work needed for it than insteon which they've been doing for over a decade. With zwave being the confusing mess that it is, more work will always be needed than for insteon. There's no set amount of devices for a given size home. I've done 1500sq ft condos where I've needed more devices than 2500 sq foot 2 story homes. I automatically assume the worse for various reasons and buy more than what I need. Most zwave issues can be directly attributed to lack of devices so don't be cheap. This goes for building your network and in the devices you buy. Those cheap devices save you money today but will cost you more long term. If you want the equivalent to insteon or better it will cost you. If your looking at going into zwave as something cheap, don't bother. Save yourself the frustration, hair, and money. If you're willing to invest in it properly then it can be extremely rewarding (except for the lighting experience). I've attached a link to a tips and tricks write up I did not to long ago to help get you started

Did you clear your Java cache

At this point you have to start with a fresh slate anyway so I would factory reset the zwave dongle. If all of your devices are zwave plus, start with the closest device to the isy and start re-adding them in. If not, you may need to bring them closer to the isy

No. Scenes resides in devices which respond much faster than programs can so there no way to override it. There will be a delay with a program but wouldn't be too much of one. I'd try it and see how bad it is. You may be able to live with it.