Fix for reported LiteBeam signal in Disconnected

[CoMPaTech]

Summary by CodeRabbit

• New Features

  • None.

• Bug Fixes

  • Improved compatibility with devices that may not report signal strength while disconnected (e.g., certain LiteBeam firmware), preventing parsing failures and ensuring more robust status handling.

• Documentation

  • Updated changelog for 0.4.4 with clarified notes; removed an outdated bullet and refined wording for prior entries.

• Chores

  • Bumped version to 0.4.4.

[coderabbitai]

Walkthrough

Updated version to 0.4.4, adjusted CHANGELOG entries, and made the Disconnected.signal field optional (int | None = None) and repositioned it after airos_connected in airos/data.py. No exported/public API signatures changed aside from the field’s optionality.

Changes

Cohort / File(s)	Summary of Changes
Versioning & Changelog CHANGELOG.md, pyproject.toml	Added 0.4.4 entry; reworded a 0.4.3 bullet; removed a 0.4.2 bullet; bumped version from 0.4.3 to 0.4.4.
Data Model: Disconnected schema airos/data.py	Made signal optional: from signal: int to signal: int | None = None; moved field to follow airos_connected.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my ears at version four-dot-four,
A signal may be none—yet we explore.
Changelog crumbs, I nibble as I go,
Data fields hop neatly, row by row.
With gentle paws, I stamp “approved”—
Onward, burrow—bugs removed! 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch litebeam_disconnect_signal

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbit in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbit in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbit gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbit read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbit help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbit ignore or @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbit summary or @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbit or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[CoMPaTech]

As reported home-assistant/core#151145 (comment) (own issue pending)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.36%. Comparing base (7e67cb8) to head (5d0f3ad).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #82   +/-   ##
=======================================
  Coverage   91.36%   91.36%           
=======================================
  Files           4        4           
  Lines         730      730           
=======================================
  Hits          667      667           
  Misses         63       63           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

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

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

CHANGELOG.md (1)

17-22: Fix 0.4.2 changelog entry inconsistency
The “Aligned quality targets either improved or tagged” bullet remains in CHANGELOG.md (line 21) despite the AI summary stating it was removed. Delete this line or update the summary to match.

🧹 Nitpick comments (3)

airos/data.py (2)

405-405: Nit: fix brand capitalization in inline comment.
Change “Litebeam” → “LiteBeam” for consistency with the rest of the file.

-    signal: int | None = None  # Litebeam 5AC can have no signal
+    signal: int | None = None  # LiteBeam 5AC can have no signal

---

387-391: Docstring says “Wireless” inside Remote.pre_deserialize.
Minor copy/paste mismatch; should reference Remote.

-        """Pre-deserialize hook for Wireless."""
+        """Pre-deserialize hook for Remote."""

CHANGELOG.md (1)

15-15: Fix grammar and double space in 0.4.3 line.

-- Made antenna_gain and nol_* optional as reported on  Prism and LiteBeam 8.7.8 support
+- Made antenna_gain and nol_* optional as reported on Prism and LiteBeam 8.7.8.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7e67cb8 and 5d0f3ad.

📒 Files selected for processing (3)

• CHANGELOG.md (1 hunks)
• airos/data.py (1 hunks)
• pyproject.toml (1 hunks)

🔇 Additional comments (3)

pyproject.toml (1)

7-7: Version bump matches CHANGELOG; LGTM.

airos/data.py (1)

405-405: No downstream .signal usage detected—making signal optional is safe. Please still add a test covering deserialization when signal is absent.

CHANGELOG.md (1)

5-10: 0.4.4 entry reads clearly; matches code change.