Xathros

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

The way I understood the request is: If Neither Scene is on, Turn Scene A on. If Scene A is On, Turn Scene A Off, Turn Scene B On If Scene B is On, Turn Scene B Off, Turn Scene A On Continued presses of RL-B toggle between the two scenes. I would do this with a variable for tracking assumed scene status. I am assuming from the OP that the RL buttons are in NonToggle ON mode. RL-B SHOULD NOT BE a controler of either scene. 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 Assuming that there would be another button used to turn off the scenes. If Control RL-A is Switched On then Set Scene A Off Set Scene B Off If RL-B is in normal Toggle mode, then the second program should be replaced with the following: If Control RL-B is switched Off Then Set Scene A Off Set Scene B Off The combination of the first and third programs would loop through: Scene A On - A & B Off - Scene B On - A & B Off -Xathros

Mine are relays as well. The replacements function flawlessly in the same locations. Pretty sure these 2 togglincs are just duds. Almost think they fail due to the heat they create. Once they warm up the stop working. Even with no load at all.

I have a few old togglincs that act like that. I replaced them and now use them for bench tests only.

Can you do that again with the event viewer at level 3? -Xathros

i814u2- Your screenshots and descriptions match right up with what I have seen on three of my systems. It does seem to be more predictable with the admin console than with other apps but I have still seen this in other places. It is quite possible that the admin console was running and minimized when I saw this elsewhere. I will try to do some further testing. -Xathros

$X3 being a state variable will cause the If to reevaluate any time it's value changes. The waits will be canceled when it changes to anything > 0. The timers will only expire if $X3 remains at 0 for the full duration. I'm quite sure that will meet your requirements. -Xathros

I also see this with Dropbox, Google drive, Evernote, MS Word etc. I don't believe it is Java related, I do believe this is a Mountain Lion Bug/Feature but have no solid proof either way. -Xathros

I got lost trying to follow that logic so I thought about the requirement and have the following to offer: I am assuming $X3 is a State variable. If $X3 = 0 Then wait 5 minutes Notify #1 - 15 mins till shutdown... $AwayNotified = 1 wait 10 minutes Notify #2 - 5 Minutes till Shutdown... wait 5 minutes Set scenes off Set thermostat back. If $X3 > 0 and $AwayNotified > 0 then Notify Away Mode cancelled Set Thermostat to normal settings. Set whatever else $AwayNotfied = 0 Why wouldn't that work? -Xathros

Need more information as to which "folders" are you referring to. Those under programs or the device tree? Have you cleared your Java cache? i814u2- I can confirm this behavior on my macs running 10.8.2 & 10.8.3. Very annoying and totally unrelated to the ISY & UDI. Clicking away and back shows the folder contents almost immediately. Best I can figure so far is a spotlight issue. -Xathros

I'm using some one wire DS1822 temp sensors in conjunction with a CAI web control board. The CAI supports up to 8 of these sensors in addition to a humidity sensor and eight digital inputs and 8 analog inputs. This is not a plug and play, out of the box solution but works well for me and is far cheaper than installing a bunch of Insteon or Zwave thermostats. -Xathros