Xathros

andyf0- I also am unable to reproduce your issue. What does the ISY show for details on your Swicthlinc Relay? -Xathros

Timster- A) For loads that cannot handle the chopped sine wave output of the dimmer's triac circuitry (non dimmable CFL, low voltage lighting transformers etc) Even at 100%, the dimmer still produces a chopped sine wave output that certain things don't like. For loads that exceed a dimmer's capacity. C) For Multi-Way dimmer setups where only one device controls the load, slaves can be cheaper relay only devices. D) To save a few $$ where dimming is not needed. (Boiler room, garage, barn, basement stairs etc) -Xathros

Andy- Try Tools / Error Log, Cancel. Repeat for two or three cycles and see if it locks. It looks like a glitch with the file chooser. -Xathros

I have a 10.7.5 system at home. I'll see if the kids will let me use it for a bit this evening and I'll test there. -Xathros

Hi Michel- Moving back to the forum since 4.0.3 beta now released. I downloaded and upgraded to 4.0.3 with no problems. Per your last email, I checked and the java symlink in /usr/bin did in fact point to a 1.6 version. Even with that there, the Java preference panel only shows 1.7 installed and when running the console I would see the Java 7 splash screen about 5 seconds after I clicked the admin shortcut and a few seconds before the console main screen displayed. I renamed the symlink as requested. This eliminated the 5 second delay between clicking on the admin shortcut and the Java7 splash screen but otherwise has had no effect. I am now testing on another MAC at the office and am running into the similar problems. Here are the details: Downloaded and installed the 4.0.3 beta. Cleared cache, renamed old java symlink. Went to https:///admin/admin.jnlp and saved the resulting file. Double clicked the above file - application downloaded to cache and launched. Somewhere in this process I was prompted to trust this developer which, of course, I did. Logged in and verified 4.0.3 for both FW and UI. Selected Tools / Error Log, File chooser opened (Defaulted to my home folder! ), clicked cancel. Repeat the line above a few more times and on the third time, console hangs. When the console locks, the clock stops, the java console is unresponsive and the only way out is force quit. Both test systems are on MAC OS X 10.8.3 The hang appears to be directly related to the new file chooser - all other aspects of the console seem fine. -Xathros

I use variables for this. i.HomeAway=0 for home or 1 for Away s.Occupied=0 for vacant or 1 for Occupied i.Company=0 for normal or 1 when guests are present. Many of my programs contain if s.Occupied=1 or If i.HomeAway=0. I have toggle programs for some manually controlled mode variables like i.company or i.HomeAway that look like: If i.HomeAway =0 Then I.HomeAway=1 Else i.HomeAway=0 I set these programs as favorites in Mobilinc -Xathros

Sorry to have been misleading on this. ISY Mvars DO in fact support negative values. I have been operating under the belief that we were limited to positive values for quite some time now. -Xathros

Actually, variables can also contain negative integer values. I use -1 all the time because my formal computer training always represented TRUE with a -1. There may be some confusion due to the syntax of the following operation: Mvar = Mvar - 1 in ISY syntax is: Mvar =-1 which to the unsuspecting looks like the variable is being assigned a value of -1 when in reality we are decrementing an existing positive value by 1

Right click the micro dimmer and select show device links. When the display is complete click compare.

The test "if control Dimmer is switched on" is looking to the dimmer to be turned on by its own button not by a remote controller. Try changing that to: "If control RL2-H is switched on" -Xathros. Edit: sorry, missed the part about the sense line. Im thinking that should have worked. What happens if you right click that program and run then?

Right click on the KPL Primary node in the admin console and select Query Insteon Engine. Then try again changing the value to something other than the value that you tried last. -Xathros

If I had to guess, I'd say you have a load that doesn't like to be dimmed coupled with a very long ramp rate. Try swapping the load for an incandescent and check the ramp rate in the scene definition. -Xathros

How about this: Program: BasementAandCoff If Control BAS2 3WAY1 is Switched Off or Control BAS2 3WAY2 is Switched Off Then Set Scene BAS1 Off Set Scene BAS3 Off Or replace the last two with your whole basement scene: Set Scene BasementAll Off But to me, that scene is unnecessary and is just wasting links. -Xathros

TannerH- As LeeG pointed out, you could just use multiple scenes with different On levels defined in each but if you are activating these with Keypads or Swtichlincs that are defined as controllers, you are limited to one scene per controller. I am using the same approach as you (adjusting then re-activating scenes). Works well for me and some others here that are doing the same thing. Actually, I recently removed the re-activate step from a few of mine as the lights dimming by themselves seems to bother a few of my family members. So in certain cases I adjust the on levels and they will be used the next time someone turns on a switch. This, they don't seem to mind. One thing I noticed is that you have your reset to 100% as a stand alone program called by your 3am turn off routine. Unless you are calling that from multiple programs, you could just roll all of that into the 3am off routine and have one less program. Also, I would move that to 2:55am to avoid a traffic jam with the default 3am query (unless you have disabled that). -Xathros

