HSPI_mcsMonitor.exe

[backkri]

In the documentation a HSPI_mcsMonitor.exe is mentioned to monitor the plugin. Anyone know where to find it, the internal broker stops responding around once a week in my case. So I would like to use this.

Regards,

Kristof.

[Michael McSharry]

This plugin looked for messages in the HS log as a means to restart the plugin. It will not help in your situation. When using the internal broker, mcsMQTT publishes every minute a message on mcsMQTT/Heartbeat. If this message is not received for three minutes then the plugin restarts the internal broker. If you are running in developer mode then the heartbeat is echoed to the console. There is also data placed in the mcsMQTT debug log, if it is enabled, when a broker restarted is being attempted.

If you have a means to detect when you want a restart then you can restart the plugin if you have associated the pseudo-topic HS:MCSMQTT to a HS device. You do this from the Association table using the T1 filter of HS to find it. You can then use event action for device control to the restart value of the device.

[backkri]

Thanks Michael,

Implemented this (some values have to change regularly through the plugin). If thy don't, I trigger the restart.