Michel Kohanim

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

Hi Bruce, You have finally caught up to what everyone else has been requesting: scheduling triggers and triggering schedules. Unfortunately, it has taken us a lot longer than expected to "redesign" and implement this feature. But, rest assured that it will be in our next "major" release. With regards,

C Martin, Is Load identifies whether or not a button/switch is actually physically conntected to a load. This is especially useful for KPL button 1 when in some cases it's controlling its own load. With kind regards, Michel

Mark, Thanks so very much for your query ... one has been created for you. With kind regards, Michel

Bruce, Have you renamed My Lighting? Otherwise, it's just one of the items in the Location list (in New/Edit Schedule, at the top) alongside all other devices and scenes. If you want to turn EVERYTHING off, all you need is to create a schedule for the "My Lighting" location. Please let me know if you can't find it. With kind regards, Michel

Mark, Instructions and example in our Wiki Site ( http://www.universal-devices.com/mwiki ). Here's a direct link to the article Thanks and with kind regards, Michel

Hello All, Release 2.4 is now available. Thanks and with kind regards, Michel

Hello All, Version 2.4 is now available. For more information, please checkout our Wiki Site. This release migrates the file system. As such, please make sure to backup your configuration BEFORE and AFTER the update. Thanks and with kind regards, Michel

Bruce, Thank you! With regards, Michel

Hello Bruce, No questions are dumb here ... they will help us tailor ISY to be more intuitive for everyone. Please find my comments below. With kind regards, Michel The ramifications - as Sub Routine so eloquently pointed out are: 1. No schedules shall be run 2. No triggers shall be sensed 3. All Insteon devices will work as programmed since the programming resides in each device Yes! Administrative console is simply a UPnP client which automatically "finds" other UPnP clients on the local network. Administrative console is part of ISY but since in MAC, there's no UPnP to find ISY, that's why you have to go to our website. The effect is that the administrative console is downloaded from our website instead of ISY. 95% correct. PLM contains responder links for every "controller" in your Insteon network. That's the only way that ISY (through the PLM) is notified of physical button presses/clicks on the actual Insteon devices. ISY only interprets the received events and a)updates the administrative console with the latest status of each device b)in case of triggers, figures out if conditions have been met and fires the responses You can unplug ISY and EVERYTHING (except schedules/triggers) will continue working as normal. ISY does NOT meddle with Insteon network; it only senses the traffic through the PLM (simply another Insteon device). Now, if you unplugged the PLM, then the only adverse effect would be that your KPL load buttons would blink because they cannot find the responder (PLM in this case). Replacing a bad PLM is as simple as installing a new PLM and issuing File->Restore Modem (PLM) Excellent post. Again, all your Insteon programs (scenes/ramp rates/on levels) would continue working as programmed regardless of ISY/PLM being on the network. thanks, Bruce

sfhutchi, Thanks for your patience ... would you be kind enough to let me know for what aspects you use HouseLinc? There might be some simple fixes/enhancements that we can include to alleviate those scenarios. Thanks and with kind regards, Michel

Kib, Thanks so very much for the update, the compliments, and your business. We are indeed very proud of our little box but none of it would've been possible without the feedback and suggestions of our clients. Security random timer/schedule is for a fact in our trigger/scheduler release which, as you may already know, could slip yet again. I truly apologize. Thanks again and please don't hesitate to contact us in case you have any questions/suggestions/comments. With kind regards, Michel

sfhutchi, Long time no see! We are working very hard to put at least some of the trigger functionality into release 2.4. Due to a complete redesign, this process has taken us longer than anticipated. Please be assured that we recognize the importance of the this new enhacement and will do our utmost to support it as soon as possible. If triggers don't make it in release 2.4, the next release would be in approximately a month. In release 2.4, we have added a work-around for All Off/On which alleviates at least some of the needs for complex triggers. With sincere apologies and with thanks for your patience. Regards, Michel