Moderators: grovkillen, Stuntteam, TD-er
-
alabama
- Normal user
- Posts: 90
- Joined: 24 Nov 2017, 10:04
#1
Post
by alabama » 09 Oct 2018, 10:38
Feedback:
I'm running a NodeMCU-V3 with mega-20180826. Sometimes I get the message "failed to fetch", but after that everything continues to work. Only sometimes not. This happens very rarely, only every some days or even some weeks. But today it happens twice in 6 hours. Then the message is repeaded very often and then the contact from breaks. I can only do a hard reset (switch off voltage). I think the NodeMCU-V3 continues to work but it couldn't build up the network connection. The Wifi RSSI is between -79 and -83.
Here is my system info
Code: Select all
Build
20102 - Mega
Libraries
ESP82xx Core 00000000, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3
GIT version
mega-20180826
Plugins
46 [Normal]
Build time
Aug 26 2018 02:14:44
Binary filename
ESP_Easy_mega-20180826_normal_ESP8266_4096.bin
-
grovkillen
- Core team member
- Posts: 3621
- Joined: 19 Jan 2017, 12:56
- Location: Hudiksvall, Sweden
-
Contact:
#2
Post
by grovkillen » 09 Oct 2018, 12:04
Are you talking about the web log viewer? If so it's just that the unit didn't respond within time. The log will make a new try within ten seconds (or so) and if a response is then received it'll start to get the log entries again. Nothing alarming.
-
alabama
- Normal user
- Posts: 90
- Joined: 24 Nov 2017, 10:04
#3
Post
by alabama » 09 Oct 2018, 12:29
Yes, I talk about that. So the reason that my connection sometimes completely breaks must be something other.
Thank you
-
grovkillen
- Core team member
- Posts: 3621
- Joined: 19 Jan 2017, 12:56
- Location: Hudiksvall, Sweden
-
Contact:
#4
Post
by grovkillen » 09 Oct 2018, 13:15
How long are you keeping the log viewer running? I don't ever clear the buffer so in time the browser will crash. Never thought anyone would use it for that long.
Maybe a buffer limit should be added...
-
alabama
- Normal user
- Posts: 90
- Joined: 24 Nov 2017, 10:04
#5
Post
by alabama » 09 Oct 2018, 13:51
Oh, sometimes really very long. I have run some virtual windows on my NAS and that ist running 7/24. So sometimes I start the log viewing and close the remote of the VM, then it runs over night and even longer. But when I know this I will stop it in future. The log is also written to tha NAS with the advanced settings and I wondered why there ist no message about this failure.
-
grovkillen
- Core team member
- Posts: 3621
- Joined: 19 Jan 2017, 12:56
- Location: Hudiksvall, Sweden
-
Contact:
#6
Post
by grovkillen » 09 Oct 2018, 14:44
The failure is on browser side, not node side. Well indirect it could be the node if it's crashing or something.
-
alabama
- Normal user
- Posts: 90
- Joined: 24 Nov 2017, 10:04
#7
Post
by alabama » 09 Oct 2018, 14:58
Okay, the the total break of the connection in some cases isn't the "failed to fetch".
But what happens, wenn the Wifi connection is down for some time? Some devices try several times to reconnect but stop if this is not successful for longer time. I see in the log that sometimes the node reconnects. But of cause if this is not successful, I get no information.
-
grovkillen
- Core team member
- Posts: 3621
- Joined: 19 Jan 2017, 12:56
- Location: Hudiksvall, Sweden
-
Contact:
#8
Post
by grovkillen » 09 Oct 2018, 15:45
The fetch error is just that, the fetch didn't succeed. It is not the actual log that is displaying that error, it's the web browser. So why it did not succeed is unknown, could be anything between the browser and the node.
-
alabama
- Normal user
- Posts: 90
- Joined: 24 Nov 2017, 10:04
#9
Post
by alabama » 09 Oct 2018, 16:10
Yes, I got it, thank you for your patience.
Who is online
Users browsing this forum: Ahrefs [Bot] and 3 guests