Almond & Ada: privacy-focused voice assistant

What about Snips ? does HA & Snips stop colaborating ? Snips was looking more advanced with more languages.
Will be nice to ear from both sides.

Just find out Snips was bought by Sonos a week after the state of the Union. funny timing, ā€¦

Snips community in shock ā€¦

I am a Mycroft advocate myself. Open sourced, privacy focused, multi language, mature community, easy skill development.

Snips Voice Assistant is available already. Why reinvent the wheel?

Snips may not exist for us too much longerā€¦ see a few comments upā€¦

Also snips is not open source.

How does this work when HASS is in its own container and Almond is in another? From what I can tell, the Almond container requires an Origin header of http://127.0.0.1:3000 to authenticate, but if I attempt to force that from the HASS container, I get a 403 CORS response.

EDIT: I can confirm that right now, both containers need to have host networking enabled. The reason: the local Almond server is set up to only allow API calls from the same host; if the Docker container doesnā€™t share the same networking stack as the HASS container, any request from HASS to Almond will get a 403 back. Seems a bit brittle, but Iā€™m assuming it was the speediest way to get up and running.

1 Like

Now all we need is ESPHome modules for microphones (ideally with local ā€œwake wordā€ support) and speakers!

2 Likes

Iā€™m not sure what hardware you would use here, does the ESP32 have an ADC for a Mic?

Exciting developments, very interested to see how this goes. Fully agree with the need for privacy.

I think Mycroft would be a great addition as well.

Almond seems to misunderstood quite often. For example, I have switches called Humidifier and Coffee Machine in HA. I DO see these in Almondā€™s My Skills, with correct names. But when I actually issue a ā€œturn on Humidifierā€ or Coffee Machine command, it always goes:

which is obviously wrong. There are no errors or warnings in Almondā€™s log. Any tips?

1 Like

Love where this is heading.
It would be great if Almond could use light groups to create automations though. Currently it can only use physical lights, which is a pain when I want to say turn all interior lights off when I leave home, which I have in a light group called light.interior.
For now, I will still be primarily needing to skip Almond.
Is there a way to set the automation editor to manual and not have Almond pop up first?

1 Like

This sounds promising to me. I updated my HA from 0.92 to 0.102 because of this.

From my understanding, the Almond server that I have installed locally will not work when there is no internet, right? Because it needs to communicate with LUInet?

im trying to do the same. did you have any success?

I created a folder called ā€œtelegram_bot_conversationā€ in custom_components folder and added the 2 files into it; init.py and manifest.json

But what is the next step? Do I need to add anything into the configuration file?

If you have the telegram bot configured, that will be all, but itā€™s not working for me

I managed to make it works (sort of). You need to add this into the configuration.yaml fileā€¦

telegram_bot_conversation:

It can tell me jokes, etcā€¦ but when I asked it to turn on lights, it responds ā€œSorry, I did not understand that. You might need to enable a new skill before I understand that command.ā€. I got the same response from HA frontend.

2019-12-04_144436

1 Like

@balloob, I have tried out the telegram_bot_conversation custom component. Actually, there is something that concern me greatly. Anyone who knows my bot ID can actually start a conversation with my bot and thus able to control my home. Is there anyway, to prevent that?

There is a new ā€œVoice Assistantā€ :tada: subforum. Iā€™ve created a topic Replacing Alexa or Google Home by Almond and Ada that some here might find interesting!

I would love to completely replace Alexa but I am still in the research phase. If anyone has ideas, please share :slight_smile:

1 Like

Hi, Iā€™m on 100.3, got notification that the component telegram_bot_conversation could not be set up, did you see this?