Michel Kohanim

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

Rand, My pleasure. And, thank you so very much for your continued feedback and guidance on the forum. I sincerely appreciate it. With kind regards, Michel

Rand, As usual, you have outdone the whole UDI team all by yourself. Thank you so very much. HAS, You can "hold" schedules for a any given date and you will have, at the least, the desired effect for that date. Simply, create a "Hold" schedule and make the date/time the date/time for your party (or interval). With kind regards, Michel A bit contrary to your thought, but, in fact, I rely on the scheduler to dim the lights when the party should end. I use the longest ramp rate available and the change is very subtle. I call it a Midnight Scene, the lamps dim to a very low level, only enough light to allow one to navigate. It's a pretty good hint that people should at least quiet down if they are not yet ready to crash Since we can pretty much party any night here I have it scheduled for earlier times on weekdays and later times on the weekends. It reads as if this is what your 9PM scene is like, so all you really want to do is change that to a later time when you party. I have to believe the upcoming triggers will allow you to press a button to do this. As of now, calling the Party Scene again if the lights begin too dim to early (9PM) for you should keep them on until your Morning Scene is called. If you use long ramp rates you may be the only person to notice the 9PM dimming in time to hit the Party Scene again. I would suggest that you call your 9PM scene twice every night, once at 9PM, and if you override that (or not) again at the end of Party Time, which will make absolutely no difference if it was already implemented at 9PM. Rand

HAS, I totally understand. The issue is not the triggers ... the issue is the existing links between switches and lights which ISY has NO control over. Here's the main question: All devices in your party scene, are they controlled only by your Party Mode button? If not, then ISY cannot control the communications between other controllers that also control the same and/or sub/set of devices as in your Party Scene. Do I make sense? With kind regards, Michel All devices are INSTEON. ISY should have a lock down function in the "trigger" section IE: If 7 DB 30 A is on : Lock all Not trying to be a "party pooper", but nobody wants the lights going off in the middle of a party

Precisely!!!

Hello All, Here's a high level list of what to expect in Release 2.4: Bug Fixes Right mouse click on MAC/OSX does not work: Done File dialog on MAC/OSX does not allow filename entry: Done Regression: adding a KPL/SWL manually (using the address) caused ISY to hang: Done Regression: removing devices left residue: Done The cross reference tree view did not reflect both Manages and Is Managed By relationships: Done Enhancements Show default backup filename: Done All on/off on My Lighting and Network icons: Done All on/off from controllers such as ControLinc: Done Full support for RemoteLinc: Done The window opens maximized: Done The state of the window is now persisted between sessions: Done The state of the tree is now persisted between sessions: Done EZRain timer support: Testing All On/Off workaround: Testing 80% likelihood to be included Replace Device: Testing Keep existing links: Testing Merge existing links: Testing 40% likelihood to be included Enchanced Triggers/Schedules: Testing With kind regards, Michel

Mark, Can you make an Inseton fan black-box yourself (already)???? With regards, Michel

HAS, This is a wonderful and very useful requirements some of which we can help you with (triggers/schedules to be locked down) and others which have to be directed to SmartLabs: ISY does not control the traffic between devices so, if your Party Time devices are controlled by other controllers besides your Party Time button, then there's practically not much we can do to stop them communicating amongst each other (or locally any of the lights are connected to the load). I do welcome any suggestions technical or otherwise on how to achieve these requirements. Thanks so very much for your feedback, With kind regards, Michel

HAS, I sent you (PM) some instructions couple of days ago and never heard back from you. Did you receive them? With kind regards, Michel -50000,null,null,null -50000,null

Hi HAS, For some reason, ISY cannot resolve our mail server address. Would you please: 1. download http://www.universal-devices.com/tools/udfinder.zip 2. save it as udfinder.jar in a directory of your choice 3. double click on udfinder.jar (see step 2) 4. click on your device (on the top) 5. Make sure you have DHCP IP - assigned DHCP Subent - normally 255.255.255.0 DHCP DNS - your router's IP address Interface - Ethernet MAC Address - 6 Hex numbers Static IP - 0.0.0.0 Static Subnet - 0.0.0.0 Static Gateway 0.0.0.0 Static DNS 0.0.0.0 Thanks and with kind regards, Michel -50000,null,null,null -50000,null

evarsanyi, I am so very sorry for the troubles you are experiencing and we'll do our utmost to find workarounds for that 5% which causes so much frustration. Now, for your All Off scene, you can do a simple work-around which we call Aliasing and which does not require triggers + it works around the problem of having controller/responder relationship between KPL load and one/more of its buttons. What we are going to do is to trick the system: 1. Make your KPL Load the controller for the scene (All Off) 2. Remove your KPL button from that scene 3. Use Synchronized Groups to group your KPL button with the KPL load So, this way, when you click on the KPL load, in effect you will control the whole scene where as when you click on the KPL button, you will only control the load for that KPL. The only issue - which we are going to solve in the next release (very ugly workaround) - is that when you click on the KPL button which turns on/off your load, ISY is not going to be notified so the status of your load will be out of synch with ISY while you are in 2.3. With kind regards, Michel

HAS, Would you be kind enough to let me know what error you get when you try to do a TM on the shell? I am so very sorry for all the trouble. With kind regards, Michel Correct. I am on DHCP and I can access my ISY remotely I did the above. No email.

Rand, Yes, you are 100% correct. The ability to drag/drop multiple devices at a time is in 2.3. evarsanyi, The question I have - and as Rand suggested - is whether or not the different scenes you are creating (for the same devices) are to be controlled by Insteon Controllers within the same scenes or by the scheduler/triggers? If all you are trying to do is to have different on level/ramp rates for each one of the controllers in the scene, then - and as Rand suggested - you can simply put all your responders and controllers in the SAME scene (don't create different scenes) and then change the on level/ramp rate for each one of the responders based on each one of the controllers: 1. Click on each one of the controllers in the scene (in RED) 2. Change the on level and ramp rate for each of the devices in the same scene in the Right Bottom pane Import/Export! Well, since you seem to be quite well versed in Java/programming, may I humbly suggest that you take a crack at our JSDK and implement this functionality (bulk import/export). I am sure you will receive a lot of interest from our little community here. With kind regards, Michel

Rand, Thansk so very much. Yes, it's on the todo list ... With kind regards, Michel