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

I have a KPL button that enables/disables ISY control. Button Lit = Wife override - Button Off = ISY in control. ISY Control started as a basic schedule and evolved as track occupancy and since I took control of my pellet stove and gained access to outside temp. A basic schedule for setback is where I would start and add on from there as your skills and needs dictate. -Xathros

Can you be more specific as to wat you want to do? Ill see if I can post an example to match.

In a browser: http:///rest/nodes should return a list of all nodes including their group numbers. -Xathros

50' is a generally accepted maximum for a serial interface but recommended is far less. Mine is 10'. You can however move the ISY with the PLM keeping them together and extend the ethernet uplink much further. BUT, I think you misunderstood my suggestion. What I meant was: Use an AC extension cord. Unplug the PLM from power and plug it into the extension cord then plug the other end of the extension cord into an outlet on the same circuit as the problem KPL(s) for the duration of the reprogramming. -Xathros

I would go the IP / Network resource route. Depending on the arduino's response time, I would expect you could get very near real time responses unless the ISY is very busy with other tasks at the time. I would be interested in what you have sourced for the roller shades as I am also considering building my own. -Xathros

Put the PLM on a long extension cord and plug it into the affected circuit for the updates. -Xathros

Here is another recent thread on this topic: http://forum.universal-devices.com/viewtopic.php?p=76508#p76508 -Xathros

In that dialog, "Recipients" is the only column header and does kinda sorta look like an elongated rectangular button. Dunno if its possible in the Java GUI to indicate sort Ascending/Descending with Up/Dn arrows on the column headers like in some other environments but if it is, that may help to clarify the purpose of that header. If there is a hidden ID# assigned to each recipient line, revealing that as another column like program or mvar ID's may make the headers more recognizable as headers. Also changing "Add" to "Add Recipient" may help steer new users toward the correct target. I do have to say however, it took me a few re-reads of that post to find the error as I just always assumed that "Recipients" was just a column header and being that I've never had more than 2 recipients in that dialog, I had never felt the need to click it to sort before. In any event, that error message needs to be changed to "That was Easy!" unless Staples has that trademarked. -Xathros

Or you didn't look at the very bottom of the tree after you added. New scenes/folders appear at the very bottom initially until a restart of the console or a re-sort of the tree. -Xathros

arw01- Are you certain that both the subject and body fields have content? If either are blank it won't send. -Xathros