Xathros

Barry- You may want to pick up some Ram Sinks similar to these and chop them into 1/2" sections and adhere your DS18b20's to these before placing them in your wall boxes. -Xathros

I am assuming that the variables are State variables. If that is the case, anytime a state variable's value changes, any If statements that reference it will be triggered and evaluated true (then) or false (else). In this case, since you have a notification in both the then and else sections, you will get notified anytime the temp changes. I think you need to remove: And Status 'Outdoors / Pond - winter pump' is 100% It's pointless. Remove the notifications from this program altogether. Create a second program to notify on status change of the pump: If Status 'Outdoors / Pond - winter pump' is 100% Or Status 'Outdoors / Pond - winter pump' is Off Then Send Notification to 'Tom' content 'Pond' Else Hope this helps. -Xathros

I am assuming that what you want is the light to run automatically via the motion detector after sunset but to stay on if you have switched it on manually. If this is the case, here is how I would do this: Define a Scene: Entrada sala, Make the device Entrada sala a responder. Set the Ramp rate to your desired "Fade Down" rate. Program 1: EntradaSalaMotion If Control 'Sensores Motion / Motion Entrada Depa-Sensor' is switched On And From Sunset To Sunrise (next day) Then Run Program 'EntradaSala1Min' Then Path Else Program 2: EntradaSala1Min If Control 'Sala / Entrada sala' is not switched On or Control 'Sala / Entrada sala' is not switched Fast On or Control 'Sala / Entrada sala' is not switched Fade Up Then Set Scene 'Sala / Entrada sala' Fast On Wait 1 minute Set Scene 'Sala / Entrada sala' Off Else Program 3: EntradaSaleMotionEnable-Disable If ( Control 'Sala / Entrada sala' is switched On or Control 'Sala / Entrada sala' is switched Fast On or Control 'Sala / Entrada sala' is switched Fade Up ) And ( Control 'Sala / Entrada sala' is not switched Off or Control 'Sala / Entrada sala' is not switched Fast Off ) Then Disable Program 'EntradaSalaMotion' Else Enable Program 'EntradaSalaMotion' The reason for the scene is to get your fade rate without using Fade Down. A Fade Down or Fade Up should always be followed by a Fade Stop or the device may be left in a unknown state. Fade Down is the equivalent of holding the bottom of the paddle in, fade stop is the equivalent of releasing the paddle. Using the scene for the ramp rate avoids having to deal with this issue. Set the scene fast on for instant light with motion. Set the scene off for the fade to dark. The third program watches the local control for Entrada sala and disables the motion sensor program when you have manually turned on the lights. It re enables the motion program when you turn the local control off. The If in the second program will terminate the 1 minute timer if you switch the lights on while the countdown is already running preventing the timer from turning the lights back off at expiration. Hope this makes sense and addresses your requirements. -Xathros

I can second that suggestion. In addition, you can embed URL's in a prowl notification to: Display images/video from a network accessible camera, Launch a specific app on the iPhone, Issue a /rest call back to the ISY to perform an action, whatever you can dream up... The prowl notifications are much more reliable and timely than MMS/SMS at least on the AT&T network here in the states. That said, there have been a few times that I have seen "late" prowl notifications. Those times have been far less frequent than the times I have encountered late or never delivered SMS/MMS messages on my phone. There are other alternatives as well: Push4.0, Boxcar and a few others that I can't remember at the moment all do push notifications much like prowl. Prowl is free - some of the others are as well I believe. MWareman put together a nice writeup on this in the WiKi here:http://www.universal-devices.com/mwiki/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification -Xathros

