Michel Kohanim

Hi Jon, Thanks so very much. I checked the portal logs and everything is looking fantastic. This said, I must admit that recently I have been plagued with Echo being unreliable and do strange things: 1. Two Dots work perfectly every time 2. The Echo, on the other hand, is now responding with "Turned on x" instead of "Ok". And, in some cases, and for the same device, it keeps saying "I cannot find x in Michel's profile" or "that command does not work with x" or a simple beep (as if it didn't understand it even though the app says it did). Note that this behavior is very much like the Skill's behavior and not connected home Something very strange is going on. Hopefully we'll hear back from Amazon soon. With kind regards, Michel Michel

Hello everyone, Amazon has been extremely helpful and professional. They were going to take a look and let us know. I shall keep you posted. With kind regards, Michel

Hi Jon, Can you please check your error log? All systems have been 100% up and we have had no resource usage above the ordinary. With kind regards, Michel

Hello all, Just a quick update: we had a very good call with Amazon on Friday. I made sure to mention the issues related to names not being recognized and the answer was that they specifically train Alexas with certain names and others may not work. I explained that they used to work and was promised that they would take a look at the document and see what may have contributed to this issue. Please note that all Connected Home features are now called Smart Home Skill (different API) which also includes thermostats and other things. We are working to implement them as we speak. All this said, I do suspect we'll have some disruptions and intermittent issues as they move their APIs. With kind regards, Michel

Hello everyone, I suspect it's Amazon ... everything is fine on our side including memory utilization and cpu. With kind regards, Michel

Hello everyone, There were incessant subscription calls in the portal (http://forum.universal-devices.com/topic/18744-04-11-2016-615-am-est-the-portal-appears-to-be-down/?p=174848) and we think that may be the root cause. We are currently investigating and your help and feedback is extremely invaluable to us. With kind regards, Michel

Hello all, I am so very sorry for the trouble. For those of you have had this issue, can you tell me: 1. Was https://my.isy.iodown? 2. Was Echo down? 3. Do you use MobiLinc? If not, what app are you using? We found incessant subscriptions to the portal and think that may have been the root cause. The only clients we know that currently subscribe are: 1. MobiLinc 2. Admin Console 3. eKeypad 4. Agave Are you using any of the above? If so, how were they behaving? With kind regards, Michel

Hi rehills, Thanks so very much for letting us know! With kind regards, Michel

Hi marcin, I know Steve contacted you yesterday. Has this been resolved? With kind regards, Michel

Hi mapeter, Unfortunately not! With kind regards, Michel

Hi rehills, All systems have been stable and fully functional since the last production release. Is it simply not responding or do you get any other errors? With kind regards, Michel

Hi jimlamb1944, If you have a good backup, you can factory reset ISY and then restore your backup. Once prompted to change your network settings, choose no. With kind regards, Michel

By the way, we made the change and waiting to push to production during our next maintenance schedule. With kind regards, Michel

Hi Michael, Sorry for not being clear: Amazon Echo server does NOT like wildcards (not our servers). With kind regards, Michel

Hi guys, So very sorry: Amazon does not accept wildcard certs so we had to put back the original my.isy.io. We'll do a redirect. With kind regards, Michel

Hi heyphets, Thanks so very much for the report. We do indeed have a wildcard certificate you should not have this problem. We'll take a look. With kind regards, Michel

I shall keep everyone posted with anything we hear back from Amazon. With kind regards, Michel

Hi all, Sincere apologies: http://forum.universal-devices.com/topic/18744-04-11-2016-615-am-est-the-portal-appears-to-be-down/?do=findComment&comment=174214 With kind regards, Michel

Hello everyone, We went through the logs and there were two instances of 100% CPU utilization and major network activity between 4:50 and 5:50 AM and then again 9:50 and 11:50 AM UTC. Upon checking the logs, they were both related to Amazon doing auto discovery. Upon further investigation, it turned out - for some reason - Amazon Auto discovery was going against non-existing accounts (should not happen) which caused an exception which was not caught. A fix has already been put in. We shall monitor closely and make sure everything is running smoothly. Sincere apologies for the inconvenience. With kind regards, Michel

Thank you all. Just sent the list to our contact at Amazon. With kind regards, Michel

Hi Chuck, Thanks so very much! Included them on the list! With kind regards, Michel

Hi James, thank you and good to hear! With kind regards, Michel

Hi James, 1. What URL are you posting to? 2. Do you have Preferred ISY set in My Profile (my.isy.io/top right corner)? With kind regards, Michel

Thank you. I have saved the updates. Any others? With kind regards, Michel

Hi sloop, What you need to do is to have multiple Amazon accounts and multiple ISY Portal accounts: http://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration#Instructions_for_using_Multiple_Echos_Connected_Home Then you put a DOT or Echo in each room tied to specific Amazon Accounts. With kind regards, Michel