nicoduj / homebridge-deebotEcovacs

Homebridge Deebot (from Ecovacs) plugin

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Homebridge cannot find my deebot vaccum 920,

axiangz opened this issue · comments

I already follow the instruction on how to configure connection with my account. But homebridge cannot find my deebot 920 vaccum eventhough i already set all the connection string. Any help?

@axiangz

The Deebot Ozmo 920 usually works fine with the plugin.
What does the log output?

@axiangz

You can try if it works if you set the country manually in the configuration:

"countryCode": "ID"

@axiangz
Have you already restarted homebridge after changing the country code?
What country or region are you using for your account in the mobile app?

@axiangz

Can you please check if the following messages appear in the log after restarting Homebridge:

[25.12.2020, xx:xx:xx] [DeebotEcovacs] INFO - connected
[25.12.2020, xx:xx:xx] [DeebotEcovacs] INFO - getDeebots : [ ..., "class": "vi829v", ... ]

If these messages appear, please check if there is a "class" element in the output and post the value of the "class" element (should be something like "vi829v").

Btw: Is "Deebot 920" the full name of the model or is it "Deebot OZMO 920"?

Is this correct?
[cid:DF67AF0E-6D86-446A-BF90-8316FD30F683-L0-001] [cid:692C6273-2367-4D84-B7A5-33C24E823F26-L0-001]

No, I need the value of the "class" attribute from the "getDeebots" message (should be "vi829v"):

[25.12.2020, xx:xx:xx] [DeebotEcovacs] INFO - getDeebots : [ ..., "class": "vi829v", ... ]

And also the full name of the model (should be "Deebot OZMO 920")

@axiangz

Do you get some or maybe all of the following messages (after restarting Homebridge)?

[25.12.2020, xx:xx:xx] [DeebotEcovacs] Initializing DeebotEcovacs platform...
[25.12.2020, xx:xx:xx] [DeebotEcovacs] INFO - API :AS/ID
[25.12.2020, xx:xx:xx] [DeebotEcovacs] DidFinishLaunching
[25.12.2020, xx:xx:xx] [DeebotEcovacs] INFO - connected

Here what i get after restarting homebridge, after “DidFinishLaunching” msg than comes out deebot cannot find any device message

Sent from my iPhone [cid:CEDB23BB-7153-45A8-BC96-FACFFF3BC7B8-L0-001][cid:F6245591-D9A5-4C2B-9779-387E3040146D-L0-001] On 25 Dec 2020, at 22.07, Sascha notifications@github.com wrote: [cid:0044C5F7-8234-4124-957D-2FCC66D5A12E-L0-001]  @axiangzhttps://github.com/axiangz Do you get some or maybe all of the following messages? [25.12.2020, xx:xx:xx] [DeebotEcovacs] Initializing DeebotEcovacs platform... [25.12.2020, xx:xx:xx] [DeebotEcovacs] INFO - API :AS/ID [25.12.2020, xx:xx:xx] [DeebotEcovacs] DidFinishLaunching [25.12.2020, xx:xx:xx] [DeebotEcovacs] INFO - connected — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#46 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKDTGCOQQJ2WPBBDRC2B2LLSWSTDVANCNFSM4VILCQ5A. [cid:692C6273-2367-4D84-B7A5-33C24E823F26-L0-001]

@axiangz
sorry, I cannot see any output in your post

@axiangz

Please post the log output and also please use the GitHub Website for posting your replies.
It's not easy to help you if you only post snippets of the log output ;)

Here what i get after restarting my homebridge
First this log appear

image

Second this log

image

Third this log

image

Then the rest is this log

image

@axiangz

There may be a problem with your Internet connection:

getaddrinfo EAI_AGAIN portal-as.ecouser.net

These are 2 quotes from Google search results:
"EAI_AGAIN is a DNS lookup timed out error, means it is a network connectivity error or proxy related error"
"EAI_AGAIN means the DNS server replied that it cannot currently fulfill the request"

I'm also able to reach this address (portal-as.ecouser.net)

What should i do? This is what i get now

image

@axiangz

It seems that you are successfully logged in, but no bots were found in your account.
Are you sure your account and device are set up properly?

Yes i can use my deebot 920 using the ecovacs app on my device and using alexa device too. I just dont know why it could not discover my device using homebridge. Any suggestion what else to do?
image

@axiangz

Please enable Debug Mode in Homebridge Settings ("Startup Options" => "Homebridge Debug Mode") and post the log output after restarting Homebridge.

Here is the log output after changing homebridge debug mode

image

@axiangz

ok, please check the nickname in your configuration ("Name of the deebot to publish") and the name (nickname) of the device in your Ecovacs account.

There are 3 options how your device can be detected:
1.) You leave the field "Name of the deebot to publish" blank
2.) The nickname in the configuration of the plugin has to be equal to the nickname in your Ecovacs account (which is currently blank)
3.) You can also use the "name" ("E05612...") of that device in the configuration of the plugin

I recommend the first option, since you have only one device.

So how to write in the config file? I already match the name in config same as nickname in ecovacs app

@axiangz

So how to write in the config file? I already match the name in config same as nickname in ecovacs app

Have you already set a nickname in the Ecovacs App?
When the screenshot was taken, no nickname was set yet ("nick": null)...

In the config file of Homebridge countryCode and deebotNames should look like this:

"countryCode": "ID",
"deebotNames": [
                "Deebot Ozmo 920"
            ],

But you have to make sure that you're using the exact same nickname in Ecovacs app.

So you mean, if i use nickname as "Deebotic" on my ecovac app, then the config i have to match the deebotname as "Deebotic" too? If thats the case i already input the same nickname on ecovac app as deebotname on configuration

This is on my ecovac app

image

This is what i write in the config

image

So you mean, if i use nickname as "Deebotic" on my ecovac app, then the config i have to match the deebotname as "Deebotic" too? If thats the case i already input the same nickname on ecovac app as deebotname on configuration

@axiangz

Yes. If it's still not working please send me screenshot of the log output again.

Still cannot find the device, here is the log

image

@axiangz

Now I see what the problem is: "Deebotic" is the preset name in the Ecovacs App.
You still have to set that name manually.
You can use "Deebotic" but you have to type it in manuallly (and save it).

No luck i type manually, and i also try change the name and the nickname with other name also no luck image

No luck i type manually, and i also try change the name and the nickname with other name also no luck

@axiangz

The value of the nick attribute is still null (empty).

You can also try one of the other 2 options:

There are 3 options how your device can be detected:

1.) You leave the field "Name of the deebot to publish" blank

2.) The nickname in the configuration of the plugin has to be equal to the nickname in your Ecovacs account (which is currently blank)

3.) You can also use the "name" ("E05612...") of that device in the configuration of the plugin

@axiangz

I recommend to choose option 3:

"countryCode": "ID",
"deebotNames": [
                "E05612789B09HD2V0354"
            ],

Thank you, it find my deebot. I just leave the nickname blank then it find it 🙏🏼

Hi, sorry, was not available those days. thank you @mrbungle64 for dealing with the issue !