I recently added a 3rd Bond Bridge Pro to PG3 and now every time I reboot the Eisy the Bond Node Server comes up in a disconnected state and I have to go into PG3/Bond/Details and do a restart. It takes a few seconds but the Node Server does go into a connected state and everything seems to be normal until I reboot the Eisy again. Anybody have any ideas what is going on?

If you haven't run upgrade packages in awhile, try doing that. There was a recent version that caused some issues with certain plugins. It's best to get to at least v6.4.

Went from 6.0.3 to 6.0.4. The node server came up connected after the reboot this time. Hopefully this continues. Thanks for the help!

@theitprofessor I learned recently that there's been a few "bugs" under the surface that UD is suggesting you only access PG3 through the eisy_ui connection rather than the "old" port 3000 method. Now that you're on 6.0.4 make sure you get in the habit of connecting to PG3 through eisy.local (web ui) moving forward and not through the "old" method of directly accessing PG3. The bugs seem to cause some connection issues with plugins when using local or eisy.local credentials. I'm not sure what plugins were/are impacted, but just out of precaution use the eisy_ui method moving forward.

(Thanks @DennisC for pointing this out to me!)

Sounds like a plan. Thank you.