Generic HTTP Advanced controller cause reboots

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
jurczap
New user
Posts: 2
Joined: 15 Nov 2017, 07:54

Generic HTTP Advanced controller cause reboots

#1 Post by jurczap » 15 Nov 2017, 08:20

Hi,

I found out that using Generic HTTP Advanced controller cause all of my ESPs (nodeMCU, Wemos D1 v2) to reboot very often (every 5-60 minutes).
I use it to report data to Nettemp system - simple GET: receiver.php?device=ip&name=%tskname%&ip=%ip%&key=q1w2e3r4&type=%vname1%;%vname2%;%vname3%&value=%val1%;%val2%;%val3%

I have tested it on 3 devices - one without any external sensors - only reporting device uptime, one with dust sensor and one with 3 different sensors. All of these devices work stable in standalone mode or with Domoticz HTTP controller (more than 24hours uptime) and when I use Generic HTTP Advanced all of them start to reboot very often.

I can do some debug logging to help to solve this problem - but I need information what and how to collect.
For a start some log from console:

Code: Select all

SYS : 64.00
WD : Uptime 65 ConnectFailures 0 FreeMem 21592
WD : Uptime 65 ConnectFailures 0 FreeMem 21592
SYS : 65.00

Panic C:\Users\PK.platformio\packages\framework-arduinoespressif8266\cores\esp8266\core_esp8266_main.cpp:131 loop_task

ctx: sys
sp: 3ffffdd0 end: 3fffffb0 offset: 01b0

            stack>>>
            3fffff80: 401007ca 00000000 00000002 3fff2c00
            3fffff90: 00000000 3fffdad0 3fff2bec 402033f1
            3fffffa0: 3ffeaf98 40000f49 3fffdab0 40000f49
            <<<stack<<<

ets Jan 8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09826c6d
~ld
▒U

