Tominnh Posted December 28, 2019 Share Posted December 28, 2019 I manually updated the firmware of my ISY to the required 5.0.16B firmware/ That process went fine. When I first connected Polisy it could not locate the ISY and kept beeping. At this time the left light is on and Polisy shows connected to my router however with no TX or RX data showing. I cannot log into it wither by IP address or through https://polisy I remain stuck at this point of being able to access anything. Suggestions? DHCP is enabled. Link to comment Share on other sites More sharing options...
oberkc Posted December 28, 2019 Share Posted December 28, 2019 Same here so far. My router shows it connected, but trying that address results in the same thing: nothing. I will let you know if I find a solution. I hope this is not one of those apple and safari things. Link to comment Share on other sites More sharing options...
asbril Posted December 28, 2019 Share Posted December 28, 2019 28 minutes ago, oberkc said: I hope this is not one of those apple and safari things. I use both Windows 10 and Mac computers, and I can access Polisy on either. However you may need to clear your browser's cache. Link to comment Share on other sites More sharing options...
simplextech Posted December 28, 2019 Share Posted December 28, 2019 What is the full URL that you have been trying? If you have the IP Address have you tried using that? Have you tried with the longer named convention of "polisy.local"? Link to comment Share on other sites More sharing options...
oberkc Posted December 29, 2019 Share Posted December 29, 2019 "Polisy.local" does not work (or I am missing something). Neither does HTTPS://polisy.local. I tried http://192.168.0.48. This did not work. I finally tried https://192.168.0.48. This worked, but only on firefox. Safari and chrome continue to resist my efforts. Clearing the cache did not change this. Link to comment Share on other sites More sharing options...
larryllix Posted December 29, 2019 Share Posted December 29, 2019 1 hour ago, oberkc said: "Polisy.local" does not work (or I am missing something). Neither does HTTPS://polisy.local. I tried http://192.168.0.48. This did not work. I finally tried https://192.168.0.48. This worked, but only on firefox. Safari and chrome continue to resist my efforts. Clearing the cache did not change this. https://192.168.xx.yy assumes port 443 but my polyglot would never accept https://192.168.xx.yy:443 for some reason. I have to ignore and bypass all the security warnings every time until I found how to use http only. I may have to undo that due to polyglot v2.2.6 confusing the ISY comms with the admin comm access now. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted December 29, 2019 Share Posted December 29, 2019 Hello all, It seems that we can never run away from cache! It used to be Java cache and now it's browser cache especially if you had accessed Polyglot on your computer. It's best to clear your browser's cache. With kind regards, Michel Link to comment Share on other sites More sharing options...
AnthemAVM Posted January 1, 2020 Share Posted January 1, 2020 On 12/28/2019 at 1:19 PM, Tominnh said: I manually updated the firmware of my ISY to the required 5.0.16B firmware/ That process went fine. When I first connected Polisy it could not locate the ISY and kept beeping. At this time the left light is on and Polisy shows connected to my router however with no TX or RX data showing. I cannot log into it wither by IP address or through https://polisy I remain stuck at this point of being able to access anything. Suggestions? DHCP is enabled. Hello, I have installed my Polisy today and am not able to gain access. I can see it on my router and its IP address, but neither work. I cleared cache on Edge and no change. Any suggestions would be greatly appreciated. I did put a ticket in with UD, but was hoping to look around on my day off. Thanks Link to comment Share on other sites More sharing options...
DennisC Posted January 1, 2020 Share Posted January 1, 2020 Are you using https://xxx.xxx.x.xxx? If that doesn't work, try adding ":443" after the IP address. Link to comment Share on other sites More sharing options...
4481hoods Posted January 1, 2020 Share Posted January 1, 2020 Members 2 11 posts Report post Posted December 31, 2019 (edited) I also had trouble connecting with any browser. If your unit has WIFI try the following: Discovered open WIFI ports are not compatible with polisy. Removed WIFI card from polisy and all works well. Waiting for a fix! don't really need WIFI I have a wired connection. Conclusion WIFI at this point is a problem! Link to comment Share on other sites More sharing options...
AnthemAVM Posted January 1, 2020 Share Posted January 1, 2020 50 minutes ago, 4481hoods said: Members 2 11 posts Report post Posted December 31, 2019 (edited) I also had trouble connecting with any browser. If your unit has WIFI try the following: Discovered open WIFI ports are not compatible with polisy. Removed WIFI card from polisy and all works well. Waiting for a fix! don't really need WIFI I have a wired connection. Conclusion WIFI at this point is a problem! Thanks, I was able to get in via the direct IP address, but https://polisy doesn't work. Link to comment Share on other sites More sharing options...
Tominnh Posted January 1, 2020 Author Share Posted January 1, 2020 I opened A ticket and Michel was quickly able to do a remote session and resolve the issue! Link to comment Share on other sites More sharing options...
MWareman Posted January 6, 2020 Share Posted January 6, 2020 Hello all, It seems that we can never run away from cache! It used to be Java cache and now it's browser cache especially if you had accessed Polyglot on your computer. It's best to clear your browser's cache. With kind regards, Michel You can quickly test for a cache issue by testing with an Incognito or in-private browser instance.... If it fails in a new private session it’s not a cache issue... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.