-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Upload voice chapter 10 blog #39711
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.
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
Upload voice chapter 10 blog #39711
Conversation
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ready to go
📝 WalkthroughWalkthroughA new blog post titled "Next iteration of our Voice Assistant is here - Voice chapter 10" has been added. The post describes recent advancements in the Open Voice project, including expanded language support, improved hardware integration, updates to speech-to-text and text-to-speech tools, conversational enhancements, and future development directions. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant VoiceAssistant
participant ESPHome
participant SpeechToPhrase
participant Piper
participant LLM
participant MediaLibrary
User->>VoiceAssistant: Issues voice command
VoiceAssistant->>ESPHome: Integrates with firmware (if on device)
VoiceAssistant->>SpeechToPhrase: Converts speech to text/phrase
SpeechToPhrase-->>VoiceAssistant: Returns recognized text/phrase
VoiceAssistant->>Piper: Converts text to speech (if response needed)
Piper-->>VoiceAssistant: Returns synthesized voice
VoiceAssistant->>LLM: Handles conversational context (if required)
LLM-->>VoiceAssistant: Returns conversational response
VoiceAssistant->>MediaLibrary: Executes media search/play intent (if requested)
MediaLibrary-->>VoiceAssistant: Returns media playback result
VoiceAssistant-->>User: Delivers response or executes action
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 (
|
There was a problem hiding this 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 (7)
source/_posts/2025-06-25-voice-chapter-10.markdown (7)
17-22
: Prefer “take a look” over “have a look” for US-English consistency
Minor diction tweak to match the project’s US-English style.-...feel free to have a look and participate in the discussion. +...feel free to take a look and participate in the discussion.
44-47
: Hyphenate the compound adjective and tone-down “amazing”
When “open source” precedes a noun it should be hyphenated. “Amazing” is informal; “impressive” keeps the excitement while sounding more professional.-Combined with our open source firmware files, this will allow anyone to build on the work we've done ... -...and we're already seeing some amazing creations with this open technology. +Combined with our open-source firmware files, this will allow anyone to build on the work we've done ... +...and we're already seeing some impressive creations with this open technology.
60-61
: Add a clarifying comma after “luckily”
The parenthetical phrase reads more smoothly with a comma after the introductory adverb.-...which is now defunct, but luckily their work was open source --- +...which is now defunct, but luckily, their work was open source ---
82-90
: Use “for untangling” instead of “at untangling”
“Great at” is idiomatic but slightly informal; “great for” is the more formal preposition in this context.-...which is great at untangling misunderstood words or complex queries. +...which is great for untangling misunderstood words or complex queries.
98-100
: Consider a leaner alternative to “take into account”
“Consider” conveys the same meaning with fewer words.-Importantly, these scores take into account the availability of voice commands translated by our language leaders. +Importantly, these scores consider the availability of voice commands translated by our language leaders.
128-132
: Insert a comma before the coordinating “and”
This joins two independent clauses; the comma avoids a run-on sentence.-...are still at the early stages of development and it may be some time before you see some of these features. +...are still at the early stages of development, and it may be some time before you see some of these features.
160-163
: Swap adjective order & remove unnecessary comma before “so that”-We are focusing first on making custom conversations possible, so that you can show us what you are building with this new powerful tool. +We are focusing first on making custom conversations possible so that you can show us what you are building with this powerful new tool.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting
⛔ Files ignored due to path filters (4)
source/images/blog/2025-06-voice-chapter-10/art.png
is excluded by!**/*.png
source/images/blog/2025-06-voice-chapter-10/circuits.png
is excluded by!**/*.png
source/images/blog/2025-06-voice-chapter-10/devices.jpg
is excluded by!**/*.jpg
source/images/blog/2025-06-voice-chapter-10/intents.png
is excluded by!**/*.png
📒 Files selected for processing (1)
source/_posts/2025-06-25-voice-chapter-10.markdown
(1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_posts/2025-06-25-voice-chapter-10.markdown
[style] ~19-~19: Consider rephrasing for a more formal tone.
Context: ...eer Open Voice Before we get going, we just want to say that Voice Chapter 10 isn't just a broa...
(WANT_TO_SAY)
[locale-violation] ~19-~19: In American English, “take a look” is more commonly used.
Context: ...en for comments, so please feel free to have a look and participate in the discussion. 👉 ...
(HAVE_A_LOOK)
[uncategorized] ~46-~46: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...-assistant-voice-pe). Combined with our open source firmware files, this will allow anyone ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~46-~46: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...hardware, and we're already seeing some amazing creations with this open technology. #...
(AWESOME)
[uncategorized] ~48-~48: A period might be missing here.
Context: ... technology. ## Now you're speaking my language ### Speech-to-Phrase gets more fluent ...
(AI_EN_LECTOR_MISSING_PUNCTUATION_PERIOD)
[uncategorized] ~54-~54: A comma is probably missing here.
Context: ...o-Phrase is getting an upgrade! Besides making it simpler for community members to con...
(MISSING_COMMA_AFTER_INTRODUCTORY_PHRASE)
[typographical] ~60-~60: Consider adding a comma after ‘luckily’ for more clarity.
Context: ...els) project (which is now defunct, but luckily their work was open source --- *another...
(RB_LY_COMMA)
[style] ~60-~60: Consider using a different adverb to strengthen your wording.
Context: ...le of FOSS saving the day*), and we are very grateful for the chance to use them! Pe...
(VERY_DEEPLY)
[uncategorized] ~84-~84: The preposition ‘for’ seems more likely in this position.
Context: ...ge language model (LLM), which is great at untangling misunderstood words or compl...
(AI_HYDRA_LEO_REPLACE_AT_FOR)
[uncategorized] ~92-~92: “out” (outside) seems less likely than “our” (belonging to us).
Context: ...vices. For these reasons, we have split out language support into three categories ...
(AI_HYDRA_LEO_CP_OUT_OUR)
[style] ~98-~98: ‘take into account’ might be wordy. Consider a shorter alternative.
Context: ...ed hardware). Importantly, these scores take into account the availability of voice commands tran...
(EN_WORDINESS_PREMIUM_TAKE_INTO_ACCOUNT)
[style] ~104-~104: To elevate your writing, try using a synonym here.
Context: ...m language to language, which made gaps hard to spot. We're switching to a new forma...
(HARD_TO)
[style] ~109-~109: ‘On top of that’ might be wordy. Consider a shorter alternative.
Context: ...e need for you to say "Ok Nabu" again. On top of that, you can now initiate a conversation wi...
(EN_WORDINESS_PREMIUM_ON_TOP_OF_THAT)
[formatting] ~110-~110: The comma can be removed here: “an automation or a dashboard”
Context: ...lled start_conversation
directly from an automation, or a dashboard. This provides the full spectrum of con...
(NOUN_OR_NOUN)
[uncategorized] ~128-~128: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...still at the early stages of development and it may be some time before you see some...
(COMMA_COMPOUND_SENTENCE)
[typographical] ~162-~162: The conjunction “so that” does not have a comma in front.
Context: ... on making custom conversations possible, so that you can show us what you are building w...
(SO_THAT_UNNECESSARY_COMMA)
[style] ~162-~162: This is not the usual sequence for adjectives that have no special emphasis.
Context: ...show us what you are building with this new powerful tool. We will then tackle the critical ...
(EN_ADJ_ORDER)
🔇 Additional comments (1)
source/_posts/2025-06-25-voice-chapter-10.markdown (1)
64-70
: Verify the GitHub repository slug for Piper
The link points topiper1-gpl
. The canonical repo is usuallypiper
(orpiper-tts
). Please double-check to avoid a 404.
Proposed change
Type of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.Summary by CodeRabbit