apostolakisl

You would use the "wait" and "random" feature 2 Copy - [ID 0153][Parent 0093] If On Sat Time is 1:00:00AM Then Wait 168 hours (Random) put whatever you want to happen here Else - No Actions - (To add one, press 'Action') There are 168 hours in a week. This program triggers once per week at the same time (makes no difference what day of week or time you pick), then it waits a random amount of time between 0 seconds and 168 hours (one week). The next line after the wait is where you put what you want to happen. Once it finishes the random wait time, it executes your desired action, then the program ends. The process restarts the random one week event starting at the "if" time. In summary, whatever your action item is, it will happen once per week at some random time during that week.

I solved it by 1) Rebooting ISY 2) Restoring Device

I actually tried that already, but again. . . ."request failed"

I just added two new 2477 dimmers to replace two older ones. ISY found the two devices, added them, then I did a "replace with" to replace the two old devices with these two new devices. All of this appeared to work. Then I tried to move the two devices into the folder they belong in. The one device worked fine. The second device failed to move. I then tried to query it and control it. I either get no response at all from ISY or it says request failed. I tried rebooting the admin console a couple times with no affect. What gives here? The device does seem to have been properly programmed as it does control and respond to scenes.

No worries, I understand that they have shut off electricity in SF today. That will keep the bill down. EDIT: And you are correct, programs with from/to times and nothing else in the "if" will trigger at the from and to times only. So they will not conflict with each other.

This is probably not what you want, however, you can get a global cache ir device. Via the network module, you can send tcp commands specific to each ir signal to the global cache, and it "shines" out the ir signal. It is only one way of course, you get no feed back from the unit. Basically, it is a learning remote, but instead of pushing buttons, you send tcp commands to it. The GC doesn't store the commands, rather, when you "learn" the commands, it gives you a long string of values that you put into your tcp command. They also have some libraries which I imagine include your mini-split system.

Any reason to suspect that the radio would stop working after doing the fix? At least one of the two I repaired does not seem to have a working radio. The other I haven't tested yet. Of course I can't say if the radio ever worked on either of them since I have lots of dual band devices through the house which would put com onto the airwaves and vice-versa independent of a working radio on the plm.

Yes, only UD can transfer the license for your modules to the new ISY. It is done remotely.

If you want the same message both times, then yes. I thought it would be nice to have the first statement say "pump turned on" and second one two minutes later to say "pump now on for 2 minutes".

I don't think you need variables at all. Now I am taking stusviews word on this that control synchrolink terminology is correct since I don't have any of those, but it looks good to me. If control synchrolink is switched on and control synchrolink is not switched off (when pump shuts off, this line kills the "then" wait and reruns the program, which is now false causing the else to run) Then send notification pump switched on wait 2 minutes send notification pump still on after 2 minutes optional additional wait 10 minutes send notification pump still on after 12 minutes etc. Else - - - blank optional send notification pump shut off

If you do it from the on/off switch on the unit I'm sure it won't. But you should also make sure that the same is true if you go from on to off to on again by pulling the power.

Yes, if you turn off, then back on too soon, the downstream refrigerant will still be under high pressure. So if the compressor tries to start against that load, it won't spin, electricity will flow, and the coils will overheat and fry. If you wait, after a few minutes, the pressure bleeds down until the suction side and the compressed side become equal. Then the compressor can start without undue loading. I'm assuming an Insteon thermostat has short-cycle protection built-in to its programming?

The simplest way to do that would be to put a switch on the power supply. But as mentioned, restoring power to the unit might not turn it on if it has any sort of "smart" control. It might come on to a standby mode requiring you to push a button on it.

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.