I am facing a strange issue with two NodeMCU's installed at different locations.
The ESP8266 seems to be still running but the HTTP interface is not responsive,
so not GUI Access via Webbrowser nor a ping works after some time of running.
This effect can happen after 20 minutes but also after 2 hours.
NodeMCU#1 is outside with 3x TS2561 and 1x BME280 connected via I2C.
(used as a sensor to determine the direction of sunlight - east, south, west)
NodeMCU#2 is inside with 1x TS2561, 1xBH1750 and a LCD2004, all via I2C.
NodeMCU#1 sents current Temperature of BME280 to NodeMCU#2 via sendToHTTP.
NodeMCU#2 displays this temperature and also displays its own systime.
That's the way I see the systime running on the display but HTTP-Access does not work on both modules
nor the sendToHTTP works from the outside module#1 to the inside module#2
On both NodeMCU's, the controller is configured (ThingSpeak).
Interesting behaviour is that on NodeMCU#1 the controller to ThingSpeak seems to continue
running for some time while HTTP GUI access is not possible anymore as I see values at the
ThingSpeak-Channel - however also after some time later, this communication to ThingSpeak gets stuck.
The only way then to restart the devices is a power cylce to reset them.
Anyhow sometimes, both NodeMCU's also do a software reset, however this is the more rare case.
At both devices I tested with F/W 2018-10-14, 2018-10-11 and also 2018-08-04.
The behaviour is the same.
Does anybody has an idea about the root cause for that behaviour?
Please find below the rules I am using. The rules are just preliminary
and more or less for testing as I first want to achieve a reliable behaviour of the devices.
NodeMCU#2 inside:
Code: Select all
On Time#Initialized do // connected to Wifi-AP and NTP
notify 1, "ESPEasy_SERVER 192.168.1.100 started"
timerSet,1,9
endon
on BH1750#Lux>400 do
if [dummy#var1]=0 do
TaskValueSet 9,1,1
notify 1, "Lux BH1750>400"
endif
endon
on BH1750#Lux<400 do
if [dummy#var1]=1 do
TaskValueSet 9,1,0
notify 1, "Lux BH1750<400"
endif
endon
On Rules#Timer=1 do
TaskValueSet 3,1,[BH1750#Lux]
TaskValueSet 3,2,[TSL2561#Lux]
TaskValueSet 3,3,[TSL2561#Infrared]
TaskValueSet 3,4,[RSSI#dBm]
LCD,1,1,[RSSI#dBm] dBm %systime%
LCD,2,1,BH1750: [BH1750#Lux]
LCD,3,1,SR: %sunrise%
LCD,4,1,SS: %sunset%
timerSet,1,9
endon
On 50_x_Alive do
LCD,3,1,50_x:ok
endon
NodeMCU#1 Outside:
Code: Select all
On Time#Initialized do // connected to Wifi-AP and NTP
timerSet,1,5 // set Timer1 for event in x sec - Umkopieren der Werte
//timerSet,2,2 // set Timer2 for event in x sec - Heartbeat HTTP
timerSet,3,1 // set Timer3 for event in x sec - Heartbeat LED
notify 1, "50_x WX-Sensors 192.168.1.108 started"
endon
On Rules#Timer=1 do // when Timer1 expires do...
TaskValueSet 5,1,[TSL2561_East#Lux]
TaskValueSet 5,2,[TSL2561_South#Lux]
TaskValueSet 5,3,[TSL2561_West#Lux]
TaskValueSet 5,4,[TSL2561_West#Infrared]
sendToHTTP 192.168.1.100,80,/control?cmd=LCD,3,1,Temp:[BME280#Temperature]C
sendToHTTP 192.168.1.100,80,/control?cmd=LCD,4,1,Uptime:[uptime#minutes]min
timerSet,1,5 // Resets Timer1 for another x sec
endon
//On Rules#Timer=2 do // when Timer2 expires do...
//sendToHTTP 192.168.1.100,80,/control?cmd=event,50_x_Alive
//sendToHTTP 192.168.1.100,80,/control?cmd=LCD,3,1,Temp:[BME280#Temperature]C
//sendToHTTP 192.168.1.100,80,/control?cmd=LCD,4,1,Uptime:[uptime#minutes]min
//sendTo 1,event,50_x_Alive
//timerSet,2,2 // Resets Timer2 for another x sec
//endon
On Rules#Timer=3 do // when Timer3 expires do...
Pulse,0,1,400 // Pulse the LED on GPIO0 shortly
timerSet,3,1 // Resets Timer3 for another x sec
endon
Any ideas or hints about the possible root cause for this strange behaviour I would appreciate
as I am struggling since more than a week at debugging without any success.
thanks in advance,
ao16