-
Notifications
You must be signed in to change notification settings - Fork 5
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
Amazing work. Could you update the repo with the functions you havent reported? #8
Comments
That would be great! |
also waiting for zone cleaning function <3 |
I think this is a good start:
without reverse engineering the app, you probably have to guess that segmentId=7 for your zone, but the command should be ok, than add a script in scripts.yaml that calls this proscenic_zone rest command and you are good to go |
Thank you so much @Jandorello. Ill give it a try |
Hi there, first - many thanks for your package and the ongoing development! With the zone cleaning function, I am still searching for the segmentId. Does anybody has some experience in which range it should be? I tested Id 1 to 30 so far but all I get is a robot that drives off his charging station, then immediately a message "cleaning completed" and a robot, that drives back to his station. |
Hello, |
I also would love to have the not yet reported features, mainly the status/last repored message tho since you can't tell what the vacuum is doing if you are alway, would be really great! |
Hi there, |
If one could bring the controlling app to a host, like a PC... maybe at the very end a wireshark dump could reveal the relevant payload on data level... what do you think? |
Hi @andker87,
thank you so much for your amazing work!
I'd love to use the M7 from homeassistant to use the multi-zone cleaning function. In the readme you mention that you have already managed to extract this function and just need to upload them here:
"
Already obtained (just need to report them here)
"
It would be amazing if you could add this functionality!
Cheers,
Felix
The text was updated successfully, but these errors were encountered: