Release v2.0.0-dev7 - possible Bug in Controller

Message

toffel969 · #1 Post by **toffel969** » 17 Apr 2017, 12:27

Hi

I want to report strange behaviour with the dev7 version of ESP easy.

Node (Wemos D1 pro mini + PIR+ Door switch+ Gas pulse counter + two relays) was running stable for about a week as standalone. Then I added my domoticz controller and everything seemed to work nicely. After some time (not sure how long, maybe 12h) the http connection started failing (weblog of esp) and the webserver became unresponsive. I could not open the controller page again after that, no matter how many reboots. I could however issue the reboot command by http and also managed to downgrade firmware to 148RC via OTA. Since then the node is running stable. No idea what caused the issue.

regards

Shardan · #2 Post by **Shardan** » 17 Apr 2017, 14:04

Hello,

i can confirm the webserver of 2.0.0dev7 is broken. It does not work with FHEM either.

Tested with a self compiled dev-version and the "normal" binary from github.
Both uploaded to a WeMOS D1 mini (ESP-12E), configured to send RSSI and the data from a BMP-180 to my FEHM server.
For testing the delay was set to send data every second.

Internaly the ESP works, i can monitor RSSI and BMP-data on the serial port.

Within less then one minute the webpage is no longer available.
I get a "Page did not send data" Error from my browser, no more data recorded in FHEM.
About a minute later i get a blank page from the webserver.

On hard rebooting (off/on) it gets back to work. If the webpage is not called it keeps working for
some minutes,then the ESP crashed and restarts:

Code: Select all

BMP  : Temperature: 27.58
BMP  : Barometric Pressure: 1052.25
SYS  : -60.00
BMP  : Temperature: 27.56
BMP  : Barometric Pressure: 1052.27
SYS  : -60.00

Exception (29):
epc1=0x4000e1b2 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: sys 
sp: 3ffffd70 end: 3fffffb0 offset: 01a0

>>>stack>>>
3fffff10:  07d7ad83 000002f4 3ffeeb60 401004f4  
3fffff20:  3ffeec58 3ffeed00 3ffeeb60 40107abc  
3fffff30:  00000007 00000007 00000000 4023ee1e  
3fffff40:  40104a3c 02734075 4023f2e6 00000008  
3fffff50:  00000000 00000000 4023f393 3ffeec14  
3fffff60:  3ffeed00 02734075 4023f2a8 40203a44  
3fffff70:  40242095 3ffeec14 3ffeed00 07d7ab5d  
3fffff80:  402420da 3fffdab0 00000000 3fffdcb0  
3fffff90:  3ffeed18 3fffdad0 3fff24d8 402031fb  
3fffffa0:  40000f49 000035ea 3fffdab0 40000f49  
<<<stack<<<

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

The webserver outage and the crash are reproducible on my WeMOS.
Hardware is ok, checked with R148 running issue free.

Regards
Shardan

Shardan · #3 Post by **Shardan** » 20 Apr 2017, 21:42

Hello again,

i did some further tests today.
First i cleaned up the flash with a "zero binary" and reflashed the "normal" 2.0.0dev7 from github.

Well, up to now the permanent crashing seems to be gone.
Sadly that's all changes.

If i reset the ESP-12 and wait one or two minutes i can't connect via browser - i get a blank page, that's all.

Communication with FHEM runs for a while then stops.

Regards
Shardan

toffel969 · #4 Post by **toffel969** » 22 Apr 2017, 13:07

Shardan wrote: ↑20 Apr 2017, 21:42 Hello again,

i did some further tests today.
First i cleaned up the flash with a "zero binary" and reflashed the "normal" 2.0.0dev7 from github.

Well, up to now the permanent crashing seems to be gone.
Sadly that's all changes.

If i reset the ESP-12 and wait one or two minutes i can't connect via browser - i get a blank page, that's all.

Communication with FHEM runs for a while then stops.

Regards
Shardan

hi shardan

i flashed a "virgin" wemos with dev7 --> works flawless. i think its residues from previous version in flash. seehttps://www.letscontrolit.com/forum/vie ... 281#p15281
I think its a related problem. if so , then we should update info on github to flash 0 binary when installing dev mega coming from previous espeasy

psy0rz · #5 Post by **psy0rz** » 22 Apr 2017, 14:06

Shardan wrote: ↑20 Apr 2017, 21:42 Hello again,

i did some further tests today.
First i cleaned up the flash with a "zero binary" and reflashed the "normal" 2.0.0dev7 from github.

Well, up to now the permanent crashing seems to be gone.
Sadly that's all changes.

If i reset the ESP-12 and wait one or two minutes i can't connect via browser - i get a blank page, that's all.

Communication with FHEM runs for a while then stops.

Regards
Shardan

shardan can you try resetting to factory defaults via the reset command in serial. ( or by connecting rx to tx while powering up)

Shardan · #6 Post by **Shardan** » 22 Apr 2017, 17:36

Hello psy0rz,

i tried the following things:

Reset to defaults (reset command via serial port)
Cleaning up the flash by writing with a "zero binary", then reflashing.
Nothing helped.

If i call the page via browser it is gone, - a minute after rebooting a "Device didn't send any data" error,
some minutes later the webserver is back but the page is just blank. Data transfer to FHEM stopps.

If i reboot and let it just run without opening the webpage i see the crash mentioned above every three minutes.

I'll try two things this evening:
- I'll set the serial monitoring to highest possible level.
- Maybe removing the tasks completely shows changes.

I should have a "virgin" nodeMCU or WeMOS too so i will use that for checking.

Maybe i can see anything then. I'll report here.

Regards
Shardan

Shardan · #7 Post by **Shardan** » 22 Apr 2017, 19:12

Hello again,

meanwhile tested this:

A brand new nodeMCU (still the AI thinker flashed). Flashed it with 2.0.0dev7 from github and the included flash tool.

Starting up with no tasks, configured the FHEM server as controller 1.
This runs, but without any task no data is sent to the FHEM server.

Then I configured just System Info: WiFi RSSI. And the same happened.
The website is unavailable after some minutes. I get a "site didn't sent data" Error.
After some more minutes i get a blank page. Data transfer to FHEM stopped.
If i don't call the page it transfers data to the server until I oipen the webpage.
If I open the page I get an error on the webpage and transfer is gone.

Again i flashed a zero binary to clear up the flash and tried again, but same, nothing changed.

Internal measurement is still working, i see the data on the serial port. Just webservices are gone.

The only thing that seems has changed i don't see any crashes atm.
This may change over time, i'll let it run for a while.

P.S.
Just had the next crash.
Resetted and just let it transfer data to FEHM without opening the webpage

Code: Select all

Exception (0):
epc1=0x40205c26 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: cont 
sp: 3fff31a8 end: 3fff3500 offset: 01a0

>>>stack>>>
3fff3348:  3fff222c 4020ea12 000003d6 3fff1268  
3fff3358:  3fff24e0 3fff1268 000416c7 3fff1268  
3fff3368:  4020323c 3fff24e0 00000000 00000000  
3fff3378:  3fff33f0 402032b4 000416c7 3fff1268  
3fff3388:  3fff33f0 4022ba84 000003d6 3fff1268  
3fff3398:  3fff33f0 4022bb54 50545448 44203a20  
3fff33a8:  79616c65 32383920 00736d20 3fff33f0  
3fff33b8:  3fff341c 402023f2 3ffe8663 00000000  
3fff33c8:  00000001 00000000 00000019 00000001  
3fff33d8:  3ffe8663 3fff1268 3fff115e 3fff07f4  
3fff33e8:  00000010 4022bd26 08020100 3f04dad0  
3fff33f8:  00000000 00000001 3fff3694 00000118  
3fff3408:  00000118 4010020c 3fff4ce4 0000000f  
3fff3418:  00000000 3fff65cc 0000000f 00000000  
3fff3428:  3fff24e0 c2400000 4d86498a ece7b948  
3fff3438:  a402c286 40215375 3fff05b8 00000005  
3fff3448:  00000001 4021a30d 00000100 00040000  
3fff3458:  00000000 40203201 00000000 00000000  
3fff3468:  3fff1950 4020b801 00000000 00000000  
3fff3478:  00000000 3fff161c 00000001 3fff0798  
3fff3488:  00000001 4022e521 6c696146 00000000  
3fff3498:  00000001 3fff24d8 3fffdad0 00000000  
3fff34a8:  3fff05a0 4022e59f 00000000 00000000  
3fff34b8:  3fff1268 3fff24d8 3fffdad0 00000000  
3fff34c8:  3fff05b0 3fff24d8 3fffdad0 00000000  
3fff34d8:  3fff1268 40231615 3fffdad0 00000000  
3fff34e8:  3fff24d2 40203288 feefeffe feefeffe  
3fff34f8:  3fff24e0 40205c2c feefeffe 3fff24e0  
<<<stack<<<

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

