An unofficial python package to access Cookidoo.
The developers of this module are in no way endorsed by or affiliated with Cookidoo or Vorwerk, or any associated subsidiaries, logos or trademarks.
Disclaimer: This library needs a runner (browser) to execute the calls through web automation. Make sure to have it correctly set up using one of the following options before proceeding.
Once you have tested your runner, install the library and use it with your preferred runner.
pip install cookidoo-api
See below for usage examples. See Exceptions for API-specific exceptions and mitigation strategies for common exceptions.
The API is based on the async implementation of the library playwright in collaboration with a runner for browser emulation.
Make sure to have stored your credentials in the top-level file .env as such, to loaded by dotenv. Alternatively, provide the environment variables by any other dotenv compatible means.
EMAIL=your@mail.com
PASSWORD=password
Run the example script and have a look at the inline comments for more explanation.
In case something goes wrong during a request, several exceptions can be thrown. They will either be
CookidooActionExceptionCookidooAuthBotDetectionExceptionCookidooAuthExceptionCookidooConfigExceptionCookidooNavigationExceptionCookidooSelectorExceptionCookidooUnavailableExceptionCookidooUnexpectedStateException
depending on the context. All inherit from CookidooException.
With the async calls, you might encounter an error that another asyncio event loop is already running on the same thread. This is expected behavior according to the asyncio.run() documentation. You cannot use more than one aiohttp session per thread, reuse the existing one!
Due to a known issue in some versions of aiohttp when using Windows, you might encounter a similar error to this:
Exception ignored in: <function _ProactorBasePipeTransport.__del__ at 0x00000000>
Traceback (most recent call last):
File "C:\...\py38\lib\asyncio\proactor_events.py", line 116, in __del__
self.close()
File "C:\...\py38\lib\asyncio\proactor_events.py", line 108, in close
self._loop.call_soon(self._call_connection_lost, None)
File "C:\...\py38\lib\asyncio\base_events.py", line 719, in call_soon
self._check_closed()
File "C:\...\py38\lib\asyncio\base_events.py", line 508, in _check_closed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closedYou can fix this according to this StackOverflow answer by adding the following line of code before executing the library:
asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())There is an inbuilt bot detection on cookidoo which can block the login process. There is a clear error message, when that happens. The tokens are valid for a fixed duration and therefore the library tries to minimize the amount of logins required to avoid the captcha process. Unfortunately, this is not always possible when developing or debugging a setup, and you might run into it. To continue, either wait a day or switch to a runner with a gui and enable captcha mode to manually solve the captcha during the login or a service such as capsolver.
It is generally advised, to first try the login in fail mode and only activate a recovery mode on a CookidooAuthBotDetectionException raised.
cookidoo = Cookidoo(<your headful browser setup>)
await cookidoo.login(captcha_recovery_mode="user_input")Be aware, using this option with a headless browser will indefinitely block the process in login, as it is waiting for user action.
This requires the capsolver to be installed.
pip install capsolvercookidoo = Cookidoo(<your browser setup>)
await cookidoo.login(captcha_recovery_mode="capsolver")This is not yet implemented.
Alternatively, they also provide a browser extension, which might be a cleaner way.
Setup the dev environment using VSCode, it is highly recommended.
python -m venv .venv
source .venv/bin/activate
pip install -r requirements_dev.txtInstall pre-commit
pre-commit install
# Run the commit hooks manually
pre-commit run --all-filesFollowing VSCode integrations may be helpful: