LeeG

The ISY does not yet support using the Scene name such that some of the Responder KPL buttons will turn Off with a Scene On. Where multiple KPLs are being using if the KPL firmware is v.40 or later than the buttons on either KPL will works as you want when operated from either KPL. They will not operate as desired if using the Scene name for the reason stated above. If the KPL firmware is below v.40 then ISY Programs triggered from KPL button press which turn Scenes Off which have the Responder KPL buttons that should turn Off must be used.

The port forward LAN IP address should be that of the ISY LAN IP ADDRESS: 11.222.33.444 (same IP as above Modem IP Address) - should be the ISY IP When the Modem receives a message from the outside world using the WAN address:port it looks at the port number on the inbound message. If the port has been forwarded the modem will route the inbound message from the outside world using the WAN address:port to the LAN IP:port address defined in the port forward which would be the ISY LAN address.

It is forwarded to the ISY IP address rather than the PC address.

The Internet modem has an external WAN IP address that is used to access the modem from the outside world. That external WAN IP address is not 192.168.xxx.xxxx anything. All the addresses posted (do not post your WAN IP address) are internal LAN IP addresses which are on your local LAN. No IP address on the local LAN can be seen by the outside world. There are literally hundreds of thousands of folks using some combination of 192.168.xxx xxxx as local LAN IP addresses. Logon to the modem/router. There will an option to display the WAN IP address. Use that WAN IP address plus the port number you forwarded to the ISY to access the ISY from the outside world. For example, https://111.222.3.444:443 Obviously a made up IP address which is expecting port 443 to be forwarded to the ISY. Substitute your WAN IP address and whatever port number you forwarded to the ISY.

Duplicate post. See viewtopic.php?f=27&t=9192

Dim lowers the On Level about 3% (from memory) for each Dim command issued. Not many devices can issue a Dim/Bright command. RemoteLinc is one that can as it has specific Dim/Bright buttons. When a button/paddle is pressed and held, a Start Manual Change (Up or Down) command is sent to the Responder(s) to begin a Ramp Up or Ramp Down. The ISY Program equivalent is Fade Up or Fade Down. When the button/paddle is released a Stop Manual Change command is sent to the Responder(s) to stop the Ramp Up or Ramp Down. The ISY Program equivalent is Fade Stop. The Insteon device hardware/firmware sends one Start Manual Change when the button/paddle is pressed and held and sends one Stop Manual Change when the button/paddle is released. The Program would have to Repeat the Network Resource until the Fade Stop is received.

Firmware cannot be up graded or downgraded.

What we are looking for is why are some of the nodes in the My Lighting tree (not in Scenes) in Italics. The OP system is Java 7 which may have some relation to the question.

The last time someone posted that error it was caused by adding the device, not waiting for the add to complete, rebooting ISY. There is a post in the last few weeks that Michel did with a telnet command to get rid of the device record if the device Insteon address is not already known to the ISY. Michel suggested clicking My Lighting, sorting on the address column to see if the address already exists. Here is the link to the topic. About the 9th post into the topic from Michel. viewtopic.php?f=28&t=9037&hilit=%2Fconf%2F

Unless you configured the ISY for a static IP it is using the router DHCP to get the IP address. If the IP address changes it is the router doing it. The Router can be configured for a static IP. The Wiki has some instructions if that is not a familiar process. The ISY configuration also has to change to define the static IP rather than use DHCP.

No, not programmatically.

I've been using KeypadLincs in the house since 2006, with the ISY for going on 4 years. About 12 between the house and detached garage with several more in the test bed. Can't think of any reason not to use them. Like most Insteon devices the firmware has evolved over the last 7 years or so. Some firmware issues have surfaced and been resolved. They have not been plagued by the tact switch problem associated with the SwitchLincs years past. The choice between 6 and 8 button is how many different Scenes will be controlled and preference for button layout. KeypadLincs can be changed from 6 to 8 button or 8 to 6 button in the field.

I missed your point. Yes, that node is a Responder Only.

No Ifs in the Then Clause. A Program could loop (Repeat) calling a Program every 15 minutes which checks the temperature and changes the set point but the temperature values would be fixed. If/When variables can be set with device information such as temperature and the value in the Set Point change statement can be a variable that is incremented, then something like you are thinking about is possible. Until then it is absolute temperature checks and absolute set point changes.

It means the node is a Responder to the Scene. A SwitchLinc, which is a Controller/Responder, can be assigned to a Scene as a Responder. When defined as a Responder the SwitchLinc does not function as a Controller for the Scene even though the SwitchLinc has Controller capability. The posted image has no Scenes listed under "Is Responder to".

I see "Is Responder to" and "Is Controller for".

Specific temporatures can be checked as well as ranges by combining checks with an And. If Status 'T2491T1E - Main' <= 65° (Temperature) Then Set 'T2491T1E - Main' 65° (Heat Setpoint) Wait 10 minutes Set 'T2491T1E - Main' 67° (Heat Setpoint) If Status 'T2491T1E - Main' >= 65° (Temperature) And Status 'T2491T1E - Main' <= 75° (Temperature) Then Set 'T2491T1E - Main' 65° (Heat Setpoint) Wait 10 minutes Set 'T2491T1E - Main' 67° (Heat Setpoint)

Membership shows the Scenes if any the node is associated as a Responder or as a Controller. I do not have the words "responder to". What level ISY firmware is being used? If 3.2.6 run Help | About and verify Firmware and UI lines both say 3.2.6.

I see that Landscape Lights are not Italics, Fish Pump is Italics. Also the Primary KeypadLinc node of Upstairs - Main is not in Italics, Downstairs - Main is. Also the Primary Nodes are Blue which would indicate a Responder only which they are not. Abscent other information I take this to be an issue with Java 7.

I am running Java 6 as there were problems with Java 7. In the case of the selected item the Italics give it some additional visual difference. The Italics have no meaning to the ISY.

What operating system and what level Java? As you can see below my Nodes are not in Italics. I suspect a difference in Java level.

If the load is connected to the 2477D Dimmer in one room and connected to the 2487S Relay in the other room the results will be as described.

The Scene name can be used in ISY Programs and the Scene can be turned On/Off with the Admin Console. The Controller is the ISY PLM. As was noted each Controller can establish a unique set of Responder values for On Level and Ramp Rate. The On Level and Ramp Rate values are stored in each Responder keyed to the Controller Insteon address.

Post an image of the Italics in the main Node area. Include all the nodes for the device in question as well as a few nodes before and after.

Assuming the variable started with a value of 0, the following Program at 1 minute past midnight today (Thursday) changed the variable value to 1. That made today a non-cleaning day. If On Thu at 12:00:01AM And $Every.Other.Thursday is 0 Then $Every.Other.Thursday = 1 init $Every.Other.Thursday = 1 Else $Every.Other.Thursday = 0 init $Every.Other.Thursday = 0