Closed hsaturn closed 1 year ago
My two esp's worked all the day. The client published a topic randomly every 15 mins without any disconnection.
17:20:09.656 -> --> client A received sensor/temperature, 18.10 17:34:32.879 -> --> client A received sensor/temperature, 18.00 17:44:16.089 -> --> client A received sensor/temperature, 18.00 17:52:38.903 -> --> client A received sensor/temperature, 18.10 17:57:17.112 -> --> client A received sensor/temperature, 18.10 18:02:39.064 -> --> client A received sensor/temperature, 18.20 18:11:14.041 -> --> client A received sensor/temperature, 18.30 18:26:05.190 -> --> client A received sensor/temperature, 18.40 18:33:17.603 -> --> client A received sensor/temperature, 18.30 18:37:01.366 -> --> client A received sensor/temperature, 18.20 18:48:42.512 -> --> client A received sensor/temperature, 18.30 18:55:35.435 -> --> client A received sensor/temperature, 18.40 19:01:59.265 -> --> client A received sensor/temperature, 18.30 19:12:45.374 -> --> client A received sensor/temperature, 18.20 19:25:11.875 -> --> client A received sensor/temperature, 18.20 19:30:00.177 -> --> client A received sensor/temperature, 18.20
So I'm closing this issue
I have been testing for 48 hours and I confirm it works for me as well without timeouts. Thank you, great job!
Hmmm, I've just fixed today a timeout issue in a specific case (broker connected to another broker). But this should impact every single client connection. The Mqtt Specs says that 0 is a value accepted for keep_alive (infinite). This should work in other cases.
Hello
I'm starting this new issue and close others in order to solve this.
I'm running a setup for the day on the main branch (not a release). If this evening this setup still runs, then I'll close all timeout related issue and will release a new version of TinyMqtt
My setup is
The ESP Broker sketch, derived from client-with-wifi (as alranel said in previous discussion):
The ESP Client sketch, directly derived from simple-client.ino example: