Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yeedi 3 Support Request #164

Open
thegeekybeng opened this issue Mar 29, 2024 · 12 comments
Open

Yeedi 3 Support Request #164

thegeekybeng opened this issue Mar 29, 2024 · 12 comments

Comments

@thegeekybeng
Copy link

  • Please explain your feature request in a one or two sentences.
    The plugin works fine, only realising that my device, Yeedi 3 is not supported.

  • Is your feature request related to a problem? Please describe.
    No

  • Any particular ECOVACS devices that this relates to?
    None.

  • Anything else?
    Greatly appreciated and if you do figure out a support for Yeedi 3, let me buy you a coffee.

@mrbungle64
Copy link

@thegeekybeng

The plugin works fine

If you say that it works fine, what doesn't (because you request support)?

only realising that my device, Yeedi 3 is not supported.

What exact model do you have?

@mrbungle64
Copy link

@thegeekybeng

only realising that my device, Yeedi 3 is not supported.

What exact model do you have?

Is it a yeedi "Floor 3 Station" or a "Floor 3+"?

@thegeekybeng
Copy link
Author

I have just checked. It is floor 3+.

@mrbungle64
Copy link

@thegeekybeng

I have just checked. It is floor 3+.

Please try the current beta of this plugin (6.1.2-beta.2).

I updated the model dict information in the library for the "Floor 3+".
I think it was linked to the wrong model template.

The plugin works fine

If you say that it works fine, what doesn't (because you request support)?

Btw. You still haven't given us any information about what is currently not working ...

@thegeekybeng
Copy link
Author

Ah that explains. Well from what I can observe the codes works fine just that I cannot seem to locate the Yeedi 3+ ... and noted that it wasn't listed on the list of supported devices thus I approached you instead.

@mrbungle64
Copy link

@thegeekybeng

Well from what I can observe the codes works fine just that I cannot seem to locate the Yeedi 3+

What does this mean now? Have you already tried the current beta?

@thegeekybeng
Copy link
Author

yea I have just successfully installed the beta but it still reflects the same thing. Basically I am able to access the tab in the plugin config center tab.

I have keyed in the correct login credentials again and it is still empty under my device.

So I tried removing the device details section leaving only the bare essentials to be managed in configuration and have checked the logs. It just cannot detect any devices in my plugin configuration.

@mrbungle64
Copy link

@thegeekybeng

Have you set up the correct account?
Are you using the Ecovacs or the yeedi mobile app and account?

@thegeekybeng
Copy link
Author

@thegeekybeng

Have you set up the correct account? Are you using the Ecovacs or the yeedi mobile app and account?

Currently, we are using the Yeedi Mobile App - and yes i have selected for the Yeedi login.
I have downloaded the Logs - let me just browse through to ensure i don't leak details that are not required - maybe you can see that better?

Deebot LOG

What I do find strange is the retrival of library info is still going to ecovac when I am a 100% certain that i have clicked to enable Dee

SettingsIn Config

Hence would greatly appreciate if you can highlight what I might have done wrongly?

@thegeekybeng
Copy link
Author

Updated to the newer beta and still the same thing. Cannot detect my yeedi floor 3+

@mrbungle64
Copy link

@thegeekybeng

Updated to the newer beta and still the same thing. Cannot detect my yeedi floor 3+

As far as I can see, the only thing that changed was that the brand is now in the log output:
"... device(s) found in your ... account"

What is output in your log?

@thegeekybeng
Copy link
Author

I think I have solved it. The issue was with the app, and it wasn't registered into the new account as the original account's password was lost. And somehow the process of registering the device did t capture it perfectly so it didn't turn up in the cloud but the previous timing set was still in the device thus it was functioning as per normal.

Until I went back and revisit the steps then It dawned on me that the device wasn't registered at all and I redid the registration of the device into the new account that was linked to the plugin and the device appeared shortly after.

It had three controls switch and a hidden switch which is the presence sensor. So I had utilized that function as a late night trigger for anyone who is walking past the area.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants