Michel Kohanim

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

HAS, Don't throw in the towel yet. We'll figure it out. So, let me get it right: You are on DHCP You can access your ISY remotely But, email notifications don't work If so, please do me a favor: 1. Click on configuration 2. Remove all recipients 3. Add a regular email address 4. Click on save 5. Create a simple trigger with Notify as the response I'd appreciate your feedback, With kind regards, Michel email failing / no gateway issue

Rand, I am glad your fears are alleviated ... unless, of course, I've been given the wrong information by SmartLabs. I've sent an email to get a confirmation and I will let you know if I am told otherwise. Thanks so very much and with kind regards, Michel

sfhutchi and Mark, We are working on it and should have a work-around in the next release. With kind regards, Michel

Hi Mark, This is "the workaround" for now but the main issue is that the status of the load is not reflected in ISY using this method. We are looking for a another workaround (in the code) to update the status of the load when a synchronized button attached to the load button is on/off. This is going to be very ugly but we think it's a needed feature. With kind regards, Michel

Rand, Hello. You are correct! PLM is supposed to allow for 417 links. So, I don't think you will run out of PLM links any time soon. Does this answer your question? With kind regards, Michel

Rand, Wow, I just realized that this submission of yours had remained unanswered. My sincere apologies (can't trust the auto notificiation). In case you exceed 255 nodes (device/scene), you will have to get a our new product which handles 512. I've yet to see anyone going beyond the 210 devices (for a 12000 sq feet house) and 45 scenes. With kind regards, Michel

HAS, Please try the Any for source port ( I was wrong ... it has to be Any since we tested it with Sloop and it didn't work any other way). We will figure this out one way or another since out of the 3 clients with ActionTec/FIOS, yours is the only one that seems to be causing problems. Please let me know if you wish me to call and get this resolved quicker. With kind regards, Michel mine too! Did ya see that by clicking on the Globe? I saw my Gateway was 71.180.***.* I've tried ALL those....blah LoL

sloop, Thanks so very much. We can cautiously assume that all Verizon customers use the same DNS. And, YES, I read your instructions to another one of our customers and BOOM: it all worked! With kind regards, Michel

HAS, 192.168.1.1 is your routers IP; I am not sure this would work. Would you like me to call you and walk you through this? Thanks to sloop's instructions, another one of our customers with ActionTec/FIOS modem was able to configure his ActionTec/FIOS modem and it all works. With kind regards, Michel yes -50000,null,null,null I left the IP Address, NetMask and Gateway settings, but removed the DNS Server (0.0.0.0) and no longer have the -500000,null,null,null message. The new message is: Failed to send message to: (my email address) I tell ya, I think all the settings in my router are correct. The ISY should have access to the internet / email

evarsanyi, The issue with triggers in 2.3 is that they work based on "state change" and not "button press". As such, if you have a non-toggle button, the state never changes (always off) and therefore the trigger is not run. Our new enhanced trigger/scheduler functionality rectifies this issue (2.4). With kind regards, Michel

evarsanyi, The Replace function (very similar to Replac Modem) will be available in our next release (2.4). I'd appreciate your patience. With kind regards, Michel

Rand, Excellent idea. The only issue is that I don't think most people would want to buy an extra InlineLinc for every KPL they have. In short, we have to find a workaround no matter how ugly it looks. Wouldn't you think? With regards, Michel There is no way to change the load button. It does not change going from 6 to 8 mode, only that links are created when in 6 button mode that are not present in 8 button mode. An option would be to use an InlineLinc for the load you have now and put no load on the KPL. Rand