Skip to content

Add hardware requirements section (power supply and storage guidance)#828

Open
raspberry-tips wants to merge 1 commit into
SensorsIot:masterfrom
raspberry-tips:add-hardware-requirements
Open

Add hardware requirements section (power supply and storage guidance)#828
raspberry-tips wants to merge 1 commit into
SensorsIot:masterfrom
raspberry-tips:add-hardware-requirements

Conversation

@raspberry-tips
Copy link
Copy Markdown

What this PR does

Adds a hardware requirements section before "getting started" with practical guidance on power supply and storage.

Why

New users frequently run IOTstack on underpowered supplies or SD cards, leading to random crashes and data corruption. This section addresses both issues upfront with free calculator tools to help size the setup correctly.

Changes

  • Power supply: explains why adequate wattage matters for Docker workloads, links to a Pi power supply calculator
  • Storage: explains SD card wear under continuous log writes, links to an SD card lifespan calculator

@Paraphraser
Copy link
Copy Markdown

A few comments.

I think the focus on "Raspberry Pi 4 or 5" risks being slightly misleading. Technically, IOTstack will run on anything that supports Debian or a downstream derivative such as Raspberry Pi OS or Ubuntu. It also doesn't matter whether the OS is running on the metal or as a guest (eg Proxmox-VE).

When IOTstack came into being in 2019 it was sort of during the transition to the Pi 4. It was known to run on the 3B+ and I have personally also run it on a Zero2W. The main limiting factors are RAM and whether you want to swap to SD. I'm not going to pretend a Zero2W would be able to run a full stack but it can definitely run one or two containers OK.

I agree that power is a key issue and that what you have written is true. However, I think the focus on supply risks being misleading. Perhaps I could ask you to read this gist. Basically, my experience is that you could throw a 100W supply at the problem but if the Pi's on-board regulator can't provide the power, there's nothing you can do.

Lastly, while I tend to agree that the current README could probably do a bit more of the heavy lifting for new makers, the general idea is that the Wiki is the preferred delivery vehicle because there's better formatting control. Perhaps I could suggest reviewing docs/Basic_setup/index.md#requirements and incorporating your information there because I do think the advice and links to calculators is very worthwhile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants