Warnings "Request failed with status code 502/504" #412

Draexl · 2022-12-24T10:26:54Z

Is there an existing issue for this?

I have searched the existing issues and no issue is describing my issue

The problem

I found this messages in my Log

2022-12-24 09:43:11.062 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 502 for command GetPos
2022-12-24 09:48:08.146 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 502 for command GetPos
2022-12-24 09:57:08.253 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 502 for command GetCleanSum
2022-12-24 10:08:05.171 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 504 for command GetCleanSum
2022-12-24 10:40:08.783 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 502 for command GetSleepStatus
2022-12-24 10:53:05.606 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 502 for command GetCleanSum
2022-12-24 11:05:14.763 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 502 for command GetCleanSpeed
2022-12-24 11:08:05.672 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 502 for command GetCleanSpeed
2022-12-24 11:09:08.039 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 502 for command GetCleanState
2022-12-24 11:15:08.794 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 502 for command GetSleepStatus
2022-12-24 11:19:08.263 - warn: ecovacs-deebot.0 (10736) Error message received: Received error message: Request failed with status code 502 for command GetCleanSum

Version v1.4.8
Model: DEEBOT 710

With which model does the problem occur?

Deebot 710/711/711s

From which source you have installed the adapter?

Stable (default)

Version of the ioBroker adapter ("info.version")

v1.4.8

Version of the ecovacs-deebot.js library ("info.library.version")

0.9.0-beta.2

Version of the JS controller

4.0.23

Version of Node.js

v16.19.0

Operating system

Linux

Anything in the logs that might be useful?

Additional information

Which "other" models are you using?

Ecovacs device class ("info.deviceClass")

Communication protocol ("info.library.communicationProtocol")

None

Is the canvas module installed? ("info.library.canvasModuleIsInstalled")

None

The text was updated successfully, but these errors were encountered:

mrbungle64 · 2022-12-24T10:38:36Z

@Draexl

Currently, this happens more often.

Useful links:

mrbungle64 · 2022-12-24T12:29:53Z

@Draexl

In Deebot 4 Home Assistant I also get similar errors today:

Logger: deebot_client._api_client
Source: runner.py:120
First occurred: 13:20:28 (1 occurrences)
Last logged: 13:20:28

Error calling API (504): https://portal-eu.ecouser.net/api/iot/devmanager.do

Logger: deebot_client.commands.common
Source: runner.py:120
First occurred: 13:10:00 (92 occurrences)
Last logged: 13:24:11

Command "getCachedMapInfo" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
Command "getSpeed" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
Command "getStats" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
Command "getPos" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}
Command "getChargeState" was not successfully: {'ret': 'fail', 'errno': 500, 'debug': 'wait for response timed out'}

mrbungle64 · 2022-12-25T20:00:29Z

@Draexl

I still get several timeouts per day, but I think that we have to be patient until Ecovacs takes care of it ...

Bullet586 · 2022-12-27T10:39:36Z

Version v1.4.8
Model: DEEBOT 850

With which model does the problem occur?
Deebot 850

From which source you have installed the adapter?
Stable (default)

Version of the ioBroker adapter ("info.version")
v1.4.8

Version of the ecovacs-deebot.js library ("info.library.version")
0.9.0-beta.2

Version of the JS controller
4.0.23

Version of Node.js
v16.19.0

Operating system
Linux

Same Problem from my side, the alerts began a few days ago.

Does anybody know is that a problem from the evovacs server or from the adapter??

Best Regards

mrbungle64 · 2022-12-27T19:24:30Z

"... a 502/504 error is usually not something you can fix, but requires a fix by the web server or the proxies ..."

502 Bad Gateway
The HyperText Transfer Protocol (HTTP) 502 Bad Gateway server error response code indicates that the server, while acting as a gateway or proxy, received an invalid response from the upstream server.

504 Gateway Timeout
The HyperText Transfer Protocol (HTTP) 504 Gateway Timeout server error response code indicates that the server, while acting as a gateway or proxy, did not get a response in time from the upstream server that it needed in order to complete the request.

Note: A Gateway might refer to different things in networking and a 502/504 error is usually not something you can fix, but requires a fix by the web server or the proxies you are trying to get access through.

Sources (which I had already linked above):

@Bullet586

Does anybody know is that a problem from the evovacs server or from the adapter??

It is very unlikely that this errors are caused by the adapter.

Btw.: Do you really own a Deebot 850?

Bullet586 · 2022-12-27T19:30:40Z

No sorry my bad, you are right! It's an ECOVACS DEEBOT OZMO 950,

So what I hear is we can do nothing at the Moment.

Thanks for the good news, I thought there is something wrong on my system.

mrbungle64 · 2022-12-27T19:41:02Z

To make it a little clearer, the warning messages say:

this part means that the adapter (via underlying library) received an error message:
"Error message received: [ Received error message ... ]"
followed by the actual error message:
"Request failed with status code 504 for command getSleep"

That means that a "502 Bad Gateway" or "504 Gateway Timeout" occurred on the server side when (in this example) the "getSleep" command was executed.

mrbungle64 · 2022-12-27T19:42:05Z

@Bullet586

I thought there is something wrong on my system.

No there's nothing wrong with your system ... you're "not alone" 😉

krobipd · 2022-12-28T13:42:48Z

hey, I have the same "problems" everything works fine but the log is filling with this messages. ozmo 950 ;-)

mrbungle64 · 2022-12-28T21:44:44Z

@krobipd @Draexl @Bullet586

You can set the interval ("Abfrage-Intervall (Sekunden)") to 600 seconds if you use the Ecovacs mobile app only rarely.

mrbungle64 · 2022-12-30T16:09:11Z

@krobipd @Draexl @Bullet586

Do any of you still have warning messages?
I think that Ecovacs has fixed the hiccups...

krobipd · 2022-12-30T16:23:58Z

@krobipd @Draexl @Bullet586

Do any of you still have warning messages? I think that Ecovacs has fixed the hiccups...

today only in the very early hours. (0-1 am). nothing since then.

Bullet586 · 2022-12-30T17:46:38Z

No warnings anymore (at the moment) 👍🏻

mrbungle64 · 2022-12-30T18:11:41Z

@Draexl

Please close this issue if you have no more warnings either.

Draexl · 2022-12-30T18:13:02Z

All fine, thanks

Draexl added Potential bug Potential bug Verification Verification labels Dec 24, 2022

mrbungle64 changed the title ~~Warnings "10736"~~ Warnings "Request failed with status code 502/504" Dec 24, 2022

mrbungle64 removed the Potential bug Potential bug label Dec 24, 2022

This comment was marked as outdated.

Sign in to view

mrbungle64 mentioned this issue Dec 25, 2022

ioBroker Warn Message mrbungle64/ecovacs-deebot.js#271

Closed

1 task

mrbungle64 pinned this issue Dec 25, 2022

Draexl closed this as completed Dec 30, 2022

mrbungle64 unpinned this issue Jan 15, 2023

mrbungle64 mentioned this issue Feb 9, 2023

Request failed with status code 502/504 #432

Closed

1 task

mrbungle64 mentioned this issue Mar 19, 2023

getaddrinfo ENOTFOUND api-app.dc-ww.ww.ecouser.net bwp91/homebridge-deebot#131

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Warnings "Request failed with status code 502/504" #412

Warnings "Request failed with status code 502/504" #412

Draexl commented Dec 24, 2022 •

edited by mrbungle64

Loading

mrbungle64 commented Dec 24, 2022

mrbungle64 commented Dec 24, 2022

This comment was marked as outdated.

This comment was marked as outdated.

mrbungle64 commented Dec 25, 2022

Bullet586 commented Dec 27, 2022 •

edited

Loading

mrbungle64 commented Dec 27, 2022 •

edited

Loading

Bullet586 commented Dec 27, 2022 •

edited

Loading

mrbungle64 commented Dec 27, 2022

mrbungle64 commented Dec 27, 2022 •

edited

Loading

krobipd commented Dec 28, 2022

mrbungle64 commented Dec 28, 2022 •

edited

Loading

mrbungle64 commented Dec 30, 2022

krobipd commented Dec 30, 2022

Bullet586 commented Dec 30, 2022

mrbungle64 commented Dec 30, 2022

Draexl commented Dec 30, 2022

Warnings "Request failed with status code 502/504" #412

Warnings "Request failed with status code 502/504" #412

Comments

Draexl commented Dec 24, 2022 • edited by mrbungle64 Loading

Is there an existing issue for this?

The problem

With which model does the problem occur?

From which source you have installed the adapter?

Version of the ioBroker adapter ("info.version")

Version of the ecovacs-deebot.js library ("info.library.version")

Version of the JS controller

Version of Node.js

Operating system

Anything in the logs that might be useful?

Additional information

Which "other" models are you using?

Ecovacs device class ("info.deviceClass")

Communication protocol ("info.library.communicationProtocol")

Is the canvas module installed? ("info.library.canvasModuleIsInstalled")

mrbungle64 commented Dec 24, 2022

mrbungle64 commented Dec 24, 2022

This comment was marked as outdated.

This comment was marked as outdated.

mrbungle64 commented Dec 25, 2022

Bullet586 commented Dec 27, 2022 • edited Loading

mrbungle64 commented Dec 27, 2022 • edited Loading

Bullet586 commented Dec 27, 2022 • edited Loading

mrbungle64 commented Dec 27, 2022

mrbungle64 commented Dec 27, 2022 • edited Loading

krobipd commented Dec 28, 2022

mrbungle64 commented Dec 28, 2022 • edited Loading

mrbungle64 commented Dec 30, 2022

krobipd commented Dec 30, 2022

Bullet586 commented Dec 30, 2022

mrbungle64 commented Dec 30, 2022

Draexl commented Dec 30, 2022

Draexl commented Dec 24, 2022 •

edited by mrbungle64

Loading

Bullet586 commented Dec 27, 2022 •

edited

Loading

mrbungle64 commented Dec 27, 2022 •

edited

Loading

Bullet586 commented Dec 27, 2022 •

edited

Loading

mrbungle64 commented Dec 27, 2022 •

edited

Loading

mrbungle64 commented Dec 28, 2022 •

edited

Loading