Surely that is cart before horse! Who would buy nice looking hardware if there is no functional voice assistant.
Development first, hardware second.
I want to know first of all a roadmap about voice assistant experience with HA,
I want to know how will integrate our smart home? For example Google Assistant have Google Nest mini and audio devices with audio and mic. We will use them? Or must to throw all these Google and Amazon devices and make/buy another that we can use the microphones for speaking in HA Assistant?
Can we give at our assistant a name? Can we speak it without “hey” or name at all?
Thanks 
Alexa and Google devices will probably not be possible to change into Rhasspy devices.
They are made on a closed proprietary technology and the vendors would be giving away the incoming resources.
Rhasspy will be an local alternative to the cloud based VRs.
There might be someone that comes up with a replacement kit to the Google and Alexa kits, but it will still cost money, because the current electronic probably will have to be ditched.
Already now you can set up Rhasspy to the wakeword(s) you want. The wakeword is probably what you think of as a name, like “Hey Google” or “Alexa”. Mine is wakeword is actually “Hey Wally” 
and I did not need the “Hey” if I did not want it.
You probably need some kind of wakeword, since without a wakeword Rhasspy will be processing all you are saying as commands, which will take a lot of resources and sometimes it will think it has found some command and do it, but you where just talking in general, so omitting a wakeword would probably not be a good idea.
1 Like
It would appear so. RIP Genie f/k/a “Almond.” You promised so much.
1 Like
in theory, this is already possible - at least with amazon echo it is exactly what I am doing at the moment.
I create scripts in HomeAsistant to turn things on / off - or do a chain of certain actions.
Then, HomeAssistant does provide this Script to Amazon Echo (via Nabu Casa)…
In the echo, I’ll type some sentences with which I want to trigger the script.
With this method, I can use sentences I Want - I don’t need to remember Entity Names or Aliases - and I don’t need to expose all entities to Amazon Echo.
IF homeAssistant will be able to do such kind of Voice Controll out of the box, I am fine with it.
While getting a nice response from Echo / Alexa - I don’t need this.
As long as the Speech-To-Text is working sustainable… I will give it a try.
This would probably be handled through naming. “Turn on {device}” but they are named “{wife}'s bedside lamp” and “{husband}'s bedside lamp”. This would not let you use “My bedside lamp” without the ability to identify individual speakers.
Which might be possible with individual hotwords.
it would be required that you can link USERS with PERSONS within homeassistant.
Persons are basically a group, and it would be possible to assign devices and so on to a person.
But as long as you don’t have a link between the logged in user and a person, it would be hard to cover…
Except - you would need to create a routine similar to that:
if {{user}} == {{person}}
But then, you should probably have the same naming between people / person and user-name.
Or did I maybe miss some already available options?
When you add a person you toggle this and it makes a user for that person as well. Essentially every user is tied to a person entity, although not all person entities have an associated user.
Granted this information is not accessible in templates and automations to my knowledge. But HA has this information internally and integrations could leverage it.
yes. right Did not remember that option, since I already have all users / persons created long time ago and since then just added some “system users” … ^^
I have a problem (bug) when turning on/off the fan in the bathroom by voice. Polish language used “Włącz wentylator w łazience midi”. As a result I got an error. What could be causing it? Other voice commands work fine (no errors). The alias for the entity has been added. Tested with and without alias. The area has an alias with the corresponding grammar of the room.
Logger: homeassistant.components.conversation.default_agent
Source: helpers/intent.py:389
Integration: Rozmowa (documentation, issues)
First occurred: 14:26:02 (1 occurrences)
Last logged: 14:26:02
Intent handling error
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py”, line 146, in async_process
intent_response = await intent.async_handle(
File “/usr/src/homeassistant/homeassistant/helpers/intent.py”, line 86, in async_handle
result = await handler.async_handle(intent)
File “/usr/src/homeassistant/homeassistant/helpers/intent.py”, line 389, in async_handle
raise IntentHandleError(“No entities matched”)
homeassistant.helpers.intent.IntentHandleError: No entities matched
Edit:
Problem solved. The fan was added as a switch, just changed its type to fan and the commands work fine.
Interesting that Mycroft seems to have had a setback, dunno how it relates to Mike’s move to Nabu Casa.
Same here, in theory this seems like an ideal device for that. Not sure if this already has advanced in that direction in the mean time.
Esphome 2023.4 has support for voice assistant. ESPHome 2023.4.0 - 19th April 2023 — ESPHome
2 Likes
Justin Alvey tore down a Google Nest Mini and designed a main PCB replacement that uses an ESP32-S3 that can be programmed with Arduino IDE… and I am guessing ESPHome too. I wonder if this could be a way to get some ok looking hardware to run Assist…
Edit: Replaced article with better one
5 Likes
very cool… here’s more info
his X has a post from August 9th
https://twitter.com/justLV
his github repo
order the PCB… coming soon
1 Like
That’s X now 
Be aware, this Elon guy is known for being crazy and doing stuff with blue check marks… Sorry, couldn’t resist… 
fixed it 
this link doesnt work: https://www.home-assistant.io/2023/10/12/year-of-the-voice-chapter-4-wakewords/
have to be Year of the Voice - Chapter 4: Wake words - Home Assistant