You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and no issue is describing my issue
The problem
i have some warnings:
ecovacs-deebot.0
2022-12-25 19:45:05.022
warn
Error message received: Received error message: Request failed with status code 502 for command getBlock
ecovacs-deebot.0
2022-12-25 19:41:45.847
warn
Error message received: Received error message: Request failed with status code 502 for command getAutoEmpty
ecovacs-deebot.0
2022-12-25 19:41:37.627
warn
Error message received: Received error message: Request failed with status code 502 for command getPos
ecovacs-deebot.0
2022-12-25 19:36:40.428
warn
Error message received: Received error message: Request failed with status code 502 for command getBreakPoint
ecovacs-deebot.0
2022-12-25 19:22:53.117
warn
Error message received: Received error message: Request failed with status code 502 for command getCleanCount
With which model does the problem occur?
Deebot T8 series
From which source you have installed the library?
other
Version of the ecovacs-deebot.js library
Adapter 1.4.8
Version of Node.js
v16.19.0
Operating system
Linux
Anything in the logs that might be useful?
i see it today in the logs and i don't know how it is coming...?
in my mobile android app is no message or warning.
have you any solutions to fix the warning?
the robot is also cleaning and do his job every day.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
The problem
i have some warnings:
With which model does the problem occur?
Deebot T8 series
From which source you have installed the library?
other
Version of the ecovacs-deebot.js library
Adapter 1.4.8
Version of Node.js
v16.19.0
Operating system
Linux
Anything in the logs that might be useful?
Additional information
No response
The text was updated successfully, but these errors were encountered: