Update tutorial.md - local directory

[dooblem]

more info on where to store the local addons

Proposed change

Type of change

• Document existing features within Home Assistant
• Document new or changing features which there is an existing pull request elsewhere
• Spelling or grammatical corrections, or rewording for improved clarity
• Changes to the backend of this documentation
• Removed stale or deprecated documentation

Additional information

• This PR fixes or closes issue: fixes #
• Link to relevant existing code or pull request:

Summary by CodeRabbit

• Documentation
  • Clarified the tutorial instructions to guide users on creating the add-on directory at the correct location.

[coderabbitai]

📝 Walkthrough

Walkthrough

The update revises the tutorial documentation for add-on development. It changes the directory creation instruction so that users now create the directory inside the addons/local folder instead of using the original hello_world name. No changes were made to exported or public entities.

Changes

File(s)	Change Summary
docs/add-ons/tutorial.md	Updated instruction to create the new add-on directory inside addons/local instead of hello_world.

---

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

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/add-ons/tutorial.md (1)

21-22: Improve clarity on add-on directory placement
The updated instruction now clearly states that users should create the new directory inside the addons/local directory, which aligns with the PR objective of clarifying the location for local add-ons. One suggestion is to cross-reference the earlier explanation (at line 9) that mentions the shared folder "addons" to clarify the relationship between addons and addons/local (for example, explaining that addons/local is the designated subdirectory for custom/local add-ons).

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 74bd140 and 7d9fd34.

📒 Files selected for processing (1)

• docs/add-ons/tutorial.md (1 hunks)

[frenck]

That sounds incorrect? As per the paragraph above, the correct folder for that is /addons.

[dooblem]

yes, I think it's incorrect to create the directory in addons/hello_world

in my fresh install from last week I have the following directories after HA install :

addons/core (contains all standard addons)
addons/data (contains some data)
addons/local (empty in a fresh install)

My guess is that in the new HA versions it has changed and the custom addons have to be placed in the local/ directory.

I followed the tutorial creating the addons/local/hello_world directory and all was good.

I must say I did not even try to create the directory as addons/hello_world

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.