lilyoyo1

I never use them for yale but I looked at mi e and it's missing too

I agree with ELA. That's extremely fast...Waaaaay to fast for it to be doing anything

No. 2 separate and incompatible systems. You could get the insteon ID from your admin console to add your devices to the hub. However, you would not be able to factory reset it. In this case, I would write down the id, unlink it from whatever scenes it is part of, and delete it from the Isy PRIOR to adding it to the hub. The same would need to be done for any other embedded devices. The rest, you would manually factory reset prior to adding to the hub.

All over the forums (including the 5.3 page) and wiki. The same as migrating using the same controller. Back up zwave (if you have zwave), backup isy, restore zwave, verify programs

The problem with forums is that so many people comment on different things, issues can get lost in the process. UDI can't read every post to find whats what (though they chime in regularly). A ticket is the best way to get a bug fixed long term.

Did you clear your Java cache

What steps did you take to add them to alexa

@Samedarkcloudsyou're going way too far with your language....you might want to step away from your computer for a while.

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

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