Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Since we are adding an "Import settings" feature in 2.1, we can also create some nice ready-made settings users can simply import in the app. I would suggest we create a few and place them in a folder like "example settings" here in GitHub with preview images in the README file. Let me k

The documentation is lacking or outdated in a lot of areas ; a lot of spelling errors and bad translations are also present. I open this issue to break the problem in smaller tasks so we can see how we progress (plus ticking checkmarks is quite enjoyable don't you think ? ^^)

Some items are already done and up-to-date, and I have probably forgotten a bunch of things too. Please correct me below

Unit tests with actual fan data, including multiple variable on one line data, would be nice for this. As would unit tests in general, tbh.

Complete an initial version of documentation:

• Usage/Getting Started
• Example data
• Detailed configuration
• PID tuning
• Hardware constraints (fe. no-save on Teensy LC, pin setup, etc.)

Tiles should animate/pressed.

Tiles and buttons and components that use MQTT should display a busy animation until it has an actual state.

Also misc. enhancements and fixes.