"Failed to send reboot to ISY..." error from PG3

[dex]

It appears PG3 is not fully communicating with my ISY (IoP).  Two symptoms:

• If I try to reboot the ISY from the PG3 UI (System > Reboot ISY), I get an error "Failed to send reboot to ISY" (screenshot attached).
   
• If I add and configure node servers (following wiki instructions) and they show "connected" status in PG3, there is absolutely no sign of them in the IoP Admin Console.  The Node Servers menu shows no node servers (screenshot attached).

It feels like some authentication thing, so I've gone through all logins (Portal, PG3, IoP) to ensure they are entered carefully in all the places they are supposed to be entered.  What are the pitfalls here that I may have missed?

What else could be causing this?  Thanks!

 - Dex

 

Version: 3.1.11
Status: Connected
Frontend Version: 3.1.11
ISY Version: 5.4.4

 

[DennisC]

Are you using a ISY or IoP?

What are your IoP settings in Polylot?

Are there any errors in Polglot log?

[Geddy]

@dex Did you setup the IoP in PG3 correctly? It does seem that there's authentication issue talking to the IoP.

In the PG3 web access look for "ISYs" and "Edit Current ISY"

 

Make sure you followed the steps in the Polisy User Guide in the Wiki to set up correctly. 

 

I think once you get this setup correctly you'll be good to go.

I know in the past I also had issue with sending a reboot to the IoP, but I think that's been corrected in a recent update. I don't usually try to do it that way so haven't tried recently. (And don't really like to randomly reboot the IoP so didn't want to test now.)

I think the best way to reboot the IoP process is in Admin Console.  Configuration Tab -> "Restart IoP"

 

 

[dex]

My ISY configuration matches the Wiki instructions (localhost; http; 8080).  Admin username and password match what's set in the Admin Console.  

I deleted and re-added the ISY on a few prior attempts to start from scratch.  Each time the Polisy automatically discovered the ISY (IoP, of course) and the problem persisted.

I think I made progress, though:  I deleted the ISY again.  This time, however, immediately after deleting it, I manually added it (ISYs > Add New ISY).  

The Node Server running on PG3 now shows up in the Admin Console.  I think I'm up and running again.  Thanks!