Xathros

Gotcha. -Xathros

You are correct. This will require 2 programs. This: Run Program 'Front Door2' (Then Path) is the problem. Should be If Path. You are bypassing the time test by calling the Then directly. A few suggestions: 1) Make a new notification address group that contains both Gary and Sandy's addresses/Numbers. That way you can issue a single transaction to notify both. 2) You programs will turn the light off when triggered during the day even if you turned it on manually. Try something like this: If Control 'Front Porch / MS (DD)' is Switched On Then Send Notification to 'Text Gary/Sandy' content 'FrontDoor.Motion' Run Program 'Front Door2' (If Path) $FrontDoor.Triggered = 1 Else Wait 10 seconds $FrontDoor.Triggered = 0 Sub Program ---------------------------- If From Sunset - 3 hours To Sunrise (next day) Then Set 'Front Porch / Front Porch Switch' On Wait 5 minutes (Adjust this delay to your needs) Set 'Front Porch / Front Porch Switch' Fast Off Else The program summary is showing how the programs last ran. The FrontDoor2 program was forced to run tue by your runThen call. Hope this helps. -Xathros

Larry- The variable must be a State variable and it's value must change for it to trigger an evaluation. Integer variables are evaluated when a program is triggered but they do not trigger a program when their value changes. -Xathros

Lets say that after modifying the unit with an external probe and testing against a known accurate thermometer, the unit is reading 3 deg above actual. (ie: 80 deg actual reads as 83 deg on the multi sensor) Lets say we want to keep the temp between 80 and 85: If Status 'ZWave MultiSensor' < 83° F Then Set 'Heater' On Else - No Actions - (To add one, press 'Action') and If Status 'ZWave MultiSensor' > 88° F Then Set 'Heater' Off Else - No Actions - (To add one, press 'Action') So - simply move your decision points up by 3 degrees. Make sense? -Xathros

I'll have to dig out the docs that came with it. I vaguely remember a way to adjust the unit but can't say for sure. At worst, you could just deal with the reading being off and adjust for it at the ISY. -Xathros

Excellent! Glad we could help. -Xathros

I opened up my Everspring unit and it appears to use a thermistor for temp sensing. The thermistor is nestled together with the humidity sensing grid and may be somewhat difficult to remove and replace with leads to and external sensor. If done, you would likely need to recalibrate the unit to account for the added resistance of the leads to the external probe. The sensors fit tightly into a molded area of the front case that is vented to the outside and fairly well sealed from the inside when the sensors are in place. -Xathros

Hello arndtk86- As you have likely figured out, my program does not really disable the response to the motion sensor at all, it simply changes how the linked device responds to a motion event to make it appear that nothing happened. For daytime, simply turning off an already off light seems to do nothing. However, as you have discovered, it you were to manually turn on the light, the motion sensor will turn it back off when in this psudo-disabled state. The solution is to modify the responder link record to match what you want the light to be set at. So, if you manually turn the light on to 40%, then you will want to issue an adjust scene for the light when controlled by the motion sensor and set it to 40%. That way when the sensor is tripped, it turns the light on to 40% (where it already is, ie - no change.) Larry's programs above are an example of this concept using several different on levels based on time of day. When the 5.X firmware is released, this will become much easier. We will be able to monitor the for the manual control of a device, capture the current on level to a variable and use that variable in an adjust scene statement. -Xathros

I don't believe we will see very many more 4.x releases before we see a 5.X beta. I expect there will be a final 4.X in the next week or two then we are on to 5.X betas. Lots of awesome stuff coming in the 5.X series: New variable types, the ability to get/set values to/from devices, two way network communications, multi channel ZWave, and the ability to link multiple ISYs are just some of the things we have been teased with over the last year. 2015 looks like it will be a great year for the ISY community. -Xathros

The ethernet port on my 994 has both Link and Act LED's As do most switches I have seen. The OP stated that there was no blinking, I took that to mean there was a Link but no activity. If neither Link LED's are lit then, I have to agree and suspect fried port(s). -Xathros

ISY programs are event driven. The if section of a program does two things: Define Triggers and evaluate True/False. Both are critical. A time based program (From to...) triggers twice. Once at the beginning of the time range and once at the end. When triggered, the if clause is evaluated for true/false. True runs then, False runs else. Once triggered at the From time, the if is not re-evaluated again until the To time is reached (unless there are other triggers in the if section other than the time range) It is important to understand what triggers an if and what doesn't. Time From/To, Device Status changes, Device Control events, State variable value changes, Elk, Energy and Weather module variable value changes will can trigger an If. Integer variable changes DO NOT trigger an if but ARE evaluated when used in an if that gets triggered by other means. With regard to variable value changes, the value has to change to trigger, not just update to the same value. Same with the status of a device. The If section of a program will always be evaluated when called by another program or when manually called. When the if is evaluated, the evaluation follows what one would expect from other languages in terms of And, Or and the use of (Parens to group items). Given the above, in your example, if the ISY were started up at Noon on Monday, nothing would happen until Sunday @ 10PM when the program would trigger and run the Then. It would then trigger again at Sunday @ 11:55Pm and run the Else. As Shannong points out above, the function of the Then is not undone when the else runs at 11:30. You would need to deal with that in the else section if necessary. Hope this helps -Xathros

I haven't opened up my Everspring unit but I suspect it's using something like the Dallas one wire sensors (DS1822) or similar. If it is, there are a number of nicely packaged external probes that could be used in place of the internal sensor. -Xathros

Hi Gregg- Thats very much the same as my setup. I agree - IP conflict is unlikely here. When you get home, unplug the PLM (From the wall) and remove power from the ISY. Plug the PLM back in, wait 5 seconds then repower the ISY and watch for activity on the switch port as well as ISY blue light activity. Post results. -Xathros

