ChrisMcA

I have upgraded to 4.9 and have the SNI box checked but I am still getting the same errors which are captured in the attached screen shot. I have tried it with and without the encode URL and SNI enabled. A bit of good news, I was able to get my Pushover notifications and my Philips Hue working again again. All it took was manually upgrading to 4.9. Note, first thing I did when I noticed these issues was upgrade from 4.8 to 4.9, but I used the auto upgrade tool. I have not been able to get my Yamaha and Onkyo receivers to work, but I haven't troubleshot them enough to say what the issue is yet. My Onkyo is not liking whatever I am sending it. A simple query or on/off command from the ISY locks the receiver up for an hour or more. It wont respond to any network devices including the Onkyo app. Unplugging the receiver is the quickest fix. Both of the receivers worked previously but its been several years since I have used the network resources with these receivers to say its an ISY issue. I have attached a screen shot of my Prowl message setup. Any input you all could lend would be greatly appreciated.

Well this is curious. So it might be tied to the Prowl notifications after all. I will say that I still cant run very simple network resources like turning on my Yamaha AVR. Everything I try outside of the Prowl notifications just gives the same n/a in the response window, the event viewer says failed to open.

@larryllix and @lilyoyo1, thanks for the replies. I will try clearing the Java files and use the new launcher, but as I mentioned, this was an issue prior to upgrading the f/w to V4.9. Also, I originally purchased the networking module before it became a subscription based item. If I suddenly have to pay for it again, that's news to me. The only feedback I get from the admin console regarding my modules is that they are up to date. I use the networking resources for various things but the main one is for Prowl push notifications. My networking resources issue happened coincidentally around the same time Prowl reported some overnight issues with their server. Initially I thought the problem was with Prowl so I ignored it, but several days later I finally got around to testing it and discovered it was the ISY and not Prowl. I have tested several other Items that I know should work. I even tried ones that are internal to my home network like my AVR or Philips Hue but everything I test generates the same failed response prompt and "n/a" in the response window. I can confirm that Prowl is back up and working because I have successfully generated Prowl push notifications from my PC. There isn't anything that has changed with my keys and Prowl API appears to be the same.

My network resources stopped working all together a little less than a week ago. I was running 4.8 when it stopped working so I upgraded to 4.9 thinking that might help, but no luck. This is the error I get when I run a test for the first time, the following tests will just show n/a in the response window or come up with a request failed prompt. I skimmed through the forums to see if there was a certificate or security issue that I would have to address but didn't see anything. As far as I know my modules are up to date, portal access shows online and registered and and I can view my ISY through the portal. Everything else is working fine so I don't think it would be a PLM issue. I tired enabling the internet assess from the admin console to see if that had anything to do with it but I get a failed message. I did notice that the firmware version and UI version are different, not sure if that's an issue, but this problem started when I was running 4.8.X. My ISY has been running for nearly 10 years but sadly I have not spent much time playing with it the last 5 years. I have a Savant system that is slowly replacing the ISY, but the ISY still has its place in my house. I have wanted an excuse to upgrade to firmware 5 and try out some of the node servers, this may be my excuse, but first I need to get my push notifications working again from the network module. Any input you all could offer regarding my issue would be appreciated. Thanks, Chris

When I was troubleshooting this morning none of the devices were responsive. The set LED on the PLM was red. I power cycled the PLM and the LED returned to green. The PLM links table was empty. When I ran a restore on the PLM everything returned to normal. Sounds like I need a new PLM?

This morning I noticed that my motion and contact sensor devices were not changing state. My motions were still blinking however the ISY was not registering it. Upon further investigation the ISY was also not seeing the local status change in my dual ban devices like my switches. I can control the devices through the ISY and the status will show correctly in the ISY however only if I operate from ISY. Does this mean that my PLM is possibly on the way out? I have updated the firmware to 4.2.30 and still the same troubles. I have power cycled my PLM. The event viewer only shows Insteon traffic when I operate the device from the ISY. It does however show the two way communication of operation being sent and ack being received. My PLM is a 2413S V1.6. I was going to try the restore PLM step next but was going to see if there are any other steps I should try first. Thanks, Chris

I followed the Wiki for adding the WeatherBug station via my zip code however the Chose Area box never populates regardless of the zip code or city name I type in the Find field. I tried clearing the Java Cache and upgraded to v.4.1.2 but that didn’t help. I can enter a few station names into the Location ID field and it will retrieve the station info however the data appears to be stagnate.