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

Roborock Vacuum Bin full #546

Closed
isabellaalstrom opened this issue Sep 5, 2019 · 9 comments
Closed

Roborock Vacuum Bin full #546

isabellaalstrom opened this issue Sep 5, 2019 · 9 comments

Comments

@isabellaalstrom
Copy link

isabellaalstrom commented Sep 5, 2019

I was wondering about the possibility to implement the "bin full" state, as the app sends notifications about this. Is this information possible to get from the api?

@rezmus
Copy link

rezmus commented Sep 5, 2019

i'm not 100% sure, but i don't think you can fetch such info. i mean there is an event.bin_full, but no way to get events from local miio api.

@isabellaalstrom
Copy link
Author

Alright, that's a bummer, but thank you!

@rezmus
Copy link

rezmus commented Oct 30, 2019

i've checked plugin and you should be able to get bin_full info when status is fetched. error code 644 is related to bin problems. just not sure if it works for older models like v1/s5.

@isabellaalstrom
Copy link
Author

Is there any way I can test this for s5?

@rezmus
Copy link

rezmus commented Oct 30, 2019

make you bin full so you get push notification, then send "method":"get_status" and look for error_code value.

@isabellaalstrom
Copy link
Author

I know this is a long time ago now, but I haven't really had the time. Today my bin got full though and I though of this. I don't really understand how I should do it. I installed so I can use the cli, but I'm not sure that's where I should be doing this?

@rytilahti
Copy link
Owner

When the bin is full, simply execute mirobo -d to see if the state or error_code in the returned payload indicates something about its state.

@isabellaalstrom
Copy link
Author

This is what I got!

DEBUG:miio.miioprotocol:192.168.1.56:54321 >>: {'id': 3, 'method': 'get_status', 'params': []}
DEBUG:miio.miioprotocol:192.168.1.56:54321 (ts: 2020-04-02 12:48:08, id: 3) << {'result': [{'msg_ver': 3, 'msg_seq': 1953, 'state': 8, 'battery': 100, 'clean_time': 1132, 'clean_area': 21057500, 'error_code': 0, 'map_present': 1, 'in_cleaning': 0, 'in_returning': 0, 'in_fresh_state': 1, 'lab_status': 1, 'water_box_status': 0, 'fan_power': 101, 'dnd_enabled': 0, 'map_status': 3, 'lock_status': 0}], 'id': 3}
State: Charging
Battery: 100 %
Fanspeed: 101 %
Cleaning since: 0:18:52
Cleaned area: 21.0575 m²
DEBUG:miio.vacuum_cli:Writing {'seq': 3, 'manual_seq': 0} to /home/isabella/.cache/python-miio/python-mirobo.seq

@rytilahti
Copy link
Owner

Unfortunately there is nothing indicating that the bin is full. Does the vacuum allow starting it, or does it indicate an error at the moment you try to start it? If the latter, you could try executing the command straight after hearing the error, some errors are "reseted" after a while.

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

3 participants