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

add 2228z as an alternative to 2228o #769

Closed
wants to merge 2 commits into from

Conversation

Krastanov
Copy link

@Krastanov Krastanov commented Oct 19, 2024

Resolves #734

An L10s Ultra from 6 months ago worked fine (2228o), but a newly bought one, from the very same Amazon listing, same make and model, turned out to be a 2228z

An L10s Ultra from 6 months ago worked fine (2228o), but a newly bought one, from the very same Amazon listing, same make and model, turned out to be a 2228z
@Krastanov
Copy link
Author

This single change does not seem to be enough. "Add Entry" now works, but the newly added entry just shows this:

image

@Krastanov
Copy link
Author

I take that back. After waiting a few hours the vacuum seems to work fine. Could you please consider merging this?

@Tasshack
Copy link
Owner

Merging this wont be enough since private key and capabilities needs to be added also.

@Tasshack Tasshack closed this Oct 20, 2024
@Krastanov
Copy link
Author

Could you elaborate a bit? Locally this PR works for me:

image

@Krastanov
Copy link
Author

If there is some data you need me to extract from the new vacuum or from the app, let me know, happy to attempt to help with that.

@Tasshack
Copy link
Owner

Could you elaborate a bit? Locally this PR works for me:

Basic functionality will work but current map and some advanced features won't because integration needs to know capabilties for each model before generating specific entities with compatible option values.
Some features for different generation of vacuums uses same parameter ids with different set of values and setting a parameter value that the vacuum does not expect can result unwanted behaviour and also break the app too.

If there is some data you need me to extract from the new vacuum or from the app, let me know, happy to attempt to help with that.

Adding new supported models to the integration is standard life cycle of maintaining the project and I have several custom tools for automating that procedure so you don't have to extract anything but thanks for asking to help.

You just have to wait for the next release...

@steve-fraser
Copy link

@Tasshack any chance you will be adding this model soon?

@SebastianLarsson
Copy link

Also interested. New L10s Ultra but isn't found in my account

@Mc-Rust
Copy link

Mc-Rust commented Nov 27, 2024

Also interested. New L10s Ultra but isn't found in my account.
The Name in Fritzbox is listed as "dreame-vacuum-r2228z".

@Langelus
Copy link

Thanks for the great work with the integration so far, crossing my fingers I might be able to use it in due time! =)
I just replaced my RoboRock with one of these Dreame's and it turns out mine was also this "r2228z" model so unfortunately I also get this error that the device can't be found in my account.

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

Successfully merging this pull request may close these issues.

6 participants