MikeB

Actually, it's simpler than that. All that the ISY's "enable internet access" does is automatically create port forwards for you in your router, assuming your router supports UPnP. Since IPCOP doesn't support UPnP, you simply have to create a rule on IPCOP to forward port 443 (HTTPS) to your ISY's IP address (which you should make static). If you want/need HTTP access to the ISY as well, you would also forward port 80 - but be aware that HTTP is not encrypted. Once you create the rules in IPCOP, there's nothing further you have to do on the ISY. You don't need to use the "enable internet access" function. You should be able to leave it at those ports, unless you're already forwarding them to somewhere else on your LAN. I was running IPCOP for the longest time here, but don't currently have it running anywhere - so I can't help you with the details, sorry. If you haven't already, check out this forum: http://www.ipcops.com/phpbb3/ The guys there should be able to walk you through creating the needed rules if you're having issues.

I can confirm, unless something has changed in the past 6 months IPCOP doesn't support UPnP. You'll have to create a forward manually.

aanthony - If you had the ISY configured for a fixed IP address, consider changing your PC's IP address temporarily in order to telnet to the ISY. Go into your network properties, and change your PC's IP address to 192.168.0.99 or something similar. Then telnet in and change the ISY. Then change your PC back to a dynamic IP. Good luck!

I don't believe features of the newer KPLs are supported in this release. Please let Darrell or Michel confirm, but I think you'll need to upgrade to the beta firmware.

Sounds like your router might be turning off the UPNP forward to the ISY. You might want to manually create a port forward in your router instead.

I believe a v.2C KPL (as shown in the ISY) is v1.65.

We are happy to announce the availability of version 1.2.1 BETA of our NK8 and NK8-PC software, which is compatible with this firmware release. For more information, please check out our thread here: http://forum.universal-devices.com/viewtopic.php?t=1458

Time looks OK here in EST.

This seems to be fixed in v2.6.6.

As far as the ISY goes, only the SwitchLincs, OutletLincs, and LampLincs should be listed as members of the scene in the ISY. I have experienced odd RemoteLinc flashing issues in the past that I ended up attributing to a newer KPL I had installed. However, I no longer needed a RemoteLinc in that room and was never able to pinpoint the issue 100%. You might want to completely delete the scenes and RemoteLinc from the ISY, re-add it, recreate the scene, and add devices back in 1 at a time to see if you can narrow down what seems to cause the issue.

Typically flashing after a command is sent indicates that one or more devices did not respond to the command. I'm not aware of anything that defines specific errors based on # of flashes. One question for you - are any of the members of these scenes KeypadLincs? If so, what firmware version are they? Thanks

Thanks... I had a feeling that might be the case.

No problem. Please post back your experience!

I have a question. If the following program was running because, say, the thermostat had a temperature of 80 degrees: If Status 'Thermostat' > 78° (Temperature) Then Wait 5 minutes Set 'Thermostat' 75° (Cool Setpoint) Else - No Actions - (To add one, press 'Action') And 2 minutes into the WAIT command the temperature went up to 81 degrees, would the program restart itself and the 5 minute wait period? Or would it continue to run through the original 5 minute WAIT? Thanks!

Below are some programs I'm using to automate my office thermostat - I thought others might benefit. Please keep in mind that the current Insteon thermostat does not automatically inform the ISY of it's current status. For the ISY to have a reasonable idea of the thermostat's current temp, setpoint, mode, etc. it will need to be polled periodically. Below is my poll program, which runs all day (and the ISY is set to 'RUN AT STARTUP'): OFFICE THERMOSTAT QUERY If From 12:00:00AM For 24 hours Then Repeat Every 15 minutes Set 'OfficeThermostat' Query Else - No Actions - (To add one, press 'Action') To start, I wrote a few programs to get the overall status of my office. The first simply checks to see if the current day/time is within my normal work schedule. If it is, the program is true: OFFICE WORK HOURS If On Mon, Tue, Wed, Thu, Fri From 9:00:00AM To 5:00:00PM (same day) Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Unfortunately, I often need to put in late nights. To account for times I might be in the office outside of normal work hours, I also added this program to check the status of lights. If any of the lights in my office are on, this program is true: OFFICE LIGHT STATUS If Status 'OfficeLight1' is not Off Or Status 'OfficeLight2' is not Off Or Status 'OfficeLight3' is not Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Finally, I wrote a notification program to let me know if there are any extreme temperature situations that might indicate a heating/AC equipment failure. This will both email me and send a text message to my phone if either of the conditions is true. OFFICE SAFETY CHECK If Status 'OfficeThermostat' > 90° (Temperature) Or Status 'OfficeThermostat' < 60° (Temperature) Then Send Notification to All Else - No Actions - (To add one, press 'Action') I'm up here in New England, so my thermostat controls both a furnace (for the cooler moths) and a wholehouse AC (for the warmer months). My ideal goal is to simply leave the thermostat in COOL mode in the summer, and manually switch it to HEAT mode when I want to start using the heater, then manually back to COOL mode when I want to start using the AC again. I prefer to make that switch manually, but would like to automate the rest as much as possible. All programs check to see if the thermostat is in COOL or HEAT mode, so if I'd like I can switch the thermostat to OFF or one of the PROGRAM modes to avoid the automation I've setup on the ISY. The next program checks to see if the office lights are off and if the thermostat is in COOL mode. If they are, and it's outside of normal work hours, the program will increase the setpoint of the thermostat to save energy. I don't base vacancy only on status of lights, because there are times during the day that we might run out for a quick bite to eat or simply not need the lights on. But if the lights are ON, even after hours, I don't adjust the setpoint because we're clearly in the office working. I also include a 2 minute wait before adjusting the thermostat in case I'm working late and simply turned off the lights briefly for some reason. OFFICE COOL VACANT If Status 'OfficeThermostat' is Mode Cool And Program 'Office Work Hours' is False And Program 'Office Light Status' is False And Status 'OfficeThermostat' < 85° (Setpoint) Then Wait 2 minutes Set 'OfficeThermostat' 85° (Cool Setpoint) Else - No Actions - (To add one, press 'Action') For the cooler months when the thermostat is in HEAT mode, I have the following program: OFFICE HEAT VACANT If Status 'OfficeThermostat' is Mode Heat And Program 'Office Work Hours' is False And Program 'Office Light Status' is False And Status 'OfficeThermostat' > 65° (Setpoint) Then Wait 2 minutes Set 'OfficeThermostat' 65° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') For times I am IN the office, I want to make it a bit more comfortable. Notice that I'm only checking to see if the setpoint is at LEAST a certain value, so that in the winter I can manually set it a bit warmer if I want and in the summer maybe set it a bit cooler. But, these programs ensure that the temperature is at least reasonable: OFFICE COOL OCCUPIED If Status 'OfficeThermostat' is Mode Cool And ( Program 'Office Work Hours' is True Or Program 'Office Light Status' is True ) And Status 'OfficeThermostat' > 76° (Temperature) And Status 'OfficeThermostat' > 76° (Setpoint) Then Wait 2 minutes Set 'OfficeThermostat' 76° (Cool Setpoint) Else - No Actions - (To add one, press 'Action') Here is the HEAT version for cooler months: OFFICE HEAT OCCUPIED If Status 'OfficeThermostat' is Mode Heat And ( Program 'Office Work Hours' is True Or Program 'Office Light Status' is True ) And Status 'OfficeThermostat' < 68° (Temperature) And Status 'OfficeThermostat' < 68° (Setpoint) Then Wait 2 minutes Set 'OfficeThermostat' 68° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') I'd love to hear what others are doing with their thermostats!

Thanks Chris. Is this just a cosmetic issue, or will the programs actually run as displayed? Thanks!