Certainly. I only did 2 timeframes in my example but you can continue what I started adding more to the if in the same structure that I provided. If left blank, it would have the limitation of having to wait till the next schedule arrived for the automatic changes to occur again. The folder will become enabled as soon as the 2 hr delay expires but that won't trigger the schedule programs rather will simply allow them to be triggered. The next trigger would be the first schedule time that occurs AFTER the delay has expired. If you ad Run If's of the schedule programs to the Else of StatWatcher, we can eliminate that delay. Exactly. Where Program A, B, C... are your schedule programs withing the folder. Your existing schedule programs can use either format. For the watcher, ther need to be in the From...To range format. Anytime. Happy to help. -Xathros

Hi Matt- Place all of your tstat schedule programs in a folder. Create the following program outside of that folder: Program: StatWatcher If ( On Mon, Tue, Wed, Thu, Fri From 5:25:00AM To 7:59:59AM (same day) And ( Status 'Thermostats / LR Thermostat - Main' is not 69° (Heat Setpoint) Or Status 'Thermostats / LR Thermostat - Main' is not 74° (Cool Setpoint) ) ) Or ( On Mon, Tue, Wed, Thu, Fri From 8:00:00AM To 10:59:59AM (same day) And ( Status 'Thermostats / LR Thermostat - Main' is not 70° (Heat Setpoint) Or Status 'Thermostats / LR Thermostat - Main' is not 72° (Cool Setpoint) ) ) Then Wait 2 Hours Run Program StatWatcher (Else Path) Else Then set the folder conditions for thefolder with the schedule programs to: Folder Conditions for 'Testing' Add conditions to limit when programs in this folder are allowed to run. If Program 'StatWatcher' is False Then Allow the programs in this folder to run. Obviously, you will need to duplicate the schedule and values for Heat and Cool set points in the StatWatcher If section. Be careful to get the Or's and And's in the right places. I only did 2 time frames as an example, you will need to continue with the remainder of yours and adjust the times accordingly. Also, my stat is Venstar/Insteon - the set points are represented on the "Main" node. Your Zwave stat may represent these differently. Adjust the code accordingly. This will prevent scheduled changes from occurring for 2 hours after a manual change is made. After 2 hours the folder will re enable and the next scheduled change after that point will happen normally. If the previous change was missed due to the hold, it will NOT take effect after the hold expires. If you wish for the changes to take place at the hold expiration time, we will need to trigger the schedule programs within the folder. To do that, we can modify the Else section of StatWatcher to include a "Run If" of each schedule program. Hope this helps. -Xathros

Nope. Pick up an ISY-994 and a new 2413 s PLM for the remote location. Install, enable port forwarding for the ISY through your router and possibly set up a ddns account and configure router to use it. You will want to factory reset the insteon devices before adding them to the new ISY. This will eliminate the links to the Smartlink. -Xathros Sent from my iPhone using Tapatalk

I don't see enough info in your previous post to help you form a resource rule. Need a complete url to start with. Be aware that you will only be able to build static messages with the current net resource capabilities as we have no access to substitution variable in the resources yet. -Xathros Sent from my iPhone using Tapatalk

You don't use network resources for that. Instead, use custom notifications to send email to the provider's email to sms gateway. Try @pcs.rogers.com as the address. -Xathros Sent from my iPhone using Tapatalk

wmcneil- I think it is possible to flash your 994 with the 994Z (zigbee) series firmware. The Z series firmware does not enter safe mode when no PLM is detected at startup. This would allow the ISY to operate in the event of a PLM failure at power up. As mentioned above, you can use a test of "Responding" against one or more Insteon devices to determine the PLM status and notify based on the outcome. Michel- Can you confirm that this is a viable approach? -Xathros Edited to correct typo.

