waffles

@bmercier; thanks much for your prompt response! However, I am still getting the same error message, despite a power cycle.

So I am trying to migrate the Alexa settings from the old ISY to the new one. Why do I get this error message: I saw the note in @bmercier link to the wiki-prerequisites There is nothing else to approve in the Admin Console of the new ISY: 2. Question/Observation: does the configuration on the ISY, that gets migrated from, get wiped out as part of the process? When I used the migration tool to migrate Alexa settings from the new to the old ISY, the settings seem to have gotten transferred fine, but the Alexa page on the new ISY is now blank. If this is by design, I'd rather see the existing one to be kept. There is a delete all button that allows an easy purge if needed later on.

Ahh, got it now. Thanks much @bmercier for the explanation and the migration tool!

Found it!. Thanks, @asbril Can you confirm that after the migration Alexa continues to recognize your former configuration or was a purge and 'find new devices' necessary?

@asbril; could you please share exactly which steps you took to migrate? I must be missing something.

Hello @bmercier; could you please elaborate a bit more on the <<migrated>> part? My experience thus far is that Alexa does not recognize devices/scenes/etc. even if have the same addresses, Alexa Cat. and Spoken, i.e. the only difference being that they are associated with different ISYs/UUID. So even the code on the ISYs is the same by backing up on one ISY and restoring on the other one.

....and to rebuild all Rooms and Routines in Alexa Thanks for confirming my suspicion, though.

Thank you @Michel Kohanim and @bmercier! Not to sound ungrateful, any thoughts on this one? Now, the next hurdle is how to get Alexa to recognize the second ISY. Last night I started duplicating the commands for the new ISY. I also pointed per @MrBill in my Profile to the new ISY . However, Alexa did no longer recognize the commands, named exactly the same, only now associated with the new ISY. Is there anything else one has to do? My line of thought is/was that as long as the name(s) are kept the same, there would not be any addl. steps on the Alexa sided needed. Thus far, the only way I got it somewhat working again is by purging/re-finding ally UDI devices in the Alexa app. Downside is that this killed my Rooms and Routines in the Alexa app, which I now have to recreate. I hope (here it is again :-)) there is a less destructive solution available

Thanks @Michel Kohanim while not what I had hoped for, I still appreciate getting a definitive answer. Now, the next hurdle is how to get Alexa to recognize the second ISY. Last night I started duplicating the commands for the new ISY. I also pointed per @MrBill in my Profile to the new ISY . However, Alexa did no longer recognize the commands, named exactly the same, only now associated with the new ISY. Is there anything else one has to do? My line of thought is/was that as long as the name(s) are kept the same, there would not be any addl. steps on the Alexa sided needed.

I am restoring a backup. So the (only) thing that had changed is the UUID (which associated with the ISY's H/W AFAIK). This results in (2) entries in the Portal (old and new ISY). In my initial post I included a screenshot of what it looks like if I pull up Tools/Connectivity/Amazon Echo....=> fully populated. If I do the same for the new one I get below.... i.e. the table is empty. So how to get this table populated, short of retyping everything?

Thanks Mr. Bill. I had not noticed this before. I have to check this out further. However, this does not seem to copy over/clone the Alexa settings (right part of my initial screenshot) I have on my old ISY and want to also use on my new one. How can I do this?

I am in the process of setting up a second ISY 994 as a 'hot spare' / clone. I was wondering about the best way to copy/migrate the configuration for the Alexa set up. The screenshots shows what I currently have on the existing one. How do I get this copied over to the new one? There is an export function, but I could not find a way to import. I am hoping I won't have to retype everything again. Any suggestion would be greatly appreciated!

I reverted back to RC1 to get rid of the java error. I may just hold of until the f/w update and give it another try then.

Hmm, I disabled the windows firewall, but no joy. In the meantime I also found a post about this issue: Unfortunately, the suggested steps from the Wiki don't seem to work for me here. (These are the steps I followed whenever I upgraded ISY's f/w before.)

Since I upgraded from RC1 I keep getting this error message whenever I try to log into the ISY the second time (first launch is OK): The same happens on another PC. I tried clearing java cache, re-installed java and ISY f/w to no avail. How can I fix this?

Mine now also. I did not have to reboot again.?

Same here. Still no joy.

Same here:

I did restart today AFTER I had lost connection.

Same here, ever since it was released. (I am also offline as of an hour or so ago.)

not sure about the restarted ISYs. My ISY was working fine until about an hour ago, incl. Alexa connection. First I thought the issue was on my end, so I rebooted my ISY as well as the switch it is connected to.

I believe the Maintenance scheduled for earlier today has not yet been completed:

Just found this thread, as my ISY has gone offline a little while ago (green dot in ISY portal still there, but lost connection to Amazon, Google, etc. @bmercier; I believe the thread title should say 04 (April), not 03 (March), correct?

From the limited testing I have done thus far, it seems that newly created scenes assign 'defined' Actions, e.g. '100% in 0.1 seconds' with Link Type 'Insteon' to Responders and only Controllers get the 'default', 'default'. This makes sense to me. However, I have numerous old/existing scenes where the Responders still show 'default', 'default'. Often these devices are dimmers , like shown in my initial screenshot, and are tasked to dim to 30% w/in 4 seconds. Most of them appear to be working still fine (basically still doing what they were supposed to do, even though the 'default' would suggest otherwise. It seems that these different 'Scene support' features were only introduced with V5, going by the title in the wiki. Since most of my scenes were created during V4, I wondering if I am seeing some migration issues here. Maybe I will need to go through each scene to make sure Responders no longer show 'default'/'default'. Thoughts?

Still trying to wrap my head around it.... @lilyoyo1, I think I understand your kpl example. Coming back to my initial screenshot: all the HT-LED-xx shown there are Lamplinc devices. What is their 'default', as these are dimmers and in this case, Responders?