wdt reset

Regards
Shardan

psy0rz · #8 Post by **psy0rz** » 23 Apr 2017, 18:19

Just reproduced it and working on it.

psy0rz · #9 Post by **psy0rz** » 23 Apr 2017, 19:04

fixed in commit 916de7909f33e7c83c48d854d3bbe52a866034cd

ipua · #10 Post by **ipua** » 24 Apr 2017, 08:45

Hi psy0rz,
Can you update binary release ?
Thanks

psy0rz · #11 Post by **psy0rz** » 24 Apr 2017, 13:35

done

Shardan · #12 Post by **Shardan** » 24 Apr 2017, 20:31

Hello,

I'm sorry - no.
Same behaviour as before: As soon as the FEHM server is configured web site gets unrechable after short time.
FHEM registers uptime for about one minute, then data transfer stops.

I've configured nothing first, just let it run with serial monitoring - runs.
Then i configured a BMP180 and SysInfo-RSSI without any server and got wdt resets and crashes now and then.

After configuring the FHEM service the website is down within a minute.

Data transfer gets erratic: The BMP is configured to send data every second, Uptime every 60 seconds.
For around one minute the data is transferred as described, i can see the BMP180 values float in FHEM.
When the website is down, i get values, but only evey 60 seconds, even for the BMP180-values.
I've no idea what's going on there.

Crashes come with different exceptions:

Code: Select all

Exception (9):
epc1=0x402091e3 epc2=0x00000000 epc3=0x00000000 excvaddr=0x402065f1 depc=0x00000000

ctx: cont 
sp: 3fff2fa0 end: 3fff3360 offset: 01a0

>>>stack>>>
3fff3140:  00000100 3fff4950 3fff4e14 4020938c  
3fff3150:  0000039c 3fff2274 3fff4b7a 00000000  
3fff3160:  000011ab 3fff4c0c 00000000 00000001  
3fff3170:  3fff31f1 000011ab 00000012 00300005  
3fff3180:  00000001 00000001 3fff31f0 401004d8  
3fff3190:  3fff4e14 3fff4748 3fff473c 00000001  
3fff31a0:  3fff31f0 00000001 3fff4950 4020656b  
3fff31b0:  3fff4e14 00001000 3fff4950 402067fb  
3fff31c0:  3fff4e14 00000000 00000001 3fff10dc  
3fff31d0:  3fff0f04 000001d8 000001ab 40204ec5  
3fff31e0:  3fff0f04 000001d8 00001000 40214095  
3fff31f0:  3fff4700 3fff64dc 00000003 40214139  
3fff3200:  3fff0f04 000001d8 00001000 4021b2f3  
3fff3210:  3ffe9768 00000000 000003e8 3fff2334  
3fff3220:  3fff473c 3fff64dc 3fff2274 3fff34fc  
3fff3230:  00000005 00000000 3fff0f04 4021b371  
3fff3240:  3fff4b4c 00000000 00000000 4022bc23  
3fff3250:  00000014 00002250 3fff2274 3fff2334  
3fff3260:  00000010 3fff32c0 3fff32c0 402023f0  
3fff3270:  3ffe85f9 00000000 3fff32c0 4020243f  
3fff3280:  3fff34fc 0000044a 0000044a 4010020c  
3fff3290:  3fff3b10 00000000 3fff32c0 40100688  
3fff32a0:  3fff34fc 00000118 00000118 4010020c  
3fff32b0:  3fffdad0 00000003 3fff331c 40100688  
3fff32c0:  00000000 00000000 00000000 40202390  
3fff32d0:  3fffdad0 00000003 00000000 00000000  
3fff32e0:  3fff148c 3fff0608 00000000 4022e518  
3fff32f0:  6c696146 73657275 46203020 3fff2334  
3fff3300:  3fffdad0 00000000 3fff0414 4022e597  
3fff3310:  00000000 00000000 3fff10dc 00000000  
3fff3320:  00000000 00000000 3fff0424 3fff2334  
3fff3330:  3fffdad0 00000000 3fff10dc 402314dd  
3fff3340:  3fffdad0 00000000 3fff232e 402033c8  
3fff3350:  feefeffe feefeffe 3fff2340 40205e20  
<<<stack<<<

 ets Jan  8 2013,rst cause:2, boot mode:(1,6)


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

