KMan

[Edit]See next post which does the same thing with a variable instead of enabling/disabling programs[/Edit] I would attempt to do this with a different program to represent each state, and a timer program to timeout each state, and reset the state machine. The state machine would be controlled by enabling/disabling the programs: State 1: (normally enabled) If Control 'Master Light.C' is switched Off Then Run Program 'Master Light Timeout' (Then Path) Enable Program 'State 2' Disable Program 'State 1' Else - No Actions - (To add one, press 'Action') State 2: (normally disabled) If Control 'Master Light.C' is switched On Then Run Program 'Master Light Timeout' (Then Path) Enable Program 'State 3' Disable Program 'State 2' Else - No Actions - (To add one, press 'Action') State 3: (normally disabled) If Control 'Master Light.C' is switched Off Then Stop Program 'Master Light Timeout' Run Program 'Panic Exit' (Then Path) Enable Program 'State 1' Disable Program 'State 3' Else - No Actions - (To add one, press 'Action') Master Light Timeout: (always disabled) If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 2 Minutes Disable Program 'State 2' Disable Program 'State 3' Enable Program 'State 1' Else - No Actions - (To add one, press 'Action')

If all you want to test is the ISY/messaging logic .... You can add an "Or Control 'SmokeBridge-Test' is switched On" clause to your program, and use the test button on the smoke detector. Then, once you have that working, do a test with actual smoke to verify the 'Smoke' node logic.

https://192.168.1.10/admin works fine, no multiple logins.

I just tried a bunch of other ways of opening the admin console, they all showed the problem: http://isy/admin https://isy/admin/jnlp http://isy/admin.jnlp http://isy -> "Admin Console" Download admin.jnlp and execute directly

At one time, I believed it was related to opening the program tab also, but I did a bunch of testing yesterday ... and I don't believe that is true. I can open the console and not touch anything and it will still happen for me. I use "http://isy/admin/jnlp" to open the console.

I have a similar issue with running Windows 8.1/IE 11. I've never seen the browser lock up like Clarkes71, but I *always* get 2 login prompts (I don't believe I've ever seen 3). Currently running 4.1.2, but I believe I also saw it with 4.1.1. And I believe I'm on the latest Java (51? Not at home right now, will check later).

lol ... If I'd looked to see who was online (LeeG and Xathros), I wouldn't have spent time crafting another response to the question about the set to 60!

Nothing. The '$' is just the ISY syntax for a variable. Xathros must have typed his program in here (instead of copy/paste from ISY), and just missed the $.

According to the 2441TH manual, there doesn't appear to be way to adjust the "swing" (swing is the range of temperature that it will control to). If you could adjust it, you'd just change that to 3 deg and be all set. Instead, I believe you'll have to use ISY programs to achieve what you want. The following programs should come close: If Status 'Thermostat- Main' < 69° (Temperature) Then Set 'Thermostat - Main' Mode Heat Else - No Actions - (To add one, press 'Action') If Status 'Thermostat- Main' > 72° (Temperature) Then Set 'Thermostat - Main' Mode Off Else - No Actions - (To add one, press 'Action') If you want the programs to dynamically adjust if someone manually changes the setpoint at the tstat, it becomes more complex. I think Michael has mentioned that version 5.0 will have some enhancements that will help solve these types of problems.

Are you sure Program2 is enabled? It should run when the switch is turned on, regardless of the state of the light. And make sure the "not" is in there, so the false path is taken, rather than re-starting the true path.

I *think* the following program does it all in one program. Note that it doesn't take into account that you may want to turn off the lights (via a switch or other) during the 4 hours after sunset ... it will turn them back on to 60% when the 4 hour timer expires. Also note that trying to do everything in one program in ISY isn't usually the best solution. If From Sunset To 5:00:00AM (next day) Then Set 'Rear Light' On Wait 4 hours Set 'Rear Light' 60% Else Set 'Rear Light' Off

There is a limitation of the solution posted, which is that the light is going off 10 minutes after the door opens, whether you want it to or not. That is, there is no way to keep the light on after the garage door opens. A fairly simple solution would be to add the following to Program2 (and enable the program): If Control 'SwitchLinc Relay' is not switched On Then ... With this addition, when you turn on the SwitchLinc Relay, it will cancel the Program2 timer if it was running.

If you have a smartphone, you can turn off wifi and attempt to access the external IP. May not be the best user interface, but it is a simple way to check for external connectivity. If you have mobilinc, it will automatically detect internal/external access and use the appropriate one. So just by turning on/off wifi and using mobilinc, you can quickly/easily verify external access.

Status will work and is preferred in this case, due to the issue you noted.

Are you sure that error box doesn't have a checkbox that says "allow" (or some variation)?

Not sure exactly what you are trying to accomplish, so here are a few thoughts ... If you are trying to use the Excel "group" function to make the KPL a collapsible tree, that feature is under "Data->Group". You select the lines you want to make collapsible, then select "Group". By default, the group collapses upside down from what I usually want, so I usually go into the "Outline" menu (click the little down/right arrow next to "Outline") and uncheck the "Summary rows below total" checkbox before selecting "Group". Another option is to "hide" the rows in excel, you can just select the rows, then right click and select "Hide". A third option is to create a script (prior to opening in excel) to remove the " - B" through " -H" lines.

If you are using a program to change the state variable from 0 -> 1, and you don't need it to go to 1 immediately when the program runs ... you could just add a "wait 30 seconds" before setting the state varible to 1. (Hard to know for sure if this would work without seeing the whole program though!) Otherwise, if you need the state variable to go to 1 immediately, then you'll likely need another variable that changes value 30 seconds after the state variable is set to 1 (could be done with a wait as above). And then condition the motion sensor program on that new variable.

Voice recognition? Yes, using Tasker, AutoVoice and Mobilinc (I think mobilinc is optional). Pretty simple to set up if you know how to use Tasker already.

I had the same problem when I upgraded to 4.1.1. Look at step #6 of the instructions in this post. Using one of those links will get you to the 4.1.1 console.

This needs to be 4.1.1 also. Did you clear your Java cache? http://www.java.com/en/download/help/plugin_cache.xml

This seems like a fairly common problem and solution. Perhaps the error dialog should be updated to inform the user of the likely issue (fw is not at the latest). And maybe even include a link to a UD web page that shows what version is needed for each device type.

Ah ... thanks. That wiki page is actually what I was referencing, but then I misunderstood the note at the top of that wiki page which says not all APIs are implemented in REST. I *thought* it meant that some of the documented REST API's weren't implemented! I sure thought that was strange ... now I understand. Thanks!

Hmmm ... just noticed a note on the REST API docs that says not everything is implemented. I have no idea if the rest API shown in my post will actually work.

I don't have or know iRule, but you can run an ISY program using the REST interface: rest/programs/thermostatHold/run So I would create the following state variable and program, and have a button on the iRule to run the program (this example is a toggle button, but you could use the same idea to create 2 buttons - 1 to enter hold and 1 to leave hold). This program should be disabled (you will run it via the rest interface, not via the variable triggering). if $ThermostatHold = 0 Then $ThermostatHold = 1 else $ThermostatHold = 0 Then add a rule to the thermostat folder to disable/enable it based on the state variable. Note that I'm fairly new to ISY, and I haven't tried any of this, so there is probably something wrong!

Right now, I change the variable manually in the web interface ... but I plan to add a button (probably on a remote) to do this.