smokegrub

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

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

I have bought essentially all my Insteon products from smarthome.com. They have been excellent. I am concerned that they appear to be having problems with their supply chain. My hope is that is temporary.

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.

dbuss: I think that is where I will end up. I have had problems with this since it was set up (several years) ago. I have spent about six frustrating hours with this! I am not a happy camper!

I have two ISYsThe first is Chesapeake-last two letters in UID are 7fThe second is Wolf Creek-the last 2 leters in UID are a3The profile for Chesapeake is XXXXXXXX@gmail.comThe profile for Wolf Creek is xxxxx@suddenlink.netIn the profile view if I switch my preferred ISY from Chesapeake (7f) to Wolf Creek (a3) the email address stays the same for both views.The Users view was incorrect so I changed it to display the correct User Name and Preferred ISY.In the Alexa Accounts both ISYs display the devices for 7f and ae merged. I have tried deleting and enabling the skill (ISY Optimized...) for each and the result is the same.I believe the problem(s) are in the setup of the Portal.Help will be appreciated.

I have moved this topic! I have two ISYs The first is Chesapeake-last two letters in UID are 7f The second is Wolf Creek-the last 2 leters in UID are a3 The profile for Chesapeake is XXXXXXXX@gmail.com The profile for Wolf Creek is xxxxx@suddenlink.net In the profile view if I switch my preferred ISY from Chesapeake (7f) to Wolf Creek (a3) the email address stays the same for both views. The Users view was incorrect so I changed it to display the correct User Name and Preferred ISY. In the Alexa Accounts both ISYs display the devices for 7f and ae merged. I have tried deleting and enabling the skill (ISY Optimized...) for each and the result is the same. I believe the problem(s) are in the setup of the Portal. Help will be appreciated.

Teken, thanks. I want to update to 5 but I want to first sort out a firmware problem.

I wen t to https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop and I don't see where/ho I am to resolve the disparity between UI 4.7.5 and Firmware 4.6.2. I must be missing something.

Thanks, Michel. You could not possibly recall, but when I downloaded 4.7.5 the UI did not match on my two ISYs. You told me not to download 4.7.5 to the Wolf Creek ISY until I was at that location. Three eye surgeries and COVID have kept me away for almost a year. Version 4.7.5 is now in place. Do you feel that when I next update both will match? By the way, the Chesapeake ISY did not show up in the Launcher at Wolf Creek. I had to get the UI from the Portal and add that back to the Launcher. Chesapeake now shows up. I am anxious to take the big leap to 5 as long as these problems are arising.