Xathros

It is my understanding that everything in the ISY is backed up with the exception of: The firmware itself. The contents of the web server (if you have the network module). As long as you backup before upgrading, you can always reinstall an older firmware then restore a backup matching that older version of the firmware to get back to where you were. The backup names include the firmware version number in them for your convenience. -Xathros

I tend to make backups right after I make a bunch of changes. As long as I do that consistently, I can always go back the the previous backup to undo my recent changes. This way I don't need to wait for the backup before I can get to work. -Xathros

The same applies to: User variables, Scenes, Programs, Network Resources and Email customizations. All are internally referenced by an internal ID# so the name matters only to you. -Xathros

Sorry, after reading the whole thread, it seems I had missed the point and my previous suggestion was an answer to a different problem. I suspect we could work around this with the Pi however. Use the Pi to stuff the octets of the IP into 4 ISY vars then used those in your notification. I'll think about how to accomplish that. -Xathros

Couldn't you embed an identifier in the body or subject using a variable? You would need to know the meaning of the value but you are talking a fairly limited number of locations right? Or am I not understanding the issue at hand? -Xathros

It simply check for a release version higher than the installed version from what I can see. -Xathros

It's possible that you like me have been running beta versions with numbers higher than the official release when the official release is announced. That happened to me with this release as I'm on 4.3.0 and the ISY did not notify me of the official release since it's version was lower then what I have installed. -Xathros

A long long time ago in a firmware far far away... Been there for as long as I can remember. Only works with Official Final versions however. -Xathros

I think Stu means Status not Sense. -Xathros

5.X will have more advanced ZWave support and be on the leading edge while 4.X will have fully tested and certified support is how I interpreted that. -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