webminster Posted April 30, 2022 Posted April 30, 2022 I have issues with my Polisy after it is restarted or started cold. None of the ISY nodes show functional until I restart PG2 and PG3. Here's two issues I see: PG2 - After reboot, the PG2 console shows the message: "ISY automatically discovered at http://localhost:8080 however the username and password need to be set in the settings menu." It shows that until I either reset the password in settings (again) or reboot PG2. PG3 - No nodes show any status or values in the ISY console until I restart PG3. Can PG2 and PG3 be patched or fixed to work properly after Polisy reboot? Thanks in advance. -Alan
Techman Posted April 30, 2022 Posted April 30, 2022 On the Polygot settings page, verify that you have the correct parameters for the Polyglot web port and for the ISY settings
webminster Posted April 30, 2022 Author Posted April 30, 2022 That's fine. As I said it works OK after a restart, not changing/adding parameters. What I'm saying is it doesn't start right after a reboot, I have to restart them again to work. Like a race condition where the node servers start too early and don't connect or something. I mentioned above that it says I need to set the password. But I did before the reboot. So if it's not got a password, it didn't save it. But it's fine until the reboot if I set the password in PG2 config. -Alan
Techman Posted April 30, 2022 Posted April 30, 2022 (edited) In the Polygot setup window, The ISY address should be that of the Polisy and not the ISY? Edited April 30, 2022 by Techman
webminster Posted April 30, 2022 Author Posted April 30, 2022 The ISY is same address, same box. On PG2, config for ISY is localhost:8080. On PG3, is the policy/ISY address (not changable). I'd probably set locahost there too, but cannot be edited.
bpwwer Posted May 1, 2022 Posted May 1, 2022 Yes, the ISY IP address/port is editable on PG3. From the ISY-> Edit Current ISY. If you can't update/save changes from that screen then you have other issues that need to be resolved first. Don't use 'localhost' there's a problem where that doesn't do the right thing and it seems to be a node.js problem, not something that can fixed or worked around by PG3. Using the actual IP address is best. I can't say that I've ever seen the issue you're describing after a reboot but then I also don't reboot very often, the Polisy I use to develop PG3 on has been up for 102 days. How long do wait before you restart PG3? It's possible that it could take few minutes 5-10, before it retries and connects to the ISY.
webminster Posted May 1, 2022 Author Posted May 1, 2022 It's a new Polisy, so I'm in process of moving to it, want to make sure it reboots OK in case it has to. I've had chronic issues with setting the PG2 settings and rebooting, to be given a red box "ISY automatically discovered at http://localhost:8080 however the username and password need to be set in the settings menu." Recurs even after I reenter the config, save, and reboot. Yes, I had forgotten about the "edit current ISY", that's editable. I've changed to the IP address and will see how that goes. Odd that it'd have more trouble with localhost than a DHCP-provided IP. I'd normally think loopback is easier to get right.
bpwwer Posted May 1, 2022 Posted May 1, 2022 @webminsterthanks for details. I'm always a bit concerned when I hear of someone rebooting the Polisy as that shouldn't be needed to resolve a majority of the problems. After OS upgrades, sure. Your case seems valid as well. I've added an issue and I'll try to reproduce. PG2 has bug related to saving credentials, I really know the cause as I don't work on it. Most of the time it works, sometimes it doesn't and takes multiple attempts to get them saved correctly. I had to dig back through our development channel to jog my memory. On a Polisy, 'localhost' was resolving to a IPV6 address and that would cause failures as nothing else in PG3/ISY is using IPV6. Using 127.0.0.1 instead of 'localhost' works since it's a IPV4 address. 1
webminster Posted May 1, 2022 Author Posted May 1, 2022 Appreciate the replies, and thanks for info about loopback. I've changed to PG configs to use the loopback IP instead. Didn't solve the issue, though, after a reboot the IoP is up, the node servers (PG3) show up and connected - but the status of the devices in all the PG3 nodes is not correct. It becomes correct when I do a restart of PG3 (not the IoP or Polisy proper. -Alan
Recommended Posts