Michel Kohanim

Hello siegeld, It's quite simple: UDProxyDevice dev = ISYInsteonClient.getDevice(); if (dev == null) return false; dev.queryAll(address, true); Please note the following: 1. ISYInsteonClient is the superclass of your class 2. The first parameter for queryAll method is the address of the device or the scene as a string 3. The second parameter for queryAll is whether or not the given address points to a device or a scene May I humbly ask why you would want to do "schedule" maintenance in the code? You can simply use ISY's Admin Console to schedule the query (for whatever time you wish) on any device, any scene, or even My Lighting (all the devices). As a matter of fact, you should already have a schedule for 3:00 a.m. which does precisely that. The advantages of the above are: 1. You don't have to maintain the schedules in your code 2. Whenever the schedule is run, you are "notified" of all the changes and you can act accordingly through the following callback method: public void onModelChanged(UDControl control, Object value, UDNode node) ; 3. It's much more efficient to have the query schedules since ISY will only query the status if scheduled otherwise it will try to query the on level and ramp rate as well. With kind regards, Michel

aLf, As long as ISY is "part of the outage", then as soon as it boots up it shall a) try to query all your devices for their states run any schedules that you might have set (i.e. from sunrise to sunset). So, you could simply have the Away schedule which turns everything off at sunrise and everything on at sunset. In this scenario, then, depending on when the outage took place, your lights are either turned on/off. I hope this makes sense, With kind regards, Michel

sceaton, My pleasure. You are 100% correct. In every scene, we create the master/slave links for the PLM, and we create the relationships between controllers/responders. Please also note that we are limited by the number of links supported by the PLM, so we did our best to reduce the number of links required in the PLM. In your scenario, you would have to have 3 different scenes, all with the same devices and thus 3 times the amount of links required in the PLM. With kind regards, Michel

shawn, I hope I've been able to answer your question in the other thread. The main reason is this: 1. Coming Home/Leaving Home Scene 2. Assume you have a KPL at the entrance 3. Assume you have a KPL at the exit Now, assume you have a program to turn on your Coming Home/Leaving Home Scene at 5:00 PM everyday to 60% at a ramp rate of 2 mins and turn them off at 8:30 AM. So, for this to work, at the Coming Home/Leaving Home scene, you adjust all the on level/ramp rates for all the responders to 60% and 2 mins. Ok, this takes care of the on level and ramp rate at the scene level Now, assume that on your entrance KPL (when you come home), you want the lights closest to the entrance turn on immediately and the lights closest to exit turn on last (say 2 minutes later). So, now you can adjust all the on level/ramp rates for all the responders in that scene just for this KPL button. And, you can now do the reverse on the exit KPL. So, all and all, you can have different on level/ramp rates at many different levels and all of them are written to devices. With kind regards, Michel

Hello sceaton, You can do all that you suggest and quite easily. If you don't mind, please read this thread http://forum.universal-devices.com/viewtopic.php?t=14 . I think it will surely shed some light on how things work. In summary: 1. Setting on level and ramp rate on devices under My Lighting only impact the local on level/ramp rate; i.e. they take effect if and only if you do something to the device physically. 2. When you click on a scene, adjusting the on level/ramp rate for all the controllers and responders on the scene take effect if and only if they are activated by ISY (such as a schedule that turns on/off that scene) 3. Now, you can click on any controller within a scene, and then you are able to adjust the on level and ramp rate for all other devices in that scene. These settings will only take effect if you do something to the controller (such as your KPL button) physically. In short, you have full flexibility of adjusting on level/ramp rates any which way you want. With kind regards, Michel

Mark, I think we have to go back to the basics: If you click on XYZ, then adjusting the sliders for KPL1.1 and ILL are applied IF AND ONLY IF you scene is activated by ISY If you click on KPL1.B: It can only turn on/off our KPL1.1 (load) --> NO SLIDER The onlevel/ramp rates for the ILL, take effect IF AND ONLY IF activated by KPL1.B (when you click on the B button) Regards, Michel

Mark, The debate to use Else vs. Finally is still open as such we a little hesitant doing cosmetic changes where a functional change is required. With kind regards, Michel Could a hover bubble noting this above statement be added to the "If" text so users could remember its function. Personally I can't remember ever learning about it in all the classes I took so it may be remote concept to most people.

Mark, I think you and I are talking about two different things: Let's say you have a scene: Scene XYZ: KPL1.1 - Controller KPL1.B - Controller InlineLinc - Responder Now: If you click on XYZ, then there are are sliders for KPL1.B If you click on KPL1.1, then there are NO sliders for KPL1.B If you click on KPL1.B, then there are NO sliders for KPL1.1 So, which sliders are you talking about? This scenarios have been tested numerous times. If you see a slider where one should not be, please do send me the screen shots. With kind regards, Michel 1. There is NO slider for the Load button if you click on the sub-button

Mark, Thank you. We'll revisit for the next release. Regards, Michel

Mark, Should already be fixed. Thank you, Michel

Mark, Thank you. Known issue which shall be resolved. With kind regards, Michel

Mark, Thank you so very much. We'll check into the fast on/off issue. But, since relays don't have ramp rates, I am not sure how much sense it makes to have both: they do the same exact thing. Regards, With kind regards, Michel

Mark, Thank you. With kind regards, Michel

sceaton, Thanks. Already done and will be available in the next release. With kind regards, Michel

Hi Mark, You are quite welcome. Well, the load button slider do actually work but they only change the "local" settings for the KPL (as they should). Taking them out might cause more confusion but, as you know, we are always eager to hear what our users think. With kind regards, Michel

sceaton, Sounds good. We shall review and implement. With kind regards, Michel

GPG, I think for what you want accomplish, you can simply put the 'Wait' and 'Set Office - Test LL' statements right below the first statement in your Then clause. With kind regards, Michel

Mark, If it works, then I wouldn't worry about it. With kind regards, Michel

Mark, Have you run out of the return period? With kind regards, Michel Darn I just replaced my wireless with the linksys router I suggested above and I only have an issue with the signal strength. I get 65% signal strength in the family room with the router in our bedroom closet mounting up high on the wall.

aLf, You get an A+ immediately! That's precisely what you should do and ISY shall take care of the rest (get rid of anything else that's not in ISY). Routers, well, if you are not ever going to have remote access/notifications, then the router is immaterial. I personally recommend DLINK DIR-625 for the following reasons: 1. Its range and signal strength are unbelievable (compared to Linksys) 2. It's Wireless N, so I won't have to change routers when I get my Wireless N network card 3. It has never crashed on me 4. It works beautifully with ISY Talk to you soon, With kind regards, Michel

Mark, Reproduced the problem. No worries ... it's a bug! So very sorry for all the exercise in ISY. With kind regards, Michel

Mark, I am so sorry to hear that; we'll get to the bottom of this one way or another. Ok, maybe I misunderstood the whole thing. So, let me see: Are you trying to assign different on level/ramp rates for the same KPL load button, when controlled by another sub-button from the same KPL? If this is the case, then you cannot (and I am so very sorry if I misunderstood your original question) because the linkage between the KPL buttons is not a group command; it's simply LED "follow me" logic on the KPL. If this is not the case, then please send me an email to tech@universal-devices.com so that we can discuss it over the phone and figure out the next steps. With sincere apologies, Michel

Rand, We shall do our best! Thanks so very much for the feedback. With kind regards, Michel Alright this time, just don't let it happen again Restore Devices took a normal amount of time (~20 minutes) and then displayed the failed devices by name! Thank you for that. I put my two RemoteLincs in linking mode after the failure and again selected Restore Devices. In v2.4 this would happen very quickly. I assumed it was only restoring the few missing devices. I waited over an hour and then I saw the Request Failed pop up. After that I had to unplug the PLM for some minutes to regain contact between the ISY and my Insteon devices. Of course, the UDI team has probably fixed that in the overnight update, you seem to always be one step ahead of me When the ball game starts I will play with your program some more, right now I have a railroad to run Thank you, Rand

aLf, My pleasure! ISY is unlike HouseLinc in the following manner: With ISY, whatever you do, is immediately programmed into the devices. This means that you can immediately test and see whether or not your configuration is "what you like". So, for instance, let's say you create a scene called Sunrise and you drag and drop 20 of your devices in that scene. As soon as you press OK, ISY starts programming all of your 20 devices at the end of which you can test and see if everything worked. You can then update your scene parameters to those that you want (on level/ramp rate) and make sure you are satisfied. Again, all of these happens immediately. Yes, it would really be a good idea to write down/print your current settings. When everything is in ISY, you can simply create your own topology (Tools->Generate Topology) and keep it for future reference. And, before you go to your cabin, please send us an email so that I can point you to the latest code (tech@universal-devices.com). With kind regards, Michel

Mark, Thanks so very much for the enthusiasm. That might be true because this release is only trying to cover up a PLM defect (deletes the wrong records). With kind regards, Michel