apostolakisl

You can have echo run a program. The program can set the variable. The same program can send you an email/text letting you know it activated and/or blink some lights or something. When you tell it to turn a program on, it runs the "then", and vice-versa. You also can skip the variable all-together and have that program disable the programs you don't want running while away.

No, it doesn't turn it on because the program was always false as you had it written with "same day". Your "from time" is after your "to" time. What you had written will never be true. ISY works off of triggers. Your program had two triggers, the from time and the to time. The trigger initiates the "if" evaluation. The trigger has nothing to do with it being true or false. So once triggered, it determines true vs false and executes the "then" or "else". In your case, else every time.

When I asked my google home to turn on a light, it responded with something to the affect of "universal devices is not available right now". It definitely did not say anything about permissions nor did it use the word error. Having experienced this before, I went directly to "google home" app on my phone, removed Universal Devices, then added it back in. This fixed the problem and I got no errors adding it back in.

Well, after a long time of not going down, the link went down again. So perhaps putting devices into the google home that update often (multiple times per day) doesn't entirely fix this issue.

I don't personally need to track anything, but others do. If you support http end points, there really wouldn't be anything you would need to do to make it work with ISY. Anyone can set a port forward and have an http command directly go to their ISY, or, us the universal devices portal and avoid security considerations. This could be used to set a variable for example. You could even have it send coordinates. If you wanted to get a little fancier, I'm sure one of the people on this forum who know how to create ISY nodes could create a custom node for your device. I don't know what sort of development budget you have, but it wouldn't be a very big project.

Nodelink puts the values as nodes. That is a huge plus. I already have all the values as variables from that huge batch of programs I wrote so many years ago so there was no point in using v5 date variables. I checked it out and was disappointed that the values weren't directly accessible. The issues with another device running wasn't an issue for me as I already had a rpi and a pc configured for always on reliability. It would seem to me that with polyglot, ISY is going to be leaning more and more on that method for expanding its integration and would expect that most ISY owners would end up running a polyglot rpi sooner or later. Perhaps the cloud based polyglot will make that unnecessary, but then you have the issue with the system no longer being local.

You have access to system variables (month, year, etc) only within the user configurable variables. You will need to create a user defined variable for each system variable you intend to use. Then create a program that updates the user defined variable with the system value. Then you can use that user defined variable within other programs. Frankly, the nodelink program is better. Though it uses the time from the pc or rpi's clock it runs on, not the isy clock. The program that updates the variable will need to run at logical times to make sure the value is correct.

Control: -triggers a program when: Someone physically acts upon the switch (for switches) and performed the precise statement listed. ie control "on" means the on paddle was tapped. Any other action to the switch is ignored. Like press and hold the on (which is control dim up), or double tap on (which is fast on), or any action to the down button. -the statement may be otherwise evaluated if something else triggers the program (like an additional if line) and the statement will always be false. For example, control switched on will always be false if something besides someone physically tapping the on paddle triggered the program. Usage is mostly confined to: If device x is switched on (always false, except at the instant ISY receives the "on" statement from the switch) and device x is not switched off (always true, except at the instant ISY receives the "off" statement from the switch) The above is used to have the "then" run when a switch is tapped on, and the "else" run when tapped off. Status: -triggers a program when: The device status changed for any reason. Regardless if it was acted upon directly or responded to something else. -the statement may otherwise be evaluated if something else triggers the program (like an additional line in the "if") and will be true if indeed the status of the switch is as listed or false if otherwise. ie, if status device x is off will test as true if the device is off at the time the program triggers regardless of what triggered the program. NOTE: It will also be true in the case that the triggering action culminated in that status. ie "if status device x is off" will be true if the device began in any state beside off and became off. In that case, the switch becoming off triggers the program and evaluates true. Understand that a "control" condition is an instantaneous condition corresponding to the exact point in time that the ISY receives the message from the switch that it was tapped. No two control statements are ever processed simultaneously. If using the "not" then it is just the opposite, it is always true except for the instant ISY receives that command at which point it tests false.

You can control individual keypads from Agave. I do believe you can arm the system with violated zones and it will bypass them. I don't know of a way to pick and choose zones.

To my knowledge, the only things ISY (and thus all the apps that integrate with ISY) lack is Task control on the Elk. Seeing as ISY is a much better programming interface, Elk Tasks aren't really necessary. I have kept my Elk tasks since I made them before ISY had an Elk module and use an Elk output to trigger them from ISY (which is rare). Also, you can't set "counters" on Elk from ISY, but I barely use those at all. Is there anything else I'm missing? I also use Tasks on Elk for a couple things that are strictly security system related and would never need to be manually activated.

I have android so I use Agave. An Apple person will need to give you the details.

mobilelinc is the best option for iphone. You don't need the portal, but I would highly recommend it. It takes care of keeping your ISY connected to the www in a secure and simple way with very minimal cost.

Not positive, but you might be able to respond to an email as well. I haven't looked into it. Though, I use google voice and all of my texts come as emails (as well as texts) and if I respond to the email, it goes out as a text. So, in short, I don't need to have IFTTT respond to an actual email.

I agree, this sounds like a verizon email to text issue. As a suggestion, you might consider using IFTTT for this. The ISY portal integrates ISY with IFTTT. For starters, IFTTT can send a text as a text. Secondly, you can reply back to IFTTT and IFTTT can then tell ISY to end the program via a REST command. I have a situation where IFTTT sends me a text letting me know the sprinkler is going to run in the morning. If I reply to that text #no it will cancel the sprinkler. You could just as easily have it end that program repeat. When IFTTT receives the #no, it then issues a REST command (again through portal) to ISY which sets a variable to 0. The sprinkler runs at 6am if that variable is 1. So the deal is that at 6pm on the day before my schedule wants to sprinkle, an ISY program sets the variable to 1 and tells IFTTT to send the text.

Yeah, but this is my office. I have Elk at home and I do integrate it heavily into all of that, but it is using the ISY Elk module. I just don't have much use for all that stuff at the office. If I were doing it all again, I might choose DSC at home with all of the integration that (thanks largely to you) it has now and at quite the lower price point.

OK. I might use one of my idle CAI boards to control it then. I assume that nodelink/invisalink can trigger an ISY program based on alarm status which can then control the cai webcontrol. My plan is to wait 30 minutes after arming to turn off water. I also plan on putting in some water sensors to turn it off immediately. We have laundry facilities at my office and the staff like to turn it on just before leaving which of course doesn't work if the water shuts off. EDIT: I could also just skip envisalink altogether and use a CAI board. The pgm output could go to a CAI input and trigger a program within CAI to wait 30 minutes and the turn the valve off. And I could wire water detectors directly into CAI also for instant off.

Can nodelink control the pgm outputs on a DSC system via the envisalink? It is listed in the installation manual that you can control the pgm output using the DLS software, and I understand that the DLS software can use the envisalink as its connection interface, so I know there is a pathway, I'm just wondering if nodelink has the ability to utilize that pathway. The deal here is that I am using the pgm output to turn my office main water supply off when armed away. However, I would like to have more customized control of it.

I had this problem, though it didn't self correct. It was related to the fact that I only had scenes entered into google home. Scenes don't have a status so the portal would not routinely update google and google (I guess) would time out the connection. I added a couple devices the google home that I use often and it hasn't happened since.

Those are about the cheapest I think they have ever sold most of those products. It works out to $25/switch for your 2477D/S's. In the past I have gotten them for $27 with the 20% off of the already discounted multi-pack prices. If you are thinking of upgrading an older single band system, this would be a good time to do it. EDIT: Just noticed my wife's "E-bates" account popping up claiming another 2% off. Add 2% more for a cash back credit card, now your down to $24/ea. EDIT: The on/off and dimmer wall wart modules are also $25 in this sale, but I have seen that price often.

Usually they do. Maybe 20% off.

Benoit, Will this have any impact on how things like Agave work, since Agave also links to the preferred ISY? Of course with Agave we don't need multi-ISY use since there is no Agave account issue accessing two different portal accounts.

Would that apply to google also?

Well most people don't care/want/need to control every device via Amazon. But c'est la vie.

Nahhh. It is hardly any different then setting up Amazon commands. Just use the portal to create a webhook just the same as creating an Amazon command. Then copy and paste the webhook into ISY network resource. Then write a program that runs the network resource from the "then" clause and a second webhook to turn the light off goes in the "else" clause. Now ISY 1 has a program that runs a light on/off in ISY 2. So Amazon controlling ISY 1 now has control of ISY 2 via the webhook "relay".

I agree, it does seem like having multiple ISY's on the same account serves limited functionality to anything other than the "preferred". If you don't have a ton of stuff, you can relay commands from one ISY to the other. You would create webhooks for the secondary ISY and then have the primary ISY send the webhook. You would write programs that trigger a network resource with the webhook.