Hi Gregg- Power down the ISY again and replug the power. Watch the link/Act light on your switch to see if there is any activity during the ISY startup. If there is, it's possible you have an IP conflict with another device on your LAN. Was your ISY assigned a static address? If so, was that done by hard coding the address in the ISY or by MAC reservation in the router? -Xathros

smokegrub- First, try changing your screen cap to a jpg file. Open it in Preview and save as a jpg. Then you can post the jpg. I have changed my default screen cap to jpg as it saves me a step of converting. To do that: You can change the default file type for screen captures by using a terminal command. Every installation of Mac OS X includes the Terminal application in Applications > Utilities. Most major image formats are supported including PNG, PDF, GIF, TIFF, and JPG, we’ll go with JPG since that is a common type of web graphic: defaults write com.apple.screencapture type jpg Then you must kill the SystemUIServer for changes to take effect: killall SystemUIServer Screen captures will now be saved as JPG files. To change back to PNG, just run through the process again setting 'png' as your type in the first Terminal command. Hope this helps. -Xathros

You are using the dusk-dawn node rather than the motion sensor node. No wonder its not working for you. Each sensor should have 3 nodes (Sensor, DuskDawn, and LowBatt) Change your program to use the Sensor node. The Dusk/dawn node turns on/off when the ambient light level in the vicinity of the sensor has crossed the configured threshold for more than 3.5 minutes. It's doing roughly the same thing you are with sunset/sunrise but based on light level rather than time of day. In no case does the dusk/dawn node send an on/off message in reaction to motion being sensed - thats what the Sensor node does. There is a save button on the event viewer. Once saved, you can open the resulting file in a text editor and copy / paste relevant data to the forum. Hope this helps. -Xathros

Oops! I missed one item: In Safari Preferences, Select Security Tab, Check in Allow Plugins, then click Website settings next to that check box, Select Java on the left and find the ISY url on the right, set that to run in Unsafe mode. Where is it attempting to save the zip file? Make sure its to a location that you have write privileges. Have you installed the Java application to your desktop or do you access the admin console via the browser each time? If via browser, I recommend that your install the application instead. -Xathros

Hi Gina- In Safari Preferences, General Tab, Uncheck "Open safe files after downloading" In System Preferences, Java, Security, add your ISY's url to the exception list. Hope this helps. -Xathros

Sounds to me like the relay in the IOLinc is dying or at a minimum, does not like the cold. -Xathros

Anytime! As always, Happy to help. -Xathros

Hello arndtk86- The easiest way to accomplish this (and what I believe most of us here do) is to remove the motion sensors from the scenes and use ISY programs to call the scenes when motion is detected rather than have the sensors directly in control. This will add about a 1 second delay between when motion is sensed and the lights react. Then, you can either disable the motion program or add additional criteria to the motion program(s) to enable/disable their response. Here is an example program: If Control 'MotionSensor' is Switched On Then Set Scene 'Lights' On Wait 5 minutes Set Scene 'Lights' Off Else Now lets include a KPL button to disable the motion program: If Control 'MotionSensor' is Switched On And Status 'Kitchen_KPL8-D' is not On Then Set Scene 'Lights' On Wait 5 minutes Set Scene 'Lights' Off Else In the above, Turning on the D button on the Kitchen KPL8 prevents the motion program from doing anything. Since you are using Mobilinc to control things, you could substitute a variable for the KPL button and add a program to toggle the variable: Program: MotionEnableDisable (Disabled) Important to disable this or it will just get stuck in a loop. if $s.MotionDisabled is 1 Then $s.MotionDisabled = 0 Else $s.MotionDisabled = 1 You can make the above a ML Favorite and use RunIf as the default action for the ML favorite to toggle the variable between 0 and 1 Then: If Control 'MotionSensor' is Switched On And $s.MotionDisabled is 0 Then Set Scene 'Lights' On Wait 5 minutes Set Scene 'Lights' Off Else Now, if you decide that the delay introduced by using a program is a problem, there is a sneaky way to continue using a motion controlled scene and simulate disabling the motion sensor. I wrote that up a while back here: http://forum.universal-devices.com/topic/14587-motion-sensor-programming-help/page-2?do=findComment&comment=122476 This method is not recommended for a beginner however. Hope this helps. -Xathros

You could use a Switchlinc Dimmer in the box without the load line connected then add a micro relay module in the fan housing and link the two. That might move the click to a location where it won't be heard. -Xathros

Sorry to be late to the party. To answer the original question, I have a program in place to monitor for close failures (usually caused by something left in the sensor beam). I have different programs for opening and closing the doors. I call the following from my CloseIfOpen program: GarageFailNotify - [Not Enabled] If Status 'Garage / Garage Door IOLinks / GD- Dad Garage Door Sensor' is On Then Enable Program 'GarageFailNotify' Wait 20 seconds Repeat Every 10 minutes Send Notification to 'Xathros Cell' content 'Dad Garage Door Close Failure' Else Disable Program 'GarageFailNotify' If the door closes within the 20 second wait, the program just disables itself, otherwise, it repeatedly sends notifications. Hope this helps. -Xathros

Stu- It may be worth reviewing the many posts by ELA during the time he was developing the ELAM. He has provided this community with a great deal of valuable data on Insteon signaling, noise and attenuation. See: http://forum.universal-devices.com/topic/5600-getting-serious-when-comm-issues-strike/?hl=elam That KPL diagnostic tool is a joke in comparison. -Xathros

I have to agree with oberkc on this. Is it possible that the Wait is the last thing you added to the program and it needs to be saved for it to take effect? If not, Right click the program tree and select Find/Replace, Set the Find drop down to "Raw Text" and search for Garage.Alarm and see if there are any other references to this notification. -Xathros