In the original code Mesh.on()
was immediately followed by a Mesh.connect()
so no-op or not, the actual problem was the missing delay between publish and Mesh.off()
.
In another thread I got this reply which may help mitigate the issue
In the original code Mesh.on()
was immediately followed by a Mesh.connect()
so no-op or not, the actual problem was the missing delay between publish and Mesh.off()
.
In another thread I got this reply which may help mitigate the issue