-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
DEEBOT NEO 2.0 (eyfj07) Not working in Ecovacs #125447
Comments
Hey there @mib1185, @edenhaus, @Augar, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) ecovacs documentation |
This looks like it's the same issue as #120557. There simply isn't any data being returned by Ecovacs' API. I've recently picked one up as well so this is a bit of a disappointment. |
I've submitted a ticket to Ecovacs AU asking for API info to support it. Being the second version of the Neo, perhaps the existing Neo config would work with the new model number added? |
I've tried with the existing Neo config today with no luck. I'm in the process of pulling the app apart to see how the Neo's process works. From my brief dive it seems that the Neo 2.0, Neo 2.0 Plus, Y1, Y1 Plus, etc. are all using some different API endpoint. It might be related to some recent troubles with the X2? I'll continue digging over the coming days and report back if I find anything useful. If it's enough to go on, I might put either an issue or a PR together in the deebot-client repo (no promises though!) |
@thomotron If you have enough data, we can of course extend the lib to supports these models :) |
After a number of emails back and forth with Ecovacs AU support, they will not provide any API information, unfortunately. |
@edenhaus I also have the Neo 2.0 and have taken a look with mitmproxy. |
I'm experiencing the same issues as well for the Deebot NEO 2.0 and would love to get it working with homeassistant. |
Sorry for the silence here, I was overseas for a bit but I'm back on deck now. So far I haven't managed to do anything useful with the API after MITMing it. It looks like they sign/sum their requests. My next step was going to be poking into the existing lib to see how it handles it and hopefully use it as a jig to play around with this other endpoint that they seem to be using. |
The problem
Newly purchased DEEBOT NEO 2.0 (eyfj07) in AU, not controllable in HA via the Ecovacs Integrations
What version of Home Assistant Core has the issue?
2024.8.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Ecovacs
Link to integration documentation on our website
https://www.home-assistant.io/integrations/ecovacs
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: