v3.0.0-beta.5: fix calibration on start when level == 100

This should be the last beta before final stable.

v3.0.0-beta.4

Fix the example.

v3.0.0-beta.3: yet even more flexibility 😅

API changed again, no more get state callback. Instead, you feed directly the previous state with a function call.

v3.0.0-beta.2: even more flexibility

The API changed from the previous beta, to allow greater flexibility (more specific functions).

v3.0.0-beta.1: more flexibility

This release brings more flexbility.

✨ Features

• Set the course time after instantation
• Set a different up and down course time (#11)
• Ability to set the same callbacks for multiple shutters (a pointer to the affected Shutters instance is passed to the callbacks)
• The state is now stored as a char array. This makes it easier for some platforms to store the state (some platforms don't manage 64bits integers)

v2.1.1: notify level after calibration done

🐛 Bugfixes

• Call the on level callback only after calibration for levels 0 and 100

v2.1.0: On level reached callback

✨ Features

• Add the ability to specify a callback to be called when a new level is reached

🐛 Bugfixes

• Fix bad private function call

v2.0.1: Fix library halting the shutters after first move

🐛 Bugfixes

• Don't halt the shutters after first move
• If the getState callback returns a value > 100, it will be considered as level not known

v2.0.0: Non-blocking

This release brings non-blocking code, even if the shutters state is not known.

✨ Features

• Non-blocking
• Storage is now abstracted using callbacks
• A little "delay" (non-blocking) is introduced between up, down and halt calls to avoid switching too fast mechanical relays, for example
• Optimize movements: don't call halt if setLevel(100) is called while already going down