Michel Kohanim

Hi pastro50, No, what I am saying is that Amazon decided to enable only a few devices locally. This has nothing to do with ISY. The bridge is EMULATING a Hue. Amazon THINKS this is a HUE. If that's sufficient for you, then there's no need for ISY Portal. With kind regards, ​Michel

Hi pastro50, There are only a limited set of devices that work directly with Echo (Phillips Hue). Others must go through the portal. If yo have the bridge that emulates Phillips Hue, you don't need the portal. When you purchase ISY Portal, the Network Module is tied to it. If you do not renew the ISY Portal subscription, you will lose the network module. If you don't want ISY Portal but you want the Network module, you can send an email to sales@universal-devices.com and ask them to switch it for you. This way, you will lose ISY Portal but you will have the Network module in perpetuity. With kind regards, Michel

Hi khag, The reason is that "remove all links" will also remove the device from the PLM, from other devices, and should also be removed from ISY otherwise you'll end up having all sorts of unexplainable events. With kind regards, Michel

Hi smokegrub, I am so very sorry to hear. Do you remember whether or not you had any green/gray 1011 icons next to any of your devices? Also, did you try the links I provided above vis-à-vis Admin Console hanging? With kind regards, Michel

Hi stusviews, That is related to a timeout during TLS negotiation. If your ISY is busy, the likelihood of getting this error gets higher: ISY can handle 3 simultaneous connections and 32 sockets. In 99.9% of the cases, the reason for this is that a) ISY is busy doing something which is notified to the Admin Console the Admin Console tries to call ISY to figure out what happening so that it can have relatively accurate progress bar. With kind regards, Michel

Hi guys, Not yet in production. With kind regards, Michel

Hi smokegrub, My pleasure. Please do not hesitate to contact support (links below) in case you cannot fix it. With kind regards, Michel

Hi smokegrub, Depending on your OS: http://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Hangs http://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized.2FInvisible_and_Cannot_be_Restored http://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Closes_Automatically With kind regards, Michel

Hi lhmathys, Please submit a ticket and we'll do a remote session. With kind regards, MIchel

Hi lhmathys, If you are being prompted that ISY needs to be rebooted, then most probably the certificate is something ISY does not like. Do you know the key length and signature algorithm? With kind regards, Michel

Hi lhmathys, Are you certain that you are doing this for HTTPS Server and not HTTPS Client? With kind regards, Michel

Hi RichT99, Browser cache does cause this issue. So: 1. Please make sure you follow the instructions here: http://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration#Instructions_for_using_Multiple_Echos_Smart_Home 2. For each account, close the browser and reopen (or use another browser) With kind regards, Michel

Dr. Pepper, This requires a comprehensive solution. It's on our requiremnets list but I cannot give you an ETA. With kind regards, Michel

Hi RichTJ99, Please go to Admin Console | Configuration | Portals tab and click on the Approve button. With kind regards, Michel

Hi Bernardo, Do you have MobiLinc Connect? With kind regards, Michel

Hi Athlon2k2, Thanks. This is what I suggest: 1. Move your PLM to a different outlet and one which is not shared with other transformers/power supplies 2. If you have any INSTEON thermostats, reboot them 3. Restore a good backup from before any of this (you might lose a few things). You have to make sure that it's from before replacing the PLM 4. File | Restore Devices With kind regards, Michel

Hi lhmathys , Please open Java Console, check all the debugging checkboxes (Advanced tab), redo the experiment and then paste the contents of Java console back here. With kind regards, Michel

FYI from Amazon : "8:48 PM PDT We have identified issues in AWS Lambda's capacity subsystem related to the increased API error rates and latencies in the US-EAST-1 Region and continue to work toward resolution." With kind regards, Michel

Hi all, Definitely AWS Lambda related. Unfortunately, there's no ETA. We'll keep you posted. With kind regards, Michel

Hello everyone, We are investigating but it does seem to be AWS in the east. We'll keep you posted. With kind regards, Michel

Hi Techman, Thanks so very much for the update. I very much doubt this had anything to do with Norton. With kind regards, Michel

Hi Techman, That would be highly unlikely unless you had no status updates in the Admin Console from other devices. Just to be clear, even though you see a mismatch in link records, right mouse click | Write updates to device does absolutely NOTHING. Correct? With kind regards, Michel

Hi Techman, Is there a green/gray icon right next to it? With kind regards, Michel

Thanks for the feedback everyone. With kind regards, Michel

Hi Athlon2k2, The error logs are with regards to the ISY trying to communicate with devices in which this PLM does not have a link. Did you actually do a File | Restore Devices? And, if so, did you see a series of link creations in the PLM FIRST before all the traffic you attached? With kind regards, Michel