apostolakisl

My suspicion is that there is a "forgotten" program or a program that erroneously includes the variable which is setting it to values other than 0 unexpectedly. Also you might use the "find" command to search all your programs for any instance of that variable.

What you have done by splitting the program into two and using only "then" output is eliminate the possibility that the variable is going to a value other than 0 or 1. The else clause will run in that situation, and you are precisely having issue with the else clause. A program that sends you notification every time the variable changes and what its value is is quite simple. If variable is 1 and variable is not 1 Then send notification . . . use variable substitution so that it puts the value of the variable into the email/text/whatever.

The only thing I can think of is that your variable is changing when you don't think it is. Try creating another program that sends you an email every time the variable changes. This will tell you if there is any unexpected behavior If state variable is 1 Then notify . . .variable is 1 IF state variable is 0 Then notify, . . .variable is 0 IF state variable is 10000 Then blank Else notify . . . variable changed

Thanks. It must be new in the past couple years. I haven't needed to add any new codes to it in quite some time.

Yes, I have a GC also. But you have to create a stinkin network resource for every command, not to mention learning every command. GC needs to create a library of commands and an app or something. But, you already did that part so it is a moot point. Some program running on a pc or whatever needs to parse the time and channel from your table of times/channels and deliver them via REST to variables in ISY and it needs to do that after the previous recording completed and before the next one starts. This is a lot of work for what I am guessing is your March Madness life.

I'm doubting that he is using IR. Directv and many of the other companies have IP control, as do many TV's and audio systems. Alexa can control directv for example without any IR.

The best way to manage this (at least it is what I do), is create an extra scene with all the same devices but at a different brightness level. Then I name that scene the same, but add the word "dim" to the end of it. Now if you want to control it at a whole bunch of different levels, then that doesn't work very well.

ISY can't check the date of something. Something else can send the date to ISY via the REST interface. You would post it to an ISY variable (or probably several variables for 1) day of month, 2) month of year, 3) year, 4) hour, 5) minute, and 6) channel). Then ISY can compare (with version 5 only) the current time/date against those variables and when the condition is met, trigger a "then" section to fire. Perhaps your TV has an IP interface (I assume it does since Alexa can control it) which ISY could command via the ISY network module. The biggest hurdle in all of this would be what it is that sends the info to ISY. But frankly, whatever it is that does that, could probably just as easily skip the ISY and send the network command directly to the TV. Not sure where Alexa comes to play in any of this, except perhaps to demonstrate that indeed your TV can be controlled via an IP interface?

There is a tasker tutorial in the forum which covers how to have tasker set variables (or whatever) on ISY. You could also use IFTTT with its geolocation recipe or its wifi connected recipe. This would be easier to setup. IFTTT did not exist when I first started using Tasker to do the job. No reason to change now. Tasker works great, just more complicated to setup. But also a lot more customizable, if you care to do that. IFTTT is pretty easy. You have to point port 443 to your ISY and install a security certificate, or you can get the ISY portal. Then you put in the rest command. For example, this is the command for setting a variable in ISY that I have in IFTTT https://admin:mypassword@myurl//rest/vars/set/2/27/1 of course you susbsitute your password and your url. I have port 443 forwarded to my ISY and a self signed certificate. It would be done slightly different with the ISY portal, but since I don't have it, I can't say for sure what you do. If you use tasker, you enter the same thing, but there are other steps.

Example, When my phone logs into my home wifi, tasker uses a REST command to set a variable on ISY that indicates I'm home (1). When I leave, it sets it to 0. I have dozens of variables all related to my day/date programs. Version 5 of the firmware makes them obsolete. I also have a bunch of variables for my CAI webcontrol. But again, version 5 makes them obsolete because of the ability to create custom nodes and thanks to IOGuys nodeserver interface that keeps the nodes in sync with the CAI

My console I had open when I left work last night was still working this am. Very unusual. However, I was away from my computer for a couple hours and upon return, it was dead. That is typical. 20 minutes might be an exaggeration, but lasting more than a couple hours is rare. It doesn't die so fast that I have to reload it during a single usage, but to have it last long enough for me to be done with it and then come back to it later, well that pretty much never happens.

This has been issue for me from day one 10 years ago. The top bar gray's out. There will be hidden windows that I can "phantomly" close by hitting tab enter. Sometimes that brings the console back to life, but mostly it just lets me close it without doing a ctrl alt delete. There is no way this is an issue with my OS or computer since it has happened to me on every computer and 3 different OS's. Probably I have had it happen on a dozen different computers and it ALWAYS happens. If I leave the console up, it will never last more than 20 minutes.

I don't know about you, but my admin console rarely lasts long enough for me to close it while still functional. The console hangs all the time. This happens on all of my computers both remote and local through 3 versions of windows (xp, 7, and 10).

My original PLM never died. I don't know what the version number was, but it was a single band device (no RF) and lasted me many years and may still be functioning in the home of whoever the person on ebay is who bought it from me. I replaced it with the "new and improved" dual band device about 5 years ago. I have 2 of them, the first died, I bought a new one, then replaced the caps on the old one, then the new one died and I put the repaired one into service and fixed the caps on the second one which I keep as a spare.

