I should say that in the first test, I saw the disconnect and reconnect and processing pick back up. I did a couple more tests. First, just stop publishing. No disconnect, MQTTSubscribe waited until the next message. No surprise there. Next I shut the broker down. Again, I saw MQTTSubscribe disconnect and reconnect and continue processing. So, I think the reconnect logic is working, but there still might be some other real world case that could cause a problem.
On Wednesday, 24 June 2020 13:50:22 UTC-4, Rich Bell wrote: > > Christian, > What are the symptoms that cause you to have to restart WeeWX when MQTT > connection is lost with wxmesh? The reason I ask, I tried just > disconnection the MQTTSubscribe client from the network and then > reconnecting. It seemed to behave correctly. I am hesitant to stop the > broker, but I will work on setting up a second broker to do some more > testing. > Thanks for any information/help. - Rich > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4b3f3030-b1c1-4600-94a9-4333596a8a5co%40googlegroups.com.
