Xathros

Me too!

Or at a minimum, go back to selling the dual contact Seco-larm switch with the garage kit. -Xathros

This is what you want: http://www.smarthome.com/seco-larm-sm-226l-3-magnetic-garage-door-contact-switch.html Can be wired either way. I have mine mounted at the top of the door frame. -Xathros

I must have missed that. -Xathros

No Problem. Always happy to help. Might want to have a look at the Email Substitution Variables page in the Wiki. It covers device status as used above. I recently updated it to include user variables and the Ham weather variables. And, very soon we will be able to use these in network resources as well. -Xathros

Hi Smokegrub- What is the Insteon address of your Insteon TStat? I will format the command you need to add to a custom notification for you. -Xathros EDIT: Nevermind. Just follow this: Program: If Time is 7:00PM Then Send Notification to 'Your Email' Content 'Temp Report' Else Create a custom email notification as follows: Subject: Temp Report Body: Indoor Temp: ${sys.node.11 B2 7 1.ST} Change the address in blue above to match your insteon stat. Note: Remove any leading 0's in the address sections (07 becomes 7) Hope this helps. -Xathros

For what its worth, I have always seen this issue when backing up my ISY locally or remotely via https and never locally via http. Up until this morning that is. Today I was able to complete a full backup remotely via https with no socket open failed messages. This appears to be due to improvements in the UDI firmware in a pre-release build 4.3.0 that I'm testing. This while my router and 3 processess running on a RPi were all frequently posting data to the ISY. Additionally, my backups have always been good in spite of these socket open failed messages. -Xathros

No but that capability is just around the corner I believe. -Xathros

Evernote to the rescue! -Xathros

Nope. I was referring to the DS1822 sensor. From the spec sheet: POWERING THE DS1822 The DS1822 can be powered by an external supply on the VDD pin, or it can operate in “parasite power” mode, which allows the DS1822 to function without a local external supply. Parasite power is very useful for applications that require remote temperature sensing or that are very space constrained. Figure 1 shows the DS1822’s parasite-power control circuitry, which “steals” power from the 1-Wire bus via the DQ pin when the bus is high. The stolen charge powers the DS1822 while the bus is high, and some of the charge is stored on the parasite power capacitor (CPP) to provide power when the bus is low. When the DS1822 is used in parasite power mode, the VDD pin must be connected to ground. -Xathros

I don't believe this is necessarily true. Some OneWire devices can run in parasitic mode where it only requires 2 wires (Gnd and Pwr/Data). I think this configuration is more common when there is only a single sensor wired to a host (TStat) rather than when multiple sensors are used as in your case. -Xathros

This is quite strange. It may be time to open a support ticket with UDI and they will help you get to the bottom of this. Create your ticket here: http://www.universal-devices.com/contact-support -Xathros

Clear the java cache again then goto: http:// <your.isy.ip.address>/admin/admin.jnlp Save the download and then run it, this will install a 4.2.18 version of the Admin console. Log in with that and see how it goes. I would recommend upgrading the ISY firmware to 4.2.30 once you get in. -Xathros

There are several possibilities here. First, Reboot the ISY. On occasion, they seem to hang on the restart after a firmware upgrade. Power cycling will resolve this. Second, temporarily turn off any AV or Firewall software running on your computer. If that solves the problem, you will need to exclude the ISY's IP address from the firewall. After you cleared the Java cache, did you download a new Admin console applet from the Firmware upgrade post? If not, do that and try again. Hope this helps. -Xathros

No problem. Glad you get it sorted out. -Xathros

Not sure I understand the request. Which motion sensor? Scenes don't run true or false, programs do. Your All Lights program can call a second program to look at the other sensor and turn on the LED's but if the other sensor is already controlling the LED's, it seems to me like you've already accomplished the stated goal. I must be missing something. -Xathros

I too see delays when sending notifications via SMS/MMS to my AT&T cell. I have tested sending to both my MMS and Email simultaneously and find that the email arrives in the usual 5-15 seconds and the MMS can at times be just as quick but can often be delayed for many minutes. I have moved all critical notifications to Prowl and have been much happier with the performance there. -Xathros

Is this a Gas or Electric dryer? If Gas, then I think a Synchrolinc may be the best solution for detecting the states of the dryer as you should be able to tell the various draws, Running, idle, door open with light on etc. If Electric another solution may need to be found. I'm not a fan of your Triggerlinc solution as implemented. While the dryer is running, this will be flooding the Insteon network with On/Off messages from the Triggerlinc. This seems like a bad idea to me. Can't imagine the battery in the Triggerlinc will last long with that kind of usage either. If you have Zwave on your ISY, one of these energy meters would be a good solution to this problem: http://www.amazon.com/Aeon-Labs-DSB09104-ZWUS-Z-Wave-Energy/dp/B00DIBSKFU Like the Synchrolinc, you should be able to detect run, idle and door open with this. If done right, you could use one sensor for the dryer and one for the washer. Hope this helps. -Xathros

Reboot the ISY. -Xathros

Excellent! Thanks for posting back with the result. -Xathros

Or as the op suggested, simply not use the light output of the fanlinc and wire the bulbs hot always. -Xathros Sent from my iPhone using Tapatalk

To take that a bit further, create a scene with the ramp rate you desire for the turn off ramp speed and set the controllers to that ramp rate. Then create a program as follows: If 'Control_A' is swiatched On or 'Control_B' is switched On Then Set Scene 'MyScene' FastOn When you turn the lights on with either control, thety will start to ramp up but the program will see the control on and issue a FastOn to get them on full. When you turn them off, the scene will just ramp off at the rate you set. Hope this helps. -Xathros

Glad you got it going. I have never run into a situation with any of my ISY's like this and I really don't believe this to be a common issue. If this happens again, I think it would be worth doing some additional testing to narrow down the root cause. -Xathros

Very nice! Welcome aboard and thanks for the post. -Xathros

The program runs once when the status changes to Off. The summary says the program has not run since startup. Cycle the Fan On/Off and see if the program status changes. -Xathros