J_Barrett

@nathan No problem still exist

Hi Works nows Thanks

Hi I notice the same problem on 11-8-18. I had just up graded to 5.014 and figured the thermostats did not work in the alexa app any more due the 5.014 upgrade Jim Barrett

Hi I went from 4.7.3 to 5.0.14 straight. I have about 56 z-wave devices and 40 insteon just to be clear the close_wait can be reproduced on a ISY with no device installed Thanks Jim Barrett

Hi No software firewalls only hardware one built into router - no vpn or filtering software A little more info on this. I have 2 isy having the same issue. i took my second one and reset it wiping out the config and then down graded it to 4.7.3. No issues with close_waits then upgraded it to 5.04 - no issues with close_wait upgraded it to 5.08 - no issues with close_wait upgraded it to 5.09 - close_wait problem is back and the problem remains for 5.10 - 5.11c - 5.14 Any thoughts ? Thanks JIm Barrett

Hi All the time - it appears any communication between the console & the ISY opens up a new port for each thing it does Jim Barrett

Hi I am having the same problem [11/20 22:37:28.7] 3751742252 0 -170001 [HTTP:0-17-5] 192.168.1.2:56831->80 [11/20 22:37:28.7] [11/20 22:37:28.7] 3751742252 0 -170001 [HTTP:0-17]: POST[1]-->/services [11/20 22:37:28.7] [11/20 22:37:28.7] 3751742252 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u=" [11/20 22:37:28.9] [11/20 22:37:28.9] 3751742252 0 -170001 [HTTP:0-17-5] 192.168.1.2:56832->80 [11/20 22:37:28.9] [11/20 22:37:28.9] 3751742252 0 -170001 [HTTP:0-17]: POST[1]-->/services [11/20 22:37:28.9] [11/20 22:37:28.9] 3751742252 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u=" [11/20 22:37:29.2] [11/20 22:37:29.2] 3751742252 0 -170001 [HTTP:0-17-5] 192.168.1.2:56833->80 [11/20 22:37:29.2] [11/20 22:37:29.2] 3751742252 0 -170001 [HTTP:0-17]: POST[1]-->/services [11/20 22:37:29.2] [11/20 22:37:29.2] 3751742252 0 -170001 <s:Envelope><s:Body><u:GetSystemStatus xmlns:u=" Right now i show about 1100 ports in "Close Wait" between the ISY and the console Process Name Process Proto Local Local Address ID Port Port jp2launcher.exe 7064 TCP 54385 192.168.1.2 80 http 192.168.1.238 ISY Close Wait jp2launcher.exe 7064 TCP 54244 192.168.1.2 80 http 192.168.1.238 ISY Close Wait The console is only up about 20 minutes right now - If i let it sit over night it can consumes all the port and the console will lock up "showing socket open failed java.net.sockettimeoutexception" or java.net.SocketException: No buffer space (or some thing like that) and or the isy will crash. When i close down the console all the "Close Wait" will end. It seem any communication between the console & ISY opens up a new port. Healing the network really drive up the open ports i also tried it on 2 different machines running different versions of java Java (build 1.8.0_60-b27) 32 bit Java (build 1.8.0_191-b12) 64 bit i am using 5.0.14D & start.jnlp as the console Jim Barrett

Hi This may do what you want - PowerState Tail it plugs in between the pump and the wall outlet and give you a contact closure when the the pump turns on http://www.powerswitchtail.com/powerstate-tail

on Page 16 of 25 in the 2487S - manual it says Changing a KeypadLinc Button KeypadLinc buttons may be changed to customize appearance. Please use care – the button frame can be damaged and/or broken during this process. Using a small, slotted screwdriver (ONLY) pry up on the sides of the keys from the middle of the keypad (as shown). Make sure you are centered on the key as there is a small “lip” to pull up on located there. The large buttons have a small "lip" on the left and right side. Should any damage occur to KeypadLinc during customization, please contact the INSTEON Gold Support Line at 800-762-7845 and we will be happy to replace your frame. you might give them a call and see if they will send it for free

Blueman2 Thanks I got now, you alway update the skill with the info i was thinking that the skill requested the info from the the ISY. Make sense now thanks again

Blueman2 Thanks for the quick response. I got all that i built my skill - House Utterance - whats the temperature - did the network resource and sent it when i say alexa ask house what is the temperature it responds with the last word from the network resource sent. So it look like all that works thanks But can't figure out how to get the skill to run the program on ISY to call up the proper network resource to send when i give the invocation to Alexa Sorry if i'm being dense thanks

Blueman2 Could you explain how you got the skill to run the program on the ISY to send the response thanks

Hi "Your app works great and by the way it will turn on and off the zwave light & appliance modules as it is now". I sent Joe this yesterday, but I realized this morning that my Light and radio I was controlling was actually was actually Key 1 on 2 different 8 button insteon keypad that had nothing connected to the load. So when I turned on the light with Iggyhead remote button I was turning on the insteon button which ran and a program in ISY to turn on and off the the zwave outlet. My radio was set up the same way. So I just check changing the Iggyhead remote button to directly try and controlling the zwave outlet and it does not work. In fact if you pick a zwave module it won't let you save it. So sorry for the mix and confusion. So to sum it up it does not work with zwave right now. It only appeared to work for me because I was triggering a insteon device which in turn ran a program that turned on and off the zwave device. Again sorry if I inconvenienced any one

Hi Alex This my be a dumb question but you did disconnect the ELK RP software when done programing. When ELK RP is connected the M1 does not communicate with any thing else Does any of your other Elk function work on the ISY (arm disarm)

In the ElkRP2 terminal software under Automation/Outputs make sure the show box is check for the outputs you want the ISY to see and then resync the ISY to the Elk