Cherry pick from webdjoe/pyvesync

[vlebourl]

Include fix https://github.com/webdjoe/pyvesync/blob/humid-bug-fix/src/pyvesync/vesyncfan.py
addresses #7.

[sourcery-ai]

Sourcery Code Quality Report

Merging this PR leaves code quality unchanged.

Quality metrics	Before	After	Change
Complexity	4.98 ⭐	4.98 ⭐	0.00
Method Length	53.87 ⭐	53.85 ⭐	-0.02 👍
Working memory	6.61 🙂	6.61 🙂	0.00
Quality	73.65% 🙂	73.65% 🙂	0.00%

Other metrics	Before	After	Change
Lines	1223	1223	0

Changed files	Quality Before	Quality After	Quality Change
custom_components/vesync/pyvesync/vesyncfan.py	73.65% 🙂	73.65% 🙂	0.00%

Here are some functions in these files that still need a tune-up:

File	Function	Complexity	Length	Working Memory	Quality	Recommendation
custom_components/vesync/pyvesync/vesyncfan.py	VeSyncAirBypass.get_details	12 🙂	154 😞	10 😞	51.00% 🙂	Try splitting into smaller methods. Extract out complex expressions
custom_components/vesync/pyvesync/vesyncfan.py	VeSyncAir131.change_fan_speed	14 🙂	152 😞	9 🙂	51.54% 🙂	Try splitting into smaller methods
custom_components/vesync/pyvesync/vesyncfan.py	VeSyncHumid200300S.get_details	12 🙂	146 😞	10 😞	51.84% 🙂	Try splitting into smaller methods. Extract out complex expressions
custom_components/vesync/pyvesync/vesyncfan.py	VeSyncAirBypass.change_fan_speed	13 🙂	154 😞	9 🙂	52.18% 🙂	Try splitting into smaller methods
custom_components/vesync/pyvesync/vesyncfan.py	VeSyncAir131.get_details	3 ⭐	131 😞	8 🙂	66.32% 🙂	Try splitting into smaller methods

Legend and Explanation

The emojis denote the absolute quality of the code:

• ⭐ excellent
• 🙂 good
• 😞 poor
• ⛔ very poor

The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request.

---

Please see our documentation here for details on how these metrics are calculated.

We are actively working on this report - lots more documentation and extra metrics to come!

Help us improve this quality report!