wdt reset

Code: Select all

Exception (28):
epc1=0x4000bf0e epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: cont 
sp: 3fff2f40 end: 3fff3360 offset: 01a0

>>>stack>>>
3fff30e0:  3fff2094 3fff17e8 3fff3110 3ffe85f9  
3fff30f0:  3fff2094 3fff17e8 3fff311c 402025c6  
3fff3100:  3fff2094 3fff17e8 3fff17c4 40212f60  
3fff3110:  00000000 00000000 00000000 3fffba7c  
3fff3120:  0000000f 00000001 3fff767c 0000001f  
3fff3130:  0000000a 00051a76 3fff10dc 00000030  
3fff3140:  3fffbd5c 0000000f 00000000 3fffbd44  
3fff3150:  0000000f 00000000 3fff67f4 0000000f  
3fff3160:  00000001 3fff67dc 0000000f 00000003  
3fff3170:  3fffbf54 0000008f 0000008b 4020b4c0  
3fff3180:  3fff1804 000004aa 3fff2340 00000000  
3fff3190:  00000000 40210cfc 0000000a 40214994  
3fff31a0:  00000000 3fff10dc 3fff20a0 3fff10dc  
3fff31b0:  000001bc 3fff17e8 3fff17c4 40211d3b  
3fff31c0:  00051a76 3fff10dc 4020337c 3fff2340  
3fff31d0:  00000000 3fff7c94 3fff3250 3fff10dc  
3fff31e0:  00051a76 3fff10dc 3fff3250 4022ba4a  
3fff31f0:  00000000 3fff0668 3fff3250 4022bb53  
3fff3200:  00000000 00000000 00000000 00000000  
3fff3210:  00000000 00000000 3fff327c 402024ca  
3fff3220:  3ffe85f9 00000000 3fff32bc 40202390  
3fff3230:  00000019 00000001 3ffe85f9 3fff10dc  
3fff3240:  3fff0fd2 3fff0668 00000010 4022bd1a  
3fff3250:  080201f9 00040000 00000000 40202401  
3fff3260:  3fff34fc 0000075f 0000075f 4010020c  
3fff3270:  3fff7d84 0000000f 00000000 3fff4b64  
3fff3280:  0000000f 00000000 3fff2340 c2640000  
3fff3290:  00000000 00000000 00000000 402152d5  
3fff32a0:  3fff042c 00000005 00000001 4021af93  
3fff32b0:  00000200 00080000 00000000 40203401  
3fff32c0:  00000000 00000000 3fff17c4 4020b902  
3fff32d0:  00000000 00000000 00000000 00000000  
3fff32e0:  3fff1490 3fff060c 00000001 4022e518  
3fff32f0:  6c696146 00000000 00000002 3fff2334  
3fff3300:  3fffdad0 00000000 3fff0414 4022e597  
3fff3310:  00000000 00000000 3fff10dc 3fff2334  
3fff3320:  3fffdad0 00000000 3fff0424 3fff2334  
3fff3330:  3fffdad0 00000000 3fff10dc 402314dd  
3fff3340:  3fffdad0 00000000 3fff232e 402033c8  
3fff3350:  feefeffe feefeffe 3fff2340 40205e20  
<<<stack<<<

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

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


