Hello Shev
Great app ...Bought the pro version .. and everything works fine to remote control a jacuzzi installation ...
... Nano + esp8266 infrastructure, Software serial communication between nano and ESP, sketch compiled with IDE Arduino (50% of the memory used)....
But : after a period of good working (it seems between 45 and 120 minutes ...it's variable and I don't undersatnd why), the communication with the server fails and the control from the app is no more available. What I see :
- the sketch keeps running (I can trace this on the serial monitor - and I've a watchdog in my sketch which never fire)
- the esp8266 keeps connected to the router (I see it in the list of connected devices)

It seems that it's the communication between the Nano and the ESP which is hanging
If I try to unpower / repower the ESP8266 Nothing happens and the communication with the ESP keeps hanging

If I reset the nano=> works perfect again but I loose the settings values I use in my sketch for the regulation of my installation (e.a; : the settings for the temperature of the water of the jacuzzi)

I think I've tested all what I can
- I've tested different SDK for the ESP (last SDK 0.60, also tested with 0.50),
- I've run the communication between Nano and ESP on the hardware serial port (Nano pin 0 and 1) (all Serial.print for tracing, disabled), but the result is the same. When I do that, my serial monitor is // connected with the communication between the Nano and the ESP and I can see the messages sent to the ESP by the nano. When the problem occurs, no more message are sent.... the communication freezes (Nothing on the serial monitor)
- I've let the serial monitor connected (with HW and SW communication for the ESP...) or not to the nano with or without tracing of the running sketch .... results remain the same... the communication freezes after a while. The period is variable (45 ... 120 minutes...) and before that everything works fine (the running of the sketch on the nano and the communication with the ESP when I run the App).

I'm unable to identify the origin problem as the communication is managed by the RemoteXY Library ans don't know which instruction to use to trace it

I's already spent a couple of days to solve this problem without any positive result... help please

Jean-Paul
jeamarechal@gmail.com