v2.2.0: Support for robotActionErrorMessages.contactError
Turns out when the robot cannot be reached, the current API endpoint behaves weirdly.
It returns json without any action_id, status nor message.
After about 30s it suddenly does return all that, with a new
message robotActionErrorMessages.contactError.
This release moves to pyechorobotics==1.1.0, which adds parsing support for this behaviour.
Additionally, an additional call to the current endpoint was added before running smartfetch.
This was found to prevent going unavailable in some scenarios.