Why make the default wake-word when talking to all official Home Assistant branded voice hardware something other than ”Okay Nabu” (which now looks to ship as default on the first preview voice hardware)?
Or rather, why not make the default wake-word “Okay Home Assistant”, “Okay Assist”, “Okey Open Home”, , or something else in reference Home Assistant, Assist (“Assist” as in Home Assistant’s default conversation agent), the Open Home Foundation, or alternativly something completely arbitrary that have no reference to Nabu Casa which is a commercial company? …how about maybe holding a contest to submit ideas for new unique wake words and wake word phrases?
As I understand, the idea is to both standardize and fully open-source the voice hardware platform to also make it easy for other third-party companies to make their own Home Assistant voice hardware, and then it simply makes no sense for other companies to make their standard wake-work for ”Nabu” anything, so then we will surley get a fractured standard.
In direct comparision, it is called “Home Assistant Cloud”, (and not “Nabu Cloud”), even though the service is provided by Nabu Casa.
On the contrary, Assist is Home Assistant’s free and open-source home-grown voice assistant. Assist is the underlying technology that allows Home Assistant to turn commands (“turn on the light”) into Actions (light.turn_on
).
Assist can’t understand spoken words that are needs something to take that audio and turn it into text - all this together is called an Assist pipeline. Which converts spoken commands into intents (Assist’s built-in sentences).
Assist is available to use on most platforms that can interface with Home Assistant. Look for the Assist icon.
Backstory; I read that the upcoming official Home Assistant branded smart speaker will use ”Okay Nabu” as its default wake word using these microWakeWord (micro wake word) model linked here:
I understand that the sole reason for picking ”Okay Nabu” is it the codebase has until now primarly been developed by employees from Home Assistant’s commercial partner Nabu Casa (or at least by dveelopers that are now employees of Nabu Casa even if they didn’t begin development as such) and ”Okay Nabu” is a referrence to the company name that they work for, and I know that Nabu Casa as also the company that will manufacture and distribute this upcoming official Home Assistant branded voice hardware.
But I also understand that the upcoming hardware will be an official “Home Assistant” branded voice hardware and not a “Nabu Casa” branded hardware. And while might be marked and marketed as “Home Assistant XYZ-Product by Nabu Casa”, it will not be marked and marketed as “Nabu Casa XYZ-Product for Home Assistant”.
Now that Home Assistant is owned by a nonprofit organization (NPO) which have goals to become a 501(c)(3) organization then is that really appropriate that the
If the default wake-word you pick now for the first product is likley to stick and be used by default in all official Home Assistant branded voice hardware then why not choose something that represent the Home Assistant project and community instead of the Nabu Casa company.
Chances are great that the firmware will be mainlined and many others who do not work for Nabu Casa will be contributing and help maintain the codebase in the future, however I believe there is a risk that whatever ships with the first product will likley stick as the default forever.
It not only that I personally do not want to use ”Okay Nabu” as wakeword and not that we will not be able to change it outselves to something else, it is also that I as a fan of the Free and open-source software (FOSS) philosophy do not think it is appropriate to name the default wake word after a commercial company, even though I otherwise love everything almost everything else that Nabu Casa as compoany and all their employees does to drive this project.
Again, love most what Nabu Casa does but I do not like to have ”Okay Nabu” as default wakeword and I think using it as default is a mistake.
PS: I previously submitted same as above as a feature request but think that it fits better as a WTH: