smokegrub

I deleted the Java cache and it still doesn't install the "correct" Launcher. It installs one that will run with Catalina but not Mojave.

Michel: Perhaps this will help: This launcher is incompatible with Mojave In the past when I placed the start.jnlp icon on the desktop it changed to the Launcher Icon. This time it changed to the incompatible Launcher above and temained on the desktop.

start.jnlp

I cleared the JAVA cache again and I continue to get a Launcher icon that will not run with Mojave. Need help.

I just downloaded the most recent version of JAVA and version 4.9.0. When I place the start.jnlp file on the desktop the and select the Launcher Icon I get the message that it required OS 10.15 or later. I am running Mojave because an important app will not run under Catalina. I can access ISY using the start.jnlp icon but I would like to use the Launcher. Any help?

For what its worth, there have been times when I have gotten the "I'm not quite sure what went wrong" message. In most such cases I have found that only one of seven Alexa devices was having a problem. I disconnect power to that device and reboot it. That has resolved the problem for me on several occasions.,

I appreciate the clarity added by the last few posts. I have two homes. Both have ISYs and all the devices at both are Insteon. I haven't counted them but I suspect I have about 80! My setup is solid. I am technologically challenged so I avoid change as much as possible. Thus, I have avoided the Polisy to this point because I foresaw it to be an emerging technology--the cost was not an issue. I understand UDI's business decision to move to a system based almost exclusively on node servers. However, I can already see that each node server, at least at this point in time, represents a technical challenge to the developer and the end user. So, I will be waiting until the "dust settles" on this issue. I am thankful that at present, at least, I can expect my Insteon systems will continue to function. One Insteon device, the SynchroLinc, already presents a problem to me. Insteon has dropped it, and I can't find it anywhere. Fortunately, my neighbor is very talented at replacing the caps in such devices. Perhaps he can resurrect it.

Problem resolved itself. Don't have a clue why/how.

I have my tag manager in a window. You may want to try that.

Personally, I have found my Echo's occasionally beging to behave abnormally. A reboot of all of them (7) resolves many issues.

Allow an older, lay user to make a few observations. Not all homeowners are interested in home automation. None of my family are interested nor are any of my neighbors of whom I am aware. Some are messing around a bit with Alexa; most are not. I suspect most see the task of setting up a system as too daunting and they haven't a clue who could set it up and what the cost/benefits might be. As for me I have two homes with two separate home automation systems, two ISYs and all Insteon devices. I set them up with awesome help from this forum and a lot of work. I have Echo's scattered throughout both homes and use verbal commands to execute desired automation functions. I have never used a contractor nor do I intend to do so. Is my work complete? No!!! Routine maintenance is essential. I must emphasize "routine". I enjoy the challenge but, being almost 76 years old, my wife and I have discussed who will maintain it if I am unable? The answer, it will probably have to be removed even if the home is sold or becomes the property of our heirs. As for the fate of Insteon, I want them to succeed into the foreseeable future. I don't want to, nor do I have need to, change/add technologies. The fact that devices are being discontinued is disconcerting to say the least and especially so given the description "discontinued".

I have come to the conclusion that my ISP must have blocked the CAO tags being sent by gmail. I will get it touch with Cox as soon as possible and see if I can get this sorted out. Thanks for taking the time to try to help me.

No success with that Larry. Weird. The tags still say they cannot send an email to my gmail account because "it does not exist". Do you know if others can send email from tags to a gmail account?

Will do.

I think the proble, is with Google. I will wait a couple of weeks and test again. Good luck with your problem. \

Tags will not send email notifications to my Google mail account-says the account does not exist. Test emails sent to that account from Apple mail work fine as do emails sent from my Cox account. Any help?

I use two separate Amazon accounts and point each to one of my ISYs. It is awkward and a pain when you change accounts, but it eliminates confusion in device naming.

For what it's worth, I have found that when I start having problems I reboot all my Echo's and the problems are typically resolved.

I am hoopefully awaiting an IOS version.

I finally resolved this. What a pain!

I have a problem that has plagued me for years. I have two ISYs in my portal. That, in itself, makes things more complicated than it should be in order to get the devices to display properly in the IOS Alexa app. For some reason the app wants to display the devices for both ISY accounts simultaneously! I can find no way to resolve that problem. I used to be able to delete all devices in the app, delete the Smarthome skill, re-add the skill and then discover devices. That was a major pain but it worked. Now, I can find no way to delete and discover devices in the IOS app. Interesting, on my Mac the correct devices are displayed, but I can't create routines there. I have spent days working on this problem and a lot of time with UDI. Any help you can give me will be more than appreciated. I don't think I would have this problem if the ISYs were in separate portals. Perhaps I am not executing some key step.

Finally resolved .

Thinking that the fact that both or my accounts had the same password might have caused the Wolf Creek account to display devices from both accounts I changed the password for the Wolf Creek account in the Portal. Then, I changed the password in the Wolf Creek Alexa account to match the password in the Portal. I then disabled/enabled the skill in the Alexa account. All the devices still appeared in the Wolf Creek account. I am at a loss!

Thanks, Benoit. I have been working with Brad McAdams via a ticket. We left the issue yesterday with him doing more research with your technical folks. The only thing I have seen that may be a part of the problem is that I use the same password for both accounts.

Guess I will have to submit a ticket on this.