Voice chapter 9 blog upload #37449
Voice chapter 9 blog upload #37449
Conversation
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
📝 WalkthroughWalkthroughA new markdown post has been added that outlines the Speech-to-Phrase tool. The document describes an offline speech processing tool tailored for low-end hardware in Home Assistant environments. It details how the tool uses a limited set of pre-trained phrases to rapidly recognize voice commands for home automation, lists supported and unsupported commands, and explains the potential for community-driven customizations and future enhancements. Changes
Sequence Diagram(s)sequenceDiagram
participant U as User
participant M as Microphone/Input
participant SP as Speech-to-Phrase Module
participant HA as Home Assistant
U->>M: Speak voice command
M->>SP: Transmit audio input
SP->>SP: Process audio offline (match against pre-trained phrases)
alt Command recognized
SP->>HA: Trigger corresponding home automation action
else Command not recognized
SP->>U: Provide no-match feedback
end
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
source/_posts/2025-02-13-voice-chapter-9-speech-to-phrase.markdown (2)
30-30: Add missing commas for better readability.Several sentences would benefit from proper comma placement.
Apply these changes:
- Line 30: "To run this software, you needed..."
- Line 46: "Really, any commands that..."
- Line 95: "Thanks, Allen!"
- Line 107: "Previously, Assist could only..."
- Line 118: "You can provide the opening sentence, and via..."
Also applies to: 46-46, 95-95, 107-107, 118-118
🧰 Tools
🪛 LanguageTool
[typographical] ~30-~30: It seems that a comma is missing.
Context: ...program introduced in 1997. To run this software you needed at least a 133 MHz Pentium p...(IN_ORDER_TO_VB_COMMA)
110-110: Remove trailing punctuation from headings.According to markdown style guidelines, headings should not end with punctuation marks.
Apply these changes:
-## Home Assistant phones home: analog phones are back! +## Home Assistant phones home: analog phones are back -## 🫵 Help us bring choice to voice! +## 🫵 Help us bring choice to voiceAlso applies to: 132-132
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
110-110: Trailing punctuation in heading
Punctuation: '!'(MD026, no-trailing-punctuation)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (4)
source/images/blog/2025-02-voice-chapter-9/art.jpgis excluded by!**/*.jpgsource/images/blog/2025-02-voice-chapter-9/green-pe.pngis excluded by!**/*.pngsource/images/blog/2025-02-voice-chapter-9/shared-history.pngis excluded by!**/*.pngsource/images/blog/2025-02-voice-chapter-9/stp-logo.jpgis excluded by!**/*.jpg
📒 Files selected for processing (1)
source/_posts/2025-02-13-voice-chapter-9-speech-to-phrase.markdown(1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_posts/2025-02-13-voice-chapter-9-speech-to-phrase.markdown
[typographical] ~30-~30: It seems that a comma is missing.
Context: ...program introduced in 1997. To run this software you needed at least a 133 MHz Pentium p...
(IN_ORDER_TO_VB_COMMA)
[formatting] ~46-~46: Insert a comma after “Really,”.
Context: ...oadcasts are not usable out of the box. Really any commands that can accept random wor...
(INTRODUCTORY_PHRASE_MISSING_COMMA)
[formatting] ~95-~95: Insert a comma after ‘Thanks’.
Context: ...t home will be ready to be integrated. Thanks Allen! ## Expanding Voice Capabilities...
(SENT_START_THANKS_COMMA)
[uncategorized] ~107-~107: Possible missing comma found.
Context: ...ure to 19 degrees" Previously Assist could only tell you the temperat...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~118-~118: Possible missing comma found.
Context: ...l. You can provide the opening sentence and via a new "extra system prompt" option,...
(AI_HYDRA_LEO_MISSING_COMMA)
🪛 markdownlint-cli2 (0.17.2)
source/_posts/2025-02-13-voice-chapter-9-speech-to-phrase.markdown
102-102: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4
(MD001, heading-increment)
110-110: Trailing punctuation in heading
Punctuation: '!'
(MD026, no-trailing-punctuation)
132-132: Trailing punctuation in heading
Punctuation: '!'
(MD026, no-trailing-punctuation)
⏰ 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
🔇 Additional comments (2)
source/_posts/2025-02-13-voice-chapter-9-speech-to-phrase.markdown (2)
1-11: LGTM! Frontmatter is well-structured.The frontmatter contains all required fields with appropriate values.
13-28: LGTM! Introduction and TOC are well-organized.The introduction effectively sets context with embedded video and relevant links. The table of contents provides clear navigation.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
source/_posts/2025-02-13-voice-chapter-9-speech-to-phrase.markdown (2)
110-110: Remove trailing punctuation from headings.According to markdown style guidelines, headings should not end with punctuation marks.
Apply this diff:
-## Home Assistant phones home: analog phones are back! +## Home Assistant phones home: analog phones are back -## 🫵 Help us bring choice to voice! +## 🫵 Help us bring choice to voiceAlso applies to: 132-132
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
110-110: Trailing punctuation in heading
Punctuation: '!'(MD026, no-trailing-punctuation)
30-30: Add missing commas for improved readability.Several sentences would benefit from additional commas for better flow and clarity.
Apply this diff:
-To run this software you needed at least +To run this software, you needed at least -Really any commands that can accept +Really, any commands that can accept -Thanks Allen! +Thanks, Allen! -Previously Assist could only tell +Previously, Assist could only tell -Also since the user needs +Also, since the user needs -You can provide the opening sentence and via +You can provide the opening sentence, and viaAlso applies to: 46-46, 95-95, 107-107, 114-114, 118-118
🧰 Tools
🪛 LanguageTool
[typographical] ~30-~30: It seems that a comma is missing.
Context: ...program introduced in 1997. To run this software you needed at least a 133 MHz Pentium p...(IN_ORDER_TO_VB_COMMA)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
source/_posts/2025-02-13-voice-chapter-9-speech-to-phrase.markdown(1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_posts/2025-02-13-voice-chapter-9-speech-to-phrase.markdown
[typographical] ~30-~30: It seems that a comma is missing.
Context: ...program introduced in 1997. To run this software you needed at least a 133 MHz Pentium p...
(IN_ORDER_TO_VB_COMMA)
[formatting] ~46-~46: Insert a comma after “Really,”.
Context: ...oadcasts are not usable out of the box. Really any commands that can accept random wor...
(INTRODUCTORY_PHRASE_MISSING_COMMA)
[formatting] ~95-~95: Insert a comma after ‘Thanks’.
Context: ...t home will be ready to be integrated. Thanks Allen! ## Expanding Voice Capabilities...
(SENT_START_THANKS_COMMA)
[uncategorized] ~107-~107: Possible missing comma found.
Context: ...ure to 19 degrees" Previously Assist could only tell you the temperat...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~114-~114: Possible missing comma found.
Context: ...in the living room, but not the office. Also since the user needs to pick up the hor...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~118-~118: Possible missing comma found.
Context: ...l. You can provide the opening sentence and via a new "extra system prompt" option,...
(AI_HYDRA_LEO_MISSING_COMMA)
🪛 markdownlint-cli2 (0.17.2)
source/_posts/2025-02-13-voice-chapter-9-speech-to-phrase.markdown
102-102: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4
(MD001, heading-increment)
110-110: Trailing punctuation in heading
Punctuation: '!'
(MD026, no-trailing-punctuation)
132-132: Trailing punctuation in heading
Punctuation: '!'
(MD026, no-trailing-punctuation)
⏰ 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
🔇 Additional comments (3)
source/_posts/2025-02-13-voice-chapter-9-speech-to-phrase.markdown (3)
1-11: LGTM! Frontmatter is well-structured.All required metadata fields are present and properly formatted.
102-102: Fix heading level for broadcast command section.The heading level skips from h2 to h4, breaking the document hierarchy.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
102-102: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4(MD001, heading-increment)
44-44:❓ Verification inconclusive
Verify performance metrics.
Please verify the specific performance claims:
- "150 milliseconds per command" on Raspberry Pi 5
- "under a second" on Raspberry Pi 4
🏁 Script executed:
#!/bin/bash # Search for any benchmark or test results in the codebase rg -i "benchmark|performance test" --type mdLength of output: 7108
Action Required: Verify and Document Performance Benchmarks
Please confirm that the performance numbers shown in the snippet accurately reflect recent benchmark results. In particular:
- Verify that a Raspberry Pi 5 processes commands in approximately 150 milliseconds (i.e., seven times faster than the baseline).
- Confirm that transcription on a Home Assistant Green or Raspberry Pi 4 consistently completes in under one second.
If these figures are based on internal benchmarks (for example, those linked from our LLM benchmark suite), please update the post to reference the source data or adjust the metrics according to the latest results.
Proposed change
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.Summary by CodeRabbit
New Features
Documentation