Michel Kohanim

Hi Jon, Excellent. Thanks so very much for the feedback. Mine increased by almost 100%! Almost immediate With kind regards, Michel

Hi bambamf16, Along the same lines as what ScottAvery suggested: 1. Remove the spoken word for that scene in the Portal 2. Make a program that only has Then and which turns on the scene. Don't put anything in Else 3. Create a spoken work association for that program in the Portal With kind regards, Michel

Hi Mastermog2, I am so very sorry to hear. Can you please send your error log to support@universal-devices.com? With kind regards, Michel

Hi cyberk, What is m1cloud functionality? With kind regards, Michel

Hi Jon, I have a remote session setup with Harold today. With kind regards, Michel

Hi johnnyt, I am not sure how they do it. All I know is that we contacted WeatherBug, HAM, and Weather Underground and were told that for commercial usage we need to enter into a commercial licensing agreement. And, based on prices, we used HAM. We have no incentive in paying HAM but we do because it's being used as a commercial product. With kind regards, Michel

Hi Xathros, Thanks so very much for the feedback. Definitely has to do with 5.0.2. With kind regards, Michel

Hi barrygordon, Thanks so very much for the feedback and I totally agree. Currently, Connected Home only supports commands from Amazon servers to a Lambda function (i.e. Echo -> Amazon Server -> Lambda -> Portal -> ISY -> Portal -> Lambda -> Amazon Server -> Echo). And, in each step of the way, the certificates and authentication are checked. Benoit spent a significant amount of time figuring out where the bottlenecks were and it turns out that geographical proximity between Lambda and Portal caused between 500 and 1000 m.s. delay. To make the matters worse, Amazon server only talks to a Lambda function in a specific region. So, instead of having the ability to simply have Amazon talk to a Lambda closer to ISY Portal, we had to move the WHOLE portal to be closer to Lambda. Quite painful especially since DNS records didn't get updated for about 11 hours! All and all, I am happy that we made the move and, again, I do apologize for the interruption in service. With kind regards, Michel

Hello everyone, http://forum.universal-devices.com/topic/18145-isy-portal-maintenance-02-10-2016/ With kind regards, Michel

Hello all, I am so very sorry for the inconvenience. We moved the servers closer to Amazon Echo servers for improved performance and unfortunately their server didn't update its DNS till early this morning. Please do Discover again. Also, please note that you should see at least 50% performance improvement from Echo to ISY. I would love to hear more about your experiences. Again, sincere apologies. With kind regards, Michel

Hi jpjoe, I am so very glad to hear. You can purchase the power supply from Smart Home or our store (https://www.universal-devices.com/sales/?category=accessories). This said, we do not have good shipping rates for individual units. So, if I were you, I would buy one from Frys (anything from 5-30 volts, center positive). Also, your ISY might still be under warranty and as such we would be delighted to send you one free of charge. If that's the case, please do not hesitate to contact us at sales@universal-devices.com. With kind regards, Michel

HI jpjoe, I am so very sorry to hear. The first thing I recommend is using a different power supply. Anything between 5-30 volts will work, center positive. If you still do NOT see the power light turn on on your ISY, then please contact sales@universal-devices.com and we'd be delighted to help you out. Wtih kind regards, Michel

Hi Lee, That's fantastic news and thanks so very much for the update. For your reference, here's a little Java command line utilities that takes HEX and converts them to what ISY Network Resources expects in the body: ​http://www.universal-devices.com/networkresources/HexToNRDecimal.zip With kind regards, ​Michel

Hello Automate The World, Is this a 994i? If so, do you know how many nodes/scenes/folders you have? It might be that you are reaching the 254 limit. With kind regards, Michel

Hi barrygordon, The reason is TCP State Flow diagram. Even if ISY closes the socket, it goes into a close-wait state waiting the client close. So, if your app does not close the socket, ISY will have to stay in that state for that socket for approximately 6-12 minutes as per TCP specs. So, in 4.4.3, we now actively look for sockets that are in this state for more than 1 minute (from the last packet) and release all their resources regardless of the last-ack. You might want to check your code and make sure it DOES respond to close-notify from ISY and sends a Last Ack/FIN. With kind regards, Michel

Hi bilsk, What you are suggesting is illegal from a commercial use perspective. That's why we are currently paying HAM for their services (i.e. we would very much prefer not having to pay anything!!!). With 5.0.x, you can create a node server (or maybe one will exist) and have a climate node and simply push your variables to the properties for that node. As a matter of fact, if you are a developer and comfortable with Python, you can do that now using Polyglot on a Raspberry Pi. With kind regards, Michel

Hello all, We shall look into geofence. This said, can you please provide us with a list of features that you would like to work with MobiLinc/ISY Portal? Also, has anyone tried pointing http URL/Port in MobiLinc settings to ISY's local IP address/Port? Bob P, are you certain GeoFence works with MobiLinc and Dynamic DNS? If so, then it should automatically work with ISY Portal. With kind regards, Michel

Hi Barry, Please go to 4.4.3 (which has a fix for clients that do NOT close socket and ISY waits 12 minutes before closing them). With kind regards, Michel

Hi blisk, Have you tried having your PWS publish to CWOP which is then picked up by HAM? With kind regards, Michel

LeeG, Yes, precisely. Thanks so very much! With kind regards, Michel

Hi max90034, At the moment, unfortunately so. This said, however, we may be working on some type of discount for more than one ISYs per account. The challenge is how to distinguish individuals vs. installers. With kind regards, Michel

Hello larryllix, I totally understand your point alas I just do not know how we can make this into a more human readable format. Unfortunately, TLS/SSL is a little technical. Hi MWareman, Thanks SO very much for the details. With kind regards, Michel

Hi Barry, ISY retries connecting to the portal every time it gets disconnected automatically. I think what you are experiencing is due to 5.0.2 (which does not have the fix for sockets that are left open). With kind regards, Michel

Hi barrygordon, You are using 5.0.2, correct? Can you please take a look at your error logs? Also, if you are using MobiLinc, I know it does not close sockets and keeps opening sockets and in 4.4.2 (and above) we are now actively looking for open sockets that have no activity and close them (it will eventually exhaust all ISY sockets and buffers). Unfortunately 5.0.2 does not have the fix that we included in 4.4.2. With kind regards, Michel

Release Date: 2016-04-10 [Framework] - Proxy and Web server use different VMs - Default Proxy port is now 443 (used to be 8001) Release Date: 2016-02-28 [Echo] - Support for Multiple Echo/Accounts. Release Date: 2016-02-11 [Echo] - Improved performance for Echo/ISY Communications Release Date: 2016-02-07 [Portal] Remember me [Echo] - Scene Dim/Bright - Spoken lookups in red (when already used) - Spoken aliases (5)