I had made a suggestion a while back that when you delete a program but have not yet saved your deletion, that the program should stay on the list with a red x or something to that affect next to it. Something similar in concept to the green arrow next to programs that you created/changed but have not yet saved. It probably would also be nice if the "save" button at the bottom of the screen turned bright red or something to that affect when there are pending changes that need to be saved.

Probably forgot to hit "save changes" at the bottom left Unlike a new program or a change to a program, when you delete, there is not one of those little arrows indicating you still need to save the change, since when you delete there is nothing there at all. This is why the java thing is a pita. You are basically running a program on your computer to which you make all the changes. But none of these changes actually go to ISY until you hit the "save" which then uploads it.

Think of it this way. The whole purpose of the "And control device x is not switched off" is to include pressing the off paddle as a trigger to the program. Otherwise, the only trigger would be a press of the on paddle. You might include other control statements if applicable, like fade. Also, keep in mind, that "control" statements ALWAYS refer to an action taken locally AT THAT SWITCH. A switch that turns on as a result of responding to a remote command (scene) was not "control switched" anything. Here is another possible example where pressing "on" or "fade up" is true, and pressing "off" or "fade down" is false. IF ( Control device x is switched on or Control device x is switched fade up ) And ( Control device x is not switched off or Control device x is not switched fade down )

bumping this back to the front.

This has come up before and doesn't make a lot of sense they way it is presented in the admin console programming. First off, you use a command "adjust scene" to change the local on rate of a device. This is a bit misleading Second, you select from a drop down menu labeled "in scene", but there are a bunch of individual devices listed to choose from (in addition to scenes). This is confusing. It would seem that all devices that are capable of having their local on level changed by isy are listed there, provided they are also in a scene of any sort. It would therefore follow that if you have a device that you want ISY to be able to change the local on level, and this device is not already part of a scene, you would be required to create a "dummy" scene for it. Again, somewhat confusing. While I am sure there are reasons for this based on Insteon protocols, perhaps the console nomenclature could be changed so that it makes more sense.

Exactly. Just remember "Control is . . ." statements are only triggers on the exact thing listed. Nothing Else The "control is not. . ." language is easy to remember as just the same as "control is. .." but opposite result (its a double negative) Also Remember if you have multiple triggers for a program (either other if statements or an external trigger), "control is" will ALWAYS be false whenever one of the other triggers activates. Similarly, "control is not" will always be true. Control statements are confined to the precise instant of the control event (someone pushes a switch). So breaking down the logic for an on press on the above example. IF Control device x is switched on - - - true, the on paddle was pressed And Control device x is not switched off - - - true, "off" event never happened (false), but this is opposite, so its true. Result - Then runs Now for an off press IF Control device x is switched on - - - false, the on paddle was never pressed And Control device x is not switched off - - - false, "off" event happened (true), but opposite, so its false. Result - - Else runs

Your guess is correct. Another program calling this program is a trigger event and will reset the program. You will never have multiple simultaneous running "then" or "else" executions.

What he said. The Then and Else clause are referred to as "atomic", meaning not separable (like in the old days before we understand nuclear fission), EXCEPT when a wait or repeat is encountered. These two commands separate the then/else clause into multiple atomic units. So, in short, once an atomic section of a then/else starts, all items will be executed. If during the micro-second of execution, another trigger occurs, the program will still finish the current atomic unit, and then start over. For example Then Repeat every 10 minutes do thing 1 do thing 2 do thing 3 wait 5 minutes do thing 4 do thing 5 do thing 6 The above has two atomic units. things 1,2, and 3 is the first, things 4,5,and 6 is the second. The thing 1,2 and 3 essentially happen instantly, but at the micro-second level, they may occur in any order. Regardless, all three things will happen once that section starts. If, in the midst of things 1,2,3 being executed (during that micro-second), a new trigger happens, still all 3 things finish, however, the "wait" will be a terminating point for this execution of the program (it starts fresh on the new trigger). Or, the repeat would also be a terminating point if the trigger event happened during/after things 4,5,6 and before things 1,2,3 repeated. Keep in mind, that atomic sections may execute in any order. So if your thing 1,2,3 are math functions where the result of 1 is passed to 2 and then 3, you might not get the answer you expect. Although typically they happen in order, it is not a 100% thing. If math function 1 is way more complex than math function 2, then 2 may execute before 1 finishes.

Certainly try a new cable. But odds are very very very (did I say very?) high that the PLM is dead. PLM's are a universal point of failure beyond 2 years of age. Just because the led is on, doesn't mean it is working. The green led on one of mine was on even though it's capacitors were bad. Personally I repaired 2 plm's via the capacitor replacement.

How old is your PLM? A little over 2 years I bet. Try rebooting ISY/PLM and restoring your PLM, does it work now? If yes, then your PLM is on its last legs. It might hold the links for a few minutes, or a few days, but it will happen again. You need to either get a new one or replace the capacitors as per the thread in here about that.

Yup, that was my reasoning as well. Wanted a non-admin user/pass for ifttt