I have noticed this for quite a while now. When you reboot eisy, plugins fail to populate/register. I assume this is an ordering issue where the plugins are starting up faster than iox. Restarting the plugins fixes it. However, this is less than ideal. Especially if you had an unexpected reboot of eisy (ie power interruption) and were not aware of it, things would just stop working. As I mentioned, this is not new to any recent firmware. I first noticed this a very long time ago. I just updated to the latest firmware last night and most of my plugins needed to then be restarted manually.

@apostolakisl ,

Are these local plugins or production plugins?

With kind regards,
Michel

I have not experienced this problem. My plugins always restart and work fine after power outages or other unexpected reboots. A while ago, I recall a few plugins that may not have worked after a power outage, but I percieved this was the result of a plugin restarting faster than the associated hub (hue plugin restarted faster than did the hue hub, for example). I have not noticed such problems recently, however.

I have been having a similar problem often they show disconnected in the node tree but connected under plugins

@bmercier has identified the cause via a ticket and says the issue will be addressed in the next update

I have an Acurite Plugin (for weather data - production) that has a similar issue. After a system restart, the nodes don't seem to reflect what they actually are, just the system names. Restarting the plugin cleared the issue.

I have a program that shuts down some key devices in my house when lightning strikes are close. Before the restart the program rendered "undefined <= 4 miles" and after restart it said "Lightning Last Strike Distance <= 4 miles".

The program logic still worked, but I went to check on this and noticed the node name issue.

@Michel Kohanim store plugins. I have seen this since prior to even having any local plugins.