@Dmytro if you look at the Serial Monitor and associated sketch at the start of this thread you will see that we connect, disconnect and reconnect several times over a 30 second interval. This is not the way the actual system works but it is more to highlight our problem. So the first connection gives RTC data but none of the subsequent connections.
Thinking about this it is probably the 5 / 10 minute standard interval that is set with RTC. We expect our systems to sleep for 10 minutes (maybe 5) so it might not be a problem, but when we are testing we set the sleep period very short (30 seconds sometimes) as we don’t want to wait 5 or 10 minutes to see if our latest sketch changes are working.
On second thoughts this can’t be the problem as the 1000+ connections with the standard RTC sketch we made the night before last were at 20 second intervals (with a short deepsleep included within the 20 seconds).
A sample of the 8000+ lines of Serial Monitor data for the 1000+ succesful RTC requests are shown below:
[15661] Current time: 22:42:39 29 03 2016
Connecting to GargoyleTest
[1244] Connected to WiFi
[1244] My IP: 192.168.10.226
[1245] Blynk v0.3.4
[5001] Connecting to blynk-cloud.com:8442
[5311] Ready (ping: 1ms).
[5623] Time sync: OK
[15905] Current time: 22:43:05 29 03 2016
Connecting to GargoyleTest
[1252] Connected to WiFi
[1252] My IP: 192.168.10.226
[1252] Blynk v0.3.4
[5001] Connecting to blynk-cloud.com:8442
[5344] Ready (ping: 3ms).
[5680] Time sync: OK
[15680] Current time: 22:43:32 29 03 2016
Connecting to GargoyleTest
[1250] Connected to WiFi
[1250] My IP: 192.168.10.226
[1250] Blynk v0.3.4
[5001] Connecting to blynk-cloud.com:8442
[5309] Ready (ping: 0ms).
[5638] Time sync: OK
[15638] Current time: 22:43:59 29 03 2016
Connecting to GargoyleTest
[1247] Connected to WiFi
[1247] My IP: 192.168.10.226
[1247] Blynk v0.3.4
[5001] Connecting to blynk-cloud.com:8442
[5385] Ready (ping: 1ms).
[5743] Time sync: OK
[15742] Current time: 22:44:32 29 03 2016