bwoodfl- Does anyone else have access to your admin console? This has the feel of an April Fools prank to me. -Xathros

Perfect! Thanks LeeG. -Xathros

This is probably a question for LeeG: I am considering installing a 2440 Motion Sensor in a stairwell and linking it to a Inlinelinc Dimmer that will control some step lighting. The plan is to have the 2440 as a scene controller to eliminate program lag in operating the scene. I would like to adjust the scene in the morning and evening to set the on level for the Inlinelinc Dimmer with MS as controller to 0 for the daytime and 30% for the night time. My concern is that the Adjust Scene statement will want to write changes to the MS when I do that. From my understanding, It seems like the change only needs to be written to the Inlinelinc Dimmer since in either case the MS is simply requesting scene on and nothing in it's links table needs modification. My question is: will the Adjust scene statement want to write to the 2440? If yes, then I will have to have a program in between. Thanks in advance. -Xathros

tome- The RF portion would only be useful at the far end. If you have other dual band devices there it may help but it certainly is way out of range to reach the house with RF. I am in a very similar situation with my small barn. It's approx 300' from the main house. I have 2 Togglinc Relays, an Outdoor Appliancelinc and an access point down there. One of the Toggleincs is hit or miss on comms. Everything else is 100% perfect since I added the access point. Not sure why it helped and if there is any value of having the RF down there on a single phase drop. I plan on replacing the misbehaving toggelinc soon and I expect everything will be good down there. I'll move the weak one up to my garage where it will be much closer to the PLM and the rest of the network. I suspect it will do just fine there. -Xathros

AutoDR is Automatic Demand Response. Where supported, it allows the utility (power company) to send a message that the ISY would react to by turning off heavy loads during peak times. There is likely more to it but that is my understanding. The AutoDR scene I believe is where you would place the "Heavy Loads" that should be turned off on request. -Xathros

Not Yet but they have indicated that Ecobee support is in their plans. -Xathros

Drew- This is what should be accomplished by the first program I posted and the last I posted. Go to the integer variables tab, Add a variable. Change the name to i.scenestat. Set the Init to 0 and the value to 0. Save it. go to the programs tab and build the two programs which I will repeat here: Program RL-B_Scenes_AB_Toggle If Control RL-B is switched On and i.scenestat < 2 then Set Scene B Off Set Scene A On i.scenestat=2 else Set Scene A Off Set Scene B On i.scenestat=1 Program RL-B_ScenesOff If Control RL-B is Switched Off Then Set Scene A Off Set Scene B off i.scenestat=0 You will probably want to read the Wiki and Variabls sections posted by LeeG and oberkc. That will give you a much better understanding of the usage of the variable here. Variables add much greater functionality to the ISY and are well worth learning how to use. We are expecting even greater functionality with variables in the (near-ish) future as UDI extends the capabilities of variables. -Xathros

Thanks LeeG and oberkc- I was about to go looking for those very links. -Xathros

Drew- Sorry, I can't determine what your questions is here. Also, I've been working this problem with my RL2 in mind which is an 8 button unit. I'm now remembering the old Remotelincs were 4 scene with on/off rockers so there is a RL-B Off button that I was not considering Doesn't change the toggle routine any but I think the second program should be: If Control RL-B is Switched Off Then Set Scene A Off Set Scene B off i.scenestat=0 A bit about variables in the ISY: There are two kinds, Integer and State. Both can only contain positive integer values or 0. The only difference is that a State variable can trigger a program when it's value changes much like triggering a program with the change in status of a Switchlinc. An integer variable will not act as a trigger. Variable naming is unimportant beyond your level of OCD'ness. I use i.mvarname for Integer and s.mvarname for State variables in my code to to make reading/debugging a bit easier. Variable names cannot contain Spaces or certain punctuation symbols. .-_ are fine. I also tend to catagorize my mvars for the same reason. s.SEC.HomeAway, s.UTIL.WasherRunning etc. This way I can sort the mvars by name grouping like items. -Xathros

andrew77- i.scenestat is an Integer variable and will need to be defined on the integer variables tab. Since there is no such thing as a scene status, we need a variable to track what we believe the status of the scenes to be. In this case if i.scenestat < 2 then we think either Scene B is on (i.scenestat=1) or no scene is on (i.scenestat=0 - uninitialized after startup) so we then Turn Off B, Turn On A and set i.scenestat=2. B may have already been Off - doesn't matter. If i.scenestat=2 it means Scene A is on so we turn A off and B on and set i.scenestat=1. Also note that the programs turn one scene off then the other on. This allows there to be some overlap in the scene definitions (Same light(s) in both scenes) Otherwise the overlapping lights would always be off. So, the variable is simply tracking your toggle status. -Xathros