I love that digital loggers din relay. Combined with the ISY and network module it is very reliable and quite useful. I use the first 3 relays to cut/re-establish power to my ISY, CAIWebcontrol, RaspberryPi and my Cable modem/Router. Modem and router share a relay, CAI and RPi share another. The remaining 5 relays are controlled by the ISY via state variables as follows: Program: Relay_4_Control If $s.Relay_4 is 1 Then Resource 'DINRELAY: Relay 4 On' Else Resource 'DINRELAY: Relay 4 Off' This allows me to not only control the relay by simply changing the value of s.Relay_4 from 0 to 1 but to also trigger other actions based on the state of the relay. The din relay unit allows you to define the default state of each relay on power up. If you simply set the INIT value for the corresponding state variable accordingly, the ISY and relays can/will stay in sync even through a power failure. ie: If relay 4 is supposed to be on by default, I would set the Init value for s.Relay_4 to 1. In addition, I have the DIN relay ping my ISY , CAI board and the Outside address of my cable modem (Static) every few minutes. If anything doesn't respond, the relay will power cycle the appropriate devices. -Xathros

Yes. -Xathros

Given the situation and requirements, the best solution I see i a second ISY at the remote end. Currently, you will need to write programs to manage the devices at the other end. Depending on requirements this may be as simple as defining a few modes of operation for the remote end and having the home end set a remote variable to change the remote mode. In an upcoming release of the ISY firmware, we should be gaining the ability to more cleanly merge multiple ISY's making the integration more seamless. This will work very nicely over ethernet. I would be very happy to help with getting the 2 ISY's talking if you need the help. -Xathros

I have to agree with Larry on this. While I also did not spent enough time to fully understand what you are attempting to accomplish here, I do see several programs that will loop due to the else statements. Program 'A:Russound Off' Program 'A:All Lts OFF' Are both going to cause endless loop problems as written. -Xathros

There are some issues with using Safari with the ISY. I recommend Firefox or Chrome instead. -Xathros Sent from my iPhone using Tapatalk

I hope this is just coincidence. What firmware were both of you running? -Xathros Sent from my iPhone using Tapatalk

Anytime. -Xathros

Lee, for my own clarity. While what you stated would be true when only the time frame trigger is installed in the "If" but when the time frame is used as a condition (used with another trigger) would the time constraint not be evaluated each time that other trigger even was incurred? So as an example: If Control from Motion Sensor is Switched On and From 10:00PM to 6:00AM Then Do It Else - Would the time parameters not also be examined for true or false (inside/outside the frame ) each time 'Control from Motion Sensor is Switched On' is triggered? Larry- This would only evaluate true when the Control was switched On between 10pm and 6am (next day assumed here). It would evaluate false at 10Pm and 6am due to the time triggers. IF you had used STATUS instead, then it may evaluate true at 10pm if the device was already on at 10pm. Now, to the point of your question, anytime a program is triggered, the ENTIRE IF section is evaluated and runs true or false based on ALL of the conditions together. LeeG's example was assuming no conditions beyond the time range. -Xathros

Oh well... was worth a shot. Sorry, I have no further ideas. I would submit a ticket with UDI for the fastest response. http://sales.universal-devices.com/contact-support -Xathros

I have to wonder if the ISY's IP address has changed and you are actually pinging and attempting to connect to some other device on your network. Can you check the DHCP client table on your router and verify that the ISY is where you think it is? -Xathros

My understanding says that once this program is "RunningThen" the lamp should turn on every 20 minutes for 1 to 15 minute random durations. -Xathros

When my motion detectors trigger an alarm, I have the foscams patrol predefined routes and enable FTP uploading of images once per second, This seems to work quite well for me. Of course this is not using the "Alarm" function of the cam but it may be a useful work around for some. -Xathros

I find that From/to is ideal for fixed start end end times. From/For works better for moving targets like sunset. ie: Turn on a light at sunset for 4 hours. Otherwise one is no better than the other. -Xathros

It would be less prone to powerline issues however being an RF only device, it is susceptible to RF interference. With few to no ZWave neighbors to build up the mesh, I think ZWave would be less reliable in your situation. -Xathros

The Keypadlinc is not a numeric alarm style keypad and was not designed with that usage in mind. That said, I do remember someone on this forum using one that way a year or two back. It would take a number of programs and timers to watch the keypad and validate the button sequence. If it comes down to it, I'm sure I could create a series of programs to do this for you. -Xathros