INIT : Booting version:
INIT : Warm boot #5
FS : Mounting...
FS : Mount successful, used 75802 bytes of 957314
INIT : Free RAM:24856
INIT : SPI not enabled
WIFI : AP Mode disabled
WIFI : AP Mode ssid will be ESP_Easy_0 with address 192.168.4.1
WIFI : Connecting mywifinet attempt #1
WIFI : Connected! IP: 10.255.255.204 (ESP_Easy_0)
WD : Uptime 0 ConnectFailures 0 FreeMem 21592
SYS : 0.00`
Regards

TD-er
Core team member
Posts: 8752
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Generic HTTP Advanced controller cause reboots

#2 Post by TD-er » 15 Nov 2017, 14:12

In the last few days I have seen another report about this. However, I don't know whether that was on the GitHub-issues or here, but maybe someone else knows and both threads can point to each-other, and/or knowledge can be shared?

jurczap
New user
Posts: 2
Joined: 15 Nov 2017, 07:54

Re: Generic HTTP Advanced controller cause reboots

#3 Post by jurczap » 16 Nov 2017, 00:18

It was me on github, but I was advised to open thread here before reporting bug on github - https://github.com/letscontrolit/ESPEasy/issues/582
My firs report was closed because it was about dev12 and it seems it not dev12 problem but plugin problem. Should I already open issue on github?

User avatar
grovkillen
Core team member
Posts: 3621
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: Generic HTTP Advanced controller cause reboots

#4 Post by grovkillen » 16 Nov 2017, 05:48

Yes that was what I meant with "open a new one" :)
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

ramonp
New user
Posts: 1
Joined: 20 Nov 2017, 14:09

Re: Generic HTTP Advanced controller cause reboots

#5 Post by ramonp » 20 Nov 2017, 14:21

I have the same issues with the Generic HTTP Advanced controller.

I have around 10 Wemos D1's with ESPEasy v2.0.0-dev12 test (ESPEasy_v2.0.0-dev12_test_4096.bin).
When I use the Domitcz HTTP controller there are no issues, but when I used the Generic HTTP Advanced controller the esp reboots within a day.
When I use multiple controllers with at least one Generic HTTP Advanced controller it will reboot within a couple of hours.

This is the http uri: import2.php?idx=%tskname%&value1=%val1%&value2=%val2%
I use the Environment sensor SI7021. But I also occurs with a DS18B20 and BME180 sensor.

astronomon
New user
Posts: 2
Joined: 26 Nov 2017, 20:36

Re: Generic HTTP Advanced controller cause reboots

#6 Post by astronomon » 03 Dec 2017, 21:08

When using a MQTT protocol, do not forget to set the ESP Unit number to a non-zero value, not conflicting with other ESP units.

hmoody
New user
Posts: 2
Joined: 30 Mar 2018, 18:50

Re: Generic HTTP Advanced controller cause reboots

#7 Post by hmoody » 30 Mar 2018, 19:05

Reboot issue when using v2.0.0-dev12 with OpenHab MQTT controller. Reboots occur randomly and often when NodeMCU is only doing reads from DHT22 sensor and publishing. Unit is set to 1. Will remove hardware devices and only will due SYS publishing. Not happy with reliability since custom Arduino software application on same hardware NEVER reboots

WD : Uptime 56 ConnectFailures 0 FreeMem 18784
MQTT : Topic: /esp000/PIR/Switch
MQTT : Payload: 1
SYS : 26.00
EVENT: sys#load=26.00
EVENT: Processing time:68 milliSeconds
MQTT : /esp000/sys/load 26.00
MQTT : Topic: /esp000/sys/load
MQTT : Payload: 26.00
SW : State 0
EVENT: PIR#Switch=0.00
EVENT: Processing time:69 milliSeconds
MQTT : /esp000/PIR/Switch 0
MQTT : Topic: /esp000/PIR/Switch
MQTT : Payload: 0
DHT : Temperature: 20.40
DHT : Humidity: 38.30
EVENT: DHT22#Temperature=20.40
EVENT: Processing time:70 milliSeconds
EVENT: DHT22#Humidity=38.30
EVENT: Processing time:71 milliSeconds
MQTT : /esp000/DHT22/Temperature 20.40
MQTT : /esp000/DHT22/Humidity 38.30
SYS : 26.00
EVENT: sys#load=26.00
EVENT: Processing time:69 milliSeconds
MQTT : Topic: /esp000/DHT22/Temperature
MQTT : Payload: 20.40
MQTT : Topic: /esp000/DHT22/Humidity
MQTT : Payload: 38.30
MQTT : /esp000/sys/load 26.00
MQTT : Topic: /esp000/sys/load
MQTT : Payload: 26.00
SYS : 26.00
EVENT: sys#load=26.00
EVENT: Processing time:59 milliSeconds
MQTT : /esp000/sys/load 26.00
EVENT: Rules#Timer=1
ACT : Pulse,2,0,500
SW : GPIO 2 Pulsed for 500 mS
ACT : timerSet,1,30
EVENT: Processing time:571 milliSeconds
MQTT : Topic: /esp000/sys/load
MQTT : Payload: 26.00
MQTT : Topic: /esp000/gpio/4
MQTT : Payload: 1
SW : GPIO 4 Set to 1
SYS : 26.00
EVENT: sys#load=26.00
EVENT: Processing time:72 milliSeconds
MQTT : /esp000/sys/load 26.00
MQTT : Topic: /esp000/sys/load
MQTT : Payload: 26.00
DHT : Temperature: 20.40
DHT : Humidity: 38.30
EVENT: DHT22#Temperature=20.40
EVENT: Processing time:68 milliSeconds
EVENT: DHT22#Humidity=38.30
EVENT: Processing time:72 milliSeconds
MQTT : /esp000/DHT22/Temperature 20.40
MQTT : /esp000/DHT22/Humidity 38.30
MQTT : Topic: /esp000/DHT22/Temperature
MQTT : Payload: 20.40
MQTT : Topic: /esp000/DHT22/Humidity
MQTT : Payload: 38.30
MQTT : Topic: /esp000/gpio/4
MQTT : Payload: 0
SW : GPIO 4 Set to 0
SYS : 26.00
EVENT: sys#load=26.00
EVENT: Processing time:69 milliSeconds
MQTT : /esp000/sys/load 26.00
SYS : 56.00
EVENT: sys#uptime=56.00
EVENT: Processing time:69 milliSeconds
MQTT : Topic: /esp000/sys/load
MQTT : Payload: 26.00
MQTT : Topic: /esp000/gpio/4
MQTT : Payload: 1
SW : GPIO 4 Set to 1
MQTT : Topic: /esp000/gpio/4
MQTT : Payload: 0
SW : GPIO 4 Set to 0
MQTT : /esp000/sys/uptime 56.00
MQTT : Topic: /esp000/sys/uptime
MQTT : Payload: 56.00
MQTT : Topic: /esp000/gpio/4
MQTT : Payload: 1
SW : GPIO 4 Set to 1
SYS : 26.00
EVENT: sys#load=26.00
EVENT: Processing time:69 milliSeconds
MQTT : /esp000/sys/load 26.00
MQTT : Topic: /esp000/gpio/4
MQTT : Payload: 0
SW : GPIO 4 Set to 0
MQTT : Topic: /esp000/sys/load
MQTT : Payload: 26.00
MQTT : Topic: /esp000/gpio/4
MQTT : Payload: 1
SW : GPIO 4 Set to 1
MQTT : Topic: /esp000/gpio/4
MQTT : Payload: 0
SW : GPIO 4 Set to 0
DHT : Temperature: 20.40
DHT : Humidity: 39.10
EVENT: DHT22#Temperature=20.40
EVENT: Processing time:68 milliSeconds
EVENT: DHT22#Humidity=39.10
EVENT: Processing time:72 milliSeconds
MQTT : /esp000/DHT22/Temperature 20.40
MQTT : /esp000/DHT22/Humidity 39.10
SYS : 26.00
EVENT: sys#load=26.00
EVENT: Processing time:70 milliSeconds
MQTT : Topic: /esp000/DHT22/Temperature
MQTT : Payload: 20.40
MQTT : Topic: /esp000/DHT22/Humidity
MQTT : Payload: 39.10

Panic /home/travis/.platformio/packages/framework-arduinoespressif8266/cores/esp8266/core_esp8266_main.cpp:98 __yield

ctx: sys
sp: 3fff3f20 end: 3fffffb0 offset: 01b0

>>>stack>>>
3fff40d0: 3ffeab40 00000000 000003e8 3fff3270
3fff40e0: 00000000 00000000 00000000 40203435
3fff40f0: 3fff2284 00000000 3fff11fc 4023672f
3fff4100: 3fff1e7a 3fff1f84 0033b766 40236760
3fff4110: 3fff1e7a 3fff1f84 3fff4160 40238211
3fff4120: 00000000 00000000 00000000 4020246e
3fff4130: 3ffe88b7 00000008 3fff4160 40100688

...
3fff70c0: 00000002 003394ac 003394ac 00000000
3fff70d0: 40217134 0000033b 4024a2e8 4024a2d0
3fff70e0: 3ffea3b8 6400a8c0 00000000 0000075b
3fff70f0: 00000000 00000000 03a603e1 00000000
3fff7100: 0000c350 4010567c 00000000 7325203a
3fff7110: 03de03e4 00000000 00000000 00000000
3fff7120: 00000000 3ffeee30 03e183e6 04d104b4
3fff7130: 75252e75 0075252e 03e403eb 3fff77dc
3fff7140: 00000000 00000000 00000000 00000000
3ff
ets Jan 8 2013,rst cause:4, boot mode:(3,0)

wdt reset
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09826c6d
~ld
⸮U


INIT : Booting version: v2.0.0-dev12
INIT : Warm boot #628
FS : Mounting...
FS : Mount successful, used 76806 bytes of 957314
INIT : Free RAM:21928
INIT : I2C
INIT : SPI not enabled
bcn 0
del if1
mode : sta(68:c6:3a:88:a9:82)
WIFI : AP Mode disabled
WIFI : AP Mode ssid will be esp000_0 with address 192.168.4.1
IP : Static IP :192.168.0.110
WIFI : Connecting hill attempt #1
f r-1, scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 11
cnt

connected with hill, channel 1
ip:192.168.0.110,mask:255.255.255.0,gw:192.168.0.1
WIFI : Connected! IP: 192.168.0.110 (esp000_0)
IMPT : Connected to MQTT broker with Client ID=esp000-Import
IMPT : [sniff#cmdmqtt] subscribed to /esp000/cmdmqtt
MQTT : Connected to broker
Subscribed to: /esp000/#
EVENT: System#Boot
ACT : gpio,2,1
SW : GPIO 2 Set to 1
ACT : timerSet,1,1
ACT :
EVENT: Processing time:79 milliSeconds
WD : Uptime 0 ConnectFailures 0 FreeMem 18416

TD-er
Core team member
Posts: 8752
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: Generic HTTP Advanced controller cause reboots

#8 Post by TD-er » 30 Mar 2018, 20:30

Since the dev-12 version really a lot of builds have been made.
Did you test newer versions?
Build dev-12 was made on 22 Sep 2017.
I guess I am not exaggerating when claiming close to 100 builds were made since and only builds when something was changed in the code.

Post Reply

Who is online

Users browsing this forum: No registered users and 145 guests