INIT : Booting version: v2.0.0-dev8
FS   : Mount successful
INIT : Free RAM:27464
INIT : I2C
INIT : SPI not enabled
WIFI : Connecting... 1

Exception (0):
epc1=0x4000af17 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: sys 

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

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


INIT : Booting version: v2.0.0-dev8
FS   : Mount successful
INIT : Free RAM:27312
INIT : I2C
INIT : SPI not enabled
WIFI : Connecting... 1
WIFI : Connected! IP: 192.168.17.64
INIT : Normal boot

Code: Select all

xception (29):
epc1=0x4000e1b2 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: sys 
sp: 3ffffd70 end: 3fffffb0 offset: 01a0

>>>stack>>>
3fffff10:  13b863b3 000002f4 3ffee9b0 401004f4  
3fffff20:  3ffeeaa0 3ffeeb50 3ffee9b0 40107c5c  
3fffff30:  00000007 00000007 00000000 4024039a  
3fffff40:  40104a3c 06297841 40240866 00000008  
3fffff50:  3ffeeb50 3ffeea64 40240913 3ffeea64  
3fffff60:  3ffeeb50 06297841 3ffeeb50 60000600  
3fffff70:  40243611 3ffeea64 3ffeeb50 13b85a86  
3fffff80:  40243656 3fffdab0 00000000 3fffdcb0  
3fffff90:  3ffeeb78 00000000 40000f65 3fffdab0  
3fffffa0:  40000f49 00006f80 3fffdab0 40000f49  
<<<stack<<<

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

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


INIT : Booting version: v2.0.0-dev8
FS   : Mount successful
INIT : Free RAM:27312
INIT : I2C
INIT : SPI not enabled
WIFI : Connecting... 1
WIFI : Connected! IP: 192.168.17.64
INIT : Normal boot

Regards
Shardan

Shardan · #13 Post by **Shardan** » 24 Apr 2017, 21:38

Addendum to the above:

I've removed the BMP180 for testing purposes with a bad result.
(Just emptied out the Task).
The website was no more reachable, even after resetting the nodeMCU.
I tried to send a RESET via serial to reconfigure - this was not possible.
Only very short after rebooting i was able to send a RESET and formatting the memory.
After that it was no longer possible to connect with WiFi, only reflashing the firmware
brought it back.

Reconfigured the RSSI and Uptime reading to FHEM... again, it works for a short while,
then it behaves erratic. i get sporadic readings every now and then. some tiems the RSSI
is working but the uptime not, then everything stops and so on.
Now, after around 20 minutes i see that data transfer comes up every now and then.
Uptime is configured to send every 60 seconds, updates to FEHM about every 3..5 minutes.
RSSI is configured to send every second, that runs for some "ticks" then stops, comes back after
some minutes running for some ticks and so on.

So it seems we got two different issues: The crashes might be caused from the BMP180 sketch,
as they disappeared when removing the task. The webpage is gone permanently showing "No data received"
and the data transfer is erratic... this is another issue.

Regards
Shardan

psy0rz · #14 Post by **psy0rz** » 24 Apr 2017, 21:51

ah the unreachable website is different reason: during the messagedelay the server is unresponsive. can you try setting the message delay to 0? (its at the advanced settings page)

this way it should keep responding at least. also disable that BMP180 plugin so we can rule out that its that one.

where is the code of that plugin? i can only find bmp280?

psy0rz · #15 Post by **psy0rz** » 02 May 2017, 01:07

Shardan, can you try again with the latest commit? I've fixed https://github.com/letscontrolit/ESPEasy/issues/253

