Michel Kohanim

Rand, Yes, mid October unless there's an urgent fix which should be released before then in which case we'll put all the tested features in that release. So far, finally, things are looking much better. Thanks so very much, With kind regards, Michel

Thank you so very much. HAS, any news on remote access? With kind regards, Michel

George, This is intended for informational purposes only and has no impact on anything else except the topology. With kind regards, Michel

MikeB, You should've received ISY by now. Please let us know if we can be of any assistance. With kind regards, Michel

Hello All, Here's a high level content of release 2.5: Additional Features 1. Combinesd scheduler/trigger functionality 2. EZSnSRF Support -- out 3. Minimal support for X10 devices 4. ELK Security System Support 5. Vista Media Center Plugin - allows you to control your INSTEON lights through your TV (if you have a Media Center Extender such as XBox) Improvements 1. No longer is there a need for AutoUpdate userid/password 2. Local URL is shown on Help->About Bug Fixes 1. EZRain scene and ISY/PLM hangup 2. Linux mouse handling Additional features are planned but not guaranteed. As such, I will keep this post up to date with information as they become available. With kind regards, Michel

MikeB, The following will not work: a. On the box itself, notifications (sending email/sms notifications) b. On the Admin Console, AutoUpdate notification: you will not know when an update is available With regards, Michel

shearness5150, Apologies for the inconvenience. Please make sure your PLM is connected to Port A and then please try http://www.universal-devices.com/MyInsteonISY . I will also follow up by calling you today (Sunday) if that's OK. With kind regards, Michel

bradsjm and MikeB, Thanks so very much for the feedback. We would certainly entertain supporting any protocol that enables our customers to have an "inexpensive" but feature rich home automation solution. Usually, the only problem is that "standard"/"popular" are not always universal; example: we consider our web services to be quite popular and standardized (UPnP) but apparently not to CQC! Furthermore, Microsoft (alongside many others) has already published its own device communications protocol called Web Services on Devices (WSD). Given the finite amount of resources in our controller, thus, it would be quite impractical to support "all" standards/popular protocols. All this said, however, I would be delighted to have a 3 way call and discuss the possibilities; there might be a simple solution out there which does not require the full support for xAP! With kind regards, Michel

MikeB, Yes, they have been available for a while but not maintained nor have they been kept up-to-date due to shortage of demand! Multiple ISYs can infact coexist on the same network and we even "used to" have the capability of acting upon events from different ISYs. We have gotten rid of most of this functionality since. As far as the JSDK, all the concepts are the same but we are missing the device specific packages. We would gladly start working on them as soon as we get more demand which, at the moment, is limited to 1 or 2 per year! With kind regards, Michel

MikeB, I am so very sorry for the late reply. This is our philosophy: One ISY - one protocol - make it as comprehensive as possible (as you can see from the INSTEON ISY). So, with the exception of ELK, an INSTEON ISY can only communicate with INSTEON devices. A UPB ISY, can only communicate with UPB devices. An Aprilaire ISY, can only communicate with Aprilaire thermostats and so on and so forth. So, the short answer to your question is ISY-26 only supports INSTEON devices + ELK. I hope this answers your question. Please don't hesitate to contact us with your questions/comments/suggestions/feedback. With kind regards, Michel

Could you clarify this a bit? Why would this be better if I start with a clean system? When we do a crawl, we do simply find links and not local device variables such as those that maintain the state of toggle buttons in KPL. We do, however, query the device (afterwards) to get the local on level and ramp rate. So, it simply means that during a crawl, ISY will not bring in your KPL's toggle states. If you start with a clean system, then, you have, by implication, agreed that there are NO toggle modes nor are there any Mutual Exclusive relationship between the buttons. We do have an easier alternative: 1. Choose "Overwrite existing links" when you link your devices 2. Restore Devices after you've linked all your devices into ISY. This should be quite fast since, at this point, you don't have any relationships between devices. By mid October (if not sooner). My pleasure. Yes, it's accurate. Thanks again.