For security, some people might want the ISY to notify you via email and/or text message if something unexpected happens while in 'vacation' mode. For example, a garage door opening. If your garage door is Insteon-enabled, you can use the ISY to notify you if it opens. For example: VACATION GARAGE NOTIFICATION If Status 'GarageInput1' is On Or Status 'GarageInput2' is On Then Send Notification to All Else - No Actions - (To add one, press 'Action') If your garage door is not Insteon-enabled, see this post for a solution: http://forum.universal-devices.com/view ... arage+door

I have some programs in a folder that disallows them from running unless a KPL button is ON. Even though the KPL button is OFF, these programs show a 'next scheduled run' in the Program Summary tab. Is this intended?

Makes perfect sense. The only thing I didn't like about my original program was that the amount of time between sunset and 10pm changes dramatically around here. I prefer fixing the time range with a FROM/TO instead. Thanks for the clarification!

Doh! I don't know what I was thinking, I've used the FROM/TO in that manner before. Thanks for the tip Chris! Based on Chris' FROM/TO tip, it might be cleaner to change the bathroom program to something like this: VACATION BATHROOM If From Sunset + 20 minutes To 10:00:00PM (same day) Then Repeat Every 1 hour Wait 45 minutes (Random) Set 'Bathroom' On Wait 10 minutes (Random) Set 'Bathroom' Off Else - No Actions - (To add one, press 'Action')

Thought I'd try to jump start this topic. I'd be interested to hear what others are using for 'vacation programs'. I'm thinking there would be at least 3 types of programs: - conserve energy (lower thermostats, etc.) - simulate occupancy (lights going on at random times, etc.) - security notifications (email based on unexpected activity, such as motion, door openings, etc.) For this post, I'll concentrate on randomizing some commonly used lights to simulate someone being home. Here is a program we might want to use for a young child's bedroom that typically goes to bed around 8pm: VACATION YOUNG CHILD BEDROOM If Time is 8:00:00PM Then Wait 10 minutes (Random) Set Scene 'ChildBedroomLamp' On Wait 10 minutes Wait 10 minutes (Random) Set Scene 'ChildBedroomLamp' Off Else - No Actions - (To add one, press 'Action') This would turn on the bedroom lamp between 8:00pm and 8:10pm, and turn it back off 10-20 minutes later. For an older child's bedroom or master bedroom, you might want to adjust the times and/or increase the wait time to simulate typical use. For a more lived-in room, such as a kitchen or living room, I'm using 2 separate programs since 'turn on' time is more related to sunset, but 'turn off' time is typically still related to time of day: VACATION KITCHEN ON If Time is Sunset + 20 minutes Then Wait 20 minutes (Random) Set Scene 'Kitchen' On Else - No Actions - (To add one, press 'Action') VACATION KITCHEN OFF If Time is 10:00:00PM Then Wait 20 minutes (Random) Set Scene 'Kitchen' Off Else - No Actions - (To add one, press 'Action') This would turn on the kitchen light between 20 and 40 minutes after sunset, and turn it back off between 10:00pm and 10:20pm. For a bathroom, you might want shorter duration spurts, like this: VACATION BATHROOM If Time is Sunset + 20 minutes Then Repeat 5 times (Random) Wait 1 hour (Random) Set 'BathroomLight' On Wait 10 minutes (Random) Set 'BathroomLight' Off Else - No Actions - (To add one, press 'Action') This would turn on the bathroom light between 20 and 80 minutes after sunset for between 1 and 10 minutes, then repeat up to 5 times randomly every 1-60 minutes. I'd love to hear what others are doing!

The ISY-26 requires an AC adapter to provide power to the unit. The ISY-99 still has the jack for an AC adapter, but power is typically provided to it by the PLM. Basically, plug the PLM into a wall outlet, and plug the ISY into the PLM using a standard Cat5 cable. That's it - no AC adapter needed.

WLAN would indicate Wireless Local Area Network, or the wireless portion of your router. WAN would indicate Wide Area Network, or the internet portion of the router.

Looks good here on an ISY-99.

Thanks Chris! Glad to learn something new. I went ahead and updated my initial post.