Note that you can also just download the zip file from github now, without any of the previous isseus (submodules ) https://github.com/letscontrolit/ESPEas ... e/mega.zip

Shardan · #16 Post by **Shardan** » 02 May 2017, 13:55

psy0rz wrote: ↑02 May 2017, 01:07 Shardan, can you try again with the latest commit? I've fixed https://github.com/letscontrolit/ESPEasy/issues/253

Note that you can also just download the zip file from github now, without any of the previous isseus (submodules ) https://github.com/letscontrolit/ESPEas ... e/mega.zip

At the Office atm, i'll test as soon as i get home.

Regards
Shardan

DeNB3rt · #17 Post by **DeNB3rt** » 03 May 2017, 13:06

keep up the good work

Shardan · #18 Post by **Shardan** » 04 May 2017, 18:04

toffel969 wrote: ↑17 Apr 2017, 12:27 Hi

I want to report strange behaviour with the dev7 version of ESP easy.

Node (Wemos D1 pro mini + PIR+ Door switch+ Gas pulse counter + two relays) was running stable for about a week as standalone. Then I added my domoticz controller and everything seemed to work nicely. After some time (not sure how long, maybe 12h) the http connection started failing (weblog of esp) and the webserver became unresponsive. I could not open the controller page again after that, no matter how many reboots. I could however issue the reboot command by http and also managed to downgrade firmware to 148RC via OTA. Since then the node is running stable. No idea what caused the issue.

regards

Hello toffel969,

psy0rz has committed a bugfix to get rid of the controller problem.
Be aware, it is not in the compiled binaries zip file yet.

I have tested it with several ESP's connected to my FHEM server,
atm i have uptimes on all six test nodes of 1136 minutes reporting data to the server every five seconds.

It would be nice if you could test it against your domoticz server as i don't have domoticz.

Thanks in advance

Regards
Shardan

toffel969 · #19 Post by **toffel969** » 04 May 2017, 21:30

Yes I can do that. Is it included in the dev8 ? If yes I would just need to make one of my nodes report to domoticz instead of standalone. If no could I kindly ask you to provide me with the relevant 4mbbin file?

Shardan · #20 Post by **Shardan** » 04 May 2017, 21:43

It's not included in the actual bin files,
the fix was added later.
If you need a binary let me know.

Regards
Shardan

toffel969 · #21 Post by **toffel969** » 04 May 2017, 23:48

Yes please!

Shardan · #22 Post by **Shardan** » 05 May 2017, 14:50

toffel969 wrote: ↑04 May 2017, 23:48 Yes please!

A 4096-memsized one? Or do you need another flashsize?

Regards
Shardan

toffel969 · #23 Post by **toffel969** » 05 May 2017, 16:18

Shardan wrote: ↑05 May 2017, 14:50
toffel969 wrote: ↑04 May 2017, 23:48 Yes please!
A 4096-memsized one? Or do you need another flashsize?

Regards
Shardan

Yes a 4096-mesized. Target node is a Wemos D1 mini pro with 2 D18B20 Temperature probes, 4 buttons, analog soil moisture probe and an SSR connected directly to GPIO as output actuator.

regards

Sebastian

Shardan · #24 Post by **Shardan** » 05 May 2017, 17:01

Here you go.
This is the version i used for bulk testing, it is running on nodeMCU and WeMos for around 2 days without issues.
It is compiled with the "normal" option, so no testing or development parts are compiled in.

firmware_normal4096.zip: (346.57 KiB) Downloaded 523 times

.
Anyone who wants to use it:
This is NOT an official release from the developers but one i compiled myself.
Don't expect support. Further the 2.0.0 is a work in progress so instability and crashing may occur.

Use at own risk!

Regards
Shardan

toffel969 · #25 Post by **toffel969** » 05 May 2017, 19:13

Shardan wrote: ↑05 May 2017, 17:01 Here you go.
This is the version i used for bulk testing, it is running on nodeMCU and WeMos for around 2 days without issues.
It is compiled with the "normal" option, so no testing or development parts are compiled in.

firmware_normal4096.zip

