`clean 0` will clean until the bot returns and is charging again
- equivalent of 'auto' from the bot / app
- sucks cli will execute the next command after the bot is charging again
Change portal url to use portal-ww instead of portal-continent, this seems to fix the issue with logging in from de.
Change SetIOTMQDevices to check for device company instead of pre-defined list.
This fork of SleekXMPP disables certificate validation to work around #62 and #45
This fix should be seen as a temporary hack until we figure out a long term solution.
Removing a test based on the assumption that iot products may not work as iotmq. This broke because D600 was added to the list of iotmq devices, but we can't assume the other devices from the productiotmap may not be added to the iotmq list in the future and this will just keep breaking. It really doesn't provide much value from a test perspective.
It wasn't because of a space.... The tests were failing depending on the run because the xml string may have the id in a different order from run to run.
Changed test to convert string to xml for testing id exists or matches customid.
- Changed ClientXMPP to login/bind with resource
- Changed clean to always add the action
- Wrap command calls a new getReqID to add an ID to the ctl if needed
- This was required for the ozmo commands, and shouldn't affect other boths
- Updated tests
Update SpotArea and CLI command to more closely reflect the app
Library:
SpotArea namedarea -> area
SpotArea customarea -> map_position
CLI Commands:
spotclean -> area
Ex: sucks area 0,1
- will clean areas 0 and 1 / A and B
area options:
--map-postion|-p
- will clean a specified map coordinate
Ex: sucks area -p "-602,1812,800,723"
- will clean the specified custom map coordinates
bittles