apostolakisl

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.

This is an unfortunate characteristic of Insteon thermostat. "cooling" and "heating" are not a "State" of the thermostat. They are "control" communications issued by the thermostat upon entering the heating state or cooling state. In other words, they are not considered a "state" at all by the thermostat. So you can't query them. ISY calls them a "state", because, frankly I don't know what else to call it, but it is really the value of the last recevied communication from the thermostat as to whether it turned on/off the AC compressor or turned on/off the heating element (or whatever it is that heats you). Actual thermostat "states" include 1) mode (heat/cool/auto/program) 2) fan mode (auto/on) 3) cool temp 4) heat temp From an Insteon command perspective, "heating" is like a "control on" from a switch. It is only a command issued at the time of the button press.

I have many foscam cameras (like more than 20). They pretty much work. I have had maybe 2 die on me after many years of service. I also have extended the power wire on some of mine. I tried some small guage wire and it did not supply sufficient amps. I then tried some speaker wire which I think was maybe 16 guage and it works fine. I also have done POE with a bunch of my foscams and that works great as well. I used a generic POE split out at the camera since these were not the POE version of the cameras. One of my foscam's I installed at my church and we use to live stream. Now don't get me wrong, it is far from production quality, but it does the job. Anyone can view it at http://transfiguration.org/our-parish/video/ It is live when we are actually live and then there are links to all the past recordings.

You could always delete a device and add it back. If that doesn't work, then you have something more than corrupt link tables. And when you say your programs don't work. Do you mean that the programs work, but the devices aren't being communicated with?

I do believe that 99 is actually out of range (meaning that it is impossible to set the thermostat to 99). So in this particular situation, I think he is 100% covered. But to be 100% covered in other situations, I like the if is x and is not x No matter what, that runs true on every status change. Alternatively, if you don't need a "false" outcome, you can just put the same thing in both the true and false clause. if temp is x then do thing y else do thing y Thing y will happen on every change of x

This is an example from a thermostat at my church. It triggers on every change of the thermostat set point. You can use any temp you want. Really, having "is x" is not necessary since "is not y" where y is an absurd number would work all by itself. But keep in mind, it doesn't matter what changed the temp, it will still run the program. So if your motion sensor triggers an ISY program which then changes the temp, it will run this program the same as if you manually change the temp. Notify Sanc Alter N - [ID 0020][Parent 0065] If 'HVAC Sanctuary / Altar North' Cool Setpoint is 10° Or 'HVAC Sanctuary / Altar North' Cool Setpoint is not 10° Or 'HVAC Sanctuary / Altar North' Heat Setpoint is 0° Or 'HVAC Sanctuary / Altar North' Heat Setpoint is not 0° Then Wait 10 seconds Send Notification to 'Lou and Stuart' content 'Altar North' Else - No Actions - (To add one, press 'Action')

There is no "control" output from the thermostats when you change the temp manually like there is with a light switch when you manual press the up/down paddle. In fact, all changes to a thermostat look the same to ISY regardless of how they came to be. There will be a status change reported to ISY when the temp is changed (no matter how). In other words, the built-in program on the thermostat changing the temp will look the same to ISY as a manual push. Even if ISY itself changes the temp, it will report back to ISY a status change that looks the same as any other way of doing it. You would neeed to have a program that 1) looks for a status change in the thermostat from one temp to another and 2) Excludes your motion sensor as the cause of that change. That would be tricky. I'm not sure it is really possible, I guess it mostly depends on how you have implemented the motion sensor. It would be far easier to have another Insteon device that you use to shut down the motion sensor for a period of 60 minutes.

OK, so write a program that says at 8am set thermostat to auto heat 68 cool 72 at 8pm set thermostat to auto heat 65 cool 78 or whatever. You can do at 8am on mon,tue,wed,thurs,fri set to . . or whatever.

Yeah, you definitely don't want to be rediculously cheap and not get the base/relay combo. Trying to wire it up without the base is just ugly and half-assed.

https://www.ebay.com/itm/10A-AC220V-Coil-Power-Relay-LY2NJ-HH62P-8-Pins-2-Open-2-Close-With-Socket-Base-H/222673433519?hash=item33d85ef3af:m:mTQjslPNywaTezitgj4DhSQ $2.25 with free shipping. Plus of course the iolinc

The easy thing to do is to use a 220v relay wired in parralel with the pump and then use an iolinc to detect if the relay is open or closed. These sorts of relays only cost a few bucks. Squre D senses dropped pressure -> Square D Switch throws closing 220v contacts -> Pump gets power AND relay gets power/closes contacts -> Contacts closing on relay sensed by iolinc -> ISY gets message from iolinc This of course does not confirm that the pump is actually pumping, only that it is being supplied power and should be pumping. If you want to confirm that the pump is actually pumping, you would need additonal flow switches on the outflow section. Also, if the pump were to run for an unusually long period of time you might surmise that it is not actually pumping. ISY could send you a text or blink a light or something if the pump were on for longer than some period of time that you chose.

Power failures can be pretty easily managed with a UPS. Of course the program reset thing in the other thread can not. But if it is a super critical thing you can use a variable as follows. The 30 minutes would be delayed by however long your ISY was off. I don't see any way around that. If push the off button 5 times Then set $s.siren to 30 init $s.siren to 30 run program 2 then clause disable siren program If (run at start up checked) -blank Then repeat while $s.siren > 0 wait 1 minute $s.siren = - 1 init $s.siren to $s.siren repeat 1 time enable siren program init $s.siren to $s.siren Now if you had a program reset or a power failure, you would still re-enable the program. NOTE: I used a state variable, but that isn't necessary, an integer would also work.

Why so set on programming the thermostat from a computer? You can have a default program on the thermostat's internal programming and have ISY over-ride it always, sometimes, or never. ISY of course has a virtually limitless set of possibilities as triggers to change the thermostat. You can have it change 100 times per day if you like based on anything that ISY can access. 1) time, date (specific like 11/13/17 or general like every 12/25) 2) outside temp 3) inside temp 4) motion sensors 5) alarm system 6) activity on any device linked to isy (like if someone manually turns on a light it could indicate building occupied) 7) if you have your phone posting REST commands to ISY you can do geo-location or other phone stuff like when your phone logs off of your work wifi it turns on and when you log into your home wifi it turns on. You can use your imagination for others. In short, if you can make ISY aware of something, you can make it affect your hvac.

That is done from the thermostat. You can't set the thermostat internal programming from anywhere but the thermostat itself. Personally, I write programs in ISY to control the thermostat and don't use the built in thermostat programming at all.