Polisy has arrived however I cannot connect. RESOLVED

[Tominnh]

I was able to get the beeping to stop after updating my ISY Firmware. It took many tries to connect through the browser but finally did with Firefox then Chrome. There were 14 updates for the device which stated that they were sent to the device but not installed. After quite a while a popup appeared stating updates were applied and zero left to install. 

Due to the random beeping that kept going on from time to time I powered it off for the night. Restarted this morning and I'm back to square one with no access. 

Not at all what I expected to be dealing with to get this device operational. Today after hours of attempts i'm again pulling the plug until I get answers.

More than a bit frustrated.  

 

[telljcl]

Similar issues here.

I still cannot connect using my PC / Chrome or Edge browser.

Only way I was ever able to connect was using my Android phone / Chrome.

Once connected using my phone, Polisy said ISY could not be found (it's on the same network - nothing complicated...)

I put in ISY ip, port and it found it after a reboot.

Updated a bunch of stuff - like you did - it finally said no updates. 

I tried setting a static ip but then couldn't connect in any way. Used paper clip to reset, still couldn't connect in any way. Pulled power, pressed in reset button with paper clip, then held button in while plugging in power cable and it appeared to reset again. Can once again access via phone only...

I'm not sure what Polisy is going to do for me short term, but assumed that this is likely the future of ISY and I've got a fair amount of stuff tied to it and it's programs, so ordered one.

This initial experience does not bode well however - NOTHING worked as stated in the minimal "quick start" sheet enclosed...

EDIT: My ISY was on 5.14 FW - just updated to 5.16B...

 

[randyth]

FWIW, with my Windows PC I can log in with Edge (yuck) but not Chrome.  With Chrome I get an ERR_CONNECTION_REFUSED error.

-Randy

[telljcl]

14 minutes ago, randyth said:

FWIW, with my Windows PC I can log in with Edge (yuck) but not Chrome.  With Chrome I get an ERR_CONNECTION_REFUSED error.

-Randy

Can't log in with Edge or Chrome. Are you using "https://polisy" or are you typing in the ip address?

I get a "Refused to connect" if I try the ip address, and a can't find host... if I try "https://polisy"

My router shows the entry, the ip address, and that it is "polisy" but can only connect with my phone's Chrome browser using "https://polisy"

[drprm1]

Got all the connection issues too. Used putty to hookup to it and did the things according to wiki “latest packages not installed” and “corrupt database”. Was able to connect to it after this and been working fine.

Don’t know if this affected anything but at first I tried to simply restore it using a backup from my Rpi and that’s when I got problems. Ended up deleting the node servers in AC then reset Polisy then used ssh utility to install packages and reset database...Then installed node servers. Been perfect since..

[Tominnh]

I have tried everything and am getting nowhere. I did have access last night. Powered it off being afraid that it would start beeping again. This morning I plugged it back in and NOTHING. Beeping then connects to the router and that's the end of it. Cannot access by any browser PC, or phone.  I have goven up for the night and pulling the plug!

[drprm1]

Drove me nuts too. Have you tried ssh as per Polisy instructions?

[dbuss]

I too had the same issues. Have you tried clearing your browser cache? Have you tried 192.168.x.xxx:443?

[mwester]

At the risk of offering a suggestion that might be akin to the famous help-line "Is your computer plugged into the wall?"...

Modern browsers are entirely too "helpful" for their own good -- the address bar into which one types "192.168.xx.yyy" is not actually an address bar anymore, it's now a search bar.  Meaning that if you don't type a local network address EXACTLY RIGHT, the browser is going to take what you typed, feed it to google or bing, and see what comes up in that search.  That's fine when I mistype "weather.com" because that site is public knowledge and thus the search engine can easily figure out "what I meant" -- which is probably why this mutation occurred in browsers.  However, it sucks for local addresses, because neither google nor bing know about my particular "polisy", so they generally get the wrong answer, and make me angry.

One can often fix this by being utterly pedantic with the address:  it's not "polisy", or "192.168.1.32", instead try the fully-formed, fully-qualified form:  "https://polisy/"  or "https://192.168.1.32/"  -- generally, your browser should recognize that and do the "right thing".

A word on the "polisy" address thing -- at boot, the hardware will ask for an IP, and offer it's host name to the router.  The router may or may not do something with the host name - many older or cheaper (or new-but-buggy for that matter) routers don't support local host naming.  But even if your router does, that doesn't mean that you can use the name "polisy" on your network!  The question is if your local browser's device (tablet, phone, laptop, whatever) is actually using your router for name resolution.  I've seen many cases where the user has followed some instructions, for example, to set up their PC to use Google's DNS server (8.8.8.8) or the quad-9 servers (9.9.9.9) -- and in these cases, the PC won't be asking the router about "polisy", rather the PC will send the name "polisy" to Google or Quad-9, both of which will dutifully respond with either "we don't know this one", or worse, they might actually provide someone else's IP address for some server somewhere named "polisy"... doubtful, but the fact remains that if this is the case, what you won't get back is the actual address of YOUR polisy!

So, in a nutshell, if you're troubleshooting connectivity issues, use the IP addresses, not the names.  Names can be sorted later.

(Finally, a sanity-saving suggestion: restore your Google Chrome address bar to it's proper function by defining your own dummy search engine!  Click on the three dots on the upper right and open up "Settings".  Scroll down to "Search engine",  and click on the arrow to expand the "Manage search engines" section.  In that section, click the "Add" button.  In the dialog that appears, enter "None" for the Search engine name, enter "none" for the Keyword, and enter just %s for the URL, and then click Add.  You'll see your new "dummy" search engine in the list -- click on the three dots beside it, and select "Set Default".   Congratulations -- now whatever you key into your address bar is an address, nothing more.  The Universe rejoices in the small amount of sanity that you've just brought back... )

 

[drprm1]

Showed on my router that polisy was connected  and I used  https://polisy and https://192.168.xxx.yyy on edge, chrome,ie,Firefox with no joy.  Now I’m not real savvy about all this and  tried for a full day, trying different things and it finally worked after resetting polisy and using putty to redo a couple of things. Seems a bit more than being “my computer being plugged in” ?

(at least for me anyway)

[telljcl]

47 minutes ago, mwester said:

At the risk of offering a suggestion that might be akin to the famous help-line "Is your computer plugged into the wall?"...

Modern browsers are entirely too "helpful" for their own good -- the address bar into which one types "192.168.xx.yyy" is not actually an address bar anymore, it's now a search bar.  Meaning that if you don't type a local network address EXACTLY RIGHT, the browser is going to take what you typed, feed it to google or bing, and see what comes up in that search.  That's fine when I mistype "weather.com" because that site is public knowledge and thus the search engine can easily figure out "what I meant" -- which is probably why this mutation occurred in browsers.  However, it sucks for local addresses, because neither google nor bing know about my particular "polisy", so they generally get the wrong answer, and make me angry.

One can often fix this by being utterly pedantic with the address:  it's not "polisy", or "192.168.1.32", instead try the fully-formed, fully-qualified form:  "https://polisy/"  or "https://192.168.1.32/"  -- generally, your browser should recognize that and do the "right thing".

A word on the "polisy" address thing -- at boot, the hardware will ask for an IP, and offer it's host name to the router.  The router may or may not do something with the host name - many older or cheaper (or new-but-buggy for that matter) routers don't support local host naming.  But even if your router does, that doesn't mean that you can use the name "polisy" on your network!  The question is if your local browser's device (tablet, phone, laptop, whatever) is actually using your router for name resolution.  I've seen many cases where the user has followed some instructions, for example, to set up their PC to use Google's DNS server (8.8.8.8) or the quad-9 servers (9.9.9.9) -- and in these cases, the PC won't be asking the router about "polisy", rather the PC will send the name "polisy" to Google or Quad-9, both of which will dutifully respond with either "we don't know this one", or worse, they might actually provide someone else's IP address for some server somewhere named "polisy"... doubtful, but the fact remains that if this is the case, what you won't get back is the actual address of YOUR polisy!

So, in a nutshell, if you're troubleshooting connectivity issues, use the IP addresses, not the names.  Names can be sorted later.

(Finally, a sanity-saving suggestion: restore your Google Chrome address bar to it's proper function by defining your own dummy search engine!  Click on the three dots on the upper right and open up "Settings".  Scroll down to "Search engine",  and click on the arrow to expand the "Manage search engines" section.  In that section, click the "Add" button.  In the dialog that appears, enter "None" for the Search engine name, enter "none" for the Keyword, and enter just %s for the URL, and then click Add.  You'll see your new "dummy" search engine in the list -- click on the three dots beside it, and select "Set Default".   Congratulations -- now whatever you key into your address bar is an address, nothing more.  The Universe rejoices in the small amount of sanity that you've just brought back... )

 

All good reminders - thanks.

Can the Polisy not be accessed by using the IP address? I don't know what port it uses (apparently not 80...) as I've been unable to use its IP address to get in.

Thanks

 

[telljcl]

3 minutes ago, drprm1 said:

Showed on my router that polisy was connected  and I used  https://polisy and https://192.168.xxx.yyy on edge, chrome,ie,Firefox with no joy.  Now I’m not real savvy about all this and  tried for a full day, trying different things and it finally worked after resetting polisy and using putty to redo a couple of things. Seems a bit more than being “my computer being plugged in” ?

(at least for me anyway)

What is putty and what are the "couple of things" you did? 

My phone's chrome browser access it just fine by just putting "polisy" in the address bar. My PC? Forget it with chrome or edge...

[drprm1]

Not sure if this was what helped but if you read the polisy wiki it says how to stop the beeping by using ssh (putty) to connect to it and redo the corrupt database. Now (in my case) I did this and was able to immediately connect. I changed the port from 443 to 3000 and from then on ive had no connection problems.

Not sure why this worked but it did.

[telljcl]

7 minutes ago, drprm1 said:

Not sure if this was what helped but if you read the polisy wiki it says how to stop the beeping by using ssh (putty) to connect to it and redo the corrupt database. Now (in my case) I did this and was able to immediately connect. I changed the port from 443 to 3000 and from then on ive had no connection problems.

Not sure why this worked but it did.

I never had the constant beeping issue - only connection issues. Should it be possible to log into Polisy using the IP address / port and not the Naming approach?

[mwester]

47 minutes ago, telljcl said:

All good reminders - thanks.

Can the Polisy not be accessed by using the IP address? I don't know what port it uses (apparently not 80...) as I've been unable to use its IP address to get in.

Thanks

 

If it's reasonably recent, it uses "https" on the default port (443).  There's nobody home at the "http" port (port 80).  You might also try "https" with port 3000.  And yes, you SHOULD use the IP address, and NOT the name, at least until you've ascertained that it works with the IP address.  (If you use the "polisy" name, the browser needs to look that up and translate it to the IP address -- so if you're having trouble, it makes good sense to just provide the known good IP address in the first place, and eliminate one potential source of problems.)

[telljcl]

4 minutes ago, mwester said:

If it's reasonably recent, it uses "https" on the default port (443).  There's nobody home at the "http" port (port 80).  You might also try "https" with port 3000.  And yes, you SHOULD use the IP address, and NOT the name, at least until you've ascertained that it works with the IP address.  (If you use the "polisy" name, the browser needs to look that up and translate it to the IP address -- so if you're having trouble, it makes good sense to just provide the known good IP address in the first place, and eliminate one potential source of problems.)

That's what I did before ever trying the name - like you said, one more thing that likely won't work. But it never connected with the ip address, only with the phone using "polisy".

Now however, I can't even get into it with the phone  - and have reset Polisy numerous times. 

Polisy shows up in my router's IP table, but I can't get to it using that IP --> 192.168.xxx.yyy:443

[larryllix]

2 hours ago, telljcl said:

That's what I did before ever trying the name - like you said, one more thing that likely won't work. But it never connected with the ip address, only with the phone using "polisy".

Now however, I can't even get into it with the phone  - and have reset Polisy numerous times. 

Polisy shows up in my router's IP table, but I can't get to it using that IP --> 192.168.xxx.yyy:443

Need https://192.168.xx.yy:443  IIRC :433 wasn't needed or it wouldn't work when I used it but the https was required. You may have to bypass all the security warnings in your browser. There are no certs.

[telljcl]

8 hours ago, larryllix said:

Need https://192.168.xx.yy:443  IIRC :433 wasn't needed or it wouldn't work when I used it but the https was required. You may have to bypass all the security warnings in your browser. There are no certs.

Got the cert warning in the Android Chrome browser - no warnings, no nothing in Windows 10 Chrome (latest build). Just no connection.

EDIT:  using the "https://" is definitely a requirement in my case - it works now with the IP address where it didn't w/out the https:// prefix.

Thanks for that.

 

 

[Tominnh]

15 hours ago, drprm1 said:

Drove me nuts too. Have you tried ssh as per Polisy instructions?

ssh ?  What do you mean by ssh? 

[Tominnh]

I installed Putty and ran ssh commands as listed in WIKI. Polisy beeped. Still no change and no access to device. I am about ready tp pack it back in the box and ship it back!

[TexMike]

ssh is secure shell to connect to UNIX command line. Recommend not to use it unless you know what you are doing.

For static IP,  it's much better to reserve the static IP on the router instead of manually configuring Polisy. The MAC address is on a sticker on the bottom of the Polisy.

[Tominnh]

26 minutes ago, TexMike said:

ssh is secure shell to connect to UNIX command line. Recommend not to use it unless you know what you are doing.

For static IP,  it's much better to reserve the static IP on the router instead of manually configuring Polisy. The MAC address is on a sticker on the bottom of the Polisy.

I can see it connected to my router but cannot access it through the browser. Why can I not access via 192.198.xx.xx?  I did once yesterday, powered everything down for the night and got nothing in the morning. I have hit reset more times than I can count. Still nothing, still connects through the same IP address and still refusing to connect through firefox, chrome, edge ? 

 

[TexMike]

Sorry, don't know. Other than the common issues with setting time zone and getting updates to apply, mine came up pretty smooth as far as getting access to it.

[simplextech]

10 minutes ago, Tominnh said:

I can see it connected to my router but cannot access it through the browser. Why can I not access via 192.198.xx.xx?  I did once yesterday, powered everything down for the night and got nothing in the morning. I have hit reset more times than I can count. Still nothing, still connects through the same IP address and still refusing to connect through firefox, chrome, edge ? 

 

Did you configure a DHCP reservation?  If not then with it powered down over night did you check your route to make sure it's using the same IP address? 

[randyth]

Not sure if something else changed or it's because I tried adding :443 to the IP address, but I'm connecting with Chrome now.