No MQTT connected event message sent when Octoprint autoconnects to printer about octoprint-mqtt HOT 2 OPEN

I suspect this is a race condition of some kind where the connection is established to printer prior to the plugin's code being loaded to react to the connection event.

from octoprint-mqtt.

Thanks - that makes sense. I imagine that a lot of ppl would use the auto connect function so I'm a bit surprised to be the only one reporting this. Any thing I can do the speed up the plugin or delay the connection? Do plugins load in order in which they were installed? If so I could delete and re-add them with MQTT at the front.

Alternative is it possible to get additional server events like "PrinterStateChanged" sent via MQTT. There is an event payload called "operational" which could be used as a poxy for connected I guess.

from octoprint-mqtt.