Remove all the non-functioning plugins from the initial setup

[aaronchantrill]

Description

We still have plugins, especially in STT and TTS, that have not been tested for a while and might not work. We also have plugins that require a great deal of extra configuration, like Kaldi which currently requires that the user set up a Kaldi server (the intention was that the user would set it up on a separate machine) and connect to it using GStreamer which is a pain to set up.

We also have defaults set up that are automatically installed during the naomi-setup.sh process, and I have a recommended setup using Mozilla Deepspeech and Pocketsphinx KWS for active/passive listening. My goal is to get Naomi to the point where someone can easily test the basic functionality and try adapting some speechhandler plugins as soon as Naomi is finished installing and decide if they want to continue without the fear that they are going to choose some non-default setting that makes the whole thing not work.

Expected Behavior

Any plugin the user selects at startup should just work. Plugins that don't "just work" should either be removed (if broken) or moved to NPE (if they require extensive configuration or are only available on certain system types). I would also remove cloud based stt and tts plugins to NPE, so the user has full warning.

Actual Behavior

I have not tested all the plugins, but suspect that many of them no longer work. I will run through the list of all plugins and at least try to triage them.

Possible Fix

I will test all the different plugins from a fresh Naomi install and then determine what to do with them from there.

[Pratikdate]

Assign me i will work upon it

[aaronchantrill]

Hi Pratik, thank you for joining the team! I think this is a very good issue for you if you are working with HacktoberFest because you should be able to get a number of different pull requests out of it. I also think it will give you a good overview of the project, where we are at, and where we have problems.

I would recommend starting by installing Naomi. Naomi can be installed on any Linux computer, but it is easiest to install on Debian or a derivative like Ubuntu, Mint, Armbian, etc. There are projects underway to support Arch and Suse but they seem to be stalled. Theoretically, it should be possible to install directly on Windows since Naomi uses the pyaudio library which is cross-platform compatible, but I know Naomi currently uses some Linux only commands.

We have recommended installing on a Raspberry Pi or other single board computer or on a virtual machine like for VirtualBox because this is currently mostly a research project and when writing new plugins you may find that you have to try installing dependencies a few different ways, and may find that when it comes to documenting what you did, that it is easier to reinstall the whole operating system.

Once you have installed and tested Naomi, look for the ~/.config/naomi/Naomi.log file. There you should find some lines like:

WARNING:naomi.pluginstore:Plugin at '~/Naomi/plugins/stt/julius-stt' skipped! (Reason: Skipping julius, 'julius' executable not found) WARNING:naomi.pluginstore:Plugin at '~/Naomi/plugins/stt/google-stt' skipped! (Reason: google module not installed)

These are two modules that appear to be simply missing dependencies, although they may have more serious problems. We want to move these plugins to their own repositories, fix them/write installers for them, and add them to the list of plugins at https://github.com/NaomiProject/naomi-plugins/blob/master/plugins.csv

Please let me know what questions you have. I'm happy to work with you to get this accomplished!

[aaronchantrill]

You should probably also download the naomi-docs repository at https://github.com/NaomiProject/naomi-docs. These are the files that are used nightly to build the documentation at https://projectnaomi.com/dev/docs/ so when you find the documentation to be unclear or wrong you can update it.

[aaronchantrill]

Hello @Pratikdate are you still here?

[Pratikdate]

Yes

[aaronchantrill]

Yes

Okay, thanks, just checking. Is there anything you need?

[Pratikdate]

When I run project it gave error auth/api-key-invalid

Of fierbase can to guid where to add fierbase key

[aaronchantrill]

I'm not really sure what this error message is referring to. Can you provide the full error message or a screenshot? I've never heard of fierbase.