Deebot Bot no longer available #293
Comments
Same issue here seemingly. Deebot N8. This was in the logs
|
@Mod74 The error code 4200 indicates that your device has poor WiFi connection. Can you confirm that your robot has a good wifi signal? @jonoscott Can you please check your logs and also activate debug logs |
Hi @edenhaus Logs are below, have changed the UserID, although I fear I should have probably changed some other stuff as well, hopefully not though.
|
Confirming I have the same issue with DEEBOT OZMO 920 |
Thanks for the quick reply, but like the other guy the bot does seem to have fine Wi-Fi. I did notice this started happening after it had been switched off with the on/off switch. Going to try rebooting it using that. |
I can't reproduce your errors. On my account the api works correctly. Do you have the technical skills to intercept the traffic between the app and the ecovacs servers? |
Sorry, I'm afraid not, I thought I could possibly use Wireshark, but that wouldn't work as it doesn't have an app that I could use. If you are able to give me a rough idea on what to do I may be able to work it out. |
Do you have an iPhone or iPad? |
Hi, I have access to an iPhone, and more than happy to follow some steps if you'd put them up. Thanks. |
Yeah, I have access to an iPhone as well... I have an iPad somewhere as well, but would need to track that down. either way, I've got soemthing which hopefully will work. |
This comment was marked as off-topic.
This comment was marked as off-topic.
The problem is independent of HA version, instead Ecovacs has change their api. I need try to find out whats different. The problem is only I cannot reproduce the error. For intercepting the traffic of the app, you could use https://mitmproxy.org/ A tutorial about is available under https://jasdev.me/intercepting-ios-traffic (Skip the part of the macOS if you use docker) After you have activated the certificate, you will see the requests in the mitmproxy UI. All requests of the hole device will be displayed there, so I recommend to close other apps and only use the ecovacs app. |
Can you please all of you share Diagnostic Information? Maybe we have a regional specific problem |
I just observed that the status in HA was not updated as I manually started the deebot using the app. Service deebot.refresh is working, but e.g. battery is currently still not updated automatically. But I've seen that the app also had a huge delay in displaying actual time and cleaned area. These were values from yesterday, but the map was working live/"real time". So maybe ecovacs has some other difficulties right now? I have similar logs to these here: #293 (comment) But in my case it's URL https://portal-eu.ecouser.net/api/appsvr/app.do for Europe. Here is the excerpt from the logs. It got the status DOCKED until 09:19 where I update the status with deebot.refresh service, but I started cleaning around 09:04. And the vacuum is still cleaning right now. And the state seems to transition between docked and cleaning. But HA still says cleaning.
Update: I reloaded the whole integration in HA and it seems that everything is working fine again for now. |
Same problem on T10 |
@monotonus Somehow the mqtt client is not getting any messages (on your instance) Normally you should get during a clean job a lot of debug messages. See Probably ecovacs is not anymore publishing this messages to long connecting clients. I will implement a check for it and reconnect if required. It's only a workaround but ecovacs is not sharing any information so I will go for the workaround. Strange is only, that I don't can reproduce this problem in my setup. Can you confirm that you don't have firewall or other things, which could create problems with mqtt? Also note that the mqtt url is different from the rest api url. |
Same problem with my Ozmo T8. I turned it off and back on with the red switch, then disabled and re-enabled the integration and it came right up, but without doing anything to vacuum or HA, it "became unavailable" 1 minute after turning on:
|
@fowie There is a task, which checks each minute if the bot is available. In your case the ecovacs server has answered that your bot is offline and therefore all entities become unavailable. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
just a brief reminder that this is not stale ;) |
I installed the 1.6.0b1 and I'm still having the issue where the deebot is available for 30-60 seconds right after an integration restart, but then it becomes unavailable until the next time I reload the integration. Let me know which logs you'd like to see. |
@fowie I need the debug logs from start until it is unavailable +2 minutes. Do not reload the integration this time as I want to see what happen after it is unavailable |
Here you go. Looks like it just turns the device to "Unavailable" because the messages from the API haven't changed? It works fine for the first minute after the plugin becomes active, but after 1 minute it marks everything as "unavailable", but the log just says |
@fowie you included in the log only the level warning, but I need the logs at level debug |
@edenhaus I patched and MITM'ed the app. The GetGlobalDeviceList returns two devices of status 1 and 0, which would reflect how the app UI initially appears. After the second device appears on screen within the Android app the GetBatteryInfo and GetChargeState commands are issued and it seems to "wake up" and appear normally again. Perhaps your integration assumes a "live" status on the initial device call and is updated to unavailable when it reads the 0 on a subsequent call? It appears the app is considering successful state messages as evidence of the device state. I saved off a few of the login, auth and device calls. |
settings set to EU with t8 AIVI |
Every minute the component makes one api call to get the status of all devices. It depends on that, if a device will be marked as available or not in HA. @michaelwoods Can you please verify, if the T8 will be marked offline in the app after some minutes? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
The app didn't change after a little over 10 minutes, the device remained active. |
Sorry, here you go. |
Probably ecovacs has changed something on their api (for at least newer models). I cannot trust anymore the status attribute... I have to rewrite the available check. Thanks for testing and your feedback :) |
To add a little extra information: I edited My automation did trigger the vacuum successfully to start its cycle, however as expected there's no status change within HA as it remains in the docked state. |
@michaelwoods There should be a state change. Can you check or attach your debug logs 😊 |
Quick status update:
|
I released |
So far so good.... Been available for the last 2 hours since updating to 2.0.0b3. Thanks! |
Hey, I just setup HA and I am also facing this. How do I update the integration to 2.0.0b3? |
Sorry, I didn't double-check the beta release number and it should be under 1.6.0b3. @JohannesPtaszyk To install using HACS, click integrations > Deebot 4 Home Assistant, three vertical dot icon (top right), redownload, then make sure the Show Beta version is selected, select the 1.6.0b3 version and download. Make sure to restart Home Assistant after installation is complete. P.S. still going strong after 12 hours |
Updated to 1.6.0b3 and the vacuum ran without me resetting the integration today! Thank you!!
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: elykrk ***@***.***>
Sent: Wednesday, May 31, 2023 12:15:31 PM
To: DeebotUniverse/Deebot-4-Home-Assistant ***@***.***>
Cc: Spencer Fowers ***@***.***>; Mention ***@***.***>
Subject: Re: [DeebotUniverse/Deebot-4-Home-Assistant] Deebot Bot no longer available (Issue #293)
Sorry, I didn't double-check the beta release number and it should be under 1.6.0b3.
To install using HACS, click integrations > Deebot 4 Home Assistant, three vertical dot icon (top right), redownload, then make sure the Show Beta version is selected, select the 1.6.0b3 version and download. Make sure to restart Home Assistant after installation is complete.
—
Reply to this email directly, view it on GitHub<#293 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AACMTJZNQT2JNQO53EMC2ZLXI6KFHANCNFSM6AAAAAAUK3HFS4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
1.6.0b3 works for my N8 Pro+, sadly we do not support XML-based robots right now. So 900/901 do not work |
Question
Wondering if anyone else is currently having issues with the Deebot T9+ no longer showing as available in Home Assistant.
I've removed it from Home Assistant and re added it to Home Assistant and it installs, but still unavailable. I know this was last working on one of the 2022 builds, but definately doesn't appear to be working with 2023.1.7, python_version 3.10.7
Additional information
No response
The text was updated successfully, but these errors were encountered: