Page 1 of 1
EspEasy: HTTP : connection failed
Posted: 23 May 2019, 08:47
by riker1
Hi
having a questions:
what exactly is this message?
Code: Select all
<3>1 2019-05-22T11:43:29.887978+02:00 ESPHOST EspEasy - - - EspEasy: HTTP : connection failed
what is the root cause?
what is the rule behind it?
Is it outgoing or incoming?
does this mean mqtt connection or which connection?
Thanks
Re: spEasy: HTTP : connection failed
Posted: 23 May 2019, 20:41
by ThomasB
HTTP : connection failed is a log message used in older versions of ESP Easy. It originates from a controller plugin that is unable to connect.
If that doesn't help you narrow it down then more details are needed. For example: What version are you running? What Controllers are enabled? What conditions provoke the error? And any other info that better describes your installation.
- Thomas
Re: EspEasy: HTTP : connection failed
Posted: 26 May 2019, 19:59
by riker1
Hi Thomas,
I am running different version
- lastest firmware (Test, normal, etc) , some december fw which I found more stable,
on different ESPs: ESP01, NodeMCU,
Always having 2 controllers:
- fhem
- mqtt
concerning : What conditions provoke the error? And any other info that better describes your installation.
That is what I do not know and have to identify:-)
Devices are simple:
Some rules to check status and connection to prevent AP Mode
MQTT Status publish events.
Trying to nail it down...
Re: EspEasy: HTTP : connection failed
Posted: 26 May 2019, 20:18
by ThomasB
I am running different version
Which version (exact release name) were you running when the posted log message was seen?
The log message format can vary with release. If you post the exact release version and exact log message (copy/paste) it will be easier to find which plugin sent it.
- Thomas
Re: EspEasy: HTTP : connection failed
Posted: 26 May 2019, 22:46
by riker1
Hi Thomas
for instance I am having
Code: Select all
Build:⋄ 20103 - Mega
Libraries:⋄ ESP82xx Core 2_4_2, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3 PUYA support
GIT version:⋄ mega-20190212
Plugins:⋄ 74 [Normal] [Testing]
log example
:
Code: Select all
4442013: Command: event
4442015: EVENT: var_kt=-31.0
4442073: ACT : taskvalueset,5,3,-31.0
4442089: Command: taskvalueset
4442130: ACT : Publish ESP_Kuehlschrank/Sendto,fq4_kt=-31.0 event>-31.0< um -192.168.0.149-2019-05-26 22:39:10
4442147: Command: publish
4442354: DS : Temperature: -22.13 (28-ff-75-96-92-16-5-1)
4442358: EVENT: KSW_temp#KSW_temp=-22.13
4443040: DS : Temperature: 24.00 (28-b4-6e-77-91-10-2-8b)
4443046: EVENT: Kueche_Temp#T-Kueche=24.00
4445781: HTTP : C009 connection failed (1/80)
4446189: SYS : 74.00,11536.00,-61.00,91.10
4446194: EVENT: System_Info#uptime=74.00
4446419: EVENT: System_Info#RamFree=11536.00
4446645: EVENT: System_Info#RSSI=-61.00
4446905: EVENT: System_Info#SysLoad=91.10
4447508: Command: event
4447510: EVENT: var_kt=-31.0
4447565: ACT : taskvalueset,5,3,-31.0
4447581: Command: taskvalueset
4447622: ACT : Publish ESP_Kuehlschrank/Sendto,fq4_kt=-31.0 event>-31.0< um -192.168.0.149-2019-05-26 22:39:14
4447639: Command: publish
4447796: WD : Uptime 74 ConnectFailures 1 FreeMem 9800 WiFiStatus 3
4450188: HTTP : C009 connection failed (2/80)
4453269: HTTP : C009 connection failed (3/80)
4453398: Command: taskvalueset
4453440: ACT : Publish ESP_Kuehlschrank/Send_Terrasse,t=20.3 event>20.3< um -192.168.0.149-2019-05-26 22:39:19
4453457: Command: publish
4453582: Command: event
4453583: EVENT: var_kt=-31.0
4453638: ACT : taskvalueset,5,3,-31.0
4453653: Command: taskvalueset
4453695: ACT : Publish ESP_Kuehlschrank/Sendto,fq4_kt=-31.0 event>-31.0< um -192.168.0.149-2019-05-26 22:39:19
Thanks a lot for supporting
T
Re: EspEasy: HTTP : connection failed
Posted: 26 May 2019, 23:16
by ThomasB
In that example the C009 connection failure is referring to the FHEM HTTP controller. It's saying the first attempt (out of 80 allowed) was not successful. But it could have success in another attempt (review the logs).
Not much more to go on, but at least it's a place to start the investigation.
- Thomas
Re: EspEasy: HTTP : connection failed
Posted: 27 May 2019, 06:52
by riker1
perfect thanks
Will investigate further
T