Skip to content

State Raspberry Pi 3 B is insufficient #38518

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Apr 14, 2025
Merged

State Raspberry Pi 3 B is insufficient #38518

merged 3 commits into from
Apr 14, 2025

Conversation

f3ndot
Copy link
Contributor

@f3ndot f3ndot commented Apr 13, 2025 •
edited by coderabbitai bot
Loading

Proposed change

After experiencing this first-hand as well as reading various other complaints and proposed solutions on the HA Discord, HA Forum, and Internet writ-large, I believe the Raspberry Pi 3 is no longer a sufficient hardware platform to run even the simplest setups.

The "Pi 3 Model B is ok" line has been around for around 2yrs now, and HA has evolved a lot in that time. When I read the docs initially I grabbed my Raspberry Pi Model B+ rev1.3 and followed the steps. After setting up my lights and modest IoT integrations, it only took a day to start experiencing "killed out of memory" messages on the HDMI output and the HTTP server becoming unresponsive– often persisting through reboots.

Since this page is for newbies, I feel it's best to not present asterisks and explanations of how you can potentially make a 3 B+ work if you avoid HAOS, just install core, ignore add-ons, etc. like some current users are reporting for their own successful setups on a Pi 3. Simply state that Pi 3 isn't good enough anymore and let the power users decide for themselves if that's true.

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

  • Link to parent pull request in the codebase: N/A
  • Link to parent pull request in the Brands repository: N/A
  • This PR fixes or closes issue: N/A

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

  • Documentation
    • Updated guidance for Home Assistant installation, clarifying that both Raspberry Pi 3 Model A and Model B do not provide sufficient memory for stable operation.
    • Revised the list of compatible Raspberry Pi models, now specifying only Raspberry Pi 4 or 5 with power supply.

@home-assistant home-assistant bot added the current This PR goes into the current branch label Apr 13, 2025
@netlify Netlify
Copy link

netlify bot commented Apr 13, 2025 •
edited
Loading

✅ Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit acf8100
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/67fc35863502b3000858e88f
😎 Deploy Preview https://deploy-preview-38518--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 13, 2025 •
edited
Loading

📝 Walkthrough

Walkthrough

This pull request updates the installation documentation for Home Assistant on Raspberry Pi. The description has been revised to clarify that neither Raspberry Pi 3 Model A nor Model B possesses sufficient RAM to ensure a stable installation, replacing the previous guidance that suggested the Model B was a viable starting option. Additionally, the list of compatible Raspberry Pi models has been modified to exclude the Raspberry Pi 3, indicating that only Raspberry Pi 4 and 5 are suitable for installation.

Changes

File Summary
source/installation/raspberrypi.markdown Revised hardware requirements to state that both Raspberry Pi 3 Model A and Model B lack the necessary RAM for stability.
source/installation/index.html Updated the list of required Raspberry Pi models to specify only Raspberry Pi 4 or 5, removing Raspberry Pi 3 from compatibility.

Sequence Diagram(s)

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.
📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1c85fee and acf8100.

📒 Files selected for processing (1)
  • source/installation/raspberrypi.markdown (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • source/installation/raspberrypi.markdown
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - home-assistant-docs
  • GitHub Check: Header rules - home-assistant-docs
  • GitHub Check: Pages changed - home-assistant-docs
🪧 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.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai 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:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai 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

Documentation and Community

  • 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.

coderabbitai[bot]
coderabbitai bot reviewed Apr 13, 2025
View reviewed changes
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
source/installation/raspberrypi.markdown (1)

17-17: Improve Clarity and Fix Grammar in Hardware Requirements

The updated hardware recommendation clearly indicates that neither the Raspberry Pi 3 Model A nor Model B provide sufficient RAM for a stable Home Assistant installation. However, the phrase currently reads:

(neither the Raspberry Pi 3 Model A or Model B have enough RAM to be stable).

To conform with proper grammar, consider replacing "or" with "nor". For example:

- (neither the Raspberry Pi 3 Model A or Model B have enough RAM to be stable).
+ (neither the Raspberry Pi 3 Model A nor Model B has enough RAM to be stable).

This change will enhance both the clarity and grammatical correctness of the statement.

🧰 Tools
🪛 LanguageTool

[grammar] ~17-~17: Use “nor” with neither.
Context: ...Vq) (neither the Raspberry Pi 3 Model A or Model B have enough RAM to be stable). ...

(NEITHER_NOR)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c3434cc and 4983957.

📒 Files selected for processing (1)
  • source/installation/raspberrypi.markdown (1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/installation/raspberrypi.markdown

[grammar] ~17-~17: Use “nor” with neither.
Context: ...Vq) (neither the Raspberry Pi 3 Model A or Model B have enough RAM to be stable). ...

(NEITHER_NOR)

c0ffeeca7
c0ffeeca7 approved these changes Apr 14, 2025
View reviewed changes
Copy link
Contributor

@c0ffeeca7 c0ffeeca7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @f3ndot 👍

@github-project-automation github-project-automation bot moved this from Todo to Approved in Documentation PRs Apr 14, 2025
@c0ffeeca7 c0ffeeca7 merged commit 74d9ca8 into home-assistant:current Apr 14, 2025
7 checks passed
@github-project-automation github-project-automation bot moved this from Approved to Done in Documentation PRs Apr 14, 2025
@f3ndot f3ndot deleted the patch-1 branch April 14, 2025 13:53
@f3ndot f3ndot mentioned this pull request Apr 14, 2025
Merged
8 tasks
@github-actions github-actions bot locked and limited conversation to collaborators Apr 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

@c0ffeeca7 c0ffeeca7 c0ffeeca7 approved these changes

Assignees
No one assigned
Labels
current This PR goes into the current branch
Projects
No open projects
Documentation PRs
Status: Done
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@f3ndot @c0ffeeca7