.
Anyone who wants to use it:
This is NOT an official release from the developers but one i compiled myself.
Don't expect support. Further the 2.0.0 is a work in progress so instability and crashing may occur.

Use at own risk!

Regards
Shardan

Thanks, its flashed. I had dev-dev8 installed on the node, did OTA (node is already "in the field"). It reset all my devices and settings, will try to replace the devices (what were the gpios that I used !?! lack of documentation
is a bi**ch , particularly when there is nobody to blame but yourself

) and connect it to domoticz later when my daughter is sleeping.

Regards

Shardan · #26 Post by **Shardan** » 05 May 2017, 19:21

You're welcome

toffel969 · #27 Post by **toffel969** » 05 May 2017, 20:42

Shardan wrote: ↑05 May 2017, 19:21 You're welcome

Correction to above post... I flashed the wrong node

it was still running RC147, so no wonder I lost the devices and settings. However now I flashed the correct node, it didn't reset the settings. Now on the correct node I can also find my sensors

. Its reporting the data correctly to domoticz and seems to run stable. will let it run at least until tomorrow morning.

Shardan · #28 Post by **Shardan** » 05 May 2017, 21:04

Thanks for testing.
Check the free RAM on the webside, it should not decrease over time.

Regards
Shardan

toffel969 · #29 Post by **toffel969** » 05 May 2017, 22:55

Shardan wrote: ↑05 May 2017, 21:04 Thanks for testing.
Check the free RAM on the webside, it should not decrease over time.

Regards
Shardan

After 2h30 operation
Free Mem: 22064 (11720)
so far stable and reporting values to domoticz. So it seems to be working.

If I feel adventurous I will try to flash dev8 back tomorrow morning. Gegenversuch

Regards

Shardan · #30 Post by **Shardan** » 05 May 2017, 23:51

Would be interesting indeed.

Regards
Shardan

toffel969 · #31 Post by **toffel969** » 06 May 2017, 12:31

Shardan wrote: ↑05 May 2017, 23:51 Would be interesting indeed.

Regards
Shardan

Update:
Uptime: 0 days 15 hours 57 minutes
Free Mem: 21408 (11720)

still going strong. I consider this working and will now try to flash dev-dev8 to see if "this unknown sniplet of code

" (at least to me) fixes the problem with the controller/unresponsiveness or if it was somewhat already included in the binaries of version dev.8

toffel969 · #32 Post by **toffel969** » 06 May 2017, 13:32

I flashed the dev-dev8 version. It just continues to work and send values to Domoticz. Now running for 1h stable , web interface is responsive, Data is reported to Domoticz.

Free Mem: 21840 (28520)

With the previous bug, it would have stopped working quite some time ago. Now I am not sure if the problem arises when you setup the controller, because thus far, this is where it always started going wrong. Now i setup the controller in the "shardan"-version and just OTA the dev8.

I will continue to let it run on Dev8 for now

Shardan · #33 Post by **Shardan** » 06 May 2017, 15:00

Okay.

I analyzed the failing connection with help from psy0rz and we found the memory
rapidly decreasing when my FHEM controller is connected, a memory leak.
Psy0rz was able to reproduce the bug and fixed it, That's what is compiled into
the binary.

So it would be nice if you check the free RAM now and then.

Regards
Shardan

toffel969 · #34 Post by **toffel969** » 06 May 2017, 21:57

GIT version: v2.0.0-dev8
Local Time: 2017-05-06 21:55
Uptime: 0 days 9 hours 18 minutes
Load: 10% (LC=26251)
Free Mem: 21472 (28520)

still going strong. maybe psy0orz has an explanation. next would be dev 7 though im thinking thats a bit pointless

maluko · #35 Post by **maluko** » 07 May 2017, 01:46

GIT version: v2.0.0-dev8
Local Time: 2017-05-07 0:39
Uptime: 2 days 13 hours 51 minutes
Load: 20% (LC=22798)
Free Mem: 23656 (16312)

this work with 12 tasks ( 8 mpc switch, 1 wifi info, 1 uptime, 1 lux, 1 temp) all sending to domotiz.

edit: more rules for each mpc switch with timerset

toffel969 · #36 Post by **toffel969** » 07 May 2017, 10:45

maybe i jumped the gun. last night at 0:00 i checked again and the webserver was not responding. it was still reporting sensor data to domoticz and responding to pings. i also managed to reboot it via http , but webserver was definitly not working anymore. however after reboot it has now 9h uptime again. this is not the same behaviour i saw with dev7 (after reboot i had to hurry to ota to set itback to rc148) unfortunatly i cant give serial output though the node is already installed in a ip54 box outdoors.

Shardan · #37 Post by **Shardan** » 07 May 2017, 15:27

Hello toffel,

how long is the delay for reporting?
The memory leak occurred here every time the ESP reported to my FHEM server.
If i disabled the "Send data" in the tasks it stopped leaking.

So for testing we used delays of 1s and 5s bringing down the free ram very fast
until the ESP first stopped website, then stopped reporting and at last crashed.
Keep in mind I'm using FHEM, with other servers it may behave different.

Have a nice sunday

Regards
Shardan

PS: If that is possible with your server, maybe use "System Info" in an additional task and
report "Free RAM" to your server. I've logged the data with FHEM for being lazy

toffel969 · #38 Post by **toffel969** » 08 May 2017, 12:30

After the last crash I just restarted the node.

Unit: 12 GIT version: v2.0.0-dev8
Local Time: 2017-05-08 12:23 Uptime: 1 days 11 hours 57 minutes
Load: 8% (LC=26666) Free Mem: 21656 (28520)

Now its starting to get weird. I am running with a 60 second delay.

So maybe it wasn't the controller bug after all. Not sure what to think....

Shardan · #39 Post by **Shardan** » 08 May 2017, 13:47

hmm... interesting (Spock would say "fascinating"..)

Did you re-download the dev8 or is it the same file as before?

Would be the easiest explanation.

Regards
Shardan.

toffel969 · #40 Post by **toffel969** » 08 May 2017, 21:00

Shardan wrote: ↑08 May 2017, 13:47 hmm... interesting (Spock would say "fascinating"..)

Did you re-download the dev8 or is it the same file as before?

Would be the easiest explanation.

Regards
Shardan.

I didnt reflash between the crashes. So its still the very same version that malfunctioned
Unit: 12 GIT version: v2.0.0-dev8
Local Time: 2017-05-08 21:00 Uptime: 1 days 20 hours 30 minutes
Load: 14% (LC=24912) Free Mem: 20984 (28520)

Free mem now dropping a little bit

toffel969 · #41 Post by **toffel969** » 09 May 2017, 19:31

Unit: 12 GIT version: v2.0.0-dev8
Local Time: 2017-05-09 19:30 Uptime: 2 days 18 hours 50 minutes
Load: 10% (LC=26397) Free Mem: 21840 (28520)

Shardan · #42 Post by **Shardan** » 09 May 2017, 20:52

Strange.
Well i have to pass on that point.
With FHEM the issue was reproducable easily.
I've not hte slightest idea why it disappeared on your settings.

Regards
Shardan

toffel969 · #43 Post by **toffel969** » 10 May 2017, 10:07

Shardan wrote: ↑09 May 2017, 20:52 Strange.
Well i have to pass on that point.
With FHEM the issue was reproducable easily.
I've not hte slightest idea why it disappeared on your settings.

Regards
Shardan

Ya I also give up on understanding it... I will keep the dev8 on there and monitor.

pppp33 · #44 Post by **pppp33** » 14 May 2017, 19:36

Hi there,
while definitely solved the reboot issue, with uptime of days, now (with 2.0.0-dev8) I can't read my pulse counter (that worked in dev7)
Am I the only one ?
Thx & regards
Paolo

Shardan · #45 Post by **Shardan** » 14 May 2017, 20:22

Hi Paolo,

i don't use a pulse counter atm so i can't say.
It might be better to open a new thread for that as noone will find your posting here.

Regards
Shardan

Who is online