Abdelrahman Sobhy

I suggest using Issue template like [this](https://github.com/esp8266/Arduino/blob/master/ISSUE_TEMPLATE.md) to clean up issues that do not need any updates to the library

@PhySix66 in my sketch i use this ``` WiFiClient G_espClient; PubSubClient G_PubSubClient(G_espClient); ``` when you create PubSubClient object, you pass the 'WiFiClient' object So > `virtual uint8_t connected() = 0;...

I think when you're restarting mqtt something happen to `_client` inside `PubSubClient` object - maybe gets destroyed or becomes `null` - try to check on that variable if it's available...

It's not necessary to be null to give an exception could be some malloced memory then freed or something Also according to Kolban book - which is a very good...

Iam wondering if `WiFi.waitForConnectResult(1000)` have the same effect of `delay(1000)` @TD-er Also iam using this code for reconnect ```C++ if (!WiFi.localIP().isSet() || !WiFi.isConnected()) { int ret = WiFi.begin("My_SSID", "My_password"); uint8_t...

Would you use `WiFiClient` instead of `WiFiEspClient` Also try to add some code in loop to check the connection and reconnect of wifi

> Too much time in this loop without `yield()` => WDT ? > > ```c++ > while (WiFi.status() != WL_CONNECTED && attempts < 60) > { > wifiLedUpdate(); > delay(500);...

I agree with @asturcon3 about the use of `String` Also casting c string to String class consumes memory and time so try to use `string.h` functions instead of String class...

I used to have a similar problem the problem is related to the threshold voltage value that an ISR could be fired So the problem basically is your ISR is...