Latest news:
- your fix files work for connecting MQTT broker at VC start (MQTT.Connect at VC.Loaded event). 
- today I left the PC on with the MQTT plugin disabled and, differently from the other day, I found it with CPU activity 40-60% anyway. So at this point, it may not depend from MQTT. 

I will see how it goes on with restarting VC every 2h.
Thanks again for your kind and quick support.

Thank you, I will try that.
For information, the CPU goes high even when MQTT broker is not/has never connected.

Hi, I am attaching here a couple of screenshots. Maybe I am the one doing something wrong, but actually the MQTT.connect does work if called after a first manual connection and disconnection in the same VC session. The only thing I see different is that, at VC start, the status is blank while otherwise it says "disconnected".

Thanks for your info and support. 
I am looking into restarting VC via the standard Windows activity planner and it kind of works. Of course this is not a clean method and should be temporary just for evaluation purposes.
The only issue is that VC does not connect by itself to the MQTT broker when VC restarts: I tried setting MQTT.Connect at VC.Loaded event, but it is not working. It seem that MQTT.Connect works only if there already was a first manual connection. So just for re-connection scopes. In other words, the MQTT Status can pass from "disconnected" to "connected" via MQTT.Connect but not from "null" to "connected".
Regarding the MQTT activities I have with VC, at this time they are very limited. I do not subscribe to topics via VC since it does not need to receive any data. It does need to publish data thou, but only at voice command. Hence, actually the MQTT plugin shall do perfectly nothing for 99% of the time. Still the CUP goes up for apparently no trigger at all.

Thanks for the response.
The issue seems to be related to the MQTT plugin (2.0.2.0), since I do not have this problem when disabling this plugin.
Unfortunately MQTT is an essential part of my project, so I will try to find out how to restart VoxCommando every 2 hrs or so and reconnect to the broker.

I am new to Voxcommando and I am evaluating it to use it fully in my system. It seem to work pretty good, but I am founding that VoxcommandoSP.exe starts using between 50 to 60% CPU for no reason at all after about 5h of inactivity and I have to close it and restart it to fix this.
This happens indipendently in ON and in Stanby mode.
I am using v.2.2.4.0 and trying also the beta 2.2.4.1.
Plugins MQTT and Sonos.