MikeB, Please find my comments below. Resetting does leave you with a cleaner system especially when it comes to reading the toggle/non-toggle/ states of KPLs. This said, however, you can start with the crawl function which brings all the links (including broken ones), scenes (groups), and relationships. Then, you can use ISY to tailor your configuration to your heart's content. At the end, you can do a File->Restore Devices which simply goes through the whole network and makes sure all the Insteon devices are in synch with what is in ISY (kind of like defrag). This in effect, cleans up your whole system and guarantees that what's out there is equal to what you have in ISY (unless it fails in the process). YES. You have 3 options: a. Rewrite existing links b. Rewrite existing links but simply bring any new device found in the links c. Spider the whole network, find new devices in links, and bring in all the links (which includes remote ramp rates/on levels for each scene). This, however, does not bring in the KPL toggle mode settings. It can do either. The choice is yours. Yes, it creates a scene out of them with one member. Simply delete the scene. If you want 100% clean network, follow up your installation/import with Restore Devices. Make sure you have an Access Point plugged into your PLM + you do not have any X10 devices (including KPLs with X10 addresses) on when you do a Restore Devices operation. No. ISY can sense whether a KPL is configured as 6 or 8 but we do not allow reconfiguration from within ISY Yes, as well as Mutual Exclusive buttons (when one is on make sure the others are all off) Absolutely. Absolutely without which ISY would not be privy to physical button presses Currently (release 2.4), no. Release 2.5, yes. Absolutely and, for your information, the following additional functionality: 1. Restore Modem (PLM) - if you ever have a defective modem, use this function to replace your modem. ISY will reprogram all your devices to the new PLM's address and reprograms the new modem PLM with a modified copy (different address) of the old one 2. Replace Device - if you have a defective device, ISY can replace it for you, including adjustments to all the scenes, schedules, triggers My pleausre. With kind regards, Michel

Eric, Sorry for the delay in my reply. I missed the "unanswered" posts. There's a separate URL to access ISY: simply replace the /p at the end with /x (for external). So, to access your ISY remotely, simply use: http://your.isp-ip.address:ISY_PORT/0/x. Please let me know if this solves your problems. Also, if you do have a UPnP enabled router, ISY can automatically configure your port forwarding (File->Enable Internet Access). And, to figure out what's your remote access URL, you can simply go to Help->About. With kind regards, Michel

Hello MikeB, Yes, JSDK has been out for quite a while now and we have 4 developers registered. I am not sure whether or not they are actually using it. You might want to post in the Developer forum. Thanks and with kind regards, Michel

dougos2, My pleasure and thank you so very much for your vote of confidence and patience. Triggers and schedules will be in our next release. With kind regards, Michel

Hello JEM, Unfortunately, not at the moment. This said, however, we do have all our functions externalized as web services and, as such, it would not be difficult to make a web services/opc bridge. With kind regards, Michel

dougos2, First of all, there are no dumb questions in our forum. So, please don't hesitate to post your questions/comments/suggestions. Now, "Hold" has been a confusing issue throughout our development cycle and, as such, we have decided to completely redesign our triggers/scheduler functionality. Here's how Hold currently works: 1. Hold is a schedule event in and of itself. What it does, is to put all the other schedules, for the given location, and the given date (or date ranges) ON HOLD 2. If you want to remove a Hold, simply remove the Hold schedule In short, leave all your current schedules intact. To put the schedules for a given location on Hold, create a NEW hold schedule for that location. You can create a Hold schedule for a given day (except today) or a given duration (i.e. from 12.25.2007 to 1.1.2008). I hope this makes sense. If not, please don't hesitate to contact us. With kind regards, Michel

Hello Rand, We never got a contact name from sloop nor were we ever contacted. This said, however, since we want to support inexpensive touchscreens as well, we have started developing UDMobile on C/C++ portable platform. It's coming along slowly. I shall surely keep you updated with the latest. Thanks and with kind regards, Michel

C Martin, Very interesting idea ... I think - I am not sure yet - our new trigger functionality would eliminate the need for virtual triggers (variables) especially for sequences and timed events. I will let you know if otherwise. Thanks so very much for the idea/feedback, With regards, Michel

GPG, Wow, this is a brilliant work-around for ISY's current limitations. Wow again! Thanks so very much for your feedback, With kind regards, Michel

Thanks so very much! With kind regards, Michel

sfhutchi, The more we go through the UPnP setup - and as you suggested - the more we are moving towards making it secondary. We will keep it since, in Vista, there's no setup whatsoever: it automatically shows up. Thanks so very much for your feedback, With kind regards, Michel

sfhutchi, Thanks so very much for the detailed explanation. We are going to do our utmost to get this out in our next release. With kind regards, Michel

C Martin, My pleasure! With regards, Michel

Bruce, Thanks so very much for your vote of confidence. With kind regards, Michel