ChrisMcA Posted January 20, 2022 Share Posted January 20, 2022 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 Link to comment
larryllix Posted January 20, 2022 Share Posted January 20, 2022 NRs can be a subscription paid service. Have yours expired? Maybe contact UDI with your UUID and check to see if the account is enabled correctly. Link to comment
lilyoyo1 Posted January 20, 2022 Share Posted January 20, 2022 I doubt it's a subscription since he's had it for 10 years. He may be using the portal now but he would've had to purchase the network module originally to use NRs for so long. One thing that stands out is your UI and firmware does not match. Clear your Java cake and use the launcher found on the 4.9 download page. Since the op doesn't say what his NRs are for, we can't really troubleshoot any further Link to comment
ChrisMcA Posted January 20, 2022 Author Share Posted January 20, 2022 @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. Link to comment
lilyoyo1 Posted January 20, 2022 Share Posted January 20, 2022 41 minutes ago, ChrisMcA said: @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. You don't have to pay for it again. The network module was a 1 time payment. If you don't have it separate from the portal then it's tied to your portal subscription. I don't use prowl so I don't know what it requires. Since you're using NRs with hue, if you run the THEN command of your program, does hue turn on? If not, verify that the IP address that's in your NR for hue matches what's in the hue bridge Link to comment
Javi Posted January 20, 2022 Share Posted January 20, 2022 Read file errors may be related to SD card failure, although you would likely see them when opening the Admin as well. Link to comment
larryllix Posted January 20, 2022 Share Posted January 20, 2022 @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.No. You wouldn't have to pay twice but it is always possible your ISY dropped the permission to use and UDI could renew it.Sent from my SM-G781W using Tapatalk Link to comment
lilyoyo1 Posted January 21, 2022 Share Posted January 21, 2022 6 hours ago, larryllix said: No. You wouldn't have to pay twice but it is always possible your ISY dropped the permission to use and UDI could renew it. Sent from my SM-G781W using Tapatalk His issue has nothing to do with his portal subscription. He already stated that he purchased the network module previously, outside of his portal subscription. Link to comment
MikeD Posted January 21, 2022 Share Posted January 21, 2022 I seem to have the same problem with PROWL. My last Prowl notification was on 1/14/2022. ISY-994 running v4.7.3. *NOTE: Network Resources sent within my LAN function normally. Only the PROWL notifications produce an error. Link to comment
ChrisMcA Posted January 21, 2022 Author Share Posted January 21, 2022 53 minutes ago, MikeD said: I seem to have the same problem with PROWL. My last Prowl notification was on 1/14/2022. ISY-994 running v4.7.3. *NOTE: Network Resources sent within my LAN function normally. Only the PROWL notifications produce an error. 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. Link to comment
MikeD Posted January 21, 2022 Share Posted January 21, 2022 I only received the above error once. The second time I tried to test a Prowl network resource I received a different error message, something like DNS server not found I think. Every subsequent test resulted in an “n/a” error response. I rebooted my ISY just to eliminate the possibility of something hung. My ISY rebooted normally without errors, so I doubt it is a corrupted memory card. I would think we would see a different symptom if Prowl terminated their service. Don’t know what the issue could be. Maybe someone here has an idea. Link to comment
JimWeith Posted January 23, 2022 Share Posted January 23, 2022 I am having the same issue. I've managed to get both Pushover and Pushsafer to work but prefer Prowl. Especially since I have numerous notifies setup already. I'm wondering what router everyone with a problem is using? I'm using a Unifi UDM. I have also emailed Prowl support and am waiting to hear back. Will let you know what their response is. Link to comment
Michel Kohanim Posted January 24, 2022 Share Posted January 24, 2022 Please upgrade to 4.9 or 5.3.4 and make sure you check the SNI checkbox. With kind regards, Michel Link to comment
ChrisMcA Posted January 25, 2022 Author Share Posted January 25, 2022 23 hours ago, Michel Kohanim said: Please upgrade to 4.9 or 5.3.4 and make sure you check the SNI checkbox. With kind regards, Michel 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. Link to comment
drprm1 Posted February 1, 2022 Share Posted February 1, 2022 On 1/23/2022 at 10:22 PM, Michel Kohanim said: Please upgrade to 4.9 or 5.3.4 and make sure you check the SNI checkbox. With kind regards, Michel Just realized that all my Prowl NR aren't working either (all others are fine) Any update on getting this working? I too have used Prowl with no problems for years and it recently stopped. My UI and firmware are both 5.1.0 (Rather not upgrade to 5.3.4 or higher because I still use the 300 board which works with my Schlage locks) I have a relatively new SD card... Tried generating a new Prowl api key but the test nr still didnt work Thanks! Link to comment
Michel Kohanim Posted February 2, 2022 Share Posted February 2, 2022 @drprm1, Please upgrade to 5.3.4. With kind regards, Michel Link to comment
drprm1 Posted February 2, 2022 Share Posted February 2, 2022 I normally upgrade and update whenever its available but have hesitated because my Schlage locks didn't work with the 500 board. I realized this when on 5.1.0 and downgraded back to the 300 board... I know someone will say 300 won't work with 5.1.0 but it has and has been problem free since i changed....until now with the Prowl issue. If upgrading to 5.3.4 is the only way to make it work I assume something changed on Prowls end making it incompatible with previous versions???? Link to comment
MikeD Posted February 3, 2022 Share Posted February 3, 2022 I just updated to v4.9.0 and still have this error when attempting to send a push notification to Prowl. Link to comment
drprm1 Posted February 3, 2022 Share Posted February 3, 2022 Solid system 5.1.0.....Would like Prowl notifications to work again so updated to 5.3.4 and checked SNI box. I now have system with many extra nodes, many missing nodes, and programs which won't run. (Haven't checked yet for scene adjustment problems) I’ve had to redo everything and find problems before. Just rather not….. Oh and Prowl notifications still don't work....Awesome! Link to comment
sjenkins Posted February 3, 2022 Share Posted February 3, 2022 Just realized that all my Prowl NR aren't working either (all others are fine) Any update on getting this working? I too have used Prowl with no problems for years and it recently stopped. My UI and firmware are both 5.1.0 (Rather not upgrade to 5.3.4 or higher because I still use the 300 board which works with my Schlage locks) I have a relatively new SD card... Tried generating a new Prowl api key but the test nr still didnt work Thanks!I had this same issues. I have about a hundred prowl NR’s. As per [mention]Michel Kohanim [/mention] If you update and click the sni box it will work. Sent from my iPhone using Tapatalk Link to comment
drprm1 Posted February 3, 2022 Share Posted February 3, 2022 Thanks but it doesn’t work in my case. Link to comment
Michel Kohanim Posted February 4, 2022 Share Posted February 4, 2022 @drprm1, SNI must be checked AND you need to increase your timeout. With kind regards, Michel Link to comment
drprm1 Posted February 4, 2022 Share Posted February 4, 2022 9 hours ago, Michel Kohanim said: @drprm1, SNI must be checked AND you need to increase your timeout. With kind regards, Michel Thanks for suggestion SNI is checked AND my timeout is 2000 as per wiki. I’ve tried changing a test NR timeout sequentially higher with no luck Link to comment
Michel Kohanim Posted February 6, 2022 Share Posted February 6, 2022 @drprm1, Did you try 10000? Also, the error means that the server is returning 401 which means it does not like your credentials. With kind regards, Michel Link to comment
drprm1 Posted February 6, 2022 Share Posted February 6, 2022 Don’t remember if I tried that long of a time out. My credentials didn’t change. Checked with Prowl. Just finished switching all over to Pushover. Thanks Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.