apostolakisl

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.

Yes. You could do that rather than manually re-enable. It takes the chance that at the time of the automatic re-enable you might not be ready. If state variable that counts 5 control off from switch used to disable siren is 5 Then disable program siren wait 30 minutes enable program siren

Variables are just as trust worthy as any other programmatic thing in ISY. The only failsafe would be to do an init so if there is a powerfailure it still reminds you. If Time is 8am (or whatever time you want, or multipel times, or whatever) and $i.pusheddisablebutton is 1 then send notification and anything else you want that might remind you If whatever variable you used to count 5 pushes of the dimmer switch Then disable siren set $i.pusheddisablebutton to 1 init $i.pusheddisablebutton to 1 (with this line, even if ISY loses power, when it comes back on the variable will still be 1 and you'll still get notifications) When you manually reset the variable to 0 and manaully re-enable the siren program, also manually change the variable init to 0.

Enabled/Disabled is not a condition you can test in an "If" section. You could add a line to the program that you used to disable it that sets a variable that then causes another program to send you an email every day until you reset the varialbe (which is supposed to be the time you then also enable the program). If Time is 8am and $i.pusheddisablebutton is 1 then send notification If whatever variable you used to count 5 pushes of the dimmer switch Then disable siren set $i.pusheddisablebutton to 1

In a scene like this most all the devices would be responders. You would likely have very few controllers, if any. When you add or remove or restore a responder it only writes the device itself and the controller(s). It does not write to all 70 (or whatever) devices. It is true that the responders in a scene do not confirm receipt of message. If you have consistent failures in that scene, this is not cause to use a program, rather it is cause to fix your com. If your scenes fail, you probably will also have failures on individual device com as well. Also, I would think you would want to hit the "off" button and have everything turn off. Not turn off over the next minute or two. And all the while bottling up your com for other commands.

A program would be a poor choice to turn off 70 devices. That would be 70 individual commands that would have to go out. It would be slow and have much lower reliability. A scene off command is just one command that all the devices respond to. Plus, your program would be a PITA to make as you would have to go through and list each device.

The fact that your computer went to sleep has nothing to do with it. The computer is only a "window" into the ISY. The computer is just where ISY shows you what is going on and a means for you to deliver commands to ISY. It has nothing to do with ISY executing the commands. If your lights kept cycling on/off with the PLM unplugged, then the cycling was not coming from ISY or the PLM. It means you had another device out there that was sending alternating "scene on" "scene off" commands. That is why when you restored the devices it stopped. Also, that is why restoring your ISY did nothing. I wouldn't be surprised if you had simply power cycled your house if that would not have stopped it also since I bet the device simply needed a reboot.

Yes, blank "if" runs "then" at startup. I actually don't think you need to even check the "run at startup box". But it doesn't hurt. Also, you could buy a new thermostat for your freezer. They cost about the same as an appliance linc.

Well, as I mentioned ISY is never going to fail to issue the commands, that just doesn't happen. Then repeat every 1 hour 59 minutes 40 seconds turn on device x wati 10 seconds query device x wait 10 seconds run if of notify-on program wait 59 minutes 40 seconds turn off device x wait 10 seconds query device x wait 10 seconds run if of notify-off program notify-on (disabled) If status device x is not on Then notify me nofity-off (disabled) If status device x is not off Then notify me After a power failure, the freezer will turn on for 1 hour and continue along repeating. If you want it to somehow pick up exactly where it left off, that is close to impossible to do with ISY (at least it would require a bunch of programs and variables and stuff) and is unlikely to be relevant to your chicken in the end. yes

If your cycle start/stop time don't matter then (run at startup on) If blank Then Repeat every 2 hours turn on device x wait 1 hour turn off device x (this will repeat every 3 hours because the wait 1 hour doesn't count in the two hours)

The above lacks enough info to know what it is you mean. What is checking? ISY never does not run a program when the if criteria are met. And for this program the criteria are quite obvious. It would only not run if ISY were not on. Perhaps you mean that it needs to check if the device actually turned on (an Insteon com failure?)

Does it need to be on/off at specific times during the day? Run at startup: If tims is from a to b or time is from c to d or time is from e to f or etc Then turn on Else turn off

I find that google voice recognition is better than Alexa dot. While I have a couple of the full size Alexa units, the one I use mostly for random tasks is one of my dots. Reason being is that I use the audio output jack on it, which the full size one doesn't have (nor does the google home). Google has a lot nicer integration with IFTTT. You don't have to say "trigger" and there are more options for varying the exact words, as well as varialbe substitution (which if memory serves me you can't do with Alexa).