Announcement

Collapse
No announcement yet.

Alexa Plug-in - Beta Testing

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by spud View Post
    Have you installed the Microsoft Speech Platform as explained in the user guide ?

    If so which one have you installed x86 or x64?
    Yes and x64 (on Windows 7)

    Comment


    • #17
      Originally posted by DJF3 View Post
      Yes and x64 (on Windows 7)
      please try to install the x86 version even if you are on a 64bits system.
      thanks

      Comment


      • #18
        @Spud,

        I would like to give your Alexa plugin a try with my HS3 setup which is a bit unique.

        Main mothership HS3 is running in Ubuntu 14.04 64 bit. I have a VB of Windows server 32 bit running on the same box.

        I am running HS3 stuff right now on the Wintel server which talks to the mothership running in Ubuntu.

        Downloaded zip.

        Will try first just running it remotely eh?
        - Pete

        Auto mator
        Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
        Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

        X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

        Comment


        • #19
          Here are some instructions to run the plugin remotely:

          First you need to install it on your HS machine (but you don't have to enable it) so that HS doesn't complain about licensing issue when you start your remote instances.

          Then
          • copy HSPI_Alexa.exe, and all the dlls in bin/Alexa to a directory on your remote computer
          • copy the folder Data/Alexa from your HS3 directory to the same remote directory and keep the same directory tree (i.e Data/Alexa)
          • copy HomeSeerAPI.dll, HSCF.dll and Scheduler.dll from your HS3 directory to the same remote directory
          • install the microsoft speech platform and runtime language on your remote computer as explained in the user guide.
          • open a command prompt on your remote computer
          • cd to the directory, then type HSPI_Alexa.exe server=<ip_of_your_hs_machine> instance=<instance_name>

          where <instance_name> can be anything you want but only alpha numeric characters

          Comment


          • #20
            Originally posted by Pete View Post
            @Spud,

            I would like to give your Alexa plugin a try with my HS3 setup which is a bit unique.

            Main mothership HS3 is running in Ubuntu 14.04 64 bit. I have a VB of Windows server 32 bit running on the same box.

            I am running HS3 stuff right now on the Wintel server which talks to the mothership running in Ubuntu.

            Downloaded zip.

            Will try first just running it remotely eh?
            Pete, follow the instructions above, except that to be able to install the plugin on your Ubuntu machine using the updater, you need to edit updater_override.txt and change the 4th parameter on the Alexa line from 31 to 63.

            Comment


            • #21
              - Added plugin to Ubuntu HS3 with no issues per OP stuff.
              - Created an Alexa remote directory and copied it to NAS for installation on an HSTouch 3 client on a Joggler running XPE 32 bit mode.
              - copied over alexa remote directory to hs3 touchscreen client / speaker dot exe
              - enabled Alexa (put a hard OFF switch and turned it on in one test Echo DD-WRT'd AP)
              - validated that Alexa is ON (checking status on AP) A0-02-DC (hex) Amazon Technologies Inc.
              - enabled plugin on linux mothership and get an error (was trying to register it)
              - copied over directory to Windows 10 PiPo box with speaker dot exe. (went direct to W10 instead of XPe).
              - tested Amazon echo direct chit chat and it is on
              - went to command line prompt and typed exe as posted above.
              - went to mothership to authorize plugin.



              Guessing that it will work with XPe / Speaker dot exe / SAPI running on client or Windows 10 HS3 combo similiar to XPe (testing with both).

              VB of Windows server on Ubuntu is just doing speaker dot exe with SAPI and not voice recognition at this time.
              Attached Files
              Last edited by Pete; October 1st, 2015, 08:10 AM.
              - Pete

              Auto mator
              Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
              Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

              X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

              Comment


              • #22
                Pete,
                I'm not sure this will work on XPe because you need to install Microsoft Speech Platform (http://www.microsoft.com/en-us/downl....aspx?id=27225) which require Windows Vista or later.
                It should work fine on Windows 10.

                Also you don't need to enable the Alexa plugin on your Linux mothership, you just need the files there for HS3 to check some license stuff, and for the plugin to appear in the list of installed plugins.

                Comment


                • #23
                  Yeah went directly to the W10 box. Just noticed that there is no microphone plug on the PiPoX7. Will plugin a USB sound card to test in a bit.

                  Stuck here. I cannot configure plugin (register it). See attached pics.

                  Am I missing a file on the remote computer?

                  What are my next steps?

                  Ahhh...see an error at the command line prompt. See attached. Wierd cuz I do have Neospeech SAPI voice fonts installed and they do work.

                  Checking and Language is Microsoft Speech Recognizer 8.0 for Windows.

                  Where do I check SAPI version on Win10?
                  Attached Files
                  Last edited by Pete; October 1st, 2015, 08:22 AM.
                  - Pete

                  Auto mator
                  Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                  Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                  X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                  Comment


                  • #24
                    hmmm, do you still have the Alexa plugin showing up in the list of installed plugins and showing a 30 days trial like in your first screenshot?

                    could you post your logs when you try to start the remote plugin instance?

                    Comment


                    • #25
                      ...do you still have the Alexa plugin showing up in the list of installed plugins and showing a 30 days trial like in your first screenshot?

                      yes

                      Here is the log from HS3...

                      Oct-01 8:26:52 AM Plug-In Finished initializing plug-in Alexa
                      Oct-01 8:26:52 AM Error Initializing plug-in(2): Alexa Instance::Could not load file or assembly 'Microsoft.Speech, Version=11.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.STACK: at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception& exc, System.Object[]& out_args) [0x00000] in :0
                      Oct-01 8:26:52 AM Info Plugin Alexa has connected. IP:127.0.0.1:60496
                      Oct-01 8:26:52 AM Plug-In Interface Alexa is running as a trial, 30 days remaining.
                      Oct-01 8:26:18 AM Alexa ERROR Could not load file or assembly 'Microsoft.Speech, Version=11.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
                      Oct-01 8:26:04 AM Error Getting plugin GenPage: Object reference not set to an instance of an object
                      Attached Files
                      - Pete

                      Auto mator
                      Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                      Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                      X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                      Comment


                      • #26
                        Pete, you need to install Microsoft Speech Platform Runtime version 11 (x86 version) http://www.microsoft.com/en-us/downl....aspx?id=27225

                        as well as one compatible runtime language: http://www.microsoft.com/en-us/downl....aspx?id=27224
                        e.g. MSSpeech_SR_en-US_TELE.msi

                        Comment


                        • #27
                          OK. Also just plugged in an external combo USB audio device with microphone input. Interesting that the PiPoX7 only has a speaker output. Recognized USB sound card right away here and made it default to that USB card.

                          Installing above stuff....installed.

                          Went to speech control panel to test new speech font. I am not hearing it. Wave files are playing back fine on the USB sound device. Neospeech also not playing back.

                          Defaulted speech to new voice font and rebooted PC.

                          What a PITA..rebooting it and showing that W10 is updating....back back in a few minutes.....

                          For whatever reason TTS doesn't output to USB device. Changed audio out back to PiPox7 and microphone to USB device. Speech is OK now.

                          Testing remote plugin...ok looks like the link still doesn't work...so clicked on configuration and that looks to be working now.

                          Authorization code ready, go back to the Config page and click the 'Done' button.

                          Do I have adjust microphone levels?
                          Attached Files
                          Last edited by Pete; October 1st, 2015, 09:21 AM.
                          - Pete

                          Auto mator
                          Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                          Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                          X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                          Comment


                          • #28
                            to clarify:

                            - Microsoft Speech Platform Runtime version 11 that this plugin needs is a different VR engine than the one used by the HS speaker client and the one used in Windows.
                            The difference is that it is the server version of Microsoft VR, it doesn't need training and is designed for lower quality audio.

                            - The Alexa plugin only use this Microsoft VR engine to recognize locally the word "Alexa" (or whatever you changed the attention phrase to). When "Alexa" is recognized the plugin starts streaming audio to the Alexa Voice Service in the cloud, Alexa handles the request and sends back some audio that the plugin play on your speakers. So the Alexa plugin never uses windows TTS to say something.

                            Comment


                            • #29
                              Understood.

                              Testing microphone on an old IBM USB speaker / mic device.

                              I cannot get microphone to work. Going to look for a microphone...

                              OK microphone works. Listening but Alexa not responding...
                              Last edited by Pete; October 1st, 2015, 09:52 AM.
                              - Pete

                              Auto mator
                              Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                              Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                              X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                              Comment


                              • #30
                                Originally posted by Pete View Post
                                Understood.

                                Testing microphone on an old IBM USB speaker / mic device.

                                I cannot get microphone to work. Going to look for a microphone...
                                how do you know the mic is not working?

                                when you click the Test button, Alexa starts listening and wait for you to say something, she stops listening and process your request when the plugin detects silence for about 2 seconds. So if you listen to music or have a lot of background noise, this will probably not work and Alexa will listen indefinitely and never process your request.

                                when Alexa starts and stops listening some notification sounds are played, namely Data/Alexa/sound/start.wav and Data/Alexa/sound/stop.wav
                                do you hear those when you click the test button and then say nothing for 2 seconds?

                                Comment

                                Working...
                                X