tonyn79 wrote: I am using the 0.9.5 on the esp. on the library I saw on another post you suggested the latest and I downloaded from git. The server has the same output as above. Serial monitor was frozen in middle of a cipsend command. It works perfectly other than the lock ups. I am puzzled because every other example works perfect, until there is advanced coding. I have another post up about the dimmer not working on uno or pro mini, yet fine on mega. What are thoughts on watchdog implementation? For the lockup issue. Thank you for your time.
I'm using old V.0.9.2.2. There are some strange responses like "link is not". Maybe this is fixed in latest release and that's reason EasyIoT library stops working because it does not recognize response. I will check.
I loaded 9.2.2, it seems to be running a little worse, it will stay online with server for about 5 min. It does seem like it is locking up on the "unlink" most of the time. I will try a couple other firmwares on this.
I am wondering if hooking this up to hardware serial would give different results. I have been unable to get it to communicate at all without software serial, any advice?
Might be on to something here, I cleared eeprom on unit, reflashed with Temp/Hum. Set it up downstairs on its own power supply, it stopped communicating after about 15 min. This morning brought it back upstairs and plugged into serial with its own power supply and it has been running for hours.
It looks like it really wants to see the serial comm from computer to continue operation. How to I modify the example to only use hardware serial. I would like to test that out to see if problem is corrected. Thank you for the help.
First you need good power supply. Some of cheap Chinese power supplys are not good enough for ESP8266. Also I've checked DHT22 example. Maybe it's not good to send temperature in loop. Too much data can confuse ESP8266. I suggest to change example to send data every N minutes.