-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Conversation
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
I take that back. After waiting a few hours the vacuum seems to work fine. Could you please consider merging this? |
Merging this wont be enough since private key and capabilities needs to be added also. |
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. |
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.
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... |
@Tasshack any chance you will be adding this model soon? |
Also interested. New L10s Ultra but isn't found in my account |
Also interested. New L10s Ultra but isn't found in my account. |
Thanks for the great work with the integration so far, crossing my fingers I might be able to use it in due time! =) |
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