Xathros

Techman- What are you using for an SMTP server? Are you sure that neither the subject field or body are blank? Are you positive that the program responsible for sending the notification is actually running? -Xathros

Here ya go guys: For example ${sys.node.11 22 AA 1.ST} would provide the current temp of the thermostat whose address is 11 22 AA 1 http://wiki.universal-devices.com/index ... _Variables -Xathros

I'm doing Z-Wave for my locksets since there is no good Insteon way of accomplishing that. I have added a few Z-Wave switched outlets and a dimmer or two just to build up the Z-Wave mesh network to a reliable level. I do find Z-Wave to be slightly cheaper than Insteon and there is much more competition in the Z-Wave market which will hopefully bring the prices down further. So far, it looks like the ISY will nicely integrate Z-Wave devices with Insteon devices. -Xathros

Thermostat values can be sent via email using the builtin notification system in the ISY. No PC needed for that. Variables cannot yet be used but that is coming in the next release I believe. -Xathros

Yes. The ISY is event driven. Triggers happen at the time an event occurs (Status of a device changes, value of a state variable changes, a control event is received, called by another program etc). Saving a program will NOT cause it to trigger. You will need port forwarding or internet access set up so that you can log into the admin console and select reboot from the system tab. -Xathros

You can do this using the built in notification system. There is a method to create and write to files on the ISY's webserver. See this link: http://wiki.universal-devices.com/index ... tification I do this using the network module to write to a log file on an external syslog server running on a RaspberryPi. I would have gone with the method above if it had been implemented sooner. The RPi method allows me greater flexibility since that is a full linux based system. -Xathros

I don't believe this is an error message but rather the ISY logging a DHCP address lease renewal. Unless these are appearing many times within seconds of each other, this is just normal operation of your ISY on a dynamic IP address. -Xathros

It has been mentioned in the past that an upcoming update may allow the use of variables within network resources. I'm hopeful that we will see this in the next release. If so, then the answers to Q1 & 2 will be yes. For the moment however, we cannot do that. -Xathros

Try this link: http://www.sheepwalkelectronics.co.uk/R ... ware.shtml -Xathros

I'm with Tim on this one. Network module is the way to go. Powerline is nowhere near as reliable - especially when sending X10. -Xathros

If you port forward port 443 to the ISY you should be all set. Assuming of course that your ISY's secure port is set at the default 443. -Xathros

See above - you posted while I was adding more to my previous post. Is the old KPL bad and not responding?

Assuming the replacement Keypadlinc is of the same type as the original then Replace With should do the job just fine. They need to be either both dimmers or both relays and both the same number of buttons. Otherwise, you will have to go the manual route. If taking the manual route, Add the new KPL and don't remove the old one. Give the New KPL and temporary and obviously different name to avoid confusion with the old one. Then use Find & replace for each of the buttons to replace the old with new. That will make the program updates easier. Then make go through the scene memberships for each of the old buttons, adding the appropriate new button then removing the old. Once you have removed all of the old KPL buttons from the scenes, you may remove the old KPL from the tree. -Xathros

Is the keypadlinc button H configured as Non-Toggle Off ? -Xathros

Anytime! -Xathros

I'm hopeful that the next firmware update with expanded variable support will allow me to reduce my program count significantly while greatly improving the ISY's capabilities. -Xathros

I've been on the ISY for almost 5 years now and have never encountered that behavior and while I do see reports of lost link records here now and then it does not seem to be a common problem. -Xathros

Sorry. I assumed that node 2 was the sensor. Must be the relay. Right Click the sensor node in and select Diagnostics/Show Device Links Table. When the display is complete, click compare. Post results. -Xathros

Communications look perfect with the IOLinc at the PLM location. It still looks to me like the sensor is responding. Are you looking at the relay node of the IOLinc or the Sensor Node ? -Xathros

The My Programs Folder could be collapsed thus hiding ALL programs. Click the '+' Icon on the toolbar to expand the program tree. The My programs folder could also have a folder condition preventing all programs from running. Click the My Programs folder and look for conditions in the right hand pane. These are 2 simple items that could easily produce these symptoms. -Xathros

LeeG- Aside from the obvious comm issues, it looked to me like the IOLinc Sensor IS responding. I see: Tue 09/17/2013 02:35:35 PM : [ 19 61 92 2] ST 0 Tue 09/17/2013 02:35:41 PM : [ 19 61 92 2] ST 255 Tue 09/17/2013 02:35:59 PM : [ 19 61 92 2] ST 0 Tue 09/17/2013 02:36:01 PM : [ 19 61 92 2] ST 255 Tue 09/17/2013 02:36:20 PM : [ 19 61 92 2] ST 0 Tue 09/17/2013 02:36:24 PM : [ 19 61 92 2] ST 255 Are these not the sensor status messages? I have to wonder if the OP is looking at relay status and not the sensor status. -Xathros

Have you tried LeeG's recommendation to test the IOLinc at the PLM location? If not, I think that is your best next move. From here on in, you should have the event viewer running at level 3 during your testing so we can have visibility to the communications between your PLM and the IOLinc. Open up the event viewer, set it to level 3 and cycle the IOLinc input a few times. Post the resulting trace. -Xathros

Very nice. Thanks for the data and your effort to gather it. After my recent round of battery replacements, I'm thinking it's time for some newer sensors. Most of mine are 4+ years old. -Xathros

Did you do a restore PLM after the factory reset? Have you tried a restore device on the IOLinc? -Xathros

JimsEvilTwin- The # in the alert variable need to be the Decimal value of the program ID. So, if the program you want the status of is ID: 000A then the variable should be: ${sys.program.10.status}. Leaving the '#' in the variable seems to be shorthand for ID of the calling program. -Xathros