Hm...wxMesh and even a python test script using paho.mqtt lost connection from time to time. But the python demo script reconnects while wxMesh seems not to reconnect so the empty payload starts and didn't recover. wxMQTT seems to reconnect...but it anyway stops after a while grabbing data.....(IP ....153 (debian))!
1506377499: New client connected from 192.168.2.153 as weewx_mqttc (c1, k60, u'default_usernameXXX'). 1506377506: New connection from 192.168.2.143 on port 1883. 1506377506: New client connected from 192.168.2.143 as mosqpub|7457-balin (c1, k60). 1506377506: Client mosqpub|7457-balin disconnected. 1506377506: New connection from 192.168.2.143 on port 1883. 1506377506: New client connected from 192.168.2.143 as mosqpub|7459-balin (c1, k60). 1506377506: Client mosqpub|7459-balin disconnected. 1506377516: New connection from 192.168.2.143 on port 1883. 1506377516: New client connected from 192.168.2.143 as mosqpub|7462-balin (c1, k60). 1506377516: Client mosqpub|7462-balin disconnected. 1506377516: New connection from 192.168.2.143 on port 1883. 1506377516: New client connected from 192.168.2.143 as mosqpub|7464-balin (c1, k60). 1506377516: Client mosqpub|7464-balin disconnected. 1506377517: Client mosqsub/4185-debian has exceeded timeout, disconnecting. 1506377517: Socket error on client mosqsub/4185-debian, disconnecting. 1506377520: New connection from 192.168.2.153 on port 1883. Sadly I'm not able to fix this....maybe someone will read this and maybe have a look on the wexMesh/wxMQQT driver.... In the thread Neil posted there was a hint that we have to take care that if the connection is lost to the broker the driver has to reconnect...but this seems not to be working inside weewx? Regards, Christian
