Michel Kohanim

Yes. Any chance it's still coming out today?

Hi, The PLM is NOT failing. The request failed is the inability of the PLM communicating with one or more of your devices. With Pro and 2.7.8, you will have indications of which devices are having comm errors. Nonetheless, having that list is the first step and I am sure we'll get to the bottom of it. With kind regards, Michel

Hi rlebel, Yes, you are correct. The next drop will be 2.7.8 ... we are at the final stages of testing so you should see it shortly. With kind regards, Michel

Hi pacificsloop, We are working with SHN to figure out what changed between their version 24 (which works perfectly) and their latest firmware. It's now evident that the latest version of EZFlora do not work with ISY. I do apologize for the inconvenience. With kind regards, Michel

Hi Al, in addition to the observations by oberkc, I really do think you have major communications issues. All these request failed messages are not normal and, in 99.9% of the cases, they only happen if the PLM cannot communicate with your devices. So, the first thing I would do is isolate which devices are having issues. Please make a list of those that you frequently get request failed for. Then, we are going to go through each one and figure out which one is causing the issues. With kind regards, Michel

Hi Rick, I just wanted to let you know that we spent hours trying to improve the performance of our email client. I am happy to say that we got some improvements (below 10 seconds) but we have reached the limits of SMTP specifications: authentication takes approximately 2 seconds. Every recipient takes an additional 2 seconds. TLS/SSL (gmail) takes 3 seconds for negotiating keys. The rest of the conversation is in sub seconds. We should have 2.7.8 out today so please do be kind enough to test. Make sure you change the timeout to the lowest possible number that consistently works (for me 400 ms works consistently with all my mail accounts). With kind regards, Michel

Hi Rick, Currently no, but it's surely on our todo list. With kind regards, Michel

Hi Joe, Thank you so very much! Now that you've opened the can of worms, the next firmware update is going to cost $1000.00. ... just kidding. Thanks again so very much for your patience and support. With kind regards, Michel

Hi Rick, Unfortunately you cannot install Apache and PHP on ISY ... I am going to work on our email client code and see what's causing such long delays. In software, everything is possible. Thanks so very much for your patience. With kind regards, Michel

Hi Rob, Welcome! If you want the events to be in that sequence then the program you have is the best way to do it. And, you are not using more processing power than spitting it into more programs. Waits are simply constructs that put the execution of a program (as a whole) in a queue to woken up after that period ends. With kind regards, Michel

Hi backinthelab, Thanks so very much for your kind words; I do appreciate it very much (and it felt great!). With kind regards, Michel

Hi RickL66, Thanks so very much for the detailed explanation. I am going to think about it a little. I just don't like the fact that there's another piece of hardware required just to make this scenario to work. With kind regards, Michel

Happy New Year to ALL! With kind regards, Michel

Hi mbrett, Apologies for a tardy reply. To support thermostats (which are a little unlike other INSTEON devices), we had to basically redo most of the device management/communication/synchronization code. While going through this surgery, we also included some enhancements such as: 1. Fail safe/Atomic device linking: you can turn off ISY, take out the device, and ISY knows exactly where to start from the next time 2. Batch mode (Pro only): allows you to do all your configurations/linking without having to wait for each to complete before starting the other. When you are done with everything and with a press of a button ISY goes out and does everything. Combine this with 1, and then you will have a worry free installation regardless of what happens 3. Now the UI lets you know which device is being worked on using different icons 4. You can send notifications to different groups of email recipients And more ... All this said, we do need a few more days just to make sure we are not going to crash anyone's system. I am hoping Thursday 12/31. Thanks so very much for your patience. With kind regards, Michel

Hi tome, 1. You receive both on/off in status as well. But, the evaluation happens if and only if the status has actually changed 2. You cannot query the status of a Motion Sensor but ISY keeps track of it for you and is as accurate as your communications. So, if you communications are 100% between the MS and ISY, then your status is 100% correct With kind regards, Michel

Hi Harold, Yes, please check these out: Yes, there are: 1. ISY AJAX: http://forum.universal-devices.com/view ... t=isy+ajax 2. TouchSwitch: http://forum.universal-devices.com/viewforum.php?f=49 With kind regards, Michel

Hi DevonSprings, Sonos would also work well since they do have APIs that you can use within the Network Module. With kind regards, Michel

Hi lapolonyc, Unfortunately Google Checkout's coupon processing is broken (they are fixing it with NO ETA!!!!). If this is the case, and you have already upgraded to 2.7.7, please purchase at full price, and then forward your invoice + the coupon code you are using to sales@universal-devices.com. A refund will be issued to you immediately. With kind regards, Michel

Hi, The problem is that you are using Status for your motion sensor. This means that your program off is going to cause the first program to run if the status of the motion sensor is still on. I suggest using Control for the Motion Sensor in the fist program in which case the program is evaluated if and only if motion is sensed "again". With kind regards, Michel

Hi tome, You are using Control which means that the program gets evaluated every time the motion sensor senses a motion. If you are looking for status change notifications, please use Status. With kind regards, Michel

Hi David, This is a known issue. Please upgrade to 2.7.7 (send an email to support@universal-devices.com). Thanks and with kind regards, Michel

Hi RickL66, I was hoping that you would use the network module to post (HTTP) to your twitter or facebook account. This way, you would not need to use a mail server at all. I will respond to your other post shortly. With kind regards, Michel

Hi Jason, That message in and of itself is not an error unless ISY cannot communicate with EZIO at all. Do you get any other errors? With kind regards, Michel

Hi RickL66, I think a better solution would be Network Module and perhaps a private Twitter account (or facebook). This way, the messages will get there almost immediately (http://forum.universal-devices.com/viewtopic.php?t=2795). With kind regards, Michel Thanks Michel. I was using 2.7.0 and the best I got my emails was in 18 seconds or longer. I finally tried the 2.7.6 beta and it's down to 14 seconds. If I could hear, that would be good enough for me, but since I rely on visual notifications and getting notifications to my Blackberry due to my deafness, it is critical that I get notified quicker. I am going to be getting 2.7.7/2 next week, don't know if it would make a difference in email speeds, but we'll see. Thanks for the response. Rick

Hi intellihome, Have you tried plugging them directly on top of the PLM. If they are indeed 3 years old, I remember having some strange communication issues in rare occasion where the unit was too far from the PLM. With kind regards, Michel