apostolakisl

That pulls 80ma in standby. So, lets say you decide to use 4 AA batteries. You'll be changing the batteries about every 6 days. I would be shocked if you can find anything that "listens" on any radio frequency that won't pull too much power ro reasonably run on batteries. Maybe you could use rechargables and put a solar panel on it? I have no idea what your situation details are.

If you can't even run power wires, than no. You can't do that. Nothing insteon that runs on batteries "listens". That would kill the battery. I am not aware of any battery powered wifi device that can "listen" either.

If changing the time made the program work, then I doubt there is anything fundamentally wrong with the program or how it was saved. I had an odd situation where a program that was supposed to run at a specific time (I think it might have been 1am) did not work. I changed it to 2am and it did work. Changing back to the old time and it still didn't work. This program's job was to send me an email with the values of a bunch of variables and then reset the variables. The variables were getting reset, but the email wasn't getting sent. ????? My program was a bit different in that it was a specific time. Sunset of course changes every day, so your program will run at a slightly different time each day. Since sunset -30 seems to not work, but sunset plus 2 hours does, maybe try sunset -20 minutes and see what happens. Just out of curiosity, are there any other programs that are also running at sunset -30?

You keep saying the same thing. PROGRAMMING ON-THERMOSTAT IS COMPLETELY UNNECESSARY IF YOU HAVE AN ISY ISY programs are fully capable of doing everything you might do with the on-thermostat programs plus, for all intents and purposes, infinitely more things. And it is all done from a computer which could theoretically be anywhere in the world. EDIT: And putting a "backup" program on the thermostat in the event that something happens to the ISY doesn't really work. If the ISY goes down, the thermostat will not revert to its own program, it will continue however it was last set by ISY. So unless the last thing ISY did was set the thermostat to use its own on-thermstat program (which ISY can do), it will just keep right on as ISY last set it until something changes that.

From the program summary page, the program ran true at ~4pm. True means the "then" executed. How the lights did not turn on is a mystery to me. One explanation is that you have another program that turned them off in an unanticipated way. I doubt resaving the program is going to do anything. The if section clearly is correct which you can see from the program summary page. The then section is correct since you can manually do a run then and get the correct result. You could debug it by a program such as this. If status of a light in the scene is off Then send me an email Else send me an email This program will send you an email every time your designated swithc in the scene changes status.

What Stu said. To complete the story 1) all red = currently running "else" (repeat or wait for the most part, a simple else clause will just blink red more or less) 2) all green = currently running "then" (same idea as above) 3) half green = not currently running, but last time it ran, it ren then. 4) half red = not currently running, but last time it ran, it ran else. 5) no color = hasn't run either then or else since last save. The "if" clause does not need to have ever triggered. Above applies regardless of how the "then" or "else" was made to run. In other words, a manual run then/else will do it, or if another program runs the then/else. But back to the matter at hand. Look at your program summary page and see what it says happened.

That program is not running. The half green means it last ran true, not that it is currently running true. If it is just a simple "at x time then do such" it will always be that way. There is no false.

That program should work. What does the program summary page say? It should list the next run time (whatever sunset minus 30 is). It should also say the last time it ran and whether it ran true or false. Of course, if you have a done a manual run on the program then it will tell you those times. But come next sunset minus 30, see what it says.

No, you can't do that. However, you can easily log into your ISY from a remote location after the installation and program it from there. It would be possible to add your devices at a work bench, one a time by temporarily hooking them up to power adjacent to your ISY/PLM. Once you add them all, you will have errors on each device, but you can still put them in programs and add them to scenes. I don't think you need the ISY pro, but you might. I think it will still store all the device writes until they come back online (for setting up scenes)

Any "if this" can result in a "then that" where the "that" is a web request. The web request (webhook) takes the standard http format detailed in the ISY wiki for submitting REST commands. You can run a program, set a variable, changes the status of an insteon device, etc.

Based on my reading 1) IFTTT can track nest. Since IFTTT can send REST commands to ISY (assuming you have port forwarded/set up https or are using the portal), then you can set a variable in ISY that tracks the state of your nest. 2) To the best of my knowledge, you can not tell google home to play music from anything but a voice command to it. Maybe I'm wrong. So, you can easily have a program run when the nest variable in ISY is set to some value and the garage door insteon device sends an opening command. That in turn can turn lights and stuff on, but I don't think the google home music is a possibility.

It's all in the thread. Yes, that is what he said.

He isn't saying that nothing happens when he uses Alexa/Portal, he is saying the scene gets messed up. "ok, a follow-up. The switches work fine, UNTIL I use Alexa to turn the scene off. Once I do that, they all get out of sync. I have to go to the main switch (the one that is hooked up to load), pull the tab, wait 5 seconds, then push it back in. Once I do that, they work fine again as a 3-way, until I turn them off using Alexa. Any ideas? Dismania"

He states that the scene turns on/off as expected when controlled from the Java admin console. So I don't understand how using the portal to turn on/off the same scene doesn't work.

Don't know what to tell you. Like I said, portal -> isy -> Insteon plm -> switches admin console (your pc java app) -> isy -> insteon plm -> switches Any error that could cause your switch to need a reset could only be between the plm and switch. And as you see, the plm->swtich part is the same regarless of the beginning. I guess you would need to submit a ticket.

You are using Alexa throuhg ISY, correct? Not the Insteon hub. If you have an insteon hub, well . . you should just not have an insteon hub.

Alexa turns the scene off using ISY. 1) Can you turn the scene on/off from ISY admin console? 2) Did you set Alexa to turn the scene on/off or one of the switches in the scene? It should be set to turn the scene on/off, not the switch. If you can't turn the scene on/off from ISY admin console (turning the scnene on/off should cause all 3 switches to turn on/off), then there may be something wrong with the links table in your plm. But I kind of doubt assuming you did what I outlined above. There are ways to check the links table, but first things first.

Actually, you can disable the buttons. It is in the manual, it is the same set of menus that you use to change the light settings. But it disables all the buttons, you can't just pick a button. While the buttons are disable, hitting any button will still turn the light on. Once disabled, you would need to make changes to your thermostat from ISY or from some other remote control method. The buttons can be re-enabled using the same method that disabled them.

Yes. When you come out of that 30 minute or 60 minute "holding" pattern after a manual change, what then? You may need to do some "run if" or "run thens" to other programs that would have been blocked from running during the time out. And if indeed you are changing from mobile linc (or the admin console, or any other non-isy program), then you have issues. It would be hard to streamline that for the user. You could use v5 of ISY firmware and instead of setting the thermostat, set a variable, that then triggers a program to run setting the temp to the variable, but now the user has to change a variable, not a thermostat. There would be a low WAF in that (wife acceptance factor).

Yes, that is what I suggested in my first post. You will need to look at every way the thermostat can be changed (excluding a manual button press) and figure out how to programmatically rule all of them out as the current change. How doable that is will depend on all the various things controlling the thermostat. If, the only way the thermostat changs is via 1) manual button press 2) ISY programs Then you only need to rule out ISY programs. That is not impossible. but there will be some slop in there because you will need to put delays in there. When an ISY program runs that changes the thermostat, you can have it set a varialbe indicating a recent program change to the thermostat. That variable being set could be part of the "if" clause of any program you want to run/not run during that time out. The variable could be set to 1 and then after maybe 10 seconds go back to zero. But, that doesn't rule out the possibility that someone manually changes the thermostat during those 10 seconds. You must have a delay, becauese a program changing the the thermostat will take a second or two to register on the thermostat and then a couple seconds to register that change back to ISY status.

Yes, as per both comments. Especially Pual's. You need to erase the manual setup that you did with a factory reset and do it all in ISY. 1) Factory reset all 3 (pull the tab all the way out till it stays on its own, wait 5 seconds, then, in one motion, push all the way in and hold the tab for another 5 seconds, then release it to its natural position) 2) Delete the devices from ISY (unless you never added them) 3) Click the little swirly linking button at the top of the ISY console 4) Go to each of the 3 switches, push and hold the tab in until it beeps (maybe 3 seconds) 5) Go back to ISY, all 3 switches should be showing in the popup window, click OK to have ISY add them and name them. 6) Create a scene and name it 7) Right click on the scene name and click "add device", then select one of the three switches, specifying it as a "controller", repeat for the other 2.

Sorry, but it just isn't a doable thing as the hardware is setup. The closest I can come to making this happen would be to hack your thermostat and an Insteon remote on/off switch and wire it up such that a manual press of the up/down on the thermostat not only changes the thermostat per the usual contact closure inside the thermostat, but also it would have some wires that come off of those contacts and into your hacked Insteon switch. Now pushing the up/down buttons will simultaneously send a "control on/off" from the remote switch for use in your programs.

In that case I would try factory resetting the thermostat, deleting it from ISY, and then starting from scratch. I will tell you that my thermostats occasionally miss a heat on/off or cool on/off command despite everything else populating, but that is infrequent.

If the "heat cool state" box is blank despite the thing cycling on/ff the actual heat, then you have a comm issue. Either there as in issue with the thermstat/plm having the proper links or it just isn't getting the comm.

Example: your thermostat is set to cool at 74 and you just booted your ISY so all the "cooling/heating" stuff is blank and the current temp is 73. Now the temp rises to 75. => the thermostat starts to cool =>thermostat broadcasts a "cool on" comm =>ISY populates the heat/cool state as "cooling" =>ISY puplates the cool control as "on" Now the temp drops to 73 => the thermostat shuts off the compressor =>thermostat issues a "cool off" comm =>ISY populates the heat cool state as "idle" =>ISY ppulates the "cool control" as "off" Since you have not done any heating yet, "heat control" is still blank. Of note: if a comm is missed, ISY will be wrong and no amount of querying will change that. The only way to fix it is to change the temp to force the AC or heat to kick on/off and send a new control comm.