Michael,
I'm periodically finding all my Ecowitt / mcsMQTT devices stale and not being updated. A restart of the plugin fixes the problem. I could create an event to monitor device value changes and restart the plugin using Jon00's PI utility, but I wonder if the PI might be able to monitor the connection internally and reset it without requiring a restart of the full plugin? I realize I've not given you anything to go on as to the cause of the problem, and as of now I have no idea other than possibly the GW1100 losing wifi connection or some such. Not sure why it wouldn't be able to resume reporting to the PI, though. This morning I became aware all of my Ecowitt devices had stopped reporting last evening at 7:22pm, and there is nothing unusual in the log around that time--in fact nothing logged at all within the prior few minutes. I restarted the PI and all is well again.
I've enabled debug logging in the PI and will forward the file when it happens again.
Thank you.
I'm periodically finding all my Ecowitt / mcsMQTT devices stale and not being updated. A restart of the plugin fixes the problem. I could create an event to monitor device value changes and restart the plugin using Jon00's PI utility, but I wonder if the PI might be able to monitor the connection internally and reset it without requiring a restart of the full plugin? I realize I've not given you anything to go on as to the cause of the problem, and as of now I have no idea other than possibly the GW1100 losing wifi connection or some such. Not sure why it wouldn't be able to resume reporting to the PI, though. This morning I became aware all of my Ecowitt devices had stopped reporting last evening at 7:22pm, and there is nothing unusual in the log around that time--in fact nothing logged at all within the prior few minutes. I restarted the PI and all is well again.
I've enabled debug logging in the PI and will forward the file when it happens again.
Thank you.
Comment