fix: allow API users to think about vertical oscillation "angle" in degrees.

[kylev]

A little tickery provides enough abstraction that API users can think in degrees or with byte-value awareness. This makes integrating with common input controls more natural.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Files with missing lines	Coverage Δ
switchbot/const/fan.py	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

This PR aims to make the Standing Fan vertical oscillation API more intuitive by allowing callers to specify 90° (degrees) while still emitting the correct device byte encoding (0x5F / 95) for the command payload.

Changes:

• Added a regression test ensuring set_vertical_oscillation_angle(90) produces the same command as byte value 95.
• Modified VerticalOscillationAngle to introduce a degree-aware “90” entry while still mapping it to the device byte value used on the wire.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
tests/test_fan.py	Adds coverage for passing 90 as an int and asserting correct byte encoding in the emitted command.
switchbot/const/fan.py	Adjusts the vertical oscillation angle enum to support degree-based inputs for 90°.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[kylev]

I'm also happy to rewrite this with a less "mysterious" approach:

Suggested change

	@classmethod
	def _missing_(cls, value: int) -> VerticalOscillationAngle | None:
	if value == 90:
	return cls.ANGLE_90
	return None
	@classmethod
	def from_degrees(cls, value: int) -> VerticalOscillationAngle:
	try:
	return cls[f"ANGLE_{value}"]
	except KeyError:
	raise ValueError(f"{value} degrees has no corresponding